A practical guide to RAMS on site
Connect risk assessments and method statements to review, briefing and acknowledgement, with a practical document-control workflow.
What RAMS means
RAMS is a common construction abbreviation for risk assessments and method statements. Together, they connect the risks of a task to a proposed way of carrying it out. A usable RAMS pack helps the team understand the work before it starts.
This guide explains an organisational workflow. For the underlying safety requirements, use the HSE sources below, which cover Great Britain. Check the guidance that applies to the location and nature of your work.
Start with the actual task
Begin with a short description of the activity, its location and the people involved. Give the reviewer enough context to recognise the work. A title such as ‘maintenance’ is less useful than a description that identifies the asset, access arrangements and planned activity.
A template can provide structure, but copying a previous job without checking its assumptions creates an unreliable starting point. Ask what has changed: the site, equipment, people, sequence or surrounding activity. Record the changes before sending a pack for review.
- Identify the work area and scope.
- Link the relevant workforce and asset records.
- Name the document owner and reviewer.
- Give the revision a clear identifier.
Review one current version
Send a single current version through the review process. If comments arrive by email or telephone, capture their outcome in the record so the next person can understand what changed. Keep superseded revisions available as history, while making their status clear.
HSE describes method statements as a way to communicate the planned working sequence and control measures. Reviewing the document should therefore include checking whether it is understandable to the people doing the work, rather than only whether every box contains text.
Connect approval to the site briefing
An approved document sitting in an office folder does little to help a supervisor preparing the team. Make the current pack accessible where the work is organised, and connect the briefing record to the version discussed.
Acknowledgement records help show who received information. They do not, by themselves, demonstrate understanding or that controls were followed. Leave room for questions and record changes that need to return to the reviewer.
Example: a revised work sequence
Imagine a supervisor learns that a planned access route is unavailable. The useful record is a chain of decisions: the change was raised, the pack was revised, the reviewer considered it, and the team was briefed on the new version before the affected work resumed.
Keeping those actions together makes a later review easier. A shared system can connect the document, people and timestamps; the responsible people still need to assess the change and make the appropriate working arrangements.
Keep a record you can use again
Close the loop after the task. Note whether the document needed further changes and make the final record easy to retrieve by site or activity. A useful review asks what the next team should learn, not simply whether the pack was filed.
In TheContractorsToolbox, RAMS workflows connect creation, approvals, worker acknowledgements and revision history to shared records. That reduces the need to reconstruct a document's path from separate messages.
Sources and further reading
Primary guidance checked on 17 October 2026. Refer to the source for its current wording and scope.