How to Write a Method Statement Quickly and Correctly

A practical structure UK site managers and contractors can reuse on every job.

A method statement does not need to be a weekend job. The reason most take so long is that people stare at a blank page. With a clear structure and a repeatable process, you can produce a method statement that is specific, compliant and genuinely useful in a fraction of the time. Here is how.

What a method statement is meant to do

A method statement, sometimes called a safe system of work, describes how a particular task will be carried out safely, step by step. It sits alongside the risk assessment, which identifies the hazards and controls. Together they form a RAMS. The method statement should be clear enough that a competent person can read it and understand exactly how the work is to be done, in what order, with what equipment, and with what precautions.

What to include in a method statement

Before you start writing, gather the facts. A complete method statement generally covers the following sections. If you collect this information first, the writing becomes quick.

• Project and site details. The site address, client, dates and the contractor carrying out the work.
• Scope of works. A short, precise description of the task this statement covers.
• People and responsibilities. Who is doing the work, who is supervising, and any competencies or tickets required.
• Plant, tools and materials. What will be used, including any certification or inspection requirements.
• Sequence of work. The actual step by step method, in order, from setup to completion and clear up.
• Control measures. The precautions for each stage, cross referenced to the risk assessment.
• Personal protective equipment. What is required for the task.
• Emergency arrangements. First aid, emergency contacts, rescue plans where relevant, and what to do if something goes wrong.
• Sign off and briefing. Space to record that operatives have read and understood it before starting.

A simple process to write one fast

1. Start from the task, not a template. Write the scope of works in one or two plain sentences first. This anchors everything else to the real job.
2. Do the risk assessment alongside. List the hazards for this task and the controls. You will reuse these controls in the method, so it saves time to do them together.
3. Walk the job in your head, in order. From arriving on site to clearing up, write each stage as a short numbered step. Keep each step to one clear action.
4. Attach the controls to the steps. For any step with a hazard, state the precaution right there. This is where generic statements get exposed, so be specific.
5. Add the supporting detail. People, plant, personal protective equipment and emergency arrangements. Most of this is consistent across similar jobs, so a good base saves repetition.
6. Read it as the operative. Could someone unfamiliar follow it safely? If not, tighten the wording.
7. Brief and record. Walk the team through it, answer questions, and have them sign before work starts.

Write it in clear, specific language

Reviewers and operatives both want the same thing: clarity. A few habits make a method statement far stronger:

• Use short, direct sentences. One action per step.
• Be specific. "Use a tower scaffold inspected within the last 7 days" beats "work safely at height".
• Reference the actual equipment and the actual site features, not generic ones.
• Avoid vague phrases like "take care" or "as necessary". State the precaution.
• Keep it proportionate. A higher risk task needs more detail, a routine one needs less.

Mistakes that get a method statement rejected

• Obvious template reuse. Wrong site name left in, or hazards that do not match the task. Reviewers reject these on sight.
• Method and risk assessment that do not match. Controls mentioned in one but missing from the other.
• Steps out of sequence or missing. Jumping from setup to completion with the risky middle left out.
• No emergency arrangements. Especially for work at height, confined spaces or lifting.
• No briefing record. A statement nobody signed shows it was not communicated to the team.
• Too long to be usable. A wall of generic text that the operatives will never read.

Frequently asked questions

Conclusion

Writing a method statement quickly comes down to one thing: removing the blank page problem. Start from the real task, do the risk assessment alongside, sequence the work step by step, attach specific controls, and brief the team. Keep a strong base structure so each new job only needs the genuinely different details filled in. Where the detail required for a particular activity is unclear, check current HSE guidance and your principal contractor's requirements.

This article is general guidance for UK construction and is not legal advice. For requirements specific to your work, check current HSE guidance and your principal contractor's requirements.