Writing RAMS That Get Accepted First Time

Why RAMS Get Rejected

I've reviewed hundreds of RAMS submissions over the years, and the same problems come up again and again. Generic content copied from a previous job without changing the site name or the dates. Risk assessments that list hazards without linking them to specific control measures. Method statements that describe the work in three vague sentences when the task is actually complex and multi-stage. Missing signatures, missing appendices, wrong revision numbers. And the classic: a 40-page document where 35 pages are company policies and only 5 pages actually describe the work.

The principal contractor's safety team doesn't reject RAMS to be awkward. They reject them because they need to be able to stand in front of an HSE inspector and say "yes, we reviewed this document and we were satisfied that the contractor understood the hazards and had a safe system of work." If the RAMS doesn't demonstrate that, it's going back.

Structure Is Everything

A good RAMS follows a logical structure that mirrors how the work actually happens. Here's what most principal contractors are looking for:

Scope and description. What exactly are you doing, where, and when? Be specific. "Installation of 225mm HDPE pipework from MH14 to MH17 including excavation, pipe laying, jointing, backfill, and reinstatement" is useful. "Pipework installation" is not.

Sequence of operations. Step by step, what happens first, what happens next, what happens last? Each step should be a distinct activity with its own hazards and controls. Think of it like a recipe — someone unfamiliar with the task should be able to read it and understand the process.

Risk assessment. For each significant hazard, identify the risk, score it, describe the control measures, and rescore the residual risk. The scoring system doesn't matter as much as the thought behind it. A 5x5 matrix where every risk is scored 2x2 after controls is as useless as no risk assessment at all.

Resources. People, plant, materials, permits, certificates, training records. If the job needs a CPCS-qualified operator, say so. If it needs a confined space entry permit, say so and reference the permit process.

Emergency procedures. What happens if it goes wrong? Not your company's generic emergency plan — the specific response for this task on this site. If someone falls into a trench, who does what? If there's a gas strike, who calls who?

Using AI to Get the First Draft Right

This is where tools like Ebrora's RAMS Builder earn their keep. You answer a set of structured questions about the task, the location, the hazards you've identified, and the team doing the work. The AI generates a complete RAMS document with a proper sequence of operations, a populated risk assessment matrix, control measures matched to the identified hazards, and all the standard sections that principal contractors expect to see.

The output is a Word document you can edit, add to, and put your company branding on. It's not a finished product — you still need to walk the route, check the site conditions, and add the detail that only someone who's been on the ground can provide. But it saves you three or four hours of writing, and more importantly, it ensures the structure is right so the document doesn't get bounced for missing sections.

If you've already got a RAMS and want a second opinion before submitting, the RAMS Review Tool checks your document against common rejection criteria and flags gaps. Think of it as a pre-submission audit.

Common Fixes That Prevent Rejection

Make sure the RAMS is site-specific. Search the document for the name of the last site you worked on — you'd be surprised how often it's still in there. Dates, locations, personnel, plant items — they all need to match the current job.

Include the permit requirements. If the work involves hot works, confined space, excavation, or isolation of services, reference the specific permit-to-work process that applies on this site. Don't just say "permits will be obtained" — describe the permit process and who authorises it.

Attach the relevant CPCS/CSCS cards, training certificates, and insurance documents as appendices. If the principal contractor has to chase you for these, they'll delay acceptance even if the RAMS itself is fine.

Get it reviewed internally before submission. A fresh pair of eyes catches things the author misses. Your site manager or H&S advisor should read it, challenge it, and sign it off before it goes to the PC.

The Review Conversation

When RAMS do come back with comments, treat it as a collaboration, not a confrontation. The reviewer is telling you what they need to see to be comfortable authorising the work. Respond to each comment specifically, don't just resubmit the same document with minor tweaks, and keep a revision log so everyone can see what changed and why. That professionalism matters — it builds trust, and trusted subcontractors get their RAMS accepted faster on the next submission.

If you're spending entire evenings writing RAMS for the next day's work, something's gone wrong with your planning. RAMS should be prepared well in advance, reviewed without time pressure, and submitted with enough lead time for the PC to review them properly. Rushing RAMS leads to mistakes, and mistakes lead to rejection. Plan it, write it, check it, submit it — and let a tool like the RAMS Builder handle the heavy lifting on the draft.