Method Statement Requirements: What You Need to Include

A method statement describes how a piece of work will be carried out safely. It's one of the most commonly requested documents on UK construction sites, and it's often paired with a risk assessment to form a RAMS document.

But what exactly should a method statement contain? And how detailed does it need to be? This guide covers the key requirements.

What is a method statement?

A method statement is a written document that sets out the safe system of work for a specific task. It describes the sequence of operations, the resources needed, and the safety precautions that will be in place. Unlike a risk assessment (which focuses on identifying hazards), a method statement focuses on how the work will be done.

Who needs a method statement?

Method statements are commonly required for:

• Any high-risk construction activity
• Work submitted to a principal contractor for approval
• Tasks involving significant hazards (working at height, hot works, confined spaces)
• Client or contract requirements that specify documented safe systems of work

While there's no specific law that mandates a "method statement" by name, the requirement to plan and document safe systems of work is established under the Health and Safety at Work Act 1974 and CDM 2015.

Key sections of a method statement

1. Project information — site name, location, client, contractor, dates
2. Scope of works — what work is being carried out and where
3. Sequence of operations — step-by-step description of the work
4. Plant and equipment — what machinery, tools, and equipment will be used
5. Materials — what materials are involved and any handling requirements
6. Personnel and responsibilities — who is doing what, including supervision
7. Safety measures — control measures, PPE, exclusion zones, permits
8. Emergency procedures — first aid, fire, evacuation, rescue plans
9. Sign-off and review — prepared by, approved by, review date

How detailed should it be?

A method statement should be detailed enough that someone unfamiliar with the task could understand the safe way to carry it out. That doesn't mean it needs to be 20 pages long — clarity and specificity matter more than length.

The key test: could a competent worker follow this document and complete the task safely?

Common problems with method statements

• Too generic — could apply to any job on any site
• Steps are listed but not sequenced logically
• No mention of who is responsible for each step
• Safety measures are vague ("appropriate precautions will be taken")
• No link between the method statement and the accompanying risk assessment

Generating method statements efficiently

Writing method statements from scratch is time-consuming, especially if you're producing them for multiple tasks or sites. A method statement generator can help by providing a structured framework with relevant steps already suggested based on your work type.

Riskora's method statement builder lets you define the sequence of work, link steps to hazards, and export a professional document — all within minutes.

Summary

A good method statement is specific, sequential, and practical. It should describe the actual work being done, not a theoretical version of it. Include enough detail for someone to follow safely, and review it for every new project or site.

See it in practice

The clearest way to understand a good method statement is to read one written for a specific job. These examples show the level of sequence and detail clients actually expect:

• Method statement for asbestos removal — enclosure build, decontamination, and air monitoring written as a step-by-step sequence
• Method statement for demolition-site hoarding — sequencing, exclusion zones, and public protection at each stage
• Method statement for a scaffold loading bay — erection sequence, load limits, and inspection holds

Related guides

• Method Statement Generator — build a structured method statement in 5 minutes
• RAMS Generator UK — combine method statement + risk assessment in one document
• Instant method statement generator — create method statements quickly
• How to write a RAMS document — combining risk assessment with method statement
• RAMS examples for construction — see real document structures
• Method statement examples — UK standard examples by trade
• RAMS for contractors — documentation for subcontractor access