All guides

Guide · NSW · VIC · QLD · WA · SA · TAS · ACT · NT

Safe Work Method Statements explained

What a SWMS is, when one is required, what tier-one builders look for, and how to write one that survives scrutiny.

By PolicyPack research6 min read1,582 wordsLast updated 14 May 2026
ShareTwitterLinkedIn

A Safe Work Method Statement is the operational artefact at the heart of Australian construction safety law. Every year, hundreds of thousands of them are written, reviewed, signed, and filed across the country. A surprising proportion of them are useless. This guide explains what a SWMS actually is, when the law requires one, what makes the difference between an audit-grade SWMS and a dressed-up template, and how to write one that does the job it was designed for.

Regulation 299 of the Model WHS Regulations is the source. It requires a PCBU to ensure a SWMS is prepared before high-risk construction work commences. The work in scope is defined in regulation 291 — eighteen specific categories of work that the regulator has determined carry sufficient risk of serious harm or death that ad-hoc risk management isn't sufficient.

The eighteen high-risk construction work categories are:

  1. Work that involves a risk of a person falling more than two metres.
  2. Work on a telecommunications tower.
  3. Work involving demolition of an element of a structure that is load-bearing.
  4. Work involving the disturbance of asbestos.
  5. Work involving structural alterations or repairs that require temporary support to prevent collapse.
  6. Work in or near a confined space.
  7. Work in or near a shaft or trench with an excavated depth greater than 1.5 metres, or a tunnel.
  8. Work involving the use of explosives.
  9. Work near pressurised gas mains or piping.
  10. Work near chemical, fuel or refrigerant lines.
  11. Work near energised electrical installations or services.
  12. Work in an area that may have a contaminated or flammable atmosphere.
  13. Tilt-up or precast concrete work.
  14. Work on, in or adjacent to a road, railway, shipping lane or other traffic corridor in use.
  15. Work in an area at a workplace in which there is movement of powered mobile plant.
  16. Work in an area where there are artificial extremes of temperature.
  17. Work in or near water or other liquid that involves a risk of drowning.
  18. Work involving diving.

If your work falls into any of these categories, regulation 299 requires a SWMS. There is no headcount threshold, no exemption for sole traders, no carve-out for residential work. The duty applies whenever the work is performed.

What a SWMS must contain

Regulation 299 prescribes the minimum content. A SWMS must:

  • Identify the work that is, or is to be, carried out.
  • Specify the hazards relating to the work and the risks to health and safety associated with those hazards.
  • Describe the measures to be implemented to control the risks.
  • Describe how the control measures are to be implemented, monitored, and reviewed.

That's the legal floor. Anything less than that is non-compliant by definition. Anything more is a question of practical adequacy — and in the world of tier-one head contractors and serious insurers, the practical floor is significantly higher than the legal one.

What tier-one head contractors look for

Tier-one head contractors — Lendlease, Multiplex, John Holland, Built, the Crown-aligned majors — receive several thousand SWMS per project across the life of the build. Their pre-qualification assessors and on-site safety teams have developed a fast pattern-match for the difference between a real SWMS and a generic one. The pattern goes like this:

A project reference

The SWMS must name the specific project. Not "the construction site." Not "the worksite at the address provided." The actual project — 14 Carlisle Street, Box Hill, Lot 24. A SWMS without a project reference is a template, and templates don't satisfy regulation 299.

A dated revision

The SWMS must carry a version number and a date. Tier-one head contractors typically reject SWMS more than 12 months old. If the work changes scope, the SWMS must be revised, and the revision must be reflected in the version log.

Hazards identified at the level of the actual work

A SWMS for "concreting at heights" should identify the specific risks of this concreting work. Edge proximity, edge protection installation status, access route, weather exposure, exposed reinforcement, fall arrest anchoring options. A SWMS that lists "falls from heights" as the hazard, with no further detail, has identified a category of risk, not a specific risk.

Controls in the right order

The hierarchy of controls — elimination, substitution, engineering, administrative, PPE — is taught in every WHS course. A real SWMS applies it in that order. A SWMS that goes straight to "Workers must wear a harness" without first asking "Can we eliminate the work at heights altogether by relocating the activity to ground level?" is missing the most important question.

Named responsibilities

Each control measure must name a responsible person. Not "the supervisor." A name. The reason this matters is that an incident investigation will trace the chain of responsibility back to the SWMS. If the SWMS doesn't name the responsible person, the chain breaks at the document.

Review and monitoring

Section 4 of the regulation 299 content list — how the control measures are to be implemented, monitored and reviewed — is the section most templates skip. A real SWMS describes the daily prestart check that confirms the controls are in place, the monthly review by the supervisor, and the trigger conditions that require an immediate revision (a near-miss, a change in scope, a change in personnel).

Worker consultation evidence

Regulation 299 requires the SWMS be developed in consultation with workers. The evidence is typically a sign-on sheet attached to the SWMS, with the names of every worker who reviewed it, dated, signed. A SWMS without a sign-on sheet was not developed in consultation, by the regulator's evidentiary standard.

Citation of the underlying regulation

A SWMS that names regulation 299, the specific high-risk work category from regulation 291, and the relevant Code of Practice (e.g. for heights work, the Managing the risk of falls at workplaces Code) signals to a reviewer that the author understood the regulatory basis. A SWMS without these citations doesn't fail the legal test, but it materially shifts the assessor's confidence.

Common SWMS failures

In our experience reviewing several thousand SWMS submitted to head contractor pre-qualification platforms, four failure patterns dominate.

The first is the dressed-up template. The body of the SWMS is the boilerplate from a $40 download. Only the project name and the worker names have been changed. The hazards listed don't reflect the actual work. The controls are generic. The reviewer recognises the template within a page and rejects.

The second is missing the consultation step. The SWMS exists, has good content, but no sign-on sheet. The supervisor wrote it in isolation and never walked it past the workers. This fails section 47 of the WHS Act and the consultation requirement of regulation 299.

The third is PPE-only controls. The SWMS jumps straight to "Workers will wear hard hats and high-vis." The hierarchy is upside down. Every higher-order control should have been considered first.

The fourth is no review trigger. The SWMS doesn't describe what causes a revision. When the work changes, the SWMS doesn't, and the document drifts away from the actual work over the course of the project.

How PolicyPack writes a SWMS

PolicyPack generates a SWMS for each high-risk activity you indicate on the build flow. Each SWMS contains:

  • The project reference, populated from your business details.
  • The activity, named precisely (e.g. "Tile cutting and grinding involving crystalline silica" rather than "Tiling").
  • The hazards, drawn from a maintained register of activity-specific hazards aligned to the relevant Code of Practice.
  • The controls, ordered by hierarchy, with elimination and substitution proposed where reasonably practicable for the activity.
  • Named responsibility fields ready for the competent person sign-off.
  • The review schedule, the review trigger conditions, and the worker consultation panel.
  • Citations to the WHS Regulation reference, the high-risk work category, and the relevant Code of Practice.
  • A version number, a date, and a regenerate-after date.

The output is structured the way Cm3 and Avetta reviewers expect. We have customers who clear pre-qualification on the same day they download.

When you need to write your own

PolicyPack handles the eighteen scheduled high-risk construction work categories. For project-specific activities that aren't in the scheduled list — a particularly complex lift, a one-off rigging operation, a novel installation method — you'll still need to write a SWMS by hand, or by hand with the assistance of a SWMS specialist.

The structure stays the same. Project reference, dated revision, hazards specific to this work, controls in hierarchy order, named responsibilities, review schedule, worker consultation evidence, citations. If you can hold to that structure, the SWMS will pass. If you can't, no template will save you.

What to do next

If your business performs any of the eighteen scheduled high-risk construction work categories: generate a construction pack. Tick the activities you perform on the hazards step. The pack will include a SWMS for each.

If you'd like to see what a real SWMS off the pipeline looks like before you commit: download our sample pack. The SWMS section starts on page 47.

If you have an existing SWMS portfolio and want to know whether it would survive a Cm3 assessment: read it against the failure patterns above. The four common failures account for around 80% of the rejections we see.

Build your pack

Stop reading. Generate the pack.

PolicyPack writes the documents this guide describes — for your specific industry, jurisdiction, and operational scope. Twenty minutes. $199.

ShareTwitterLinkedIn