A method statement plans and sequences a complex or one-off construction operation, naming roles, interfaces and control measures before work starts. A safe work procedure, sometimes called an SWMS or SOP, sets out the repeatable safe steps for a routine task performed by trained personnel. The dividing line is complexity and frequency, and auditors under MOM and ConSASS frameworks expect each document to appear where its own triggers apply.
TL;DR:
- Method statements are necessary for high-risk, complex, or multi-trade activities, while SWPs are suited for routine tasks with consistent controls.
- Accurate version control and clear cross-referencing between risk assessments, method statements, SWPs, and permits are crucial to passing audits and ensuring site safety.
- On-site verification through daily sign-offs and supervisor walkthroughs helps align documented procedures with actual work practices, preventing non-conformances.
- Proper documentation should include key elements such as work sequence, responsibilities, hazard controls, PPE, and emergency arrangements, tailored to each document type.
- Poor document management, such as outdated revisions and missing approvals, is a common cause of audit failures and safety risks on construction sites.
Table of Contents
- Method Statement vs SWP: A Side-by-Side Comparison
- When to Use a Method Statement Instead of an SWP
- What Belongs in Each Document: A Contents Checklist
- How Method Statements, SWPs and Risk Assessments Fit Together
- What Auditors Check and Where Documents Fail
- Harmonizing Documents So They Match Site Practice
- Copy-Ready Templates for Method Statements and SWPs
- What Clear, Harmonized Documents Actually Buy You
- Get Compliance-Ready Documentation Support
- Sources
- FAQ
Method Statement vs SWP: A Side-by-Side Comparison
The two documents diverge on scope, authorship, timing and the conditions that trigger them, and getting this wrong is one of the more common findings in a site audit.
- Scope and length: a method statement covers an entire operation end to end, often running several pages with sequencing diagrams, while an SWP is typically a concise, single-task procedure.
- Authorship and approval: method statements are usually drafted by the site engineer or project manager and approved by the project director or a competent person, whereas SWPs are drafted by supervisors or WSH officers and endorsed at department level.
- Timing: a method statement is produced during planning, well before mobilization, while an SWP is referenced daily, often during toolbox talks or shift briefings.
- Triggers: high-risk, multi-trade or non-standard activities call for a method statement, while recurring tasks with established controls, such as operating a fixed machine, call for an SWP.
Under MOM’s risk management guidance, employers and principals must establish safe work procedures whenever a risk cannot be eliminated, and those SWPs must include emergency measures and defined roles that are communicated to every worker involved. That legal anchor is why an SWP can never be treated as an optional add-on to a method statement: it is often the compliance instrument the law names directly.
When to Use a Method Statement Instead of an SWP
Choosing the right document comes down to risk level, the number of trades involved and whether a regulatory trigger applies.
- Tower crane lifts and other lifting operations demand a method statement because the Code of Practice for Safe Lifting Operations requires lifting plans to be accompanied by a risk assessment and a safe work procedure or method statement, plus a permit-to-work, with complex lifts requiring additional engineering calculations.
- Sequential demolition needs a method statement because the sequencing, temporary works and structural interfaces change at every stage, something a fixed SWP cannot capture.
- Confined space entry usually sits on the SWP side once the entry procedure is standardized, though a first-time entry into an unfamiliar space may still warrant a method statement.
- Routine plant operation, such as running a concrete pump on a repeat basis, belongs to an SWP because the task and its controls do not change from one shift to the next.
- One-off or irregular activities default to a method statement; recurring, well-understood tasks default to an SWP.
The practical mapping is simple: if the task changes shape every time it runs, plan it with a method statement; if it repeats identically, standardize it with an SWP.
What Belongs in Each Document: A Contents Checklist
Both documents fail audits for the same reason: missing fields rather than missing intent. A method statement should build out sequencing and coordination; an SWP should build out repeatable safe steps.
- Method statement checklist: work sequence, roles and responsibilities, interfaces between trades, temporary works details, plant and equipment list, and emergency arrangements specific to the operation.
- SWP checklist: step-by-step safe actions, required PPE, key hazard controls, list of authorized or trained personnel, and any certification requirements tied to the task.
- Shared metadata: document ID, revision number, date of approval, name and role of the approver, and the review date for the next update.
Pro Tip: Keep a single metadata block format across every method statement and SWP template so an auditor can verify version control at a glance, without hunting through inconsistent headers.
Version control is not a formality. A method statement that was approved for revision 2 of a structural sequence but is still being referenced at revision 4 on site is one of the fastest ways to fail a ConSASS document review.
How Method Statements, SWPs and Risk Assessments Fit Together
Every method statement and every SWP is downstream of a risk assessment, which identifies the hazards that both documents must then control. The risk assessment is the primary input; the method statement and SWP are the outputs that translate its findings into action on site.
- A SWMS or RAMS is typically required where a jurisdiction names it directly, and a method statement often supports the underlying lifting plan or high-risk work plan rather than replacing it.
- A permit-to-work is layered on top of both documents for activities such as hot work, confined space entry or lifting, and the permit should reference the specific method statement or SWP it depends on.
- Cross-referencing by document ID, hyperlink or appendix keeps the chain traceable: the risk assessment cites the method statement, the method statement cites the SWP for any embedded routine task, and the permit-to-work cites both.
Losing that traceability is a common finding on its own, and MOSAIC’s guide to risk assessment covers how the assessment itself should be structured to support this chain.
What Auditors Check and Where Documents Fail
The ConSASS user guide sets out a Band I to Band III maturity structure, and auditors verify evidence through document review, personnel interviews and physical inspection rather than paperwork alone. That three-way check is exactly where mismatches between planning documents and site practice get exposed.
- Document-site mismatch: the method statement describes one sequence, but workers on site are following a different, unwritten process.
- Missing approvals: an SWP in circulation without a signed-off revision, or a method statement missing the competent person’s endorsement.
- Poor version control: multiple copies of the same document in circulation with no clear indication of which revision is current.
Recent MOM guidance shows that public-sector tender frameworks have increased the emphasis on safety-related criteria, and tenderers may need to demonstrate their WSH documents and technology adoption directly. That shift means a company’s method statement and SWP library is no longer only an audit artifact, it is increasingly a tender qualification asset, and MOSAIC’s audit examples illustrate how these non-conformances typically surface during review.
Harmonizing Documents So They Match Site Practice
Audit non-conformances rarely stem from bad drafting alone. They stem from a method statement and an SWP that were written correctly on the day but drifted apart from what workers actually do once the job started. Closing that gap is a document control problem before it is a training problem.
- Version control should live in a document management system with locked previous revisions, not in shared folders where old copies linger alongside current ones.
- On-site verification through handover checklists, supervisor walkthroughs and daily briefing sign-offs confirms that the procedure on paper matches the procedure being followed.
- A single source of truth, built from cross-referenced templates rather than duplicated content, prevents the same control measure from being described three different ways across three documents.
Pro Tip: Require every daily briefing sign-off sheet to name the exact SWP or method statement revision referenced that day, closing the gap auditors look for between planning documents and observed practice.
Quality, Environment, and Safety consultancy services for the construction sector include certification support such as BizSAFE and ISO, with document harmonization playing a central role in this work. Further detail on how ConSASS assessments treat this alignment appears in MOSAIC’s ConSASS overview.
Copy-Ready Templates for Method Statements and SWPs
A method statement template should carry these headings at minimum: scope of work, sequence of operations, roles and responsibilities, plant and equipment, interfaces with other trades, temporary works, and emergency arrangements. An SWP template needs: task description, step-by-step actions, PPE requirements, key controls, authorized personnel, and training or certification requirements. Both need the shared metadata block covering document ID, revision, approval date and reviewer.
- Draft the document against the relevant risk assessment, filling every checklist field rather than leaving placeholders.
- Approve through the named competent person or supervisor, recording the date and signature in the metadata block.
- Verify on site through a handover checklist that confirms the current revision matches what is posted and being followed at the work face.
What Clear, Harmonized Documents Actually Buy You
The most common pitfall observed across construction sites is not a missing document, it is two correct documents that no longer agree with each other or with what happens at the work face. A method statement written for revision 1 of a sequence stays pinned to a noticeboard long after revision 3 is in use, and nobody notices until an auditor does.
Getting this right pays off beyond the audit itself. Clean, cross-referenced method statements and SWPs support a stronger safety culture on site, and they increasingly feed into PQM scoring and tender competitiveness as public-sector frameworks weight safety documentation more heavily. MOSAIC’s consultancy work spans training, auditing, manpower outsourcing and specialist solutions such as Design for Safety and ConSASS, all aimed at closing this exact gap between paperwork and practice.
— Aman
Get Compliance-Ready Documentation Support
Drafting a method statement or SWP that survives a ConSASS audit takes more than a template, it takes documents that are built to match how your site actually operates. EHS Advisory and Documentation services help construction teams produce method statements and SWPs that hold up under document review, personnel interviews and physical inspection, the same three checks ConSASS auditors run on every visit.
Where a project also needs certification support, MOSAIC’s WSH Audit and Inspection and ConSASS services prepare the evidence base auditors expect to see, from version-controlled documents to on-site verification records. Get in touch through MOSAIC’s EHS Advisory and Documentation page to have your method statements and SWPs reviewed before your next audit cycle.
Sources
- Workplace Safety and Health (Risk Management) guidance — MOM
- Code of Practice for Safe Lifting Operations (WSH Council/TAL)
FAQ
What’s the difference between an SOP and an SWP?
An SOP, or standard operating procedure, and an SWP are often used interchangeably in construction, both describing the repeatable safe steps for a routine task. Where a distinction is drawn, SOP tends to describe general operational process while SWP specifically emphasizes the safety controls within that process.
What is the difference between a method statement and a risk assessment?
A risk assessment identifies hazards and evaluates their likelihood and severity, and it is the primary input that informs both a method statement and an SWP. A method statement then translates those findings into a sequenced plan for how the work will actually be carried out.
What does SWP stand for in construction?
SWP stands for safe work procedure, a document setting out the standardized safe steps for performing a routine or recurring task. Under MOM’s risk management guidance, employers must establish SWPs whenever a risk cannot be eliminated, and these must include emergency measures and defined roles communicated to workers.
What is another name for a method statement?
A method statement is sometimes referred to as a SWMS, or safe work method statement, particularly where that term is the one named in local regulation. Both describe the same kind of document: a planning tool for how a complex or high-risk operation will be sequenced and controlled.
