A method statement is a document that describes how a specific task will be carried out safely, step by step, using the controls identified in the risk assessment. It tells the people doing the work what to do, in what order, with what equipment and under whose supervision. It is a practical working document, not a formality, and it only does its job if the people on the job have read it, understood it and followed it.
Key takeaways
- A method statement sets out how a task will be done safely, in sequence, while a risk assessment identifies the hazards and decides what controls are needed.
- A good method statement is specific to the task, the location and the people involved, not a generic template with the details left blank.
- It should cover the task, the sequence of work, the hazards, the controls, the equipment, the people and their roles, and what to do if something changes.
- Everyone doing the work should be briefed on the method statement, and if the work cannot be done as written, they should stop and ask.
- Method statements are often combined with risk assessments and called RAMS, but the two documents do different jobs.
What a method statement is for
Construction work involves many tasks where the order of operations matters: lifting a prefabricated unit into place, breaking out a floor slab, working next to a live road or installing roof edge protection. A method statement captures the plan so that everyone involved, from the supervisor to the newest operative, knows how the job is meant to go.
It answers practical questions. What is the task? Who is doing it and who is in charge? What equipment is needed? What must be in place before work starts? What happens at each stage? What do you do if the plan breaks down?
The related risk assessment answers a different question: what could go wrong and how will the risks be controlled? You can find the full explanation in our risk assessment guide. The method statement then puts the controls from that assessment into the sequence of the job. If the two documents contradict each other, that is a warning sign, and the work should not start until someone competent has resolved it.
How it fits with the law
The Construction (Design and Management) Regulations 2015, usually called CDM 2015, apply to construction projects in Great Britain. They set out duties for clients, designers, principal contractors, contractors and workers, with the aim of planning, managing and monitoring work so that risks are controlled from the start of a project through to its completion. In general terms, a principal contractor has to plan, manage and monitor the construction phase, and contractors must plan, manage and monitor their own work so that it is carried out without risks to health and safety.
Method statements are one common way of showing that this planning has happened for a particular task. The regulations are about the duties and outcomes, so what form the paperwork should take, and when a method statement is expected, is often set by the principal contractor, the client or the contract. If you are not sure what your site requires, ask your supervisor or read the regulations and HSE's construction guidance for the exact duties. This article only describes the general approach and does not replace those documents.
HSE's construction safety topics pages are a good place to look for guidance on specific activities, such as work at height, excavations, and lifting. The right controls for your method statement should come from that kind of guidance and from the risk assessment, rather than from a template.
What a good method statement contains
Formats vary between companies, but a useful method statement usually includes the following sections.
Task description and scope
Say clearly what the work is and where it takes place. Include the start point and the finish point, and name anything that is outside the scope, so that nobody assumes extra work is covered.
Sequence of work
List the steps in the order they will be done. For a task such as installing a temporary works support, this might include setting out, delivery, positioning, checks before loading and checks after. Keep each step short and specific so a worker can follow it without interpretation.
Hazards and controls
Summarise the main hazards and the controls from the risk assessment, and place them at the stage of the work where they apply. If a lifting operation needs an exclusion zone, say at which step it is set up and who checks it.
People, competence and supervision
Name the roles: who supervises, who is competent to carry out which step, and who is responsible for stopping the work if something changes. State what training or authorisation is needed for particular tasks, such as operating plant.
Equipment, materials and access
List the plant, tools, access equipment and materials, and note any inspection or checks needed before use. If a permit is required, say so. Our permit to work guide explains how permits relate to method statements.
Emergency arrangements and welfare
State what to do in an emergency, how to raise the alarm, where first aid is and where the assembly point is. Add any task-specific arrangements, such as rescue plans where relevant.
Review and changes
Say what triggers a review. A change in people, method, plant, ground conditions or weather should lead to a review, and work should pause until the document has been checked and updated.
A quick quality checklist
Use this checklist when you are handed a method statement, or when you are asked to help write one.
- [ ] It names the specific task, location and date or period of work.
- [ ] The sequence of work is clear and in logical order.
- [ ] The hazards and controls match the current risk assessment.
- [ ] The roles, supervision and competence requirements are stated.
- [ ] The equipment, access and any permits are listed.
- [ ] Emergency arrangements are described.
- [ ] Everyone doing the work has read it and signed or recorded that they understand it.
- [ ] It says what to do if the work cannot be done as written.
Method statements and real sites
A method statement that stays in the site office has no value. Brief the team before the task starts, using plain language, and give people the chance to ask questions or raise problems. A brief that is only a signature on a sheet does not show that anyone understood the plan.
Be wary of documents copied from a previous job. Ground conditions, neighbouring structures, the plant on site and the people involved all change. If the details do not match your job, the document needs rewriting, not just a new heading.
If the situation on the ground does not match the method statement, stop. Do not improvise a new method and carry on. Tell your supervisor, and wait until the plan has been reviewed and the changes briefed to everyone affected.
Practice check
These two questions are original and written for this site. They are not official CITB questions and not an official result.
Question 1. What is the main purpose of a method statement?
- A. To describe how a specific task will be carried out safely, step by step.
- B. To record how much a task will cost.
- C. To replace the need for a risk assessment.
- D. To list everyone who has ever worked on site.
Answer: A. A method statement sets out the planned sequence and controls for a task. It works alongside the risk assessment and does not replace it.
Question 2. Halfway through a task, the ground conditions turn out to be different from those described in the method statement. What should you do?
- A. Carry on as planned, because the paperwork has been signed.
- B. Change the method yourself and tell nobody.
- C. Wait for the weather to improve.
- D. Stop and tell your supervisor, so the method can be reviewed and updated before work continues.
Answer: D. A method statement only works if it matches the real conditions. If it does not, the work should stop until it has been reviewed.
For more practice, see our free practice questions and the CITB HS&E test practice page. This site is independent and not affiliated with CSCS or CITB.
FAQ
What is the difference between a risk assessment and a method statement?
A risk assessment identifies hazards, who might be harmed and the controls needed. A method statement describes how the task will be done in sequence, including those controls. They are usually prepared together and may be issued as one RAMS package.
Who writes a method statement?
It is normally written by the contractor or a competent person who understands the work, often with input from the supervisor and the people doing the task. The principal contractor or client may review or approve it. Check who is responsible on your own site.
Do all construction tasks need a method statement?
Not necessarily, and the requirement is often set by the principal contractor, the client or the contract. Higher-risk or more complex tasks are the usual candidates. Ask your supervisor what your site requires, and refer to HSE's construction guidance and CDM 2015 for the legal duties.
What should I do if I do not understand a method statement?
Ask before you start work. The person who briefed you, or your supervisor, should explain any step you are unsure about. If the document is unclear, it is better to have it clarified than to guess how the job should go.
Sources
- HSE: Construction safety topics
- Legislation.gov.uk: Construction (Design and Management) Regulations 2015
Independent guide, not affiliated with, authorised by, approved by or endorsed by CSCS or CITB. Last updated 2026-10-08.