What Must Be Included in a Method Statement

A method statement describes how a piece of work will be carried out safely. It's one of the most frequently requested documents in construction, maintenance, and specialist contracting — yet it's also one of the most commonly misunderstood. Many people confuse it with a risk assessment, or produce something so generic it could apply to any job on any site.

This guide sets out exactly what a method statement should include, why each section matters, and how to write one that actually serves its purpose.

What is a method statement?

A method statement is a written description of the safe system of work for a specific task. It sets out the sequence of operations, the resources needed, and the safety precautions that will be in place throughout. Think of it as the "how" document — while a risk assessment tells you what could go wrong, the method statement tells you how the work will be done to prevent it.

Method statements are commonly combined with risk assessments to form a RAMS document. However, they can also be produced as standalone documents, particularly where the client or principal contractor manages risk assessments centrally.

Is a method statement a legal requirement?

There's no specific UK regulation that says "you must produce a method statement." However, the duty to plan and document safe systems of work is well established under the Health and Safety at Work Act 1974 and the CDM Regulations 2015. In practice, method statements are a standard expectation on construction sites and for most high-risk activities. Failing to produce one when asked will almost certainly prevent you from starting work.

For more on the legal framework around workplace documentation, see our guide to risk assessment legal requirements in the UK.

What a method statement must include

1. Project and site information

Start with the basics: site name and address, client, principal contractor, your company name, the date of the document, and a reference number if you use one. This seems obvious, but missing project details are a common reason for documents being sent back.

2. Scope of works

A clear, concise description of the work being carried out. Be specific about the location within the site, the extent of the work, and any boundaries or exclusions. "Installing drainage" is too vague. "Excavation and installation of 150mm foul drainage from manhole MH4 to MH7, including backfill and reinstatement" gives the reader confidence that you understand the job.

3. Sequence of operations

This is the core of the method statement. List every step of the work in the order it will happen. Each step should be clear enough for someone unfamiliar with the task to understand the process. Include preparation, execution, and completion/handover stages.

For each step, consider: what's being done, who's doing it, what equipment is being used, and what safety measures apply.

4. Plant, equipment, and materials

List the machinery, tools, and materials required. Include any inspection or certification requirements (e.g. LOLER inspections for lifting equipment, PAT testing for electrical tools). Don't assume the reader knows what equipment you'll use — state it.

5. Personnel and responsibilities

Identify who is responsible for what. This includes the site supervisor, operatives, and any specialists (e.g. banksmen, fire watchers, confined space attendants). Name roles clearly and, where appropriate, state the competence or training requirements.

6. Safety measures and control arrangements

Describe the safety controls for each significant hazard. This should align with your risk assessment. Include PPE requirements, exclusion zones, traffic management, permits to work, and any environmental controls (dust suppression, noise barriers, etc.).

7. Emergency procedures

What happens if something goes wrong? Cover first aid arrangements, fire procedures, and any task-specific emergency plans. For work at height, include a rescue plan. For excavations, include procedures for trench collapse. This section is often missing from method statements, and its absence is a red flag for reviewers.

8. Sign-off and review

Record who prepared the method statement, who reviewed and approved it, and when it should next be reviewed. A method statement without a review date suggests it was written once and never updated — which undermines its credibility.

Common problems with method statements

• Too generic — could apply to any job on any site. If you can swap the site name and the document still makes sense, it's not specific enough.
• Steps aren't sequential — a method statement should read like a chronological plan, not a random list of activities.
• No link to the risk assessment — the method statement should reference the hazards identified in the risk assessment and explain how each step manages those risks.
• Written by someone who won't do the work — method statements are most effective when the people carrying out the work are involved in writing them.

Writing method statements efficiently

If you write method statements regularly, doing each one from a blank document is slow and inconsistent. A method statement generator provides a structured framework where you define the sequence of work, link steps to hazards, and produce a professional document in a fraction of the time.

For construction-specific work, using a tool that includes construction RAMS templates ensures your method statements align with the hazard profiles typical for your trade. And if you need the risk assessment component too, a RAMS generator handles both in a single workflow.

Understanding the difference between these documents is important — our guide on RAMS vs risk assessment explains when you need each one.

Summary

A method statement must describe the safe system of work in enough detail for someone to follow it. It should be specific to the site, sequential in structure, and linked to the accompanying risk assessment. Skip the generic padding, focus on practical detail, and review it before every new project.

Ready to build yours? Create your RAMS instantly with Riskora →

The regulations behind the required content

Each item on a method statement checklist maps to a specific legal duty. The "scope and sequence" section evidences the planning duty in CDM 2015 Regulation 8. The "hazards and controls" section discharges Regulation 3 of MHSWR 1999. The "PPE" section closes off the duties in the Personal Protective Equipment at Work Regulations 1992 (as updated 2022). "Plant and equipment" maps to PUWER 1998 Regulation 4 (suitability) and, for lifting, LOLER 1998 Regulation 8 (lift planning by a competent person).

"Substances used" maps to COSHH 2002 Regulation 6 (risk assessment) and Regulation 7 (control). "Emergency arrangements" satisfy MHSWR 1999 Regulation 8 and any incident reporting duty under RIDDOR 2013. "Competence and training" reflects MHSWR 1999 Regulation 13.

HSE's operational guidance documents extend these duties into practical detail: HSG150 (construction health and safety), HSG47 (underground services), HSG258 (airborne contaminants), INDG163 (5 steps to risk assessment) and the L23 ACOP on manual handling. A method statement that names the relevant guidance against each section is far harder to reject in review.

Last reviewed: 1 May 2026 · Sources: HSWA 1974; MHSWR 1999; CDM 2015; PUWER 1998; LOLER 1998; COSHH 2002; PPE at Work Regulations 1992; RIDDOR 2013; HSE HSG150, HSG47, HSG258, INDG163, L23.