Method Statement
A written document that explains, step by step, how a specific construction activity will be executed safely, in what sequence, with what resources, and under what controls.
Definition
A Method Statement — sometimes called a Safe Work Method Statement (SWMS) or Work Method Statement (WMS) — is the written narrative that translates a design and a programme into an executable, safe sequence of site activities. It answers a simple question the foreman will ask on the morning of the pour: "How, exactly, are we going to do this?" Good method statements are short, specific, and read like they were written by someone who has actually held the tool.
What It Actually Contains
- Scope of the activity and the drawings it references.
- Sequence of steps in the order they occur on site.
- Plant, equipment, and materials required for each step.
- Manpower — trades, numbers, supervisor names.
- Hazards identified and the specific controls in place (linked to the Permit to Work system where applicable).
- Inspection and Test Plan (ITP) hold points.
- Emergency procedures and rescue plan.
- Approvals — designer, engineer, HSE lead, client representative.
Why It Matters
The method statement is where the schedule meets the ground. A Gantt chart shows that "Erect Steel — Grid 4 to 8" starts on Tuesday; the method statement explains that the crane picks from the south lay-down, the ironworkers use fall arrest above 1.8 m, the temporary bracing stays until the deck is placed, and the pick weights are within 78% of the crane's rated capacity at 24 m radius. Without that narrative, execution defaults to whatever the crew did last time — which is usually fine, until it isn't.
Real-World Example
On a hospital extension in the Midlands, the steel-erection method statement identified a specific pick where the load chart put the crane at 92% capacity with a full fuel tank. The site engineer flagged it during review. The revised statement moved the pick to a lower boom angle, reduced the load radius by 3 m, and added a second slinger. The pick took 40 minutes longer than planned. Two months later the HSE inspector reviewed the same document during a routine visit and closed out the audit with no findings. The 40 minutes were the cheapest 40 minutes on the project.
Practical Lessons Learned
- Write for the person doing the work — not for the file. If the foreman won't read it, it hasn't been written.
- Photograph the site condition and paste it into the document. A 200-word paragraph rarely beats one annotated photo.
- Keep them living. A method statement written twelve months ago for a different site condition is a liability, not a control.
- One activity, one document. The temptation to write "General Concreting Method Statement" produces a document that describes nothing in particular and controls nothing at all.
- Sign-off on paper, briefing on site. Every operative in the pack should be talked through the sequence before they pick up a tool.
Common Mistakes
- Copy-paste from a previous project without adjusting for the actual site layout, plant, or crew.
- Overloading the document with generic HSE boilerplate until the actual method is buried on page 14.
- Skipping the pre-task briefing and treating the signed cover sheet as the control.
- No revision control — the crew works to Rev A while the engineer approved Rev C.
- Method statement written by someone who has never set foot on that particular site.
- No named supervisor; accountability evaporates the moment a decision is needed.
- Hazards listed without matching controls — a checklist that helps nobody.
Expert Tips
- Two pages is often enough. If it needs more, the activity probably needs decomposing.
- Draft with the foreman in the room. Twenty minutes of their time saves a fortnight of rework.
- Cross-reference the ITP. Hold points inside the method statement remove the "we didn't know we needed a survey" argument.
- Test the sequence against the programme. If the method genuinely takes 3 shifts and the schedule shows 2, one of them is wrong — usually the schedule.
- Keep old versions. When something goes sideways six months later, the version signed on the day is the document that matters.
Key Takeaways
- A method statement translates design and programme into an executable sequence — no more, no less.
- Written for the crew, briefed on site, revised when conditions change.
- Hazards and controls must be paired, specific, and site-relevant.
- Generic templates do not save time; they transfer risk.
- Signed paper without a pre-task briefing is a filing exercise, not a control.
Related Concepts
Interlocks with Permit to Work, Quality Gates, Handover Management, and Constructability Review. Templates and worked examples at PMMilestone.org.
Frequently Asked Questions
What is a method statement in construction?
A written, activity-specific document that describes the sequence of work, the resources required, the hazards involved and the controls in place. It sits between the design/drawings and the crew on the day of the work.Method statement vs risk assessment — what's the difference?
A risk assessment identifies hazards and rates them; a method statement describes how the work is actually executed and how those hazards are controlled step by step. In practice the two are written together and cross-referenced.Who writes the method statement?
Usually the contractor's site engineer or trade supervisor, ideally with input from the foreman who will run the crew and sign-off from the HSE lead and designer. Documents written in the head office rarely survive contact with the site.Is a generic template acceptable?
As a starting point, yes. As the final document, no. A generic template needs to be edited to reflect the actual layout, plant, crew and sequence of the specific job. Otherwise it controls nothing.How often should method statements be reviewed?
Any time the site condition, the plant, the design or the crew changes materially. On a long programme, a quarterly review is a reasonable minimum. Old method statements that don't reflect current conditions are audit findings waiting to happen.Do subcontractors write their own?
Yes. Each subcontractor is responsible for the method statement for the work they perform, which is then reviewed and integrated by the principal contractor. Interfaces between subcontractors should be explicit in both documents.What is the biggest common mistake?
Copying last project's method statement without changing the specifics. It looks like a control, it signs off as a control, and it protects nobody when the incident happens.What is a common misconception about Method Statement?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.Which related encyclopedia entries should I read alongside Method Statement?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Method Statement?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Method Statement is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Method Statement defined on PMMilestone Research & Insights?
A written document that explains, step by step, how a specific construction activity will be executed safely, in what sequence, with what resources, and under what controls. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
People also ask
Follow-up questions practitioners search for next — each one points to the calculator, template or reference entry that answers it.
Where is this in the glossary?
Quick-lookup definitions across 1,200+ PM terms. PM Glossary on PMMilestone.org ↗
Which learning track covers this end-to-end?
Structured tracks from beginner planner to programme controls director. Project Controls Academy ↗
Which book goes deeper than this entry?
Practitioner field handbooks with worked numerical examples. Books & Publications ↗
Which calculator on PMMilestone.org applies here?
The integrated EVM workbook covers most cost-schedule diagnostics. EVM Calculator ↗
Related Entries
How to Become a Senior Planning Engineer in Large Construction Projects
How senior planners use method statements to sanity-check durations, sequences and resource loading before a schedule ever leaves draft.
More in Construction Execution
- Letter RRFI Management
The disciplined tracking of Requests for Information — the formal channel through which contractors ask designers to clarify, correct, or resolve ambiguities in the construction documents.
- Letter SSite Logistics Plan
The drawing-and-narrative package that shows how a construction site will physically operate — access, deliveries, laydown, cranes, welfare, and traffic — through each major phase of the works.
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform, PMMilestone.org.
- For practitioners who want to go deeper, the Project Controls Academy.
- Engineers researching this topic typically continue with the Schedule Health Checker.
- A practical companion to this entry is the Failure Database.
- Closely related on the flagship platform is the Learning Tracks.
- Useful alongside this article is the Books & Publications.
- Many readers follow this up with the Risk Register Template.
- Project teams often pair this with the PMMilestone.org knowledge hub.