Why do RAMS get signed off without being read properly?

What happens when a RAMS arrives for review?

A subcontractor is due on site on Monday. On Friday afternoon their office emails a PDF to your site manager: the risk assessments and method statement for the package, with COSHH assessments, training records and data sheets attached to the back. It runs to dozens of pages. The site manager forwards it to the SHEQ adviser, who covers several sites and already has a queue of the same.

The reviewer opens it between other jobs. They check the cover for the right site name, scroll to the sequence of work, look for the two or three things they always look for, and sign. The gang is inducted on Monday and the file records that the RAMS was reviewed.

Nobody in that chain was careless. The reviewer did what the time allowed. But the signature now claims something that did not happen: that a competent person tested the document against this site, this task and these people.

Why does a competent reviewer still miss things?

Because the review is three comparisons at once, and the material to compare against is not in the document. To judge whether the method fits the site, the reviewer needs the site rules, the asbestos information, the services drawings and what other trades are doing that week. To judge the task, they need the scope of the order that was actually placed. To judge the people, they need to know who is turning up and what training they hold. Most of that sits in other folders, other systems or the site manager's head.

So the reviewer falls back on habit. One always checks work at height. Another goes straight to electrical isolation. A third looks hardest at lifting. Each is right to, and each leaves a different set of pages unread. The business ends up with as many review standards as it has reviewers, the pattern we describe in the variation nobody agreed to.

Length makes it worse. Much of a typical submission is generic: company policy, standard assessments carried over from the last job, pages of data sheets. The few paragraphs specific to this job are buried in it. A reviewer who has seen the same boilerplate many times learns to skim, and skimming is how a line that still names the previous site gets through. We cover how those lines get there in the risk in copy and edit. On a facilities management contract, where one generic document may be reused across many buildings, the specific part is all that matters: which plant room, which isolation, who else is in the building.

Why does the timing work against the reviewer?

RAMS tend to arrive late because the start date is the only deadline that bites. By the time the document reaches the reviewer, rejecting it has a visible cost: a gang standing at the gate, a programme slipping, a client asking why. Accepting it costs nothing on the day.

A reviewer who sends a document back needs a specific reason they can defend to the contracts manager in one sentence. Without a list, finding that reason means reading the whole thing properly, which is the time they do not have. So the default becomes acceptance with a general comment that nobody chases.

For a finance or operations director this reaches beyond the site. A signed review is a record the business will be asked to stand behind after an incident, in a client audit or by an insurer. A signature that cannot be backed by what was checked is a liability sitting in the file.

What should every RAMS be checked against?

The fix starts with a written list that every reviewer uses on every submission. The one below is a starting point to adapt with your SHEQ lead. It does not replace judgement. It makes sure judgement is applied to the same questions each time.

Against the site

• The site name, address and client are correct throughout, not only on the cover.
• Access, delivery and storage arrangements match the site rules and current logistics.
• Known site hazards are addressed: asbestos information, live services, occupied areas, other trades nearby.
• Emergency arrangements, first aid and welfare refer to this site.

Against the task

• The scope described matches the order or package that was placed.
• The sequence covers every stage, including delivery, access, testing and clearing up.
• Every hazard raised in the sequence has a control in the risk assessment, and every control is something the gang can actually do here.
• Permits are identified where the work needs them, such as hot works, confined spaces or isolations.
• Substances, plant and lifting operations named in the method have their supporting assessments or plans attached.

Against the people

• A supervisor is named and will be present.
• Competence cards and training records are in date and relevant to the task described.
• The document says how operatives are briefed and how they sign to confirm it.

Against the document itself

• It carries a revision number, a date, an author and an approver.
• The revision reviewed is the revision that will be on site.

Try it on the last few submissions your team accepted. The gaps it finds are the measure of the problem.

How does the review run once it is rebuilt?

A list on paper helps, but it still depends on a busy person finding the time. The stronger version has every submission read against the list before the reviewer opens it. That is the job of a risk assessment review system. It reads the document alongside the site information, the package scope and the training records the business already holds, applies the same fixed checks every time, and lists each gap with the reason and the page it was found on.

The reviewer starts from that list, not from page one. Section four refers to a different site. The sequence includes hot works and no permit is mentioned. Two operatives' cards expire before the planned finish. Each is a plain statement they can confirm against the page and return to the subcontractor while there is still time to put it right.

Who decides does not change. Risk assessments and method statements are written and approved by competent people. The system reads, checks and flags. It makes no safety decision and accepts or rejects nothing. The competent person works through the flagged points, applies their own judgement to the rest, and signs. Every check and decision is recorded, so the audit trail sets out what was tested, not only that a signature exists.

The same approach carries to the paperwork around the RAMS: subcontractor vetting, compliance evidence and inspection records once work is under way.

Where should you start?

Start with the list, because it costs nothing and exposes the gap. Agree it with the people who review, use it on every submission that comes in, and note how often a document fails a check it would previously have passed.

Then count the time. Reviewer hours a week, multiplied by the number of reviewers, by their hourly cost and by 46 working weeks, gives the yearly cost of review as it runs now. The audit runs the same sum across the rest of your admin and names the process to tackle first. If that turns out to be RAMS review, the checks are already written down.