A safe work method statement is not a general safety document. It is a specific instrument required by regulation, for specific work, and the requirements are short enough to state in full.
Which makes it striking how many of them get handed back.
When one is required
A SWMS must be prepared before high risk construction work starts. The WHS Regulations list eighteen categories, and the work only needs to fall into one:
- work involving a risk of a person falling more than two metres;
- work on a telecommunications tower;
- work involving demolition of an element of a structure that is load-bearing or otherwise related to physical integrity;
- work involving, or likely to involve, disturbing asbestos;
- work involving structural alterations or repairs requiring temporary support to prevent collapse;
- work in or near a confined space;
- work in or near a shaft or trench deeper than 1.5 metres, or a tunnel;
- work involving the use of explosives;
- work on or near pressurised gas mains or piping;
- work on or near chemical, fuel or refrigerant lines;
- work on or near energised electrical installations or services;
- work in an area that may have a contaminated or flammable atmosphere;
- tilt-up and precast concrete work;
- work on, in or adjacent to a road, railway, shipping lane or other traffic corridor in use;
- work in an area with movement of powered mobile plant;
- work in an area with artificial extremes of temperature;
- work in or near water or other liquid involving a risk of drowning; and
- diving work.
Note the fifteenth. "An area with movement of powered mobile plant" describes almost every active industrial site, which is why the SWMS obligation reaches far more work than people expect.
What must be in it
Four things, and the regulation is specific:
- The high risk construction work being carried out.
- The hazards and risks to health and safety arising from that work.
- The measures to control those risks.
- How the control measures will be implemented, monitored and reviewed.
There is a fifth requirement that is easy to miss and is the one most often failed in substance: the SWMS must be set out and expressed in a way that is readily accessible and understandable to the people who need to use it.
A forty-page document produced by a consultant, filed for the client and never opened before a shift does not meet that requirement, however complete its content.
Who writes it
The PCBU carrying out the work. On a subcontracted job that is the subcontractor performing the high risk construction work — not the principal contracting company, and not a template vendor.
It must be prepared in consultation with the workers who will carry out the work, and their health and safety representatives. This is a legal obligation, not a nicety, and it is a substantive one: consultation is what turns a generic control list into a method the team will actually follow, because they helped decide it.
The principal contracting company has its own obligations — obtaining the SWMS before the work starts, and taking reasonable steps to ensure the work is carried out in accordance with it. That second obligation is the interesting one, because it means collecting the document is not the end of the principal's duty.
Review and revision
A SWMS has no expiry date. It must be reviewed and, if necessary, revised whenever the control measures are revised — which the regulations tie to change rather than to a calendar:
- the work method changes;
- a new hazard or risk is identified;
- the control measures are not adequately controlling the risk;
- a change is made to the workplace that affects the work;
- an incident occurs involving the work.
If a SWMS is revised, all workers involved must be advised and, where relevant, further consultation and training provided.
Most principals also impose a periodic review — annually, or at each new stage. That is a sensible contractual position and it is worth understanding that it comes from the contract rather than from the regulation, because it means the trigger-based obligation still applies in between.
The three reasons they get rejected
Generic content. A SWMS downloaded as a template, with the trade changed and nothing else, listing controls that could apply anywhere. The giveaway is hazards with no site in them: no mention of the actual grade, the actual services, the actual traffic interaction, the actual exclusion zones. A reviewer who has read a hundred of these spots it in about twenty seconds.
No site specifics. Closely related but distinct. The controls may be genuine and still fail because they do not engage with this site's conditions. "Ensure adequate lighting" is a control. "Task lighting to be positioned on the eastern side to avoid glare from the haul road" is a SWMS.
No evidence of consultation. No names, no date, no record that the crew doing the work saw it before the job. This is a legal failure, not a formatting one, and it is the least defensible of the three because it costs nothing to fix.
A fourth, less often stated: controls that assume a competence nobody verified. A SWMS that says a task will be performed by a competent operator is only true if a competent operator turns up. If the SWMS names a control that depends on a licence or a verification, that credential is part of the control — and the document is a claim about a person that somebody should be able to check.
SWMS on a mine site
Worth being precise, because it is a common question and the answer is genuinely nuanced.
The SWMS obligation sits in the WHS Regulations, under high risk construction work. Queensland mines and quarries are governed by the Coal Mining Safety and Health Act 1999 and the Mining and Quarrying Safety and Health Act 1999, which are outside the harmonised WHS framework and have their own principal hazard management and safety and health management system requirements.
In practice, Queensland mine operators routinely require SWMS or an equivalent document as a contractual requirement, and construction work carried out on a mine lease may fall under the WHS Regulations depending on the circumstances and who is carrying it out.
The practical answer is to ask the operator what they require and under what authority, and to write it properly either way. A document that satisfies a good SWMS standard will satisfy an equivalent site requirement; the reverse is not reliably true.

