How to Write a Construction Method Statement

A method statement is one of the most requested documents on any UK construction site, yet many are poorly written, overly generic, or simply copied from the last project without being adapted. This guide walks you through how to write a construction method statement that is actually useful, site-specific, and meets the expectations of principal contractors, clients, and the HSE.

What Is a Method Statement?

A method statement, sometimes called a safe system of work or a safe method of work statement, is a document that sets out how a particular task or activity will be carried out on site. It describes the sequence of work, the equipment and materials required, the hazards involved, and the specific control measures that will be in place to manage those hazards.

Together with a risk assessment, a method statement forms what the industry refers to as RAMS (Risk Assessments and Method Statements). While the risk assessment identifies what could go wrong and rates the level of risk, the method statement explains how the work will be done to prevent those things from happening.

A well-written method statement serves several purposes:

• Communication - it tells the workforce exactly what is expected, in what order, and what precautions to take
• Compliance - it demonstrates to clients, principal contractors, and the HSE that you have planned the work properly
• Competence - it shows that you understand the risks and have thought through how to manage them
• Record - it provides a documented record of your intended approach, which is important if anything goes wrong

When Do You Need One?

There is no legislation that specifically requires a method statement by name. However, the Management of Health and Safety at Work Regulations 1999 require employers to plan and organise work to ensure it is carried out safely. The CDM 2015 regulations require principal contractors to plan, manage, and monitor the construction phase, which in practice means reviewing and approving method statements from every subcontractor on site.

In reality, you will need a method statement for virtually any activity on a UK construction site. Principal contractors routinely require them before allowing work to start. Common activities that always need a method statement include:

• Demolition and structural alterations
• Excavation and groundworks
• Working at height, including scaffolding erection and use
• Lifting operations with cranes or hoists
• Hot works (welding, cutting, grinding)
• Electrical installations and connections
• Concrete pours and formwork
• Asbestos removal or work near asbestos-containing materials
• Confined space entry
• Any task involving hazardous substances

Even for more routine tasks, having a method statement shows professionalism and helps ensure nothing is overlooked.

Structure of a Method Statement

There is no legally prescribed format for a method statement, but the following structure is widely accepted across the UK construction industry and will meet the expectations of most principal contractors and clients:

1. Project details - site name, address, project reference, client name
2. Task description - clear description of the specific work being covered
3. Location - where on site the work will take place
4. Personnel - who will carry out the work, their roles, and required competencies
5. Plant and equipment - what tools, machinery, and equipment will be used
6. Materials - what materials are needed and any COSHH requirements
7. Sequence of operations - step-by-step description of how the work will proceed
8. Hazards and control measures - identified risks and how each will be managed
9. PPE requirements - specific protective equipment for this task
10. Emergency procedures - what to do if something goes wrong
11. Environmental considerations - noise, dust, waste, and any environmental controls
12. Sign-off - prepared by, reviewed by, approved by, with dates

Writing Each Section Step by Step

Project Details

Start with the basics. Include the site name, address, project number if applicable, client name, and the principal contractor. Also include your own company name, the name and contact details of the person who prepared the method statement, and the date it was produced. This section should also state the revision number. Method statements should be living documents that get updated as circumstances change.

Task Description

Be specific. Do not write "groundworks" when you mean "excavation of strip foundations to a depth of 1.2 metres in clay soil adjacent to a live highway." The more precise your description, the more useful the document becomes. A vague task description is a red flag to any reviewer that the rest of the document might be equally generic.

Sequence of Operations

This is the core of the method statement and where most people get it wrong. You need to describe the work in a logical, chronological sequence that someone could follow on site. Think of it like a recipe. Each step should include:

• What will be done at this stage
• Who will do it (by role, not necessarily by name)
• What equipment or materials are needed for this step
• What hazards exist at this particular stage
• What control measures will be in place

For example, if you are writing a method statement for installing roof trusses, your sequence might look like this:

1. Delivery and offloading of trusses using HIAB - banksman to guide driver, exclusion zone around offload area, trusses stored on bearers on level ground
2. Erection of scaffolding to eaves height - by competent scaffolders, to SG4:15 standard, scaffold inspected before use
3. First truss lifted by crane and positioned - crane operator briefed on lift plan, tag lines used, no one under suspended load
4. Temporary bracing installed to first truss - operatives working from scaffold platform, bracing secured before releasing crane
5. Subsequent trusses lifted and fixed at centres - process repeated, permanent bracing installed progressively

This level of detail shows that you have actually thought about how the work will be done, rather than simply listing generic safety phrases.

Hazards and Control Measures

List the specific hazards associated with this task and the controls you will implement. Avoid generic statements like "all personnel will be briefed on risks." Instead, be specific:

• Working at height - edge protection on scaffold, harness and lanyard when installing first truss before edge protection complete
• Falling materials - exclusion zone at ground level, hard hats mandatory within crane radius, toe boards on all scaffold platforms
• Manual handling - two-person lift for bracing members, mechanical handling for trusses over 25kg
• Weather - work suspended in winds exceeding 23 mph (measured at height), trusses not erected in wet conditions that affect grip

PPE Requirements

List the PPE specific to this task, not just the generic site PPE. If the work involves grinding, specify eye protection type (not just "safety glasses"). If there is noise exposure, specify the hearing protection rating required. This section should be practical and specific.

Emergency Procedures

Include what to do in the event of an accident, near miss, or environmental incident. Reference the site emergency plan, and include the location of the nearest first aid kit, the name of the appointed first aider, and the muster point. For high-risk activities like confined space entry, include a rescue plan.

Common Mistakes to Avoid

Having reviewed hundreds of method statements over the years, these are the errors that come up time and time again:

• Copying from the last project - if your method statement mentions a site address from two years ago, it is immediately obvious you have not adapted it. Every method statement must be site-specific.
• Being too generic - phrases like "work will be carried out safely" or "all relevant regulations will be followed" add nothing. Be specific about which regulations and what measures you will take.
• Not involving the workforce - the people who will actually do the work should have input into the method statement. They know the practical realities that someone in the office might overlook.
• Writing it after the work is done - a method statement produced retrospectively is worthless. It should be prepared, reviewed, and communicated before work starts.
• Making it too long - a 40-page method statement for installing a door is not more thorough; it is less likely to be read. Be concise. Include what is needed, no more.
• Forgetting to update it - if conditions change, the method statement should be revised. A new hazard, a change in sequence, or different equipment all warrant an update.

Getting Sign-Off and Communicating to the Team

A method statement is only useful if three things happen:

1. It is reviewed and approved by the principal contractor or site manager before work begins. This is not a rubber-stamping exercise. The reviewer should check that it is site-specific, adequately addresses the risks, and is compatible with other work happening on site.
2. It is communicated to the workforce through a briefing or toolbox talk. Every person involved in the task should understand the method statement and have the opportunity to ask questions or raise concerns.
3. It is available on site for reference. Keep a copy in the site office and ideally at the work location. If someone needs to check a detail during the work, they should be able to find the document quickly.

Document the briefing with a sign-on sheet showing the names, signatures, and dates of everyone who was briefed. This is important evidence that the method statement was actually communicated, not just filed away.

Moving to Digital Method Statements

Paper-based method statements are increasingly being replaced by digital systems that allow you to create, share, and manage RAMS more efficiently. The advantages of going digital include:

• Instant distribution - send the method statement to every relevant person immediately, with read receipts
• Version control - always know which version is current, with a full audit trail of changes
• Templates - create reusable templates for common tasks while still adapting them for each site
• Storage - all documents in one place, searchable, and accessible from any device
• Sign-off tracking - see who has reviewed and acknowledged the method statement without chasing paper

Practical Example: Putting It All Together

Let us say you need to write a method statement for installing drainage pipework in a trench. Here is how you would approach each key section:

Task: Installation of 150mm diameter uPVC drainage pipe in trench, depth 1.5m, length 30m, in clay soil.

Sequence:

1. Mark out trench line using setting-out data from engineer's drawings. Check for underground services using CAT scanner and service drawings. Hand-dig trial holes at service crossing points.
2. Excavate trench using 8-tonne tracked excavator. Banksman to guide excavator. Spoil placed minimum 1m from trench edge. No pedestrian access within swing radius of machine.
3. Install trench support (hydraulic props) once trench exceeds 1.2m depth. No entry to unsupported trench. Props installed from ground level using proprietary equipment.
4. Lay pipe bedding (pea gravel) to 100mm depth. Check levels with laser. Compact bedding using plate compactor lowered into trench.
5. Lower pipe sections into trench. No manual handling in trench for pipes over 6m. Use excavator with pipe hooks for longer runs.
6. Make joints, test for falls and alignment. Inspect each joint before backfilling.
7. Backfill in 150mm layers, compacting each layer. Remove trench support progressively from bottom up.

Notice how each step includes the hazard controls built into the description. This is far more useful than a separate generic list of hazards.

Final Thoughts

A good method statement does not need to be long. It needs to be specific, practical, and understood by everyone doing the work. Write it before the work starts. Involve the people who will be on the tools. Review it whenever conditions change. And make sure it is actually communicated, not just filed.

If you are spending hours on paperwork for every job, consider whether a digital system could streamline the process. The goal is not to produce documents for the sake of it. The goal is to plan work properly so everyone goes home safe at the end of the day.