Use the structure. Build it properly in Graftly.
Static templates are useful starting points, but method statements need to be adapted to the job, site conditions, people involved and controls required. Graftly helps you create, store, export and share a cleaner site-specific version.
- Site-specific, not generic
- Stored by job or site
- Ready to export and share
Method statement template structure
A method statement usually covers five areas. Use the grouped preview below as a starting point, then create a site-specific version in Graftly rather than editing a static file.
Job details
- Project/site
- Client
- Location
- Date
- Prepared by
Work activity
- Task or activity
- Description of works
- Sequence of works
- People involved
Controls and equipment
- Plant, tools and equipment
- Materials
- Key hazards
- Control measures
- PPE required
Site arrangements
- Access and site setup
- Emergency arrangements
- Environmental considerations
- Permits or approvals required
Review and sign-off
- Communication and supervision
- Sign-off / attendees
- Review date
What is a method statement?
A method statement explains how a task will be carried out safely. It usually describes the sequence of work, who is involved, what equipment is used, what hazards need to be controlled and what safety measures should be followed on site.
For UK trades and contractors, method statements are often used alongside risk assessments and RAMS to show clients, principal contractors or site managers that work has been planned properly before it starts. For higher-risk work, the method statement should sit alongside the relevant risk assessment or RAMS document.
Why use Graftly instead of another static template?
Free templates are a useful starting point, but they often end up copied, renamed and buried in old folders. Graftly gives UK trades a more practical way to create method statements from a mobile-first workflow, keep them organised by site and export clean records when needed.
Static template
- Easy to copy
- Can become outdated
- Often buried in folders
- Needs manual editing every time
- Harder to track sign-off
Graftly
- Built around site-document workflows
- Reuses site and job details
- Keeps records organised
- Exports clean PDFs
- Supports sign-off and sharing
What should a method statement include?
Method statement vs risk assessment vs RAMS
Risk assessment
Identifies hazards, who might be harmed and what controls are needed.
Method statement
Explains how the work will be carried out safely, step by step.
RAMS
Combines risk assessments and method statements into one site safety document.
Read our plain-English RAMS guide for a fuller breakdown of how these documents fit together.
Trade-specific method statement examples
Roofing works method statement
Working at height, edge protection, safe access to the roof, material handling and weather planning.
Roofing RAMS and risk assessments →Electrical works method statement
Isolation and lock-off, safe testing, cable routes, PPE and permit-to-work arrangements.
Plumbing works method statement
Hot works, water isolation, working in occupied spaces, confined areas and manual handling.
Groundworks method statement
Excavation safety, underground services, plant movements, exclusion zones and shoring.
Scaffolding method statement
Erection sequence, loading, ties, edge protection, inspection records and handover.
Cleaning or maintenance method statement
COSHH controls, slips and trips, lone working, access equipment and site rules.
Common method statement mistakes
- Using a generic template without adapting it to the site
- Missing the actual sequence of work
- Listing hazards without clear controls
- Forgetting who is responsible for supervision
- Not recording sign-off
- Not updating the document when site conditions change
- Storing method statements where the team cannot easily find them
Frequently asked questions
What is a method statement?
A method statement explains how a task or work activity will be carried out safely, including the sequence of work, equipment, people involved, hazards and control measures.
Is a method statement a legal requirement in the UK?
A method statement is not always specifically required by law for every job, but it is commonly requested on UK sites to show that work has been planned safely. Higher-risk work will often require clear written planning alongside a suitable risk assessment.
What is the difference between a method statement and RAMS?
A method statement explains how the work will be done. RAMS usually combine a risk assessment and method statement into one document.
Can I use a method statement template?
Yes, but it should be adapted to the specific job, site, team and hazards. A generic template should not be used without checking it fits the work being carried out.
Do I need a separate method statement for each site?
If the work, site conditions, people, equipment or risks are different, the method statement should be reviewed and adapted for that site.
Can I create method statements in Graftly?
Yes. Graftly supports method statements alongside RAMS, risk assessments, COSHH assessments, toolbox talks, incident records and sign-offs.