A safe work method statement (SWMS) sets out how high-risk construction work will be done safely: the hazards, the controls, who does what and who has signed. WHS laws (OHS laws in Victoria) require one before high-risk construction work starts, such as work where someone could fall more than two metres, work in a confined space, or work near energised electrical installations.
Plenty of maintenance on operating sites falls into these categories. OpsChase keeps the SWMS on the work order.
Why multi-site teams care about SWMS
Even when a contractor does the work, you still share safety duties for your sites. If something goes wrong during a roof repair or a switchboard job, the first questions are whether a SWMS existed, whether it matched the task, and whether anyone checked it. A SWMS sitting in a contractor’s email or a site folder does not answer those questions quickly, and across many sites it is easy to lose track of which version applied where.
What a good SWMS looks like
- It is specific to the task and the site, not a generic document reused for every job.
- It names the hazards that actually apply, such as roof access, live plant, vehicle movements or members of the public nearby.
- It lists the controls in plain language and who is responsible for each one.
- The workers doing the job have read and signed it.
- It is reviewed when the work or the site changes, and work stops if it is not being followed.
Common SWMS mistakes
- Taking a generic SWMS that names the wrong site or the wrong task.
- Collecting a SWMS once at onboarding and assuming it covers every future job.
- Storing it away from the job, so nobody can show which version applied on the day.
- Asking for a SWMS on low-risk work where a simple checklist would do, so the important ones get less attention.
- Never checking that the signatures match the people who attended.
How SWMS fit contractor tracking
In OpsChase, you can attach SWMS requirements to job templates for higher-risk trades. Contractors upload or sign the SWMS from their phone, and the work order shows whether it is there before attendance or before the job can close. The SWMS sits beside the confirmation, attendance times and proof for that job, so a safety review sees the full record in one place. Licence, public liability, induction and site-access details for the contractor are kept on file and checked before booking.
See contractor compliance for what sits on file for each contractor.
On OpsChase: one queue for your team and contractors, each job tracked until the work is done, then photos or sign-off. Book a demo — one site or many.
- Does OpsChase write SWMS for contractors?
- No. The contractor prepares the SWMS for their work, or you supply approved templates. OpsChase records which document applied to which job.
- Can a SWMS be required only for some jobs?
- Yes. Template rules decide which jobs need one, so low-risk work is not slowed down.
- Is a job safety analysis the same as a SWMS?
- Not exactly. A job safety analysis is a general risk tool; a SWMS is the document WHS laws require for high-risk construction work. Store the type your policy asks for.
- Who should check the SWMS?
- Someone who knows the site, usually the facilities or site manager. They should check it matches the task, the site and the people attending.
- Do we need a SWMS for every maintenance job?
- No. It is required for high-risk construction work. For other jobs, your own safety policy decides what paperwork is needed.
