Guide

What a SWMS actually needs

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.

Eight things a SWMS has to do

01

The high risk work it covers

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.

02

The hazards from that work

The ones that actually arise on this site, on this job. Not a copied list that includes hazards you'll never encounter.

03

The control measures

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.

04

How controls get implemented

Who puts them in place, when, and what they check before work starts. The step most SWMS skip entirely.

05

How they're monitored and reviewed

Who watches that it's still being done, and what triggers a rewrite. Conditions change, and the SWMS has to change with them.

06

Evidence of consultation

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.

07

Available on site, in use

Accessible while the work is happening, and being followed. A SWMS in the ute glovebox is the same as no SWMS.

08

Proof the workers understood it

Not a signature on a sheet. Evidence the person doing the job knew the hazards and the controls before they started.

The short answer

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.

Most SWMS fail on site, not on paper

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.

The comprehension gap

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.

What we built to fix it

Fair Dinkum Safety Checks is our platform for exactly this problem. You upload the SWMS — any PDF, JSA or work instruction — and it parses the hazards and generates comprehension questions from the document itself.

Workers answer those questions in their preferred language, with narration, on their phone. They complete a pre-start wellness and fatigue check at the same time. The supervisor sees who passed, who didn't, and who isn't cleared for the shift — before the work starts, not after.

It also handles SOP audits with non-conformance and corrective action tracking, and critical risk controls that lock work out until every step is confirmed by a supervisor. Live dashboards show compliance rates and sign-off status, and it produces the PDF trail for regulators and insurers. It's ISO 45001 aligned and built for all Australian jurisdictions.

There's also Roger "Dinkum" Risky in there — an AI safety and risk manager your crew can ask about SWMS, SOPs, critical risk controls or WHS legislation, any time, without waiting for someone to get back to them.

Where this sits in your system

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. If you've already got a system and the gap is on-site verification, that's the piece Fair Dinkum Safety Checks drops into.

Our product

Fair Dinkum Safety Checks

SWMS verification, SOP audits, critical risk controls and multilingual worker sign-offs in one platform, built for the way Australian supervisors actually work. Upload the SWMS, workers verify comprehension in their own language, supervisors approve the shift, and the audit trail builds itself. Free trial, no credit card.

Common questions

What must a SWMS contain?
The work, the hazards, the controls, and how they get implemented, monitored and reviewed. Site specific, written with the crew, and on site while the work is happening.
When is one required?
Before high risk construction work starts. Work at height, powered mobile plant, confined spaces, demolition, asbestos, trenching, work near roads — prepared before, not written up after.
Is a signature enough?
No. The duty is that workers are consulted, instructed and working in accordance with it. Attendance is easy to prove. Comprehension is what holds up when something goes wrong.
What makes one non-compliant?
Generic content and no evidence. Copied controls that don't match the site, no consultation, no review after conditions changed, and nothing showing the crew understood it.
What goes in a safety management systemOff the shelf vs built around you

Want your SWMS process checked?

admin@f4ps.com.au