RAMS pre-submission checker

Why RAMS get sent back

For most small firms and sole traders, the painful part of a RAMS isn't writing it — it's the submit, reject, resubmit cycle. You send a document to the principal contractor, it gets bounced with a few lines of feedback, you patch it and resend, and work can't start until it clears. The most common reason is the same every time: the document reads as generic. It could describe any job on any site, so the reviewer can't be confident it reflects the work that's actually about to happen.

This checker walks your document through the checks reviewers make first, so you can catch those gaps before someone else does. It's designed to catch the common reasons documents get sent back — it does not certify your RAMS or guarantee it will be accepted. Acceptance is always the principal contractor's decision.

The three reviewers, and what each one tests

It helps to know who is actually checking your paperwork, because they test different things:

• The legal baseline (HSE). A risk assessment that is "suitable and sufficient" and a method statement that is clear, site-relevant and free of vague generalisations. For construction, this sits inside CDM 2015 and the construction phase plan.
• The accreditation schemes (CHAS, SMAS, Constructionline and similar). These assess your company's system — that you have a process that reliably produces site-specific RAMS — usually by sampling a few recent documents.
• The principal contractor (the hard gate). This is where the resubmission pain lives. They review one specific job's RAMS before work starts, activity by activity, against a detailed checklist of their own. A document that passes the first two can still be bounced here.

What reviewers look for first

Across all three, a handful of things clear most gates — and their absence accounts for most rejections:

• Site-specific detail. The single biggest factor. The document has to name this site, this task, these dates and these conditions — not a previous job's details left in by accident. A two-year-old assessment with another site's address is a red flag to any competent reviewer.
• Controls that can be supervised. "Take care" and "wear PPE" aren't controls a supervisor can check. Reviewers want the specific control, who does it and when.
• The hierarchy of control applied. Leaning on PPE alone, rather than eliminating or reducing the risk first, is a common rejection.
• Risk shown before and after. The scoring should show the initial risk and the residual risk once controls are in — residual-only scoring gets sent back.
• Named, competent people. A named supervisor and operatives with the right cards or qualifications, plus evidence the workforce was briefed.
• Signed, dated and version-controlled. Without these it isn't a controlled document, and an uncontrolled document isn't accepted.

The checklist above groups these into the sections a reviewer works through — document control, site specifics, hazards, controls, method, people and emergency arrangements — and flags the items that trigger an outright rejection as essential. Cover the essentials, tidy the rest, then have a competent person make the final call before you submit.