A method statement is a written document that describes step-by-step how a specific task will be carried out safely. It works alongside a risk assessment — the risk assessment identifies the hazards and the controls; the method statement explains exactly how those controls will be put into practice. Method statements are not a legal requirement in themselves, but for higher-risk work, particularly in construction, they are typically expected by clients, principal contractors, and Health and Safety Executive inspectors. Method statements are commonly bundled with risk assessments as "RAMS" — Risk Assessment and Method Statement.
If you've worked in UK construction, engineering or industrial services for any length of time, you've come across method statements. They're the document that explains how a job will be done safely. This guide explains what they are, when you need one, what they should include, and how they differ from risk assessments.
A method statement is a step-by-step plan describing how a particular task will be carried out, with specific reference to the safety controls that will be applied. It translates the conclusions of a risk assessment into concrete operational instructions — what equipment will be used, in what order steps will happen, who will do what, and how identified hazards will be controlled at each stage.
The format isn't fixed by law. Most method statements share a common structure (covered below), but the level of detail varies depending on the risk level of the task and the requirements of the client.
Method statements are sometimes called:
The terms are functionally equivalent.
This is the most common point of confusion. They're related but different documents:
| Risk Assessment | Method Statement | |
|---|---|---|
| Question it answers | What could go wrong, and what should we do about it? | How exactly will the work be carried out safely? |
| Format | Hazard / Risk / Control table | Step-by-step procedure narrative |
| Focus | Identifying and evaluating risk | Translating controls into operational steps |
| Legal status | Required under MHSWR 1999 for all work activities | Not separately required, but expected for higher-risk work |
| Order | Done first | Built on the risk assessment findings |
| Audience | Manager, supervisor, safety officer | Workers actually doing the task |
The risk assessment is the analytical document; the method statement is the operational document. Together they form RAMS — and the two are typically submitted as a single package on construction projects.
For more on the risk assessment side, see our 5 Steps to Risk Assessment guide.
UK law doesn't specifically require method statements as a named document for most work. But several scenarios make them effectively necessary:
The Construction (Design and Management) Regulations 2015 require principal contractors to plan, manage and monitor construction work and ensure it's carried out safely. In practice this means method statements for higher-risk operations — work at height, demolition, lifting, hot works, confined spaces, work near services.
Hot works, confined space entry, working at height, electrical isolation — all permit-to-work systems typically require an associated method statement before the permit is issued.
Most major UK clients (utilities, public sector, large industrial) require RAMS submissions before work starts on their sites. The method statement is reviewed and approved before workers attend site.
Anything where workers, the public, or the structure of a building could be seriously harmed if the work isn't done correctly — heavy lifting, structural work, demolition, work near live services, asbestos work.
For one-off or unusual work, a method statement helps ensure the team approach is consistent and considered.
A typical method statement runs 2-10 pages depending on task complexity. The core sections:
The core of the method statement. Step-by-step description of how the work will be carried out, with safety controls integrated:
The same method statement used across multiple projects without genuine site-specific tailoring. Inspectors and principal contractors see straight through these.
The method statement describes work that doesn't actually address the controls in the risk assessment. The two documents become disconnected.
"Take care to avoid hazards" and similar non-specific phrasing. Method statements need to be specific — what action, by whom, when.
The method statement is written, submitted to the client, and never communicated to the workers actually doing the job. The point of the document is to direct the work — if it's not briefed, it's just paperwork.
Working at height with harnesses without an effective rescue plan is one of the most common serious findings on UK construction sites. The method statement must specify how a fallen, suspended worker will be brought down — within minutes, not hours.
Original method statement assumes conditions that no longer apply (different weather, additional contractors on site, equipment substitution). Should be revised, but often isn't.
Method statements aren't named as a separate legal requirement in UK health and safety law. But for construction work, work under permits, and higher-risk activities, they are effectively required — by CDM 2015's planning duties, by client contracts, and by industry practice. Risk assessments are legally required; method statements are typically required to demonstrate the risk assessment will actually be implemented.
RAMS stands for Risk Assessment and Method Statement. It's the standard UK industry term for the bundled document covering both the analysis (risk assessment) and the operational plan (method statement) for a specific task or project.
Typically the contractor or sub-contractor doing the work — the people who know the task and the equipment. They should be reviewed and signed off by a competent person (a safety officer, project manager, or experienced supervisor) before being submitted to the client or principal contractor.
As long as needed to cover the task properly — typically 2-10 pages for a standard task. Very simple low-risk work may need only a one-page document. Complex high-risk work (large lifts, demolition, asbestos removal) may need 20+ pages with multiple appendices.
Yes, for related tasks at the same site. But each significant task with materially different hazards should be addressed specifically. Generic "all our works" method statements rarely satisfy clients or inspectors.
Best practice is a face-to-face briefing where the supervisor walks workers through the document, answers questions, and confirms understanding. Workers sign a briefing record acknowledging they've understood. For non-routine work, "toolbox talks" are often used to refresh key points before each shift.
For consultancy support on RAMS development, see our Risk Assessment & Management consultancy. Or call us on +44 (0) 3300 569534.
