What is a method statement and when do I need one?
A method statement describes, in a logical sequence, exactly how a job will be carried out safely, including the specific control measures for each step. It's not a legal document in its own right for most work, but it's how UK construction sites typically demonstrate the safe system of work that the Health and Safety at Work etc. Act 1974 requires every employer to provide.
Is a method statement actually a legal requirement?
Mostly no, with one important exception. HSE guidance confirms that for demolition, dismantling, or structural alteration, the arrangements must be recorded in writing before work starts, and a method statement is the usual way that's done. Outside that specific case, a method statement isn't named as mandatory in law, but the safe system of work it describes is a legal duty, so in practice most contractors across Guildford and Portsmouth end up needing one for any task that's high-risk, complex, or involves multiple trades working close together.
What does a method statement actually need to contain?
- A clear, step-by-step sequence for how the task will progress
- The specific hazards present at each stage
- The control measures, PPE and monitoring in place for each step
- Who's supervising and who's executing each part of the work
- The plant, tools and equipment involved
- What to do if something goes wrong
It should be written by someone who genuinely understands the process being described, not adapted from a generic template that doesn't match what's actually happening on site.
When does a job definitely need one?
In addition to the tasks mentioned earlier, working at height, lifting operations, confined space entry, and any task involving multiple trades or an unfamiliar process are other common triggers. The HSE flags method statements as particularly valuable for work at height, since falls remain the single biggest cause of fatal and serious injury in construction. A repetitive, well-understood task with an established safe way of doing it may not need a fresh method statement every time, but anything genuinely new, complex, or high-consequence usually does.
How does a method statement relate to a risk assessment?
A method statement is built from the findings of a risk assessment, it takes the hazards and controls already identified and turns them into a step-by-step plan the people doing the work can actually follow. The two are closely linked but answer different questions: one identifies and evaluates risk, the other sets out exactly how the work gets done safely. We'll cover that distinction properly in a dedicated separate post.
Frequently asked questions
Does every construction task need a method statement?
No. Routine, low-risk, well-understood tasks generally don't need one. It's higher-risk, complex, unusual work, or anything involving multiple trades and interfaces, where a method statement is required.
Who's responsible for writing a method statement?
Usually the contractor carrying out the work, since they understand the process best, though it's often reviewed or agreed with the principal contractor before work starts, particularly on sites with multiple trades operating close together.
Is a method statement the same as a risk assessment?
No, though they're closely related and often combined into a single RAMS document on construction sites. A risk assessment identifies and evaluates hazards; a method statement sets out the safe sequence of work built from those findings.
PPT Health & Safety Consultants prepares method statements and full RAMS documentation for construction and fit-out clients across Surrey, Hampshire and London. If you're not confident your current method statements reflect what's actually happening on site, get in touch.
