A signature proves someone held a pen. It doesn't prove they understood the job.
What a Safe Work Method Statement has to contain, why almost all of them fail on site rather than on paper, and how we close the gap between signing a SWMS and understanding one.
Named specifically. 'Working at heights' is not a scope. 'Installing anchor points on a metal deck roof, 6m fall zone, no edge protection installed' is.
The ones that actually arise on this site, on this job. Not a copied list that includes hazards you'll never encounter.
What you're doing about each hazard, in hierarchy order. Elimination first, PPE last. If every control is PPE, it isn't a control set.
Who puts them in place, when, and what they check before work starts. The step most SWMS skip entirely.
Who watches that it's still being done, and what triggers a rewrite. Conditions change, and the SWMS has to change with them.
Developed with the crew doing the work, not written in an office and handed down. This is a legal duty and it's the first thing that fails.
Accessible while the work is happening, and being followed. A SWMS in the ute glovebox is the same as no SWMS.
Not a signature on a sheet. Evidence the person doing the job knew the hazards and the controls before they started.
A SWMS is a Safe Work Method Statement. It's required before high risk construction work starts, and it has to do four things: say what the work is, say what could hurt someone doing it, say what you're doing about that, and say how you'll make sure it happens.
That's the whole legal test. Everything else in a SWMS template is packaging.
We've reviewed a lot of them. The document is almost never the problem — someone bought a template pack, filled in the fields, and it reads fine.
The problem is what happens next. The crew signs a sheet at induction and never reads it. Conditions change and nobody updates it. Half the crew has English as a second language and nobody checked what they actually took in. The supervisor can't produce it when asked.
Then something happens, and the investigation isn't asking whether you had a SWMS. It's asking whether the work was being done in accordance with it, and whether you can prove the workers understood it. A signature proves someone held a pen.
This is the gap nobody talks about. On an average Australian site you'll have workers whose first language isn't English, workers who won't ask a question in front of the crew, and workers who've signed so many sheets they don't read any of them.
A sign on sheet records attendance. It doesn't record understanding. If you want the SWMS to actually protect anyone — and to hold up afterwards — you need something that shows the worker knew the hazards and the controls before they picked up a tool.
Fair Dinkum WorkVault treats the SWMS as part of the system, not a document sitting off to the side. Sherlock runs the hazard discovery for the job and scores the risk, so the controls in the SWMS come out of your live risk register rather than a template.
Flo turns the method into an interactive process flow — the steps in order, who owns each one, the control at the point it applies and the record that drops out the end. Gary maps the training and competency the job requires, so you can see at a glance whether the crew on site is actually ticketed for it.
Harry then runs the verification. Inspections and audits check that the work is being done the way the SWMS says, and anything that isn't gets raised as a non-conformance with a corrective action assigned to a person and a due date, tracked to closure with reminders before it's due and every three days once it's overdue.
And when something does go wrong, Dave takes the intake in plain English — chat or voice — and drafts the record, then Sherlock runs the investigation to root cause. The SWMS, the controls, the training and the incident all sit in the one system, so the answer to 'show me how this works' is one place, not four folders.
A SWMS isn't a standalone document. It's the sharp end of your risk assessment, your training records and your consultation process — which is why a SWMS built off a template that has nothing to do with the rest of your system always feels bolted on.
If you're building the whole thing, start with the elements and work down to the SWMS. Build it in the one vault and the SWMS stops being a document you maintain and starts being an output of the system.
Hazard discovery, risk register, process flows, training matrix, inspections and corrective actions in one platform, built for the way Australian supervisors actually work. Talk it through in plain English, the agent crew drafts the record, and the audit trail builds itself. Underpinned by ISO 9001 and ISO 45001.
Bring your existing SWMS into the vault and let the crew tell you where the gaps are — controls, training, verification and records.
