Complys AU โ†’ Whs Compliance Software โ†’ Review a SWMS after high-risk construction work changes
Whs Compliance Software

Review a SWMS after high-risk construction work changes

A safe work method statement (SWMS) may have matched the task at the morning briefing, then a crane position, work sequence or access route changes. The old document remains evidence of the original plan; it is not a licence to continue under controls that no longer fit. The affected work needs a risk review, a revised method where necessary and communication to the people doing it.

This guide is about the change-control point after high-risk construction work has been planned or started in Australia. It does not teach how to prepare the first SWMS or replace a pre-start verification. Safe Work Australia's model Code of Practice for construction work explains SWMS review and revision. The model code's legal status varies by jurisdiction; verify the state or territory law and approved code for the project.

Identify the change and stop the affected step

Ask what changed: scope, equipment, people, location, sequence, weather, neighbouring work or a control measure. A change does not have to be dramatic to matter. Moving a lift point may alter ground stability and exclusion zones. A new subcontractor may create an interface not covered in the original plan. If the SWMS no longer addresses the work, pause the affected activity while a competent person reassesses the risk and controls. Do not wait until the next routine document review.

Record the old condition and the new one. Note who raised the issue, which crew is affected and any interim control. That makes the reason for revision visible. A document with only a new date and unchanged content may not demonstrate that the actual change was considered.

Review the control, not merely the wording

Compare the proposed new method with the hazard and control sequence in the current SWMS. Ask whether the original controls remain effective, whether new hazards arise and whether another party must coordinate. Review related permits, traffic management, plant isolation, temporary works and rescue arrangements as needed. If the control measures change, revise the SWMS so the document describes the work that will actually happen.

The model construction code says that if control measures detailed in a SWMS are revised, the SWMS must be reviewed and revised as necessary. It also says the review should involve affected workers, including contractors and subcontractors, and their health and safety representatives where relevant. Consultation is a practical way to discover a field constraint that an office review misses.

Communicate the revised method

After a change, people involved in the high-risk work need to know a revision has been made and how to access it. Brief those who must change their procedure and confirm they understand what is different. The model code says the principal contractor should receive a copy of a revised SWMS for a construction project. The exact duty should be checked under the applicable law; the operational point is that the coordinating party cannot supervise against an old method.

Keep earlier versions. Someone reviewing the work later should be able to establish which SWMS applied at which time. Avoid silently overwriting a PDF and leaving workers with printed copies that still describe the old controls. Mark superseded copies and retrieve them from points of use where practicable.

Decide when work may restart

Set an accountable restart decision. Confirm the revised controls are available and practical on site, any plant or equipment is suitable, permits are aligned and the affected crew has been briefed. A manager approving the document remotely should not assume the changed control exists in the field. Where a control cannot be implemented, the work should not be resumed merely because the SWMS has been edited.

The restart record can capture the revised version, briefing attendance, unresolved items and authorisation. It need not be an elaborate new document for every minor change, but it should make the decision clear. A high-risk task deserves a stronger check than an administrative typo correction.

Example: changed access for roof work

A roof repair SWMS uses a scaffold staircase and a defined exclusion zone. The staircase is unavailable, and a crew proposes a different access point near vehicle traffic. The supervisor pauses the roof work, checks access and fall controls, consults the crew and traffic controller, revises the SWMS and coordinates with the principal contractor. Workers are briefed on the new route before restart. The original version remains in the record. A photo of the alternate ladder by itself would not show that the changed risks were assessed.

For a multi-contractor project, note which version each party received. A subcontractor may use a current copy while the principal contractorโ€™s register points to the old one, or vice versa. Confirm distribution rather than assuming an upload notification was read. The change record should identify any related permit or traffic plan that needs revision, so the SWMS does not contradict live site controls.

After the revised method has been used, the supervisor should check whether it worked as expected. If workers rely on an unplanned workaround, the review has not fully addressed conditions. Reopen the assessment rather than treating the signed revision as the final answer.

Keep the operational and document trails together

A useful workflow links the change report, revised risk assessment, SWMS version, consultation, briefing and restart decision. Test whether the record can show an open change while the old SWMS remains visible but clearly superseded. The mapped Complys Australian WHS software page gives wider product context. Verify current functions before relying on it. This article does not claim Complys automatically validates SWMS content or authorises high-risk work.