Method Statement Explained

A method statement is a written document that describes how a particular task or process will be carried out safely. It sets out the sequence of work, the resources needed, and the safety precautions that will be taken at each stage. In the UK construction industry, method statements are one of the most frequently requested safety documents — alongside risk assessments — and are a standard part of site access requirements.

This guide explains everything you need to know: what a method statement is, when you need one, what it must contain, and how to write one that actually gets approved.

What is a method statement?

A method statement is a step-by-step description of how work will be done safely. It's not a risk assessment (that's a separate exercise), though the two are frequently combined into a RAMS document. The method statement focuses on the how — the practical process — while the risk assessment focuses on the what could go wrong.

Think of it as a recipe for safe work. It tells everyone involved: what's being done, in what order, with what equipment, by whom, and with what safety measures in place.

When do you need a method statement?

There is no single UK law that specifically says "you must produce a method statement." However, several regulations create obligations that are most effectively met through method statements:

• The CDM Regulations 2015 require contractors to plan, manage, and monitor construction work to ensure safety. A method statement is the standard way to document this planning.
• The Management of Health and Safety at Work Regulations 1999 require employers to make arrangements for effective planning, organisation, and control of preventive measures.
• Most principal contractors require method statements from subcontractors before granting site access — this is contractual, not just regulatory.

In practice, you need a method statement for any work that involves significant hazards, multiple steps, coordination between trades, or activities that could affect other people on site.

What must be included in a method statement?

A good method statement covers these elements. For a deeper breakdown, see our full guide on what must be included in a method statement.

Essential sections

• Project details — site name, address, client, contractor, dates
• Description of work — clear, specific scope (not vague generalities)
• Sequence of operations — step-by-step, chronological order
• Plant and equipment — every item of plant, tools, and materials needed
• Personnel and competence — roles, numbers, qualifications, and CSCS/trade card requirements
• Safety measures — PPE, barriers, permits, exclusion zones, signage
• Environmental considerations — dust, noise, waste management, contamination
• Emergency procedures — first aid, fire, task-specific scenarios
• Interfaces — coordination with other trades, site traffic, public access
• Sign-off — prepared by, approved by, date, review schedule

Method Statement Best Practice Guide

These principles separate effective method statements from documents that get rejected or ignored:

• ☐ Write the method statement before work begins, not retrospectively
• ☐ Be specific to the actual site and conditions — not a generic template
• ☐ Write each step clearly enough that someone unfamiliar with the task could follow it
• ☐ Include hold points — stages where work should pause for checks or approvals
• ☐ Cross-reference the risk assessment so every identified hazard has a corresponding control in the method
• ☐ Name roles and responsibilities — don't use vague terms like "the team"
• ☐ Include preparation and demobilisation, not just the active work
• ☐ Use plain language — operatives need to understand it, not just safety professionals
• ☐ Version control — issue new versions when conditions change
• ☐ Brief it to all workers before work starts (toolbox talk)

Common mistakes with method statements

• Too vague — "Install pipework" is not a method statement step. "Install 100mm MDPE pipework in trench at 750mm depth using sand bedding and pea gravel surround" is.
• Copied from another project — if the method statement references a different site, different conditions, or work you're not doing, it will be rejected
• Missing the safety content — a method statement that reads like a construction programme without safety measures is incomplete
• No sequence — steps listed randomly rather than in the order they'll actually happen
• Disconnected from the risk assessment — the method statement should directly address the hazards identified in the risk assessment
• Never briefed — a method statement that exists only in the site office filing cabinet serves nobody
• Overly long for simple tasks — proportionality matters. A 20-page method statement for a simple task suggests padding, not thoroughness

Method statement vs risk assessment vs RAMS

These three terms are often used loosely, but they mean different things:

• Risk assessment — identifies hazards and evaluates the level of risk, with control measures. Use a risk assessment generator for structured output.
• Method statement — describes how the work will be done safely, step by step. A method statement generator helps structure this efficiently.
• RAMS — combines both into a single document. This is what most principal contractors expect on UK construction sites.

For a detailed comparison, see our guide on RAMS vs risk assessment.

Examples of when method statements are essential

• Excavation work — sequence of dig, support, services identification, backfill. See excavation method statement guidance.
• Scaffolding erection and dismantling — high-risk activity requiring detailed sequence. See scaffolding method statement guidance.
• Hot works — welding, cutting, or grinding near combustible materials
• Lifting operations — crane lifts, mechanical handling, heavy component installation
• Demolition — structural demolition, soft strip, asbestos removal
• Work near live services — gas, electricity, water, telecoms

Creating method statements efficiently

For firms that produce multiple method statements each month, writing from scratch is inefficient. A RAMS generator provides trade-specific templates with relevant steps and safety content already structured, so you're refining a relevant starting point rather than facing a blank page.

Understanding the legal requirements ensures your method statements form part of a structured safety management system. And knowing how to write a full RAMS document means your method statement integrates properly with the risk assessment.

Create your RAMS instantly with Riskora →

Summary

A method statement is a practical safety document that describes how work will be done safely, step by step. It's a standard requirement on UK construction sites and a core part of demonstrating compliance with CDM and MHSWR. Focus on specificity, clarity, and proportionality — and make sure every method statement is briefed to the people who'll actually be doing the work.

Create your RAMS instantly with Riskora →

Regulatory framework for method statements

A method statement is the documented "safe system of work" the law requires. The parent duty is Section 2 of the Health and Safety at Work etc. Act 1974, which makes provision of safe systems of work an absolute employer duty so far as is reasonably practicable. The risk-side companion is Regulation 3 of the Management of Health and Safety at Work Regulations 1999.

On construction sites the method statement also satisfies CDM 2015 Regulation 8 (contractor planning) and feeds the principal contractor's Construction Phase Plan under Regulation 12. High-risk activities pull in topic-specific duties: WAHR 2005 Regulation 6 for work at height, LOLER 1998 Regulation 8 for lifting plans, PUWER 1998 for work-equipment selection, and COSHH 2002 Regulation 7 for hazardous-substance control.

Permits-to-work for hot works, confined spaces or excavation sit on top of the method statement and are governed by HSG250 (Permit-to-work systems). HSE also publishes activity-specific operational standards — HSG47 for buried services, HSG33 for roofing, HSG185 for excavations and L143 (the asbestos ACOP) — which a competent method statement will reference where relevant.

Last reviewed: 1 May 2026 · Sources: HSWA 1974; MHSWR 1999; CDM 2015; WAHR 2005; LOLER 1998; PUWER 1998; COSHH 2002; HSE HSG250, HSG47, HSG33, HSG185, L143.