Why Documentation Gets Rejected — and How to Pass First Time

Almost every contractor who's worked commercially has had a RAMS submission sent back at least once. It's rarely because the work itself was unsafe — it's almost always something in the document itself that gave a reviewer a reason to say no. This part is about the specific, recurring reasons documentation gets rejected, and what changes when a contractor consistently passes first time.

Chapter 11 — Why documentation gets rejected

The same handful of reasons come up again and again, and most of them are avoidable without changing how the work itself is actually done:

• Generic content — a document that reads like it could apply to any site, because it hasn't actually engaged with this one.
• No site-specific detail — missing site address, access arrangements, or hazards specific to this location.
• Risk assessment and method statement don't align — a control measure named in one that doesn't visibly appear in the other.
• Missing or unclear emergency procedures — generic instructions instead of this site's actual arrangements.
• No evidence of briefing — a document without a sign-off sheet proving the team has actually seen it.
• Submitted too late for proper review — leaving no time for questions or revisions before the work is due to start.
• Illegible or unclear — a handwritten or badly formatted document that's technically complete but genuinely hard to review.

None of these reflect the quality of the actual work being planned. They reflect the quality of the document describing it — which is exactly why they're frustrating, and exactly why they're fixable.

Chapter 12 — Passing first time

The contractors who consistently pass first time tend to share a few habits, none of which require more time spent on the actual writing:

Submit early. A document submitted with time to spare gives a reviewer room to ask a clarifying question and get an answer before the job's due to start. A document submitted the morning work begins gives them no room to do anything except reject it and stop the job.

Read what's actually being asked for. Principal contractors often have their own documentation requirements or pre-qualification packs. Assuming a standard submission will be accepted, without checking what this particular project expects, is a common and avoidable cause of rejection.

Get a second read before submitting. A colleague reading a RAMS cold will often catch the same gaps a reviewer would — a missing site detail, an emergency procedure that's clearly generic, a contradiction between two sections.

A good master document, adjusted properly for each site, will out-perform a rushed original every time.

Treat rejection as information, not judgement. A returned document with comments is telling you exactly what to fix. Keeping a short internal note of what's been flagged before — and checking new submissions against it — turns a recurring frustration into a one-time fix.

The full series

Seven parts. Each part stands alone; together they build a complete commercial documentation system.