How to Write a Method Statement for Construction (Template + Guide)

What Is a Method Statement?

A method statement is a document that describes how a specific task or activity will be carried out safely on a construction site. It is sometimes called a safe system of work (SSOW) or a method of work statement. The purpose is straightforward: to make sure everyone involved in a task understands the sequence of operations, the hazards involved, and the control measures in place before work starts.

Method statements are not a legal requirement in themselves under UK health and safety law, but they are a practical way of meeting your duties under the Health and Safety at Work etc. Act 1974, the Management of Health and Safety at Work Regulations 1999, and the Construction (Design and Management) Regulations 2015 (CDM 2015). In practice, almost every principal contractor and client will require method statements before allowing work to proceed.

A good method statement is specific, practical, and written for the people who will actually do the work. It is not a generic document pulled from a template library without modification. The moment your method statement reads like it could apply to any site in the country, it has failed its purpose.

Who Needs a Method Statement?

Any contractor or subcontractor carrying out construction work should be able to produce a method statement when asked. In practice, the following situations always require one:

• CDM-notifiable projects: Any project lasting longer than 30 working days with more than 20 workers simultaneously, or exceeding 500 person-days. The principal contractor must ensure method statements are in place for high-risk activities.
• High-risk activities: Working at height, hot works, confined spaces, excavations, demolition, asbestos removal, and lifting operations. These always need documented safe systems of work.
• Client or main contractor requirements: Most tier-1 and tier-2 contractors require method statements from every subcontractor as a condition of working on site, regardless of project size.
• Permit-to-work systems: Many sites operate permit systems where a method statement must be approved before a permit is issued for the work to start.

Even on smaller domestic projects, having a written method statement demonstrates professionalism and protects you if something goes wrong. It shows you thought about the risks before starting work.

Required Sections of a Method Statement

There is no single legally mandated format for a method statement, but the following sections are considered standard across the UK construction industry:

1. Project and Task Information

State the project name, site address, client name, principal contractor (if applicable), and the specific task being described. Include the date of the method statement and the revision number. Be precise about what work is covered — "plastering" is too vague; "application of two-coat gypsum plaster to internal block walls, ground floor, Building A" tells the reader exactly what this document covers.

2. Scope of Works

Describe what the task involves, where it will take place, and the expected duration. Include any constraints such as working hours, access restrictions, or sequencing requirements with other trades.

3. Personnel and Responsibilities

List the roles involved, including the site supervisor, operatives, and any specialist trades. State who is responsible for what, including who has authority to stop work if conditions change. Include competency requirements such as CSCS cards, IPAF licences, or PASMA training.

4. Plant, Equipment and Materials

List every piece of equipment, tool, and material that will be used. Include PPE requirements specific to this task. If equipment needs inspection or certification (scaffolding, MEWPs, lifting equipment), state who is responsible for checking it and the inspection frequency.

5. Step-by-Step Sequence of Operations

This is the core of the method statement. Describe the work in chronological order, step by step. Each step should be clear enough that someone unfamiliar with the task could follow the sequence. Include set-up, the main work activities, and demobilisation. Where hazards arise at specific steps, note the control measures immediately alongside that step.

6. Risk Assessment Reference

Method statements and risk assessments (RAMS) go hand in hand. Reference the specific risk assessment that covers this task. The method statement describes how you will do the work; the risk assessment identifies the hazards and how you will control them. Together, they form your RAMS package.

7. Emergency Procedures

State what to do if something goes wrong. Include first aid arrangements, emergency contact numbers, evacuation procedures relevant to the task location, and any specific emergency protocols (for example, rescue plans for work at height or confined space entry).

8. Environmental Considerations

Address waste management, noise and dust control, protection of watercourses, and any ecological constraints. This is increasingly important as clients and regulators focus on environmental compliance.

Step-by-Step Writing Guide

Writing a method statement does not need to be complicated. Follow this practical process:

• Step 1: Visit the site or review site information. You cannot write a credible method statement from your office without understanding the site conditions. Look at access, ground conditions, overhead hazards, adjacent activities, and any site-specific rules.
• Step 2: Identify the task and break it into steps. Walk through the task mentally from start to finish. What happens first? What comes next? Where are the handover points with other trades?
• Step 3: Identify hazards at each step. For each step, ask what could go wrong. This links directly to your risk assessment.
• Step 4: Define control measures. For each hazard, state what you will do to eliminate or reduce the risk. Follow the hierarchy of controls: eliminate, substitute, engineer, administrate, PPE.
• Step 5: Write it in plain language. The people reading this document are tradespeople, not lawyers. Use short sentences, active voice, and avoid jargon. If a step says "ensure adequate ventilation," specify what that means: "open all windows in the room and position the 110V extraction fan at the doorway."
• Step 6: Review with the team. Before submitting, walk through the method statement with the people who will do the work. They will spot gaps you missed.

Common Mistakes to Avoid

• Using generic templates without customising them: A method statement for "working at height" that does not mention the specific building, equipment, or conditions on your site is worthless. Every document must be site-specific.
• Writing for the filing cabinet, not the workforce: If your operatives have never read the method statement, it serves no practical purpose. Keep it concise and brief them on it before work starts.
• Forgetting to update it: Conditions change. If the scope of work changes, the access arrangements change, or you discover unexpected hazards, the method statement must be revised and reissued.
• Separating it from the risk assessment: RAMS should be read together. Cross-reference them clearly so the reader can move between the two documents.
• No sign-off process: The method statement should be signed by the person who wrote it, approved by the site manager or principal contractor, and acknowledged by every operative who will carry out the work.

How MyQS Generates Method Statements

Writing method statements from scratch for every task on every project is one of the biggest administrative burdens in construction. MyQS automates this process by generating CDM 2015-compliant method statements tailored to your specific project. You provide the project details and scope of work, and the system produces a professional document with all the required sections, specific to your task and site conditions.

The generated documents include proper risk identification, control measures aligned to the hierarchy of controls, PPE requirements, and emergency procedures. You review and adjust as needed, then download as a PDF ready for submission to the principal contractor or client. What used to take hours takes minutes.

Frequently Asked Questions

Do I need a method statement for every single task on site?

Not necessarily. Method statements are most important for high-risk activities and tasks where the sequence of operations is critical for safety. Low-risk routine tasks may be covered by general site rules and toolbox talks. However, many principal contractors require them for all subcontractor activities regardless of risk level, so check the site requirements before starting work.

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

A risk assessment identifies hazards and evaluates the level of risk. A method statement describes the step-by-step process for carrying out the work safely. They are complementary documents, usually bundled together as RAMS (Risk Assessment and Method Statement). The risk assessment says what could go wrong and how likely it is; the method statement says what you will do to prevent it.

Can a method statement be used as evidence in a legal dispute?

Yes. If there is an accident or HSE investigation, your method statement will be examined as evidence of whether you planned the work properly. A well-written, site-specific method statement demonstrates that you took reasonable steps to ensure safety. A generic or missing method statement does the opposite. This is why quality matters more than quantity.