The most common gaps in RAMS documents (and why reviewers miss them)
Construction compliance
Across a wide range of UK construction RAMS documents, a clear pattern emerges: the same handful of gaps appear again and again, in documents from experienced contractors and new ones alike. None of them are exotic. All of them are easy to miss when you're reviewing your twelfth document of the day.
1. Hazards without matching control measures
A hazard gets identified in the register, but no corresponding control measure is ever documented for it. It's an easy gap to introduce when a document is edited in stages, and an easy gap to miss because the hazard register and control measures section are often pages apart.
2. PPE doing the job of engineering controls
The hierarchy of control exists for a reason — PPE is the last line of defence, not the first. Documents that lean on PPE as the primary control for a high-risk activity, without engineering or administrative controls being considered first, are one of the most common findings in any thorough review.
3. Vague control measures
“Take care” and “be aware of surroundings” show up more often than you'd think. They read as reasonable in isolation but give an operative nothing specific to act on, and would not withstand scrutiny in an audit.
4. Plant listed in scope but missing from the hazard register
Scope of works gets finalised late, after the hazard register was drafted, and the two never get reconciled.
5. Emergency procedures that aren't site-specific
A generic emergency procedure copied from a template rather than written for the actual site — no named muster point, no nearest hospital, no named first aider.
6. Outdated revision history
Often the first sign a document has been reused from a previous project without a proper review pass.
None of these are complicated to fix once they're spotted. The hard part is spotting them consistently, on every document, every time — which is exactly the problem a structured second read is built to solve.
How to write a Method Statement that survives scrutiny
Document writing
A Method Statement isn't written to satisfy a checklist. It's written to be the document someone reads line by line after something has gone wrong — whether that's an HSE inspector, a principal contractor's compliance team, or a solicitor. Writing with that reader in mind changes what a good one looks like.
Be specific about sequence
A method statement that describes an activity in general terms (“excavate and install pipework”) rather than as a sequence of discrete, ordered steps gives no basis for identifying where in that sequence a hazard actually arises.
Match control measures to the actual hierarchy of control
Before PPE appears anywhere in a control measure, elimination, substitution, engineering controls and administrative controls should have been genuinely considered — and it should be obvious from the document that they were.
Cross-reference, don't duplicate carelessly
Plant, materials, and hazards should be consistent across every section that mentions them. Reusing a previous document as a template is fine — reusing it without reconciling scope, hazards and controls against each other is where inconsistencies creep in.
Write emergency procedures for this site, not any site
Name the muster point. Name the nearest hospital. Name who is the first aider on this job, not “the appointed first aider.”
None of this is about writing more — it's about writing specifically. A shorter method statement that's specific and internally consistent will survive scrutiny better than a long one that isn't.
A practical construction compliance checklist for site managers
Site management
When an auditor picks up a RAMS document, they tend to check things in a fairly predictable order. Reviewing your own documents in that same order before they leave your desk catches most problems before anyone else sees them.
1. Does the scope of works match reality?
Check the scope against what's actually planned on site — plant, materials, sequence — before checking anything downstream of it.
2. Is every hazard in the scope reflected in the hazard register?
Walk the scope of works line by line and confirm every activity has a corresponding entry.
3. Does every hazard have a control measure, and is it specific?
No hazard should be left without a control measure, and no control measure should be vague enough that two people could disagree on what it actually requires them to do.
4. Does PPE match the hazards — and is it the last line, not the first?
Check PPE requirements against the hazard register, and check that it isn't standing in for controls that should come earlier in the hierarchy.
5. Are emergency procedures specific to this site?
Muster point, first aider, nearest hospital — named, not generic.
6. Is the revision history current?
A quick check, but a telling one. An outdated revision history is often the first sign a document wasn't reviewed properly for this project.
Run through these six checks on every document before it goes out, and you'll catch the majority of what an auditor would catch — before they do.