Why SWMS Review Becomes a Bottleneck, and What Fixes It
SWMS review becomes a bottleneck because a safe work method statement is required before high risk construction work starts, every subcontractor writes its own, each one must account for the conditions at your workplace, and one person reads them all. The fix is not reading faster. It is agreeing the criteria before the document arrives, reviewing against those criteria rather than reading end to end, and sending back a rejection reason a subcontractor can act on.
Put your SWMS review criteria in front of the document.
Book a demoSafe work method statements come up in nearly every conversation I have with a head contractor. Not because anyone doubts they are worth having. Because the pile arrives on one desk, work cannot start until that desk clears it, and the desk belongs to someone who also has sites to visit.
Be honest about what that does to the review. When a crew is standing around waiting, the pressure on the reviewer is operational, not safety-driven. Nobody says approve it anyway. Everybody knows the fastest way to unblock the site.
Here is what the law asks for, why the queue forms, and what clears it.
What a SWMS Is, and When One Is Required.
A safe work method statement is required before high risk construction work starts, and only for that work. Regulation 291 of the model WHS Regulations defines high risk construction work as construction work that involves a risk of a person falling more than 2 metres; is carried out on a telecommunication tower; involves demolition of a load-bearing element or one otherwise related to the structure’s physical integrity; involves or is likely to involve disturbing asbestos; involves structural alterations or repairs requiring temporary support to prevent collapse; is carried out in or near a confined space; is carried out in or near a shaft or trench with an excavated depth greater than 1.5 metres, or a tunnel; involves the use of explosives; is carried out on or near pressurised gas distribution mains or piping; on or near chemical, fuel or refrigerant lines; on or near energised electrical installations or services; in an area that may have a contaminated or flammable atmosphere; involves tilt-up or precast concrete; is carried out on, in or next to a road, railway, shipping lane or other traffic corridor in use; in an area with any movement of powered mobile plant; in an area with artificial extremes of temperature; in or near water or other liquid with a risk of drowning; or involves diving work.1
That is 18 categories, and most construction sites hit several in a week. For other work a SWMS is not required, though the code is clear the duty to eliminate or minimise risk still applies.2
What a SWMS Has to Contain.
Regulation 299 is short and worth knowing by heart, because almost every argument about a rejected SWMS is an argument about one of four lines. A SWMS must identify the work that is high risk construction work; specify the hazards relating to it and the risks associated with those hazards; describe the measures to control the risks; and describe how those control measures are to be implemented, monitored and reviewed.1
It must also take into account all relevant matters, including the circumstances at the workplace that may affect how the work is carried out and the project’s WHS management plan where there is one, and be set out so the people using it can read and understand it.1
The code of practice turns that last point into something reviewable. The content should give clear direction on the controls, with no statement leaving a decision to a supervisor or worker. Its example is the line every reviewer has seen: use appropriate personal protective equipment does not describe a control measure.2
Who Has to Be Consulted Before It Is Written.
The code says the person responsible for carrying out the high risk construction work is best placed to prepare the SWMS, in consultation with the workers who will be directly engaged in it. Where no workers are engaged at the planning stage, consultation must happen when the SWMS is first made available to them, in workplace-specific training or a toolbox talk. Workers and their health and safety representatives must also be consulted when a SWMS is reviewed.2
Consultation has a legal meaning, which is why a signature sheet does not get you there. Section 48 of the model WHS Act requires that relevant information is shared, that workers get a reasonable opportunity to express views and contribute to the decision, that their views are taken into account, and that they are told the outcome in a timely way.3
Where more than one business holds the duty, they must consult and cooperate to coordinate who prepares it, and on a project the principal contractor gets a copy before work starts.12
Why the Review Does Not Scale.
Put those requirements next to how the work is organised and the queue explains itself.
Every subcontractor writes its own, in its own format, at its own length. A SWMS must account for the conditions at your workplace, so one that was fine on the last job is not automatically fine on this one. The code allows a generic SWMS for work done regularly, but only if it is reviewed against the hazards of the specific workplace and revised as necessary, which is exactly the part that gets skipped.2 A project can have several running at once for different high risk work, and the code expects you to consider how those activities affect each other and whether the controls contradict.2
Meanwhile the reviewer is one person, the documents are long, and work cannot start until they are done. The safety manager reading them should be on site checking whether the last set of controls is being used.
The failure this produces is not a rubber stamp. It is a drift towards reviewing format instead of content, because format can be checked in a minute and content cannot.
What Actually Fixes the Bottleneck.
Four changes, and only the last one involves software.
Agree the criteria before the document arrives. If a subcontractor knows what you will check and the standard each item has to meet, most of the rework never happens. Publish them with the tender, not after the rejection.
Give people a template that meets regulation 299 on its face: a field for each of the four required elements and a prompt for the site-specific circumstances. The code includes a SWMS template and a completed sample in its appendices.2
Review against the criteria rather than reading end to end. A read-through invites a judgement about the whole document. A criteria pass produces a list: present, partly present, missing. That list is the same length whether the document runs to 6 pages or 40.
Send back a reason the subcontractor can act on. Rejected with no comment guarantees the same document returns. In ComplyFlow the reviewer’s comments go back with the rejection, the item stays outstanding until a valid replacement arrives, and the history stays on the document.5 The Help Centre article Check Why Your Document Was Rejected and Find the Solution covers the contractor’s side of it.6
Where AI Review Fits, and Where It Does Not.
The claims made for AI here are usually broader than the thing can do, so the boundary is worth stating plainly.
A machine reads a document against criteria very well. It does not get bored on the thirtieth one, it applies the same criteria to the first and the hundredth, and it tells you what is present, partly present, and missing. That is most of the reading time, and the part with the least judgement in it.
What it cannot do is decide whether the control suits this site. Whether the exclusion zone works given where the crane is standing this week. Whether the crew has done this before. That needs somebody who has stood in the place, and the law puts the decision with a person.
So the line in ComplyFlow’s AI review is hard: an agent reads against criteria you set and returns an assessment, and a person approves or rejects. The agent attaches to a form type such as a work permit or a SWMS and to specific questions on it, so the review runs where the document is submitted.4 That is why SWMS review sits with digital permits, and the same logic runs upstream in prequalification: machine reading, human deciding, criteria you wrote.
The Obligation That Makes a SWMS Go Stale.
The requirement most sets quietly fail is not the first review. It is regulation 302: a SWMS must be reviewed and, as necessary, revised whenever the relevant control measures are revised under regulation 38.1
Regulation 38 is broad, and worth reading twice. Control measures must be reviewed when the measure is not controlling the risk, before a change at the workplace likely to give rise to a new or different risk it may not control, when a new hazard or risk is identified, when consultation indicates a review is needed, or when a health and safety representative requests one. A change at the workplace expressly includes a change to a system of work, a process or a procedure.1
Read that against a live site. The sequence changes, a different crane goes in, the ground turns, and the SWMS approved in week two describes a job nobody is doing. The code adds that every revised version should be kept, the people doing the work must be told and shown how to get the new one, and the principal contractor must be given a copy.2 The document itself must be kept until the work is completed, and for at least two years after a notifiable incident connected with it.1
What to Do with Your Next Ten SWMS.
Take the next ten that arrive and, before reading any of them, write down the criteria you will check. Then run all ten against that list rather than reading them in order.
Two things usually fall out. The list is shorter than you expected, so the review is more repeatable than it felt. And the same two or three gaps appear across most of them, so the fix is a conversation at tender, not a faster reviewer.
The queue is not caused by volume. It is caused by a review nobody has written down, so it gets reinvented on every document, by the one person who cannot be replaced while they are doing it.