Risk assessment or method statement? Know the difference.
Understand how a risk assessment and a method statement differ, how they work together, and how to keep their revisions aligned.
Two documents, two questions
A risk assessment asks what could cause harm, who could be affected and what controls are needed. A method statement explains the working sequence and how the team will apply the relevant controls. They should inform each other, rather than repeat the same paragraphs.
The HSE guidance linked below explains risk management and construction method statements for Great Britain. The documents required for a particular activity depend on the work and the rules that apply to it; a generic RAMS template is not a universal answer.
The assessment sets out the risks
A useful assessment makes the reasoning clear. Someone reading it should be able to connect a hazard with the people exposed and the measures proposed to control it. Do not rely on a colour or score without explaining what the team will actually do.
For document control, keep the context close to the assessment: activity, location, owner and revision. Those details help a reviewer identify whether the assessment still describes the work being planned.
- Describe the task and the people affected.
- Identify relevant hazards and controls.
- Record who needs to act on the findings.
- Review the assessment when the circumstances change.
The method describes the sequence
The method statement turns planning into a sequence the team can follow. It can bring together preparation, equipment, responsibilities and the controls relevant to each part of the work. A clear order is more useful than a long collection of disconnected precautions.
HSE distinguishes between activities with specific written-arrangement requirements and the wider use of method statements as a planning tool. Avoid claiming that every construction activity has the same document requirement. Explain why a statement is needed for the particular work.
Example: changing the access arrangement
Consider a team preparing a maintenance activity. Their assessment identifies risks associated with reaching the work area. The method sets out the planned access sequence and the arrangements the team will use. These are connected ideas, but they serve different reading needs.
If the route or access equipment changes, review the implications in both records. Updating only the working sequence can leave an older assessment describing different conditions. Sending a new assessment without the corresponding sequence creates the opposite problem.
Keep the pair aligned
Treat the pack as a controlled set. Use related revision identifiers, a named reviewer and a clear issue status. Store comments and decisions with the version they concern. When a change affects the briefing, make that connection explicit.
A final check can be simple: can the supervisor identify the current pack, explain what changed and find the record of the team briefing? If that takes a search through several inboxes, improve the record structure before adding more text.
The RAMS module brings review, distribution and acknowledgement into the same workflow. An audit trail then helps the team follow changes without treating an approval click as a substitute for a safety decision.
Sources and further reading
Primary guidance checked on 17 October 2026. Refer to the source for its current wording and scope.