Documenting Workplace Safety With Software

Every small business in Australia carries a quiet folder of obligations: procedures for the risky jobs, a register of hazards, a log of the incidents that nearly happened, records of who was trained on what. Work health and safety law asks for these things in plain language, and it does not prescribe the container. A lever arch file satisfies the law as well as any database, until the day it does not, because a folder cannot remind anyone of a review date, cannot show the auditor which version of a procedure a worker was trained on, and cannot be searched. This guide is about the software that does those things, what it should contain, and how a small outfit should judge it.

What a safety system actually holds

Strip away the terminology and a workplace safety system holds four kinds of records. Standard operating procedures, the written steps for the jobs that can hurt someone, operating the press, working at height, handling the chemicals, each with a version and a review date. A hazard register, the running list of identified risks, the assessment of each, and the controls decided upon. An incident log, the record of what went wrong or nearly went wrong, with the follow up attached. And training records, who was trained on which version of which procedure, and when. Everything else in the category, dashboards, notifications, audits, exists to keep those four kinds honest. A tool that cannot hold all four, and show their connections, is a filing cabinet with better fonts.

The connections are the actual product

The reason software earns its place in this work is not storage but linkage. When a procedure changes, the tool should know which workers were trained on the old version and flag them for a refresher. When an incident is logged, it should be possible to attach the procedure involved and the register entry for the hazard, so the review after the incident sees the whole picture. When an inspector asks to see the training record for one person against one procedure, the answer should take seconds, not an afternoon of leafing. This linking is precisely what the best known product of this domain's history was built around: Risky Business SOS, published by MacSOS of Sydney, kept versioned procedures and tied quizzes and audits to them, so a small business could show not just what the procedure said but who had demonstrated knowing it. The story of the domain places it in the wider catalogue; the design idea behind it has aged well.

What the software cannot do for you

A register does not identify hazards; people do. No tool substitutes for walking the workplace, asking the workers what nearly went wrong this month, and writing it down. Software that promises compliance as an outcome rather than as bookkeeping is selling the map instead of the walk. The honest division of labour is this: the humans notice, decide and act; the software remembers, reminds and proves. Any purchase decision that gets this backwards, a tool bought to make safety happen rather than to make safety visible, tends to produce a beautifully maintained empty system, which is worse than a messy full one, because it looks convincing. The national reference material published by Safe Work Australia, and the regulator in each state, describe the duties themselves; those descriptions, not any vendor's marketing, are the measure of what records a given business actually needs.

How a small business should judge a candidate

Five tests sort the field quickly. First, the walk through: can a supervisor log an incident on a phone at the scene, or does the tool assume a desk and a spare twenty minutes, because the best moment to record a near miss is the two minutes after it. Second, the version question: are procedures versioned with review dates, and does training attach to a version, not just to a title. Third, the exit: can everything be exported in a readable format, since the records belong to the business and must outlive any subscription. Fourth, the access model: can workers read the procedures relevant to them without wading through the whole register, and can the responsible person see at a glance what is overdue. Fifth, the arithmetic: the price per person per month multiplied by the years of intended use, compared honestly against the folder and a spreadsheet it would replace, which for some very small outfits remains the correct answer.

Where the category came from

Safety software for small business is older than the cloud and grew from exactly the problem described above. In the 1990s and 2000s, indie developers, often one person companies like the Sydney publisher this domain once belonged to, built register tools because their neighbours ran workshops and laboratories that had inspections to pass and no IT department. The ingredients have not changed since: the procedure library, the hazard register, the incident log, the training matrix, and the discipline to keep them current. What changed is the plumbing, web access instead of a single machine, phones at the scene instead of a form on a clipboard transcribed on Monday, reminders that arrive by email instead of a sticker on a monitor. The genre's home ground remains small and mid sized organisations, in workshops, laboratories, farms and site offices, where the person responsible for safety has three other jobs.

Keeping it alive once it is installed

The failure mode of every safety system, paper or software, is silence: procedures that pass their review dates, incidents logged without follow up, training that lapses quietly. The working habit is a short monthly ritual, fifteen minutes, walking the overdue list, closing what is finished, and reassigning what stalled. The tools that help most are the ones that make this ritual pleasant, one clear screen showing what needs a human. That maintenance instinct rhymes with the wider one this magazine preaches about the machines themselves: the calm periodic checks in the slow Mac checklist and the rehearsal habit in the backup guide are the same discipline applied to hardware. Systems that are tended run; systems that are installed merely exist.

A closing note on scope

This guide describes the shape of the category and how to judge it; it is not legal advice, and the duties of a specific business depend on its state, industry and size, which the regulators' own guidance states properly. The historical details here come from the published record of the software of the era, kept in the public web archives introduced in the shareware history. For the software side of choosing any business tool, the evaluation habits in Software and Tools apply as much to a safety register as to a database client: the daily features earn their keep, and the exit is part of the price.