How to Write a Construction Method Statement (With Examples)

If you work in UK construction, you have almost certainly been asked to produce a method statement. Whether it is a principal contractor requiring RAMS before you start on site, or a client who wants to understand how you plan to carry out the work, method statements are part of everyday life for contractors. The problem is that too many method statements are generic documents copied from the internet. This guide shows you how to write one that actually describes your work, protects your team, and satisfies the people who need to approve it.

What Is a Method Statement?

A method statement is a document that describes how a particular task or activity will be carried out. It sets out the sequence of work, the resources needed, the hazards involved, and the control measures that will keep people safe.

Think of it as a recipe for construction work. Just as a recipe lists ingredients, equipment, and step-by-step instructions, a method statement lists materials, plant, PPE, and the sequence of operations. Anyone reading it should understand what is going to happen, in what order, and how risks are being managed.

Method statements are usually paired with risk assessments to form what the industry calls RAMS (Risk Assessment and Method Statement). The risk assessment identifies the hazards and evaluates the risks. The method statement describes how the work will be done to control those risks.

When Is a Method Statement Required?

There is no specific UK law that says "you must produce a method statement for every task." But in practice, they are required in most situations.

• Principal contractor requirement. On most managed sites, the principal contractor will require RAMS from every subcontractor before they are allowed to start work. No RAMS, no start. This is standard practice
• High-risk activities. Any work involving significant risk should have a method statement. This includes working at height, excavation, demolition, hot works, confined space entry, lifting operations, and work near services
• CDM Regulations 2015. The regulations require contractors to plan, manage, and monitor construction work. A method statement is the most practical way to demonstrate that planning has taken place
• Client or designer request. Some clients and designers require method statements as part of the tender or pre-start process, even on smaller projects
• Permit-to-work systems. Activities controlled by permits (hot works, confined spaces, electrical isolation) typically require an approved method statement as part of the permit process

Key Sections Every Method Statement Needs

A good method statement does not need to be long, but it does need to cover certain ground. Here are the sections that should appear in every one.

1. Project and Task Details

• Project name and address
• Description of the specific task or activity
• Location on site where the work will take place
• Expected start date and duration
• Name of the person responsible for supervising the work

2. Scope of Works

A clear description of what the work involves. Not a vague overview. Spell out exactly what is being done. "Install first-fix plumbing to ground floor extension including soil stack, waste pipes, and hot and cold supply runs" is useful. "Plumbing works" is not.

3. Resources Required

• Personnel - how many people, what qualifications or competencies they need (CSCS cards, IPAF, PASMA, etc.)
• Plant and equipment - scaffold, MEWP, excavator, power tools, etc.
• Materials - what is being used and any specific handling requirements
• PPE - what personal protective equipment is required for this task

4. Sequence of Operations

This is the core of the method statement. Write out the work in a logical, step-by-step sequence. Number each step. Be specific enough that someone unfamiliar with the work could follow it, but do not over-complicate things.

For each step, note any hazards and the control measures in place. This links the method statement directly to the risk assessment.

5. Hazards and Control Measures

List the significant hazards associated with the work and how each one will be controlled. This should cross-reference your risk assessment. Common construction hazards include:

• Working at height - edge protection, scaffolding, harnesses
• Manual handling - mechanical aids, team lifts, delivery to point of use
• Electricity - isolation, permit to work, voltage detection
• Dust and noise - extraction, damping down, RPE, hearing protection
• Falling objects - exclusion zones, toe boards, netting
• Underground services - CAT scanning, hand digging within proximity

6. Emergency Procedures

What happens if something goes wrong? Note the location of first aid equipment, the nearest hospital, emergency contact numbers, and the procedure for reporting accidents. For high-risk activities, include specific rescue plans.

7. Environmental Considerations

How will you manage waste, prevent pollution, control dust, and minimise noise disturbance? This is increasingly important and often a specific requirement from principal contractors and local authorities.

Example: Flat Roof Replacement Method Statement

Here is a shortened example to show the level of detail expected. A real method statement would expand on each section.

That is the kind of detail that demonstrates real planning. Compare it to a generic method statement that says "work to be carried out safely in accordance with all regulations." One is useful. The other is wallpaper.

Common Mistakes

Copying Generic Templates Without Editing

The biggest sin in method statement writing. Downloading a template from the internet and submitting it with your company name on top. If the method statement describes work that does not match what you are actually doing, it is worse than having no method statement at all. It shows you have not thought about the task.

Being Too Vague

"Appropriate PPE will be worn" is meaningless. Which PPE? Safety boots, hard hat, gloves, goggles, harness? Specify what is needed for the actual task. "All operatives to wear steel toe-cap boots, hard hats, and hi-vis vests. RPE (P3 mask) required during demolition phase" gives clear instruction.

Writing It After the Work Is Done

A method statement written after the work has been completed is a waste of everyone's time. The whole point is to plan the work before it starts. If an HSE inspector finds that your method statement was created after the activity, it undermines your entire safety management system.

Not Briefing the Workers

A method statement that sits in the site office but has never been read by the people doing the work is useless. Brief every operative on the content before work starts. Get them to sign that they have understood it. This is usually done as part of the task briefing or toolbox talk.

Not Reviewing When Things Change

If site conditions change, or the work is different from what was planned, the method statement needs updating. Discovering asbestos during a strip-out means the existing method statement is no longer valid. Stop work, review, and revise.

CDM Regulations and Method Statements

The Construction (Design and Management) Regulations 2015 are the primary health and safety regulations for UK construction. While they do not specifically mention method statements by name, they create obligations that method statements help fulfil.

Key CDM duties relevant to method statements:

• Regulation 13 - Contractors must plan, manage, and monitor construction work to ensure it is carried out safely. A method statement is the planning document
• Regulation 15 - The construction phase plan must set out arrangements for managing significant risks. Method statements for high-risk tasks feed into this plan
• Regulation 8 - Duty holders must have the skills, knowledge, and experience to carry out their work safely. Method statements demonstrate that competent planning has taken place

In practice, if the HSE investigates an incident on your site, one of the first things they will ask for is the RAMS. If you have a well-written, specific method statement that was briefed to the workers, it shows your safety management system is working. If you have nothing, or a generic template, it shows the opposite.

A method statement does not need to be a work of literature. It needs to be specific, practical, and understood by the people doing the work. That is all.

Frequently Asked Questions

What is the difference between a method statement and a risk assessment?

A risk assessment identifies hazards and evaluates the risks associated with an activity. A method statement describes the step-by-step procedure for carrying out the work safely. They work together and are often bundled as RAMS (Risk Assessment and Method Statement). The risk assessment identifies what could go wrong. The method statement explains how you will prevent it.

Are method statements a legal requirement in UK construction?

There is no specific law that says you must produce a method statement. However, the CDM Regulations 2015 require contractors to plan, manage, and monitor work to ensure it is carried out safely. A method statement is the most common and practical way to demonstrate compliance. Many principal contractors and clients also require them contractually before work begins on site.

Who should write the method statement?

The person or company carrying out the work should write the method statement. They know the activity best and understand the practical steps involved. On larger projects, a safety advisor or competent person may help with the format and ensure nothing is missed, but the technical content should come from the people doing the work.

How long should a method statement be?

As long as it needs to be and no longer. A simple task like installing a door might need one or two pages. A complex operation like a steel frame erection might need ten pages with detailed sequence drawings. The test is whether someone reading it could understand what is being done, the risks involved, and how those risks are controlled. If it is too short, it lacks detail. If it is too long, nobody will read it.

Final Thoughts

A method statement is not paperwork for the sake of it. It is your plan for getting the work done safely and efficiently. When written properly, it protects your workers, satisfies your clients, and gives you a solid defence if anything goes wrong.

Write it before the work starts. Make it specific to the actual task. Brief everyone involved. And review it when things change. That is all there is to it.

If you are tired of writing the same documents from scratch for every job, start building a library of your own method statements. Each new one gets easier because you are adapting a real document from a real project, not starting from a blank page.