A method statement template is a set of prompts in the right order. Its job is to stop you starting at the interesting part and forgetting the arrival, the isolation and the clearing down, which is where a surprising share of incidents happen. What it cannot do is know your sequence, and a template that supplies the sequence is supplying a description of somebody else's job.
The order the prompts should come in
Job and site. Client and dates. Scope, stated as what is and is not included. People, with roles and competence. Plant, equipment and access. Permits and isolations required before starting. The sequence itself, numbered. Materials and substances with their COSHH references. Waste and housekeeping. Emergency and rescue arrangements. Briefing record. Review and version.
Writing the sequence so it can be followed
Number the steps. One action per step. Name who does it. State the control the step depends on before the step that needs it, not after. Say explicitly where work stops if a condition is not met, because a sequence with no stop point assumes everything will be as expected. A person who has never seen the job should be able to read it and know what happens first.
The three sections templates usually miss
Setting up and getting to the work area, which is where most access risk sits. Interfaces with other trades and with building occupants. And clearing down, including making the area safe overnight when the job spans days. Templates jump from scope to the work because that is the part that feels like the job.
Making the template earn its place
Keep one per trade task rather than one per company. A template for roof tiling and a template for gutter replacement will prompt different things, and a single generic construction template prompts none of them well. Review each after a job where something went differently from the plan, because that is the cheapest information you will ever get about what the template forgot to ask.
A method statement and risk assessment template together, and why they are one pack
The two documents answer different questions and neither stands alone: the assessment decides what could go wrong and what will control it, the statement says how the job is done in sequence so those controls actually happen. Sent separately they drift, because the sequence gets updated on site and the assessment does not. A combined pack, commonly called a RAMS, keeps them in one file with one version number and one date, with the assessment first and each control cross referenced to the step it belongs to. The test of the pack is whether a step in the statement exists for every control the assessment promised.
Where a method statement template free of charge is worth using, and where it is not
A downloaded shell is fine for the headings, the version block and the sign off sheet, which are the same everywhere and tedious to retype. It is not fine for the sequence, the plant, the permits or the emergency arrangements, because those are the parts a client's principal contractor reads and they are the parts a free template fills with somebody else's job. The practical use is to strip a downloaded file back to its structure, delete every line of content, and write the sequence from a walk of the actual site. A template still carrying its original example text is the commonest reason a RAMS is rejected.
Questions people ask about method statement template
Is there a legal format for a method statement?
No. The law requires a safe system of work and, on construction projects, arrangements for managing it. The format is yours to choose.
What should a method statement template prompt for?
Job and site, scope, people and competence, plant and access, permits and isolations, the numbered sequence, materials and COSHH, waste, emergency and rescue, the briefing record and the version.
Should a template include the sequence?
Only as a trade-specific starting point you then edit for this job. A sequence that is never edited describes work nobody has looked at.
How detailed should the sequence be?
Detailed enough that someone unfamiliar with the job could follow what happens and in what order, and could see which control each step depends on.
Is a free method statement template worth starting from?
For the headings, yes. What a template gives you is the order a reader expects: the job, the site, who is doing it, the sequence of work step by step, the plant and equipment, the controls from the assessment, the emergency arrangements and who signs it. What it cannot give you is the sequence, and the sequence is the document. A principal contractor reading a method statement is looking for what happens in what order and where the other trades are, so a pack that arrives with generic steps tells them nobody has thought about this site.
What makes a safety method statement acceptable on site?
Three things, and length is not one of them. It describes THIS job in the order it will be done, with the controls from the risk assessment built into the steps rather than listed at the end. It names people and equipment rather than roles in the abstract, so somebody can check on the day. And it is short enough to be read at a briefing, because a document nobody reads controls nothing. A statement that a supervisor can walk through with the crew in five minutes is worth more than twenty pages of standard text.