Method Statement Examples by Trade: What Clients Want to See

If you have ever had a method statement bounced back by a principal contractor with "needs more detail" scrawled across it, you know the frustration. You described what you were going to do. What more do they want?

Quite a lot — and it varies by trade. A method statement example for a plumber looks nothing like one for a scaffolder. This guide breaks down what each trade needs to include, with enough specifics to reference next time you write one.

What Is a Method Statement?

A method statement is the "how" document. It describes, step by step, how work will be carried out safely on site. It is not a risk assessment — that covers "what could go wrong." A method statement answers: given these risks, what is the actual sequence of work, and what controls are in place at each stage?

The two are usually submitted together as a RAMS package, but they serve different purposes. If you need help with the risk assessment side, we have covered risk assessment templates for construction separately.

Method Statement vs Risk Assessment

This trips up a surprising number of experienced tradespeople:

• Risk assessment: identifies hazards, evaluates likelihood and severity, lists control measures. Analytical.
• Method statement: describes the planned work sequence, incorporating those control measures into each step. Procedural.

A risk assessment says "working at height — risk of fall — use edge protection." A method statement says "Step 4: Before ridge tile replacement, erect temporary edge protection to all open edges using a proprietary guardrail system at 950mm height with mid-rail and toe board."

Standard Sections Every Method Statement Needs

Regardless of trade, a solid method statement covers:

1. Scope of works — what is being done, where, and over what duration
2. Sequence of operations — the step-by-step work method, in chronological order
3. Resources — personnel, competency requirements, supervision
4. Plant and equipment — tools, machinery, access equipment, PPE
5. Safety measures — specific controls at each stage (not generic statements)
6. Emergency procedures — what happens if something goes wrong, first aid, nearest A&E

Here is where the generic advice stops and the trade-specific detail starts.

Method Statement Example: Electrician (First Fix Domestic Rewire)

Scope: Full rewire of a 3-bed semi-detached. Strip out existing wiring to the consumer unit. New circuits: lighting, ring finals, cooker, shower, smoke detection.

Isolation procedures: This separates a good method statement from a poor one. Not just "isolate the supply" but "isolate at the DNO cut-out, lock off with a personal padlock, confirm dead using a GS38-compliant voltage indicator, test the tester before and after on a known source."

Cable routing: "Cables within safe zones per BS 7671 Regulation 522.6.6. Vertical drops within 150mm of wall corners. Horizontal runs within 150mm of ceiling or finished floor level."

Testing sequence: Dead testing (continuity, insulation resistance, polarity) then live testing (earth fault loop impedance, RCD operation times). Reference BS 7671 and IET Guidance Note 3. Electrical Installation Certificate issued on completion.

Method Statement Example: Scaffolder

Scaffolding method statements face heavy scrutiny because the scaffold is a temporary structure that other trades rely on.

Erection sequence: "Base plates on sole boards (225mm x 38mm softwood, 1.5m length) on level ground. Standards at maximum 2.1m centres. Ledgers at maximum 2.0m lift heights. Transoms at each standard and mid-bay."

Load calculations: State the duty — general purpose (2.00 kN/m2) or heavy duty (2.50 kN/m2). Reference TG20 compliance where applicable.

Tie patterns: "Ties at every other lift on alternate standards — 4.2m horizontally, 4.0m vertically. Through-ties where possible; otherwise proprietary anchor ties into solid masonry." Never write "ties as required" — that gets your method statement rejected every time.

Inspection schedule: Weekly inspections by a competent person, recorded on a scaffold register. Additional inspections after adverse weather or any alteration.

Method Statement Example: Roofer

Falls from height remain the biggest killer in UK construction, and principal contractors know it. Roofing method statements get scrutinised accordingly.

Access arrangements: "Access via an independent scaffold with a full platform at eaves level. Ladder access via an internal ladder bay with self-closing gate." If using a roof ladder, describe how it is secured — hooked over the ridge, not just resting on tiles.

Edge protection: State that the top guardrail extends at least 950mm above the roof surface at the eaves. For gable ends, describe how protection is provided — a proprietary guardrail or a restraint lanyard system with a defined anchor.

Material handling at height: "Tiles delivered to roof level by mechanical hoist. Distributed evenly across battens to avoid point loading. No materials stacked higher than three courses on the batten." This section is often missing from roofing method statements, and it should not be.

Weather restrictions: "Work ceases when wind exceeds 35 km/h, during lightning, or when surfaces are icy. Partially completed work made safe with temporary weatherproofing before operatives leave the roof."

Method Statement Example: Plumber

A commercial hot water system installation is a common scenario.

Hot works permits: "Hot works permit obtained from the site manager before brazing. CO2 extinguisher and fire blanket within 2m of the work area. Fire watch maintained for 60 minutes after hot works." Skip this section and the PC will return your paperwork the same day.

Isolation of services: "Relevant section isolated at the nearest upstream valve. System drained down and confirmed depressurised before any joints are broken. Any glycol-based antifreeze captured and disposed of per site waste management procedures."

Testing and commissioning: "System pressurised to 1.5 times working pressure (minimum 3 bar) for two hours. Pressure recorded at start and end. Maximum permissible drop: 0.1 bar. Commissioning certificate issued on completion."

Why Method Statements Get Rejected

The most common reasons:

• Too generic — copy-pasted from a template with no site-specific detail. If it could apply to any site in the country, it is not specific enough.
• Missing the sequence — listing controls without describing order of operations. A method statement is a method. Beginning, middle, end.
• No emergency procedures — include the site address, nearest A&E with postcode, and the incident reporting procedure.
• Unsigned — many PCs will not accept without a signature from the person responsible and evidence that operatives have been briefed.

If you are spending hours on RAMS documents and still getting them knocked back, it might be worth looking at whether a dedicated RAMS generator beats templates for your workflow.

Tips for First-Time Acceptance

1. Read the PC's requirements first. Some principal contractors have specific formats or cover sheets. Ask before you write.
2. Be specific about your site. Name the address. Reference floor levels, room numbers, grid references.
3. Include sketches. A drawing of scaffold tie positions or cable routes beats a paragraph of text.
4. Brief your team and record it. A toolbox talk record with signatures shows the method statement is a working document, not a filing exercise.
5. Version control. If the scope changes, reissue with a new revision number.

Writing method statements that reflect the actual job is not glamorous, but it is the difference between starting on time and waiting days for resubmission approval. If you build RAMS packages regularly, TradeRAMS generates trade-specific, site-specific documents without the blank-page problem. We are taking names for the waitlist ahead of launch.