Five RAMS Mistakes That Are Costing You Site Time

RAMS gets blamed for slowing sites down. It isn't the document that costs you time — it's a bad one, discovered at the worst possible moment: mid-inspection, mid-incident, or mid-argument with a principal contractor who's just asked to see it. Here are the five mistakes we see most, and what to do instead.

01 — Copying last job's RAMS

Same trade, different site, different hazards — different access, different ground conditions, different neighbours. A recycled RAMS technically exists but doesn't describe the job in front of you, which means it protects no one if something goes wrong. Ten minutes rewriting the hazard section for the actual site beats an hour explaining afterwards why it didn't match.

02 — Writing it for the auditor, not the crew

A RAMS stuffed with regulation numbers and no plain instructions passes a desk check and fails on site, because the person doing the work can't act on it. If an apprentice can't read a hazard and know exactly what to do differently because of it, the document hasn't done its job yet.

03 — No proof anyone read it

A briefing that happened but wasn't signed and dated didn't happen, as far as anyone checking later is concerned. A sign-off sheet takes thirty seconds per person and is the difference between "we briefed the team" being a fact and being a claim.

04 — Never updated when the job changes

Scope creeps: a bit more depth, a section of scaffold that wasn't there Monday, a delivery blocking the usual access route. The RAMS from week one doesn't cover week three unless someone deliberately goes back and updates it. Build a five-minute review into every toolbox talk, not just the start of the job.

05 — Treating it as a one-off instead of a live document

Filed in a folder and forgotten is the most common failure of all. RAMS that only gets looked at again when someone asks for it isn't managing risk, it's managing paperwork. The sites with the fewest incidents treat it as something to revisit out loud, not just store.

"A RAMS document nobody's read is just paperwork with your name on it."

— Danny Whitlock, Site Safety Contributor