Method Statement Construction: How to Write One That Actually Gets Read

Every site manager knows the drill. A subcontractor turns up, you ask for their method statement, and they hand over a 40-page document that was clearly written for a different project three years ago with the names changed. Nobody reads it. Nobody follows it. And everybody pretends that counts as safe planning.

A method statement should be one of the most useful documents on a construction project. When written properly, it tells the workforce exactly how to carry out a task safely, step by step. The problem is that most method statements are written to tick a box, not to protect people.

This guide covers how to write a construction method statement that is practical, compliant, and short enough that someone will actually read it before starting work.

What Is a Method Statement?

A method statement is a document that describes how a specific piece of work will be carried out safely. It covers the sequence of operations, the equipment and materials required, the hazards involved, and the control measures in place. In UK construction, method statements are typically required alongside risk assessments, and together they form what is commonly known as RAMS (Risk Assessment and Method Statement).

The legal basis comes from the Management of Health and Safety at Work Regulations 1999 and the CDM 2015 regulations. While CDM 2015 does not specifically mention method statements by name, it requires that construction work is planned, managed, and monitored to ensure it is carried out safely. Method statements are the standard industry tool for meeting that duty.

Method Statement vs Risk Assessment

These two documents work together but serve different purposes. A risk assessment identifies what could go wrong and how likely it is. A method statement explains how you will do the work to prevent those things from going wrong. The risk assessment is the "what if." The method statement is the "how to."

What Every Method Statement Should Include

A well-structured method statement for a construction project follows a logical sequence. Here is what to cover.

Project Information

The project name, site address, client name, and principal contractor. Also include the specific task or operation this method statement covers. "Excavation and installation of foul drainage to Plot 7" is specific. "Groundworks" is not.

Task Description

A clear summary of what the work involves. Keep it to one or two paragraphs. Anyone reading this section should immediately understand the scope and scale of the task.

Sequence of Operations

This is the core of the method statement. Break the work down into numbered steps, in the order they will be carried out. Be specific enough that someone unfamiliar with the task could follow the sequence and understand what happens at each stage.

For example, a drainage installation might be broken down as follows. Step 1: Review service plans and carry out CAT and Genny scan of excavation area. Step 2: Set out trench line using spray paint and profile boards. Step 3: Install trench support system as excavation progresses. Step 4: Excavate to formation level using tracked excavator with toothed bucket. And so on through bedding, pipe laying, testing, backfill, and reinstatement.

Plant and Equipment

List every piece of plant and equipment required. Include the size and type where relevant. "3 tonne tracked excavator" is better than "digger." This ensures the right equipment is available and operators hold the correct qualifications.

Materials

List the key materials and specify any particular requirements. If COSHH substances are involved (adhesives, sealants, cleaning chemicals), reference the relevant COSHH data sheets.

Personnel and Competence

How many people are needed and what qualifications or competence do they require? An excavation task might need a CPCS-qualified operator, a banksman, and two ground workers with appropriate CSCS cards. State these requirements clearly.

Hazards and Control Measures

While the risk assessment handles this in detail, the method statement should reference the key hazards and controls at the appropriate point in the sequence. When Step 3 mentions installing trench support, it should reference the risk of trench collapse and confirm that the support system will be inspected before anyone enters the excavation.

Emergency Procedures

What happens if something goes wrong? Who do you contact? Where is the nearest hospital? Where is the first aid kit? This section does not need to be long, but it needs to be there.

Common Mistakes That Make Method Statements Useless

Copy and Paste From Previous Projects

The single biggest problem. A method statement written for a different site, different conditions, and different risks is worse than no method statement at all. It creates a false sense of compliance while failing to address the actual hazards on this project.

Too Long

If your method statement for installing a door frame is 25 pages, nobody will read it. Keep it proportionate to the risk and complexity of the task. A simple task needs a simple method statement. Save the detail for high-risk activities like working at height, confined spaces, or demolition.

Too Generic

"Appropriate PPE will be worn" is not a control measure. "All operatives to wear hard hats, safety boots, hi-vis vests, and cut-resistant gloves. Eye protection required during cutting operations" is a control measure. Be specific.

Never Reviewed

A method statement is a living document. If site conditions change, the method should change too. Reviewing and updating method statements when circumstances shift is not optional. It is a legal duty.

How to Create Method Statements Faster

Writing method statements is time-consuming, and for busy site managers, that time comes at a premium. The traditional approach involves opening a Word template, copying sections from previous projects, adapting them to the current task, and spending an hour formatting the result.

Site Manager AI offers a faster approach. You describe the task, and the AI generates a site-specific method statement that covers all the required sections. It is built for UK construction, references CDM 2015 requirements, and produces print-ready documents in under a minute.

The output is not a generic template. It is tailored to the specific task, site conditions, and hazards you describe. You review it, make any adjustments needed, and it is ready for the site team.

Make Your RAMS Work for You

A good method statement saves lives. A bad one is just paper. Take the time to write method statements that are specific, practical, and short enough that someone standing in the rain will actually read them before starting work.

If you are spending hours writing RAMS for every task on site, try Site Manager AI. Generate professional, CDM-compliant method statements and risk assessments in 60 seconds. Built for UK construction site managers.