Construction & Field
Method Statement
MyPMP
QMS Template
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Method Statement for $1/mo, or get everything with membership ($9/mo or $99/yr).
ποΈ Construction & Field
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Method Statement template
A Method Statement is a step-by-step description of how a specific work activity will be carried out safely, setting out the sequence of tasks, resources, plant, and control measures. It is typically paired with a risk assessment (RAMS) to demonstrate that hazards have been considered before work begins. Site supervisors, principal contractors, and clients rely on it to brief operatives and prove compliance during audits.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Method Statement
- βΈBefore starting any high-risk activity such as excavation, working at height, lifting operations, or hot works
- βΈWhen a principal contractor or client requests RAMS as a condition of site access
- βΈFor tasks covered by specific regulations (e.g. confined space entry, demolition, scaffolding)
- βΈWhen briefing a new crew or subcontractor on an unfamiliar or complex work sequence
What a good Method Statement includes
- βScope of works and precise location, with start/finish dates and responsible persons
- βSequence of operations broken into logical, ordered steps
- βPlant, equipment, materials, and PPE required for the task
- βReference to the associated risk assessment and the control measures for each hazard
- βCompetency, training, and permit requirements (e.g. CSCS, permit to work)
- βEmergency arrangements, first aid, and welfare provisions
What's inside this template
The interactive form above gives you:
Purpose / summaryScope / detailsApproach / bodyDeliverables / outcomesNotes & sign-off
Tips & common mistakes
- π‘Write the work sequence in the order it will actually happen on site, not as a generic checklist, so operatives can follow it literally
- π‘Cross-reference every significant hazard to a control measure in the risk assessment, avoiding vague statements like 'take care'
- π‘Record the operative briefing with signatures; an unbriefed Method Statement offers no defence if an incident occurs
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
What is the difference between a Method Statement and a risk assessment?οΌ
A risk assessment identifies hazards and rates their risk, while a Method Statement sets out the practical, step-by-step process for doing the work safely; together they form RAMS.
Who is responsible for writing a Method Statement?οΌ
The contractor or subcontractor carrying out the work usually prepares it, often signed off by a competent person such as a site manager or SSSTS/SMSTS holder before submission to the principal contractor.
How detailed should a Method Statement be?οΌ
Detail should match the risk and complexity of the task; a simple activity needs a brief sequence, while high-risk work like lifting or excavation requires each step, control, and check spelled out clearly.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membership