RAMS quality versus box-ticking: what a genuinely good one looks like next to a bad one

RAMS exists to make a specific task genuinely safer, not to satisfy a checklist item before work can start — but under review-time pressure, on a busy site with dozens of documents to get through, it's easy for the review itself to slide into a formality: confirming a RAMS exists and is formatted correctly, rather than genuinely testing whether it would actually protect anyone.

What box-ticking looks like from the inside

A box-ticking review checks that sections are present — hazards listed, control measures named, a method described — without asking whether any of it is actually specific to the job at hand. A RAMS that would apply equally well to any site, for any client, doing broadly the same trade of work, has almost certainly passed this kind of review before, and will again, because nothing about the review actually tests for genuine specificity.

What a genuine review actually asks

A reviewer testing for quality, not just presence, asks a different set of questions: does this RAMS reference the actual site conditions — the real access route, the real nearby hazards, the specific equipment that's actually on order rather than a generic type? Does the method statement's sequence of steps genuinely match the risk assessment's control measures, or do the two read as if they were written by different people working from different templates? Would a competent operative reading this document actually be able to follow it as instructions, or does it read as a summary written after the fact to describe work that's already been planned informally?

A worked example — two RAMS for the same task

Two roofing subcontractors submit RAMS for near-identical work on different projects. Both list working at height as a hazard and appropriate PPE and edge protection as a control measure — on paper, indistinguishable. The first document stops there. The second specifies the actual edge protection system being installed, references the specific roof pitch and its effect on standing surface, names who's responsible for checking weather conditions before work starts each morning, and describes exactly how materials will be lifted to roof level. Both would pass a box-ticking review. Only the second is telling a site manager anything that would actually change how the work gets watched, or genuinely prepare the crew for the specific job in front of them.

Why box-ticking review is the more dangerous failure mode

It's tempting to think a missing RAMS is the bigger risk — and it is a serious one — but a bad RAMS that's been formally approved is arguably worse, because it creates false confidence. A missing document is visibly a gap; an approved-but-generic one looks, on the surface, like the risk has been properly assessed and controlled, when in practice nobody has actually thought through the specific hazards of that specific task on that specific day.

Building genuine review into a busy schedule

The honest constraint here is time — a site manager reviewing a dozen RAMS in a morning, alongside everything else the role involves, doesn't have the capacity to interrogate every document with the same depth. What tends to work better than trying to review everything equally deeply is triaging: applying real scrutiny to higher-risk tasks and to subcontractors whose previous RAMS have been thin, while accepting a lighter check is reasonable for routine, lower-risk, well-established work from a subcontractor with a genuinely strong track record. This connects to the same underlying judgement that matters in subcontractor competence assessment more broadly — treating every case identically regardless of actual risk wastes scrutiny where it matters least and starves it where it matters most.

Common mistakes

• –Checking a RAMS is present and formatted correctly without reading whether the content is genuinely specific to the task
• –Approving a RAMS because the subcontractor is trusted, without reading the document on its own merits
• –Not noticing when the method statement and risk assessment sections don't actually connect to each other
• –Applying the same light-touch review to every RAMS regardless of the task's actual risk level
• –Treating a formally approved RAMS as proof the risk has genuinely been thought through, rather than one signal among several
• –Giving feedback that a RAMS is rejected without specifying what genuinely needs to change, leaving the subcontractor to guess