How to Write a Method Statement: The Writing Process, Step by Step

Most guides hand you a list of fields and call it a method statement. That is not how a good one gets written. A method statement is a litigable safety document, and the hard part is not knowing which boxes exist — it is the work of turning a real site, a real task and a real risk assessment into a sequence that the people doing the job can actually follow. This guide is about that process: how to gather the right information, sequence the work, fold your risk-assessment controls into the steps, write for the operatives in front of you, avoid the mistakes that get documents bounced, and self-check before it leaves your business.

If what you actually want is a ready-made document to fill in — a field-by-field template with each box explained — that is a different job, and we cover it on a dedicated page. See Method statement template for construction work for the template resource. This page teaches you how to write one; that page gives you a structure to fill in.

---

What a Method Statement Actually Does (and What It Is Not)

A method statement describes, in sequence, how a task will be carried out safely. It is the practical vehicle through which the people doing the work — and those managing them — demonstrate that risks have been thought through and controlled before work begins.

It is not a risk assessment. A risk assessment identifies hazards and evaluates likelihood and severity. A method statement takes the outputs of that assessment and turns them into a step-by-step safe system of work. The two documents are distinct; they are commonly issued together as a RAMS (Risk Assessment and Method Statement) pack, but conflating them produces a document that does neither job properly.

This distinction matters for the writing process because it tells you where to start. You do not write a method statement from a blank page — you write it from a completed risk assessment. If you do not yet have one, stop and do that first. The method statement is the second half of the conversation.

---

Is a Method Statement a Legal Requirement in the UK?

There is no single statutory instrument that says "you must produce a document called a method statement." The legal driver is broader: the duty to plan and manage work safely.

The Construction (Design and Management) Regulations 2015 impose duties on contractors and principal contractors in relation to planning and managing construction work safely (CDM 2015). Separately, task-specific regulations — the Work at Height Regulations 2005, COSHH 2002, LOLER 1998, and others — each require that particular hazardous activities are assessed and controlled. A method statement is the practical mechanism through which those duties are demonstrated in writing. On most commercial projects, principal contractors require them contractually before permitting high-risk work. In practice, the question is not whether you need one — it is whether yours is good enough.

---

Before You Write: Gather the Site Information

The single biggest difference between a method statement that gets accepted and one that gets returned is whether it describes a specific job. You cannot write specifically about a site you have not characterised. Before you draft anything, assemble:

• The exact task and its boundaries. Not "roofing works" but "cleaning box gutters on the north and west elevations of the flat roof, approx. 45 m total run." Where the scope ends matters as much as where it starts.
• The site address and access route. How do operatives get to the work position? Fixed ladder, tower, MEWP, internal stair? The access method is itself a source of hazard and belongs in the sequence.
• The completed risk assessment for the task. This is your raw material. Every control it identifies has to land somewhere in the method statement.
• The site's own constraints. Principal contractor rules, permit-to-work systems, exclusion zones, working-hour restrictions, neighbouring occupiers, deliveries.
• The team. Who is doing the work, what they are trained and competent to do, and who supervises.
• The plant and substances involved. Every item of work equipment and every material — because each can pull a specific regulation into scope.

If you cannot fill these in, the method statement will be generic, and a generic method statement is the one that gets rejected. Gathering this first is not bureaucracy; it is the part that makes the writing honest.

---

The Writing Process: From Site Information to Safe System of Work

With the information assembled, the writing itself follows a repeatable sequence. Work through it in order — each stage feeds the next.

Step 1 — Fix the task to a specific context

Open by naming the site, the specific task, the principal contractor (if any), the issuing company, the document revision and the date. This is not throat-clearing: it grounds everything that follows to one job, and under CDM 2015 it ties the document into the project's management framework. A method statement that could be about any site on any project tells the reviewer you have not engaged with this one.

Step 2 — Sequence the work as it actually happens

This is the operational core. Write numbered steps in the order events occur, from arrival to demobilisation. Each step should be specific enough that an operative who has not done this exact task before could follow it safely. Where a step introduces a new hazard — moving from ground preparation to working at height, or from dry to hot work — make the transition explicit rather than burying it. Vague steps such as "work safely at all times" carry no information and are the single most common reason a principal contractor returns a document for revision.

Sequencing well is mostly a matter of imagining the job minute by minute. What is the first thing the operative does on arrival? What has to be in place before they can do the second thing? Writing in that order surfaces dependencies — you cannot ascend until edge protection is confirmed, you cannot apply sealant until ventilation is established — and those dependencies are exactly where risk lives.

Step 3 — Map each risk-assessment control onto a step

Now bring in the risk assessment. For every hazard it identified, find the step in your sequence where that hazard arises, and state the control at that step — not in a generic list at the end. A reviewer reading "all operatives wear harnesses" at the foot of the document cannot tell whether the harness is worn at the moment of exposure. The same control written against step 4 ("before moving onto the roof surface, operative clips EN 361 harness to the tested anchor point") can be verified.

This step is where the two documents become one safe system of work. If a control in your risk assessment has no home in the sequence, either your sequence is missing a step or the control was theoretical. Both are worth catching now.

Step 4 — Pull each hazard's regulation into view

As you map controls, each hazard carries a UK regulation that shapes what "adequate" looks like. Work at height engages the Work at Height Regulations 2005 and its hierarchy of control; work equipment engages PUWER 1998; hazardous substances engage COSHH 2002; manual handling engages the Manual Handling Operations Regulations 1992; lifting engages LOLER 1998. You do not need to recite the law in the body, but the controls you write must satisfy it. A gutter-cleaning method statement that never reflects COSHH 2002 against the biological matter in the gutters, or the Work at Height hierarchy against the roof access, signals that the hazard profile was not thought through. (The template resource page carries a full hazard-to-regulation trigger table you can cross-check against.)

Step 5 — Specify equipment, PPE and competence concretely

List every item of work equipment with its inspection or service status, because under PUWER 1998 it must be suitable and maintained, and under LOLER 1998 lifting equipment carries an examination certificate. Specify PPE by type and standard — "EN 361 full-body harness," "FFP2 disposable mask" — not "PPE as required." State the competence each operative must actually hold for this task, and do not claim qualifications your team does not have. Specificity here is what separates a real document from a template of good intentions.

Step 6 — Write the emergency arrangements for this site

Generic emergency text helps no one. Name the first aider and where they are, the nearest A&E, the company emergency contact, and the procedure if the primary hazard materialises — a fall, a substance exposure, a collapse. For work at height, the Work at Height Regulations 2005 include requirements for dealing with danger areas and for what happens when an unsafe condition is found mid-task; your emergency section should answer "what do we do if a fall occurs" in concrete terms.

Step 7 — Set up sign-off and briefing

Finish by recording who approved the document (a competent person — see below) and how operatives will be briefed. An unsigned, unbriefed method statement has no practical value on site. Build the briefing record into the document: date, names, signatures.

---

Write It for the People Who Will Be Briefed on It

A method statement has two audiences, and most authors only write for one. The principal contractor's reviewer reads it to decide whether to accept it. But the operative reads it — or is read it, at a toolbox talk — to know what to do. If you write only to pass review, you produce a document that is legally tidy and operationally useless.

Writing for the operative changes your choices. Use plain, direct instruction ("descend the tower; do not move it with anyone on the platform"), not passive abstraction ("tower relocation shall be undertaken in a controlled manner"). Put the control next to the action it governs, because that is the order in which the operative meets it. Keep each step to one decision where you can. Assume the reader is competent but has not done this exact job on this exact site, because that is usually true.

A useful test: read your sequence aloud as if briefing two operatives at 7am. Anywhere you would instinctively add a verbal aside ("oh, and watch the third roof light, it's cracked"), the document is missing a step. Put the aside in.

---

Worked Example — Writing the Gutter-Cleaning Method Statement

About this scenario: Gutter cleaning on a commercial flat roof simultaneously engages the Work at Height Regulations 2005, PUWER 1998, the Manual Handling Operations Regulations 1992, and potentially COSHH 2002. It is also the category of work HSG33 specifically flags: roof work accounts for a quarter of all deaths in the construction industry, and many of those killed are not trained roofers but maintenance workers accessing roofs (HSG33). Below, we walk the writing process against this task — not a blank template, but the reasoning that produces each step.

Gathering the information. The task is manual cleaning of box gutters on the north and west elevations of a flat roof, roughly 45 m of run, at Meridian House, Bristol. Access is by a site-installed fixed ladder on the north elevation. The risk assessment has flagged: fall from the roof edge, fall through fragile roof lights, biological matter in the gutters, manual handling of debris, and falling objects. Two operatives, one of whom is the designated first aider. That is enough to write specifically.

Sequencing the work. Imagine the morning. The operatives arrive and are briefed (step 1). Before anyone climbs, the access ladder is checked (step 2) and the roof surface is assessed for fragile materials with exclusion zones marked (step 3). Only then is edge protection confirmed or harnesses rigged to a tested anchor (step 4). Operative 1 ascends with hand tools while Operative 2 stays at the base as banksman and first aider (step 5). Debris is removed into sealed bags, reaching tools used rather than leaning over the edge (step 6); defects photographed (step 7); bags lowered by rope and bucket rather than thrown (step 8); the roof inspected and barriers removed on descent (step 9); waste disposed of as controlled waste (step 10). Writing in arrival-to-demob order is what surfaces the rule that you cannot ascend (step 5) until step 4 is satisfied.

Mapping controls and regulations onto the steps. Now the risk assessment's controls find homes:

• Steps 2–4 — fall from height. Work at Height Regulations 2005. The hierarchy is applied in order: exclusion zones and collective protection (parapet/edge protection) before personal fall protection (harness). Step 2's pre-use ladder check reflects HSE construction ladder guidance that a check is done before each use and after anything changes (HSE ladders).
• Step 3 — fall through fragile surfaces. Work at Height Regulations 2005, Regulation 9, and HSG33: falls through fragile materials such as roof lights account for more deaths in roof work than any other single cause. The control is identifying and marking fragile areas before ascending.
• Step 6 — biological matter. COSHH 2002 (COSHH 2002). Bird droppings may harbour biological hazards; a COSHH assessment accompanies the method statement, and the control (nitrile gloves, FFP2 mask, eye protection) is written against the step where exposure happens.
• Steps 6–8 — manual handling and falling objects. Manual Handling Operations Regulations 1992 (Manual Handling 1992) for the repetitive bending; Work at Height Regulations 2005, Regulation 10, for the rope-and-bucket control that stops debris being dropped.

Writing the emergency arrangements. Because the dominant hazard is a fall, the emergency section answers that directly: Operative 2 calls 999, does not move a fallen person unless they are in further danger, and provides first aid until services arrive; nearest A&E named; assembly point stated. A second clause covers the realistic mid-task event — a fragile surface discovered after work starts — with a clear instruction to stop, descend and report rather than improvise.

The point of the example is not the finished text but the order of thinking: information first, sequence second, controls and regulations mapped onto that sequence third, emergency and sign-off last. Reproduce that order on your own task and the document writes itself honestly.

---

Who Should Review and Sign Off a Method Statement, and When?

The person who approves a method statement must be competent to assess the safe system of work described — someone with sufficient knowledge of the task, the relevant regulations, and the specific site conditions. In practice that is a senior site manager, H&S manager, or director depending on the risk level. There is no single regulatory definition of who must sign, but the document is a legal record: whoever signs it is attesting that the method is safe and appropriate.

When to produce or revise one:

• Before starting any task for which a safe system of work is required
• When site conditions change materially (new hazards identified, access route altered)
• When the original method statement is found to be inadequate on site
• When the task scope changes beyond what the original document described

Operatives must be briefed on the method statement before they begin work — not just handed a copy. The briefing should be recorded.

---

Common Writing Mistakes That Get Method Statements Rejected

Generic controls. "Take care when working at height" or "wear appropriate PPE" describe nothing. A reviewer will reject a document whose controls could apply to any task on any site. The fix is in Step 3 — write the control against the step where the hazard occurs.

Sequence and controls disconnected. Listing all controls together at the end, with no link to a step, means no one can verify the control is applied at the right point. This is a writing-order problem, not a content problem.

Missing the regulatory trigger. A method statement whose hazards are present but whose regulations are never reflected in the controls signals that the author did not work through the hazard profile. Use Step 4 deliberately.

Writing for the reviewer, not the operative. Passive, abstract prose may read as "professional" but cannot be briefed at a toolbox talk. If you cannot read a step aloud as an instruction, rewrite it.

Undated, unversioned documents. With no date or revision number, no one can confirm the operative is working from the current approved version.

No evidence of briefing. A method statement without a signed briefing record demonstrates compliance on paper only.

Fragile surfaces not addressed. Falls from height are among the biggest causes of UK workplace fatalities (INDG401), and falls through fragile materials account for more roof-work deaths than any other single cause (HSG33). Any roof access task that does not explicitly address fragile surfaces will be challenged.

---

Pre-Submission Self-Check (12 Questions)

Run through these before a method statement leaves your business. Every "No" is a rework item — and each maps back to a step in the writing process above.

#	Question	Yes / No
1	Does the document identify the specific site address and task — not a generic description?
2	Is every step in the sequence of operations numbered and specific enough for an operative to follow?
3	Has each hazard been linked to a specific step in the sequence, not listed generically at the end?
4	For any work at height, has the method addressed collective protection before personal fall protection (the Work at Height Regulations 2005 hierarchy)?
5	For ladder use on a construction site, does the document require a pre-use check before each use, and after any change in the ladder's condition or location?
6	Has each item of work equipment been identified and its suitability/inspection status noted (PUWER 1998)?
7	Where biological matter, chemical cleaners, or dust are present, has a COSHH 2002 assessment been cross-referenced?
8	Are manual handling risks addressed with specific controls (not just "use good technique")?
9	Does the PPE section specify item types and standards — not just "appropriate PPE"?
10	Is the competence requirement stated with reference to specific training or experience?
11	Does the emergency section include first aider name, nearest A&E, and the procedure if the primary hazard (e.g. fall from height) materialises?
12	Has a competent person approved the document, and is there a mechanism for recording operative briefing before work starts?

Informed by HSE INDG401 and CDM 2015 duty-holder obligations for contractors to plan and manage construction work safely.

---

Start From a Structure, Not a Blank Page

Everything above is faster when you are not also inventing the document's skeleton from scratch. A good template removes the structural decisions — which fields, in what order, with what each one is for — so your effort goes where it matters: the site-specific sequencing and control-mapping that no template can do for you.

How RamsDocs supports the writing process

RamsDocs gives you that structure and then guides you through the very process this page describes. It prompts you to characterise the site and task first, holds the field order so you sequence the work before you reach controls, and surfaces the relevant regulations as you go so the hazard-to-control mapping in Step 3 and Step 4 is harder to skip. When the draft is complete it routes the document to a nominated competent approver, logs the timestamped approval, and generates the operative briefing record alongside it — so the sign-off and briefing in Step 7 leave an auditable trail rather than a pile of emails.

The platform enforces structure and process; the competent person on your team supplies the site-specific content and verifies it before issue.

For a ready-to-fill template with every field explained and a second worked scenario, see Method statement template for construction work.

---

Frequently Asked Questions

How do you actually write a method statement, step by step? Start from a completed risk assessment, not a blank page. Gather the site information (task boundaries, access route, team, plant, substances), then write the sequence of operations in the order the work happens, map each risk-assessment control onto the step where its hazard occurs, pull the relevant regulation into view for each hazard, specify equipment, PPE and competence concretely, write site-specific emergency arrangements, and finish with sign-off and a briefing record.

What is the difference between a method statement and a risk assessment? A risk assessment identifies hazards and evaluates risk. A method statement translates those findings into a step-by-step safe system of work. They are distinct documents, commonly issued together as a RAMS pack, but each must do its own job — and you write the method statement from the risk assessment.

How do you write a method statement for work at height? Apply the Work at Height Regulations 2005 hierarchy as you sequence: can the work at height be avoided? If not, which collective protection (edge protection, barriers, towers) is used before any personal fall protection? The sequence must reflect that hierarchy explicitly, address fragile surfaces and ladder pre-use checks, and set out an emergency rescue procedure. Cross-reference HSG33 for roof work.

How long should a method statement be? Long enough to cover every step, hazard and control specific to the task — no longer. A straightforward maintenance task may run two to three pages; a complex multi-trade operation, ten or more. Specificity, not length, is the measure of quality.

Do I write a method statement or download a template? Both have a place. A template gives you the structure and field definitions; writing is the part where you make it true for your site by sequencing the work and mapping in your controls. Start from a template to save the structural effort, then apply the writing process on this page. The template resource page covers the field-by-field side.

Who should sign off a method statement? A competent person — someone with sufficient knowledge of the task, the hazards and the applicable regulations to confirm the method is safe. Typically a senior site manager, H&S manager, or company director depending on the risk level.

What should I do when a method statement needs to be revised mid-project? Increment the revision number and date on the document face before reissuing — every revision creates a new version that supersedes its predecessor, and the superseded version should be clearly marked as such or withdrawn from circulation so operatives cannot work from an out-of-date document. Crucially, anyone already briefed on the previous version must be re-briefed on the changes; a fresh briefing record should be signed by each operative to confirm they have been notified of the revised controls. Where circumstances have changed materially — a change in access method, a new subcontractor, or a significantly different sequence — treat the revision as substantive and re-check that every risk-assessment control still has a home in the updated steps.

---

Disclaimer: This guide and the worked example within it are provided for general information and structural guidance only. Every method statement must be reviewed and adapted to the specific site, task, work equipment, personnel, and conditions by a competent person before issue and before any work begins. Nothing in this page constitutes legal advice or guarantees regulatory compliance. RamsDocs content does not substitute for site-specific professional assessment.