Method Statement Review Process

A method statement describes the safe sequence of work for a specific construction activity, step by step.
The principal contractor must review subcontractor method statements before permitting any work to begin on site.
A good method statement is site-specific, task-specific, and written by someone who understands the actual work involved.
The review checks that the method statement describes a logical, safe sequence with clear steps from start to finish.
Resources including plant, equipment, materials, and competent personnel must be identified and confirmed available.
Hazards at each stage must be identified with corresponding control measures that are practical and achievable on this site.
PPE requirements must be specified for each phase of the work, not just listed generically at the end of the document.
Emergency procedures and first aid arrangements specific to the task and location must be included in the method statement.
The method statement must be communicated to every worker carrying out the task — an unread document protects nobody.
Method statements must be reviewed and updated when the work changes, conditions alter, or lessons are learned from incidents.

Safe sequence	The method statement defines the order in which work is done safely — a missing step or wrong sequence causes incidents.
Site-specific	Generic method statements from other projects miss this site's specific hazards — the review ensures the document matches reality.
Communication	A method statement only works when workers have read and understood it — the review must confirm briefing arrangements.

Do

Don't

Review every method statement for completeness and site-specificity before approval.
Check the work sequence is logical, safe, and covers every stage from start to finish.
Verify that resources including plant, materials, and competent persons are identified.
Confirm hazards at each stage have practical, achievable control measures specified.
Ensure PPE requirements are stated for each phase, not just listed generically.
Check emergency procedures and first aid arrangements are included and site-specific.
Confirm the method statement will be briefed to every worker before the task starts.
Return inadequate method statements with clear feedback on what needs improving.
Update method statements when work conditions change or incidents reveal new hazards.
Keep approved method statements accessible on site throughout the work activity.

DON'T approve method statements without reading them thoroughly for completeness.
DON'T accept an illogical or incomplete work sequence — it creates unsafe gaps.
DON'T approve without checking that resources and competent persons are confirmed.
DON'T accept generic hazard lists — controls must address this site's specific conditions.
DON'T approve documents that list PPE generically without linking it to each work phase.
DON'T accept method statements without emergency procedures for the specific task.
DON'T file method statements without confirming workers will be briefed before starting.
DON'T reject documents without telling the subcontractor exactly what needs improving.
DON'T continue using outdated method statements after conditions on site have changed.
DON'T lock approved method statements in the office — they must be at the point of work.

See also: Subcontractor RAMS Review | Pre-Task Briefing Best Practice

Presenter		Project
Location		Date

Toolbox Talk Record