Digital SWMS in Australia: What the Regulations Actually Require

It is 6:20am at a site gate in western Sydney and a scaffolding crew is not working. Their SWMS is on the leading hand’s phone, which is the version his office emailed him in March. The site supervisor has a different version in a folder on the shared drive. Neither of them can say which one the crew actually consulted before they signed it.

The work is high risk construction work. Until somebody resolves this, nobody goes up.

Is a digital SWMS legally valid in Australia?

Yes. The WHS Regulations require a safe work method statement to be prepared as a document, and they have never specified paper. State regulators explicitly confirm that a SWMS can be kept electronically, so the people doing the work have ready access to it.[1]

State regulators put it plainly. WorkSafe ACT states that “a SWMS can also be kept electronically”, and regulator guidance adds a condition most people miss: consideration must be given to the format’s capacity for revision, and to how worker consultation in the preparation process can be demonstrated.[1]

That second clause is the whole game. A PDF emailed to a leading hand is technically an electronic SWMS. It is also unrevisable, unversioned, and carries no evidence that anyone was consulted. It satisfies the format and fails the substance.

18

Categories of high risk construction work that require a SWMS under the WHS Regulations

Safe Work Australia

When is a SWMS required?

A SWMS is required for any of the 18 categories of high risk construction work defined in the WHS Regulations. Safe Work Australia sets out the list, which covers work at height, confined spaces, live electrical work, demolition, asbestos, trenching, work near traffic, powered mobile plant and the rest.[2]

If you are not sure whether a task falls inside one of the 18, the answer on most commercial sites is that several do, on the same day, run by different subcontractors. That is the operational reality the paperwork has to keep up with. For the definitional detail on what a SWMS is and what goes in one, see our guide to safe work method statements.

Who has to prepare the SWMS, and who gets a copy?

The duty sits with the person conducting the business or undertaking that is carrying out the high risk construction work. In practice that is the subcontractor doing the task, not the head contractor.[2]

The PCBU must prepare the SWMS in consultation with the relevant workers, comply with it, review it, and provide a copy to the principal contractor before the work starts.[2]

That last obligation is where the head contractor’s exposure lives. You do not write forty SWMS. You collect forty SWMS, confirm each one is current, confirm the crew on site today is working to the version you hold, and be able to produce all of it on request.

“A SWMS can also be kept electronically.”

WorkSafe ACT, Safe Work Method Statements[1]

How long must a SWMS be kept?

Until the high risk construction work it covers is completed. If a notifiable incident occurs in relation to that work, the SWMS must be kept for at least two years from the date of the incident.[3]

If the SWMS has been revised, every version should be retained, not just the current one. This matters more than it sounds. After an incident, the question is not what the SWMS says now. It is what it said on the morning of the incident, and whether the crew had been consulted on that version.

Where digital SWMS rollouts actually fail

Not on legality. On the four obligations in that table that have nothing to do with format.

Version control. A SWMS emailed as a PDF forks the moment it lands. The subcontractor revises theirs, the site office keeps the original, and nobody can prove which one was in force on a given day. Digital only helps if there is one record, not one file per inbox.

Demonstrable consultation. The regulations require consultation with the workers doing the task, and the format must be able to show it happened. A signature block on a printed page that was signed in the crib room three weeks ago is weak evidence. A time-stamped acknowledgement against a named version is strong evidence.

Accessibility at the point of work. Readily accessible means the scaffolder can open it at the gate, not that the site admin can find it if given ten minutes. If the crew cannot retrieve the current version on their own phone, the obligation is not met in any practical sense.

Retention across revisions. Two years after a notifiable incident is a long time for a folder structure to survive a project close-out, a staff change and a shared-drive migration.

2 years

Minimum period a SWMS must be kept after a notifiable incident, including every revised version

WHS Regulations

What good looks like

The head contractors who have this under control did not just replace paper with PDFs. They changed where the SWMS lives.

• Every subcontractor uploads their own SWMS against their own work package, so the obligation stays with the PCBU that owns it

• The current version is the only version a worker can open, and it is on their phone at the gate

• Acknowledgement is captured against a specific version with a name and a timestamp, so consultation is evidenced rather than assumed

• A revision notifies everyone who previously acknowledged the superseded version and asks them to review the change

• Expired or unacknowledged SWMS surface before the crew arrives, not after an inspector does

• Every version is retained automatically, so the two-year obligation survives project close-out without anyone maintaining a folder

None of that requires a heroic administrator. It requires the SWMS to sit in the same system as the site sign-in and the worker record, so the person, the version and the acknowledgement are one linked record instead of three separate ones.

The Australian context

SWMS is not a paperwork convention. It is a specific statutory instrument under harmonised WHS law, and the duty falls on real people. Every state and territory regulator publishes its own guidance, and while the model regulations are harmonised, WorkSafe Victoria and the other jurisdictions each have their own enforcement posture and their own inspectors.[4]

Safe Work Australia now publishes an interactive SWMS tool with step-by-step guidance, examples and templates, which is a reasonable signal about how often SWMS are being prepared badly.[5]

For a head contractor running four active sites with thirty subcontractors each, the compliance surface is a hundred and twenty live SWMS, each owned by someone else, each revisable without your knowledge. That is not a document management problem. It is a control problem, and it sits inside the broader HSEQ obligations a principal contractor carries.

Where Plexa fits

Plexa holds the SWMS against the subcontractor and the work package, not in a folder. When a subcontractor uploads or revises a SWMS, it is the version the site sees, and the previous version is retained rather than overwritten.

Workers acknowledge on their phone at induction or at the gate, and the acknowledgement records who, when, and against which version. Because the same platform runs site sign-in and worker records, the system knows whether the person walking through the gate this morning has acknowledged the SWMS that is currently in force for their task.

When a SWMS is revised mid-project, everyone who acknowledged the old version is asked to review the change. The audit trail is a byproduct of that workflow rather than a report someone assembles later.

At that gate in western Sydney, the scaffolder opens the current SWMS on his phone because there is only one. It shows he acknowledged revision 3 at 6:04am. The supervisor’s tablet shows the same record. Nobody is searching a shared drive, and the crew is on the scaffold by 6:25.

Frequently asked questions

Is a digital or electronic SWMS legally valid in Australia? Yes. The WHS Regulations require a SWMS in writing but do not require paper. State regulators confirm a SWMS can be kept electronically, provided the workers doing the task have ready access to it.[1]

Does a SWMS need a wet signature? No. The regulations require consultation with the workers carrying out the work and require that the format can demonstrate that consultation occurred. A time-stamped digital acknowledgement against a named version satisfies this and is stronger evidence than an undated signature on paper.[1]

How many types of work require a SWMS? Eighteen. The WHS Regulations define 18 categories of high risk construction work, covering work at height, confined spaces, live electrical work, demolition, asbestos, trenching, work near traffic and powered mobile plant, among others.[2]

Who is responsible for preparing the SWMS, the head contractor or the subcontractor? The PCBU carrying out the high risk construction work, which is usually the subcontractor. They must prepare it in consultation with their workers and provide a copy to the principal contractor before the work starts.[2]

How long do you have to keep a SWMS? Until the high risk construction work is completed. If a notifiable incident occurs in relation to that work, it must be kept for at least two years from the date of the incident, and every revised version should be retained.[3]

Related reading

For what a SWMS actually contains and how to write one, start with what is a SWMS. The gate-level controls that make SWMS acknowledgement enforceable are covered in seven ways construction teams sign in to site. And for the wider compliance picture a principal contractor carries, read what HSEQ actually means on a construction site.

If you want to see how Plexa keeps SWMS current across every subcontractor on every site, book a 30-minute demo with the Plexa team.