Construction Method Statement: Free Template, Examples, and How to Write One

A construction method statement is a written, step-by-step plan that sets out how a specific task will be carried out safely from start to finish. It describes the sequence of work, the people and plant involved, the hazards present, and the control measures that keep everyone safe. In UK practice a method statement is almost always paired with a risk assessment to form a RAMS document, and it is one of the documents a principal contractor will ask for before any subcontractor is allowed to start on site.

This guide explains exactly what a method statement should contain, gives you a worked UK example and a free method statement template, and shows how to turn a task that used to take half a day into a 15-minute job with AI.

What is a method statement and why does it matter

A method statement, sometimes called a safe system of work or a safe work method statement (SWMS), is the practical "how" that sits alongside the risk assessment's "what could go wrong". The risk assessment identifies hazards and rates their risk. The method statement explains, in plain sequence, how the work will actually be done so that those risks are controlled.

It matters for three reasons:

• Legal compliance. Under the Management of Health and Safety at Work Regulations 1999 and CDM 2015, employers and contractors must plan work and provide safe systems of work. A method statement is how you demonstrate that planning. For higher-risk activities it is effectively expected, not optional.
• Access to site. Principal contractors will not let a subcontractor start until acceptable RAMS are submitted and reviewed. No method statement, no access.
• Actually keeping people safe. A good method statement is briefed to the crew before work starts, so everyone knows the sequence, the hazards, and their role. That briefing is where the document earns its keep.

A method statement is not a generic form to be filed and forgotten. It must be specific to the task, the site, and the people doing the work.

Method statement vs risk assessment vs RAMS

These three terms are used loosely on site, so here is how they relate.

In short, the risk assessment is the analysis and the method statement is the plan. RAMS is simply the two documents combined into a single submission, which is why most contractors talk about "submitting their RAMS" rather than the two separately. If you need the assessment side, see the risk assessment template; to combine both, use the RAMS template.

What to include in a construction method statement

A complete method statement covers the same core sections every time, which is exactly why a template is so useful. Include:

• Project and task details. Project name and address, the specific task covered, the contractor carrying it out, and the dates.
• Scope of works. A clear definition of what this method statement covers, and just as importantly what it does not.
• Site details and access. How the work area is reached, exclusion zones, and any restrictions such as live services, occupied buildings, or shared access.
• Sequence of operations. The heart of the document: a numbered, step-by-step description of how the task is carried out from setup to completion and clean-down.
• Plant and equipment. Every item of plant, tools, and equipment, including inspection and certification requirements (for example LOLER thorough examination dates for lifting equipment).
• Materials and substances. Materials used, with any hazardous substances cross-referenced to their COSHH assessment.
• Personnel and competence. Who does the work, supervision arrangements, and the training, cards, or tickets required (for example CSCS, CPCS, IPAF, PASMA).
• PPE. The specific personal protective equipment required for the task.
• Hazards and control measures. The key hazards drawn from the risk assessment and the controls applied in the context of this method.
• Emergency arrangements. First aid, fire, rescue plans (for example a rescue plan for work at height), and emergency contacts.
• Sign-off and briefing record. Space for the author, the reviewer, and every operative to sign to confirm they have been briefed.

A worked method statement example

Here is a shortened example for a common UK task: installing a structural steel beam using a mobile crane.

Project: Maple Court refurbishment, Leeds Task: Installation of structural steel beam SB-04 at first-floor level Contractor: Northgate Steel Ltd Date: 18 May 2026

Scope: Off-load, position, and bolt down one 4.2m universal beam (approx 380kg) into pre-installed padstones at first-floor level, using a 35t mobile crane. Excludes temporary propping, which is covered by a separate method statement.

Sequence of operations:

1. Set up exclusion zone around the lift area using Heras fencing and signage. Brief all operatives and confirm the area is clear of the public and other trades.
2. Position the 35t mobile crane on the pre-checked hardstanding. Banksman confirms ground bearing and outrigger mats in place.
3. Appointed person confirms the lift plan, weather (lift suspended if wind exceeds 38mph or per the lift plan), and that all lifting accessories have in-date LOLER certificates.
4. Attach certified lifting accessories to the beam at marked lifting points. Slinger/signaller takes control of the lift.
5. Lift the beam, controlled by tag lines, to first-floor level. Two operatives wearing harnesses clipped to the MEWP receive and guide the beam onto the padstones.
6. Bolt the beam to the connection plates using the specified bolts to the engineer's torque. Do not release the crane until connections are confirmed secure.
7. Release lifting accessories, lower and clear the crane, and remove the exclusion zone once the area is safe.
8. Brief, inspect, and sign off. Record completion in the daily report.

Key hazards and controls: Suspended load (exclusion zone, tag lines, no one under the load), work at height (MEWP, harnesses, edge protection), crane stability (lift plan, ground checks, banksman), manual handling (mechanical lifting, minimal manual input).

Competence: Appointed person, crane operator (CPCS), slinger/signaller (CPCS), MEWP operators (IPAF). All hold valid CSCS cards.

Notice how the document ties together sequence, plant, people, and controls. A crew briefed on this knows exactly who does what and in what order, which is where most on-site incidents are actually prevented.

How to write a method statement in minutes with AI

Writing method statements from scratch is one of the most time-consuming admin jobs in construction, and it is why so many firms end up copy-pasting old documents that no longer match the task. That is exactly the habit that gets RAMS rejected by a principal contractor, or worse, briefed to a crew when it does not describe the real work.

AI fixes this by drafting a task-specific, properly structured method statement in minutes:

1. Give the AI the task and context. The activity, the site, the plant, the crew, and the key hazards. Bullet points are fine.
2. Use a structured prompt that asks for all the standard sections, written in a clear numbered sequence.
3. Review and make it site-specific. Check the AI has not invented plant or certificates, add anything site-specific it could not know, and confirm the hazards and controls match your risk assessment.
4. Brief, sign, and submit.

The AI handles the structure and the professional wording. You provide the facts, the site knowledge, and the judgement, which is the part that must never be automated away. Our draft method statement workflow gives you the exact prompt, and the full set of construction prompts is in the BuildCopilot Prompt Pack.

A word of caution: never submit an AI-drafted method statement without a competent person reviewing it. The document is a legal safety record and the responsibility for its accuracy stays with you, not the tool.

Common method statement mistakes

• Generic and not task-specific. A method statement copied from a different job, with the project name swapped, is the most common reason RAMS get rejected. It must describe the actual task on the actual site.
• No clear sequence. A wall of text instead of numbered steps. The crew cannot follow it and the briefing falls apart.
• Mismatch with the risk assessment. Hazards in the assessment that the method does not control, or controls in the method that were never assessed. They must line up.
• Out-of-date certificates and competence. Listing plant or accessories without checking LOLER dates, or naming operatives without confirming current cards and tickets.
• Never briefed. A method statement that sits in a file and is never read to the crew has no safety value at all. The briefing is the point.

Free method statement template

Use our free construction method statement template to standardise your safe systems of work across every task and project. Pair it with the AI workflow above and the matching RAMS template, and you get task-specific, professional method statements without losing half a day to admin.

Frequently asked questions

What is a method statement in construction?

A construction method statement is a written, step-by-step plan describing how a specific task will be carried out safely. It sets out the sequence of work, the plant and people involved, the hazards present, and the control measures applied. It is usually submitted alongside a risk assessment as a combined RAMS document.

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

A risk assessment identifies the hazards of a task, who could be harmed, and how the risk is rated and controlled. A method statement explains, step by step, how the task will actually be carried out safely. The risk assessment is the analysis; the method statement is the plan. Combined, they form RAMS.

Is a method statement a legal requirement in the UK?

There is no single regulation that names "method statement", but the Management of Health and Safety at Work Regulations 1999 and CDM 2015 require employers and contractors to plan work and provide safe systems of work. For higher-risk or complex tasks, a written method statement is the standard way to demonstrate that planning, and principal contractors almost always require one before granting site access.

Who writes the method statement?

The contractor carrying out the work is responsible for producing the method statement, usually prepared by a competent person such as a site manager, supervisor, or health and safety advisor. It should then be reviewed, and on site it is briefed to and signed by everyone doing the work.

How long should a method statement be?

There is no fixed length. A simple task might need one or two pages, while a complex lifting or demolition operation could run to many pages. The right length is whatever it takes to describe the task clearly and specifically. Padding a document with generic content does not make it better, and over-long statements are less likely to be read and briefed.

Can AI write a method statement?

AI can draft a clear, well-structured, task-specific method statement in minutes from your notes about the task, site, plant, and hazards. It handles the structure and wording, but a competent person must always review it for accuracy and make it site-specific before it is briefed or submitted. The legal responsibility for the document stays with you, not the AI.