How to Write a Method Statement for Construction Work
A method statement is one of the most practical documents in construction health and safety. When someone asks for your RAMS — your Risk Assessment and Method Statement — the method statement is the "how" that sits alongside the risk assessment's "what could go wrong." Getting it right means your workers know exactly how the job is to be done safely, and your client or principal contractor can see that you've thought it through.
What a Method Statement Actually Is
A method statement is a document that sets out, step by step, how a specific task or work package will be carried out safely. It is not a legal document in its own right — there is no single regulation that says "you must produce a method statement." Its value comes from being paired with your risk assessment, which is a legal requirement under Regulation 3 of the Management of Health and Safety at Work Regulations 1999.
Together, the risk assessment identifies the hazards and suitable controls; the method statement translates those controls into a clear sequence of work that operatives can follow on site.
Who Needs One
Method statements are standard practice on most commercial and construction sites. Under the Construction (Design and Management) Regulations 2015 (CDM 2015), principal contractors must ensure that work is properly planned, managed and monitored — and well-written method statements are a core tool for doing that. Subcontractors and specialist trades are routinely required to produce them before starting high-risk tasks such as working at height, confined space entry, demolition, or work with hazardous substances.
What to Include: The Core Sections
There is no single prescribed format, but a credible method statement for construction work should cover the following:
1. Project and Task Details
- Project name, site address and dates
- Specific task being described (be precise — "installation of structural steel to ground floor" rather than "steelwork")
- Company name, document reference and version number
2. Scope of Works
A short paragraph explaining what the task involves and its boundaries. This keeps the document focused and avoids scope creep.
3. Personnel and Competence
List the roles involved — supervisor, operatives, appointed persons — and note any required qualifications, training or certification (e.g. IPAF licence for MEWP operation, CSCS cards, PASMA training).
4. Plant, Equipment and Materials
List the tools, plant and materials to be used. If substances are involved, reference the relevant COSHH assessment (Control of Substances Hazardous to Health Regulations 2002). If plant requires thorough examination under LOLER or PUWER, note where records are held.
5. Step-by-Step Sequence of Work
This is the heart of the document. Break the task into logical stages in the order they will happen. For each stage, describe:
- What is being done
- How it is being done
- Which controls from the risk assessment are applied at that point
Keep each step concise but specific enough to be useful. Avoid vague language like "take appropriate precautions" — state the actual precaution.
6. Hazard Controls in Context
Rather than repeating the full risk assessment, reference it and call out the key controls at the relevant steps — for example, noting where exclusion zones must be in place, where edge protection is required, or when atmospheric testing must be completed before entry.
7. PPE Requirements
PPE sits at the bottom of the hierarchy of control — it should be specified clearly but only after higher-level controls (elimination, substitution, engineering measures, administrative controls) have been addressed in the risk assessment. List the minimum PPE required for the task and any task-specific items.
8. Emergency Arrangements
Include the site emergency contact, nearest first-aider, evacuation procedure and the location of the nearest hospital with A&E. If the task carries specific emergency risks — a fall arrest system deploying during rope access work, for instance — address the rescue plan here.
9. Environmental Controls
Note any measures to prevent pollution, manage waste or protect the surrounding area — particularly relevant for work near watercourses, in urban environments, or involving hazardous materials.
Common Mistakes to Avoid
| Mistake | Why it Matters |
|---|---|
| Copying a generic template without editing | The document won't reflect the actual task or site conditions |
| Describing controls without a sequence | Operatives can't follow it as a working document |
| Listing PPE only, ignoring higher controls | Suggests the hierarchy of control hasn't been applied |
| No version control or review date | Outdated documents can cause harm if conditions change |
| Separating the RAMS so they don't cross-reference | Controls identified in the risk assessment must appear in the method statement |
Briefing Operatives on the Method Statement
Writing the document is only half the job. Before work starts, operatives must be briefed on its contents — this is often done as a toolbox talk, with a signature sheet to confirm attendance. Under CDM 2015, principal contractors must ensure workers are provided with relevant information and instructions. An unread method statement sitting in a site file provides no protection in practice.
Keeping It Reviewed and Current
If site conditions change, plant is substituted, or the scope of work shifts, the method statement must be reviewed and reissued. Date and version-number every revision, and brief the team on what has changed before work resumes.
A well-written method statement is not a bureaucratic box-tick — it is a practical safety plan that gives your workers clear direction and demonstrates to everyone on site that the work has been properly thought through.