Free method statement template (Word download)

A method statement sets out, step by step, how a job will be done safely: the order of work, who does what, the equipment used and the controls at each stage. Principal contractors usually want one before you start on site.

Download the method statement template (.docx)

[DISCLAIMER — DRAFT, FOR SOLICITOR REVIEW] This template is a starting point only. You are responsible for assessing the risks of your own work, and for making sure any document you produce from it is suitable and sufficient for the task, the site and the people involved. It is not health and safety advice.

What's in the template

  1. Document control — company, client, site, revision and approval
  2. Scope of works
  3. Location and site access — routes, exclusion zones, deliveries, other trades
  4. Programme and working hours
  5. Roles and responsibilities
  6. Plant, equipment and tools
  7. Materials and hazardous substances
  8. Sequence of works — each step with its hazards, controls and who is responsible
  9. PPE required
  10. Permits and isolations
  11. Supervision and monitoring
  12. Emergency arrangements
  13. Environmental controls — waste, dust, noise, spills
  14. Related risk assessments
  15. Briefing record — sign-off sheet

Method statement or RAMS?

A method statement describes how the work will be done. A risk assessment identifies what could go wrong and how likely and serious it is. Many principal contractors ask for both together as a RAMS. If that's what you've been asked for, use the RAMS template, which combines the two in one document.

How to write the sequence of works

The sequence of works is the part a site manager actually reads, so it's worth getting right.

  1. Write the steps in the order you'll really do them, from arriving on site to leaving it clean.
  2. Keep each step to one activity. "Erect tower scaffold" and "install fixings" are separate steps.
  3. Name the hazards for that step specifically, not a generic list for the whole job.
  4. Make each control something a person can check — "barrier the work area" rather than "take care".
  5. Put a name or role against every step, so it's clear who is responsible.
  6. If the method changes on site, update the document and re-brief the team.

Common reasons a method statement gets rejected

ProblemFix
Copied from another jobMake the scope, site address and steps specific to this job
Vague controlsSay exactly what will be done, by whom
No link to the risk assessmentReference the relevant risk assessments in section 14
No briefing recordGet everyone working to it to sign before starting
RAMS generator — coming soon.

Answer a few questions about the job and get a completed RAMS in Word, ready to send.

More free templates