Key takeaways
- A SWMS must describe the specific high-risk work being done on that site, not restate a generic hazard list, because the document is the evidence that the sequence and controls were thought through before work started.
- Each step in the sequence needs its own controls, and each control needs an owner and a trigger, so a reader can tell what happens, who does it, and when.
- Review and revision are separate acts: the document must show when it was reviewed, what changed, and why, not simply carry a new date on an unchanged page.
- Sign-off is only meaningful if the people signing have read the version that applies to the work they are about to do, which means the current version must be identifiable on site.
- Where a control depends on a figure set by a manufacturer, a standard or a regulator, the SWMS should point to that source rather than quote a number the builder cannot verify.
An inspector who arrives on your site and asks for the SWMS is not testing your trade knowledge. They are testing whether the document in your hand could have been written by someone who had actually thought about this job, on this site, with these subbies, at this stage of the programme. A generic document fails that test regardless of how neat the folder is.
The failures that cost builders are almost always documentation failures. The work itself might be perfectly safe on the day. But the SWMS describes a different job, the review history is a row of dates with no explanation, and the signatures are from people who were never shown the version now being worked to. That is what turns a routine inspection into a notice.
This article is about the document: the level of detail, the review and sign-off process, and the wording gaps that inspectors pull builders up on. It assumes you already know the high-risk work categories and how to control the hazards in them.
The SWMS is evidence, not a plan
It helps to be clear about what the document is for. A safe work method statement is a written record of how a specific piece of high-risk construction work will be carried out, what could go wrong, and what is being done about it. Its value is not in the writing. Its value is in what it proves: that before work started, someone identified the sequence, matched controls to each step, and assigned responsibility.
An inspector reads it with that question in mind. Does this document demonstrate that the crew knew what they were doing and in what order? Or does it read like a template with the project name typed into the header?
The practical consequence is that length is not the measure. A short document that names the actual task, the actual access method, the actual plant and the actual people is stronger than a long one that lists every hazard in the trade. Padding makes it harder to find the part that matters, and it invites the reader to skim.
Match the document to the actual sequence of work
The first thing an inspector checks is whether the SWMS describes the work as it will be done, not as it appears in a template. That means the steps are in the order they occur on site. If the job involves setting up plant, then accessing the work face, then doing the task, then dismantling, the document should follow that order. A hazard list that runs alphabetically or by category does not show sequencing, and sequencing is the part that demonstrates planning.
In practice this means writing the steps in plain language a subbie would recognise: what happens first, what happens next, what has to be in place before the next step starts. Each step then carries its own controls. A control that appears once at the top of the document and is assumed to apply throughout is a common gap, because it does not tell the reader when the control is actually needed.
Where the work is split between trades, the SWMS should say where the handover happens. Who is responsible for the edge protection before the next trade arrives? Who checks it? A document that leaves the boundary between trades undefined is the document an inspector will keep reading, because that is where incidents cluster.
Every control needs an owner and a trigger
A control with no owner is a suggestion. The wording gap inspectors pull builders up on most often is a list of controls with no indication of who applies them or when. ‘Barricades to be erected’ does not tell anyone whether the barricades go up before the excavation or after the first inspection. ‘Spotter to be used’ does not say who the spotter is or what they are watching for.
The fix is mechanical. For each control, write three things: what it is, who applies it, and what triggers it. The trigger might be a stage of work, a change in weather, the arrival of a delivery, or the completion of the previous step. Once the trigger is written down, the control becomes checkable. Someone can walk the site and see whether it has been done.
This is also where the document connects to supervision. If the SWMS says the leading hand checks the control before the next step, the leading hand needs to know that, and the site diary needs to show it happened. A control that only exists on paper is the first thing an inspector will test against what is actually in front of them.
The life of a SWMS on a job
- 1Scope the high-risk workIdentify which tasks on this site fall into high-risk construction work before anything is written.
- 2Draft the sequenceBreak the work into the order it will actually be done, not the order it appears in a template.
- 3Attach controls and ownersFor each step, name the control, who applies it, and what triggers it.
- 4Consult and signWalk the draft past the subbies and the people doing the work, then have them sign the version they have read.
- 5Review when things changeReview on a change of method, crew, plant, site condition or a near miss, and record what changed.
Review is not the same as re-dating
Review is a distinct act from revision, and inspectors treat them differently. A document that has been re-dated without change tells the reader nothing. A document that records what was reviewed, what was found, and what was changed tells the reader that someone is actually managing the work.
Review should be triggered by something: a change of method, a change of crew or subcontractor, different plant, a change in site conditions, a near miss, or a direction from the principal contractor. When any of those happen, the document is opened, the relevant section is examined, and the outcome is recorded. If the outcome is that nothing needs to change, that is still a review entry, and it is worth writing down.
The commercial reality is that review history is what protects you after an incident. If the work method changed on site and the SWMS was not updated, the gap is visible, and it is visible in a document you controlled. Keeping the review log honest is cheaper than explaining a missing entry later.
Sign-off has to be tied to a version
Signatures are only meaningful if the people signing have read the version that applies to the work they are about to do. That sounds obvious, but it fails in a predictable way: the SWMS is signed at the start of the job, the method changes, a new version is issued, and nobody re-signs. The signatures on file belong to a document that no longer describes the work.
The practical fix is to make the current version identifiable at a glance. A version number or issue date on the cover, referenced in the site diary and in the pre-start, means anyone can tell whether the page in the folder matches the work being done. When the version changes, the people doing the work sign again. That includes subbies who arrive mid-job, and it includes anyone whose role in the sequence has changed.
Consultation matters here too. A signature collected without a conversation is worth very little. The people doing the work often know a step that the office missed, and the SWMS is the place to capture that before it becomes a problem in the field.
Before you file it, check these
- Every high-risk task on this site appears by name, not as a category.
- Each step lists controls, and each control has an owner and a trigger.
- The current version number or date is visible on the cover and referenced in the site diary.
- Review entries state what changed and why, not just a new date.
- Signatures are from people who were on site for that version of the work.
- Any control that depends on a figure points to the source document rather than quoting a number.
- Emergency and rescue arrangements are described for the specific task, not copied from a generic page.
Where a figure matters, point to the source
Some controls depend on a number: a clearance, a fall, a load limit, a temperature threshold. You may not have that number in front of you, and you should not guess it into a document. The stronger wording is to reference where the figure comes from and who is responsible for confirming it.
For example, where a control depends on a manufacturer’s specification, the SWMS should say that the installation will follow the manufacturer’s published requirements, and name who holds that documentation on site. Where a control depends on a standard or a regulatory requirement, the SWMS should say the work will comply with the current requirement and identify the document being worked to. That way, the reader is directed to the authoritative source rather than to a number someone typed from memory.
This is particularly relevant for work near services. Electrical safety guidance from Safe Work Australia treats isolation, verification and the competence of the person doing the work as core controls, and those are things a SWMS can describe in words without quoting a figure. The same applies to asbestos: where the work involves a material that may contain asbestos, the SWMS should describe how the material is identified, who assesses it, and what happens next, rather than asserting a conclusion the builder cannot support.
Where a figure genuinely matters and you do not have it, say so in the document and name the document it should be checked in. An inspector will accept a clear pointer to the source. They will not accept an invented number.
Worked example: a builder in western Sydney
A builder in western Sydney is running a renovation that includes removal of an existing structure and installation of a new roof. The high-risk work on the job includes work at height and demolition, so a SWMS is required for both. The builder downloads a template, fills in the project address, ticks the hazard boxes, and files it. The crew signs the back page.
Two weeks later the method changes. The original access was going to be via a scaffold; the scaffold is delayed, so the crew switches to a boom lift. Nobody updates the SWMS, because the work is still ‘working at height’ and the hazard list still looks correct.
An inspector arrives after the lift is on site. The SWMS describes scaffold access, edge protection and a sequence that no longer matches what is happening. The review log shows a single entry with no explanation. The signatures are from the scaffold version. The controls that are actually being used on the day are not written down anywhere, which means there is no record that anyone planned the lift setup, the ground conditions, the exclusion zone or the rescue arrangement.
The cost of this is not just a notice. Work stops while the document is rewritten, the crew is stood down or redeployed, and the programme slips. The principal contractor has to be told. If something had gone wrong during the lift, the builder would be explaining a document that described a different job.
The alternative was not a longer document. It was the same document, updated when the method changed, with a review entry saying what changed and why, a new version, and fresh signatures from the people doing the work. That is a ten-minute job on the day the scaffold delay is confirmed. It is a week of disruption later.
Common wording gaps inspectors pull builders up on
These are the recurring failures, and they are all fixable in the drafting stage.
- The task is described as a category. ‘Working at height’ or ‘demolition’ is not a task. The SWMS should name the specific activity, its location and the access method.
- Controls have no owner or trigger. A list of controls with no indication of who applies them or when is not checkable on site.
- The review log is a row of dates. A date with no explanation does not show that anything was reviewed.
- Signatures are not tied to a version. If the document changed and nobody re-signed, the signatures prove nothing about the current work.
- Emergency arrangements are generic. Rescue and emergency response should be described for the specific task, because the response to a fall from a roof is not the same as the response to a fall from a lift.
- Figures are quoted without a source. If a control depends on a number, point to where the number comes from.
- The document does not say where trades hand over. The boundary between trades is where responsibility gets lost, and it should be written down.
If you want a structured way to keep this current across your projects, the PointCPD guide to how NSW builder CPD works explains how safety and compliance topics fit into your annual hours, and the PointCPD course catalogue lists the courses that cover them. You can start from the PointCPD home page for NSW builder CPD courses.
Keeping the document alive through the job
A SWMS written once and filed is a liability. A SWMS that is reviewed when things change, re-signed when the version changes, and referenced in the pre-start is evidence of management. The difference between the two is a habit, not a skill.
The habit is simple. When something about the work changes, open the document. Record what changed and why. Issue a new version. Sign the people doing the work. Put the current version where the crew can see it. Then get on with the job.
Inspectors are not looking for perfect prose. They are looking for a document that shows the work was sequenced, controlled and owned before it started, and that the record was kept current as the job moved. That is the standard, and it is achievable on every project you run.
Questions builders ask
How much detail does a SWMS actually need?
Enough detail that a reader can tell what happens in what order, what control applies at each step, who applies it and what triggers it. That is the test, not page count. A short document that names the actual task, access method and plant is stronger than a long one that lists generic hazards.
Do I need a new SWMS every time the method changes?
You need to review the SWMS when the method changes, and if the change affects the controls or the sequence, you need a new version that the people doing the work sign again. If the review concludes nothing needs to change, record that outcome. What you should not do is re-date an unchanged page.
Who has to sign the SWMS?
The people who will be doing the work, and anyone whose role in the sequence is affected. Signatures should be tied to the version they have read. If a subbie arrives mid-job or the version changes, they sign the current one, not the original.
Can I use one SWMS across multiple sites?
A single method statement can be adapted across similar jobs, but the version that applies on a given site has to describe that site: the access, the ground conditions, the services and the sequence. Copying a document across sites without checking it against the actual conditions is one of the fastest ways to fail an inspection.
What should I do if I do not know a figure the SWMS depends on?
Do not guess it into the document. Write the control so it points to the source: the manufacturer’s specification, the applicable standard, or the regulator’s requirement. Name who holds that documentation on site and who is responsible for confirming the figure before the step starts.
How long do I need to keep a SWMS?
The retention period is set by the work health and safety legislation that applies to your project, so check the current requirement for your jurisdiction and keep the document for at least that long. In practice, keep the version history as well as the current document, because the review trail is what demonstrates the work was managed.
Sources
- BPC issues warning over pool fence safety following inspector ban · Building and Plumbing Commission
- Electrical safety · Safe Work Australia
- Pools and pool safety · NSW Government
- Asbestos in the home · Asbestos and Silica Safety and Eradication Agency
Published 21 June 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
