What Makes a RAMS Fail an Inspection – Common Failures Explained
A RAMS – your Risk Assessment and Method Statement combined – is one of the first documents a principal contractor, CDM coordinator or HSE inspector will ask for on site. Getting it wrong doesn't just mean paperwork bouncing back; it can mean a prohibition notice, a delayed start, or worse, a worker hurt because the hazards were never properly thought through. Here is what actually causes a RAMS to fail, and what you can do about it.
Understanding What a RAMS Is (and Isn't)
A RAMS is two separate documents working together: a risk assessment (required under Regulation 3 of the Management of Health and Safety at Work Regulations 1999) and a method statement (the step-by-step sequence of work that shows how you will manage those risks in practice). Neither one alone is sufficient. A risk assessment without a method statement leaves the reader with no confidence the controls will actually be applied on site.
The Most Common Reasons a RAMS Gets Rejected
1. It's Generic and Clearly Not Site-Specific
This is the single biggest failure. A RAMS downloaded from the internet or copied from a previous job without amendment is immediately obvious to any experienced inspector. If it references a different site, a different task, or simply lists every conceivable hazard with no relevance to the actual work, it signals that no genuine risk assessment has taken place.
Fix it: Name the site, the specific task, the relevant dates, and the real conditions — confined spaces, proximity to the public, working at height, overhead services. The detail must reflect the actual job.
2. Hazards Identified but Controls Are Vague or Missing
Listing "manual handling" as a hazard and writing "take care" as the control is not a control measure. It tells a worker nothing useful and demonstrates no understanding of the hierarchy of control: eliminate the risk first, then substitute, then engineering controls, then administrative measures, and finally PPE as a last resort — not a first response.
Fix it: For each hazard, state the specific control. For manual handling, that might mean mechanical aids, reduced load weights, team lifts, or revised task sequencing. For working at height under the Work at Height Regulations 2005, "use a harness" is not enough — you need to show why collective protection (guard rails, scaffolding, MEWPs) was considered first.
3. Risk Ratings That Don't Add Up
Marking a task as high likelihood and high severity — then recording a residual risk that is somehow "low" with no meaningful controls listed in between — destroys credibility. Inspectors look at whether the risk rating journey makes sense.
Fix it: Your residual risk score should only drop once you have listed controls that genuinely justify that reduction. Be honest: if the risk remains medium after all reasonably practicable controls, say so.
4. The Method Statement Doesn't Match the Risk Assessment
The two halves of a RAMS must join up. If your risk assessment identifies a particular chemical hazard under COSHH 2002 but your method statement says nothing about ventilation, exposure limits, or the safe disposal of waste, you have a disconnect that any inspector will flag.
Fix it: Cross-reference as you write. Every significant hazard in the risk assessment should have a corresponding control visible somewhere in the method statement's sequence of work.
5. Competence and Supervision Not Addressed
Who is doing the work? Who is supervising? What qualifications, tickets or training do they hold? A RAMS that doesn't name or describe the competence requirements for the task gives no assurance that a suitably trained person will actually be there.
Fix it: Include roles, responsibilities, and relevant competencies. For electrical work, that means appropriate qualification. For working at height, relevant training. Don't name individuals where the workforce changes — describe the required competence instead.
6. No Emergency Arrangements
What happens if something goes wrong? A RAMS with no reference to first aid, emergency contacts, rescue procedures (particularly for work at height or confined spaces), or site evacuation routes is incomplete.
Fix it: Even a brief section covering first-aid provision, nearest hospital, emergency communication and the rescue plan for high-risk tasks is enough to demonstrate the work has been thought through end to end.
7. Not Signed or Not Communicated to the Workforce
A RAMS that sits on a server somewhere and has never been read by the people carrying out the work is not functioning as a safety document. Inspectors regularly ask workers what's in the method statement. Blank faces are a problem.
Fix it: Brief the RAMS before work starts, record who attended, and get signatures. Keep a copy accessible on site.
A Quick Reference: Common Failure Points
| Failure | What the Inspector Sees |
|---|---|
| Generic, unedited template | No genuine assessment carried out |
| Vague controls | Hierarchy of control ignored |
| Disconnected RA and MS | Controls won't work in practice |
| Inflated residual risk reductions | Ratings not credible |
| No competence requirements | No assurance of safe workforce |
| No emergency plan | Incomplete planning |
| Not briefed to workers | Document exists; safety doesn't |
The Underlying Standard
The HSE's test under the Management of Health and Safety at Work Regulations 1999 is whether the risk assessment is suitable and sufficient. That phrase means proportionate to the risk, specific to the task, and genuinely useful to the people doing the work — not a box-ticking exercise for the project file.
Getting a RAMS right from the start saves time, protects workers, and keeps a job moving. Getting it wrong costs more than the time it would have taken to do it properly.