Home/Resources/RAMS Compliance Hub/how to write method statement construction

How to Write a Method Statement for Construction

Step-by-step guide to writing a construction method statement. Covers required sections, common mistakes, and how to get your method statements accepted first time.

Overview

A method statement describes the safe system of work for a specific construction activity. It is a practical document that explains, step by step, how the work will be carried out, what equipment will be used, who is responsible, and what safety precautions are in place. A well-written method statement gets accepted by the principal contractor first time and reduces the risk of incidents on site. This guide walks through the process from start to finish.

What Is a Method Statement?

A method statement -- sometimes called a safe system of work or SSOW -- is a document that describes the sequence of operations for a task, the resources needed, and the safety measures that will be applied at each stage. It is one half of a RAMS (Risk Assessment and Method Statement) and is written to complement the risk assessment for the same activity.

  • Describes the step-by-step process for carrying out a specific task safely
  • Works alongside the risk assessment to form a complete safe system of work
  • Must be specific to the task, site, and conditions -- not a generic template
  • Should be understandable by the people who will carry out the work
  • Required by most principal contractors before work can start on site

What Sections Should a Method Statement Include?

A complete method statement should cover all the practical details someone would need to carry out the work safely. Missing sections are the most common reason for rejection by principal contractors.

  • Project and task description: what work is being carried out and where
  • Scope of works: the boundaries of what is and is not included
  • Sequence of operations: step-by-step work process in logical order
  • Plant, equipment, and materials: everything needed for the task
  • Personnel and competency: who is involved and what qualifications they hold
  • PPE requirements: specific personal protective equipment for each stage
  • Safety measures and control methods: tied to the risk assessment findings
  • Emergency procedures: what to do if something goes wrong
  • Permits required: hot works, confined space, excavation, etc.
  • Waste and environmental controls: disposal arrangements and pollution prevention
  • Sign-off: names and signatures of author, reviewer, and approver

Step-by-Step Writing Process

Writing a method statement is most efficient when you follow a structured approach. Start with the risk assessment, then build the method statement around the control measures you have identified.

  • Step 1: Complete or review the risk assessment for the activity first
  • Step 2: Visit the site or review site-specific information (layout, access, neighbouring works)
  • Step 3: Define the scope -- what exactly is included in this activity?
  • Step 4: Write the sequence of operations in the order they will happen
  • Step 5: For each step, note the equipment, materials, and personnel involved
  • Step 6: Add safety measures that address each hazard from the risk assessment
  • Step 7: Include emergency procedures relevant to the activity
  • Step 8: List all permits and approvals needed before work starts
  • Step 9: Have the document reviewed by someone competent in the activity
  • Step 10: Submit for approval and keep a record of the approved version

Common Mistakes That Lead to Rejection

Principal contractors reject method statements that are too generic, incomplete, or clearly copied from another project without being tailored. These are the most common problems.

  • Copying a template without changing it to reflect the actual site and task
  • Missing the sequence of operations -- just listing safety measures is not enough
  • Failing to reference specific site hazards (overhead services, live traffic, etc.)
  • Not naming competent persons or specifying qualification requirements
  • Omitting emergency procedures or assuming the main contractor will handle them
  • Using vague language like "appropriate measures will be taken"
  • Submitting without signatures or approval

Tips for Getting Method Statements Accepted First Time

The goal is a method statement that is clear, specific, and gives the principal contractor confidence that you have thought through the work properly. Quality method statements also protect you legally if something goes wrong.

  • Use the principal contractor's format or template if one is provided
  • Reference specific site conditions, access routes, and welfare facilities
  • Include clear step-by-step diagrams or photos where they add value
  • Cross-reference the risk assessment so the two documents work together
  • Keep language simple and direct -- the people doing the work need to understand it
  • Have someone who has done the work before review it for practical accuracy

Key Takeaways

  • A method statement describes how work will be done safely, step by step
  • Always write the risk assessment first, then build the method statement around it
  • Include all required sections: scope, sequence, equipment, PPE, emergency procedures, and sign-off
  • Tailor every method statement to the specific site and task -- generic documents get rejected
  • Digital RAMS tools provide consistent templates that can be tailored quickly

Write method statements faster with templates and AI

Site Samurai turns these templates into automated workflows with deadline tracking and audit trails.

Frequently Asked Questions

Is a method statement the same as a risk assessment?
No. A risk assessment identifies the hazards and evaluates the risks. A method statement describes the step-by-step process for carrying out the work safely, including the control measures identified in the risk assessment. Together they form a RAMS.
Who should write the method statement?
The contractor or subcontractor responsible for carrying out the work should write the method statement. The author should be competent and familiar with both the activity and the site conditions. It should then be reviewed by an experienced person before submission.
Do I need a new method statement for every project?
You need a method statement that is specific to each site and task. You can start from a standard template for the activity, but you must tailor it to reflect the actual site conditions, access arrangements, and any site-specific hazards. A copy-paste from another project is not acceptable.
Can Site Samurai help with method statements?
Yes. Site Samurai provides trade-specific RAMS templates that include method statement sections. You can generate a first draft with AI, tailor it to your site, capture digital sign-offs, and keep an audit trail of every version.

Ready to Automate Your Workflows?

Site Samurai turns these templates into automated workflows with deadline tracking, audit trails, and team collaboration.