Learn · rejection

How to Resubmit a RAMS After It Has Been Rejected

Getting a RAMS rejected is frustrating, especially when you are under pressure to start on site. The good news is that most rejections come down to a small set of fixable problems. Understanding what reviewers are actually looking for, and responding to feedback in a structured way, will get you back on track far more quickly than simply resubmitting the same document with minor tweaks.

Understand What a RAMS Reviewer Is Looking For

A RAMS is a Risk Assessment combined with a Method Statement. The risk assessment element sits under the Management of Health and Safety at Work Regulations 1999, regulation 3, which requires a suitable and sufficient assessment of the risks to workers and others affected by the work. The method statement describes, step by step, how the work will actually be carried out safely.

A principal contractor or client reviewing your RAMS is checking whether it demonstrates that you have genuinely thought about this specific job, not just copied a template. Reviewers are also checking that they can discharge their own duties by satisfying themselves that your RAMS is fit for purpose. CDM 2015 applies to all construction work, not only to larger projects that have to be notified to the HSE, and a principal contractor has to be appointed whenever more than one contractor is involved.

Read the Rejection Feedback Carefully

Before changing anything, read every comment. Rejection feedback is usually one of three types:

  • Factual errors or omissions: missing task steps, wrong legislation cited, no mention of specific site hazards.
  • Insufficient detail: controls described at a level too vague to be useful (for example, "follow safe working practices" tells nobody anything).
  • Document administration failures: unsigned, undated, no revision number, wrong company name, or not specific to the actual site address.

Write down each point raised. If the feedback is unclear, contact the reviewer before you start revising. A short phone call or email asking for clarification is not a sign of weakness; it saves everyone time.

The Most Common Reasons for Rejection

ReasonWhat to fix
Generic template, not site-specificName the site, the structure, the exact task and the location within the building or plot
Hazard list does not match the methodIf your method says you will use an angle grinder, the hazard section must address disc failure, sparks, noise and vibration
Controls do not follow the hierarchyEliminate first, then substitute, then engineering controls, then administrative controls, then PPE last. PPE-only responses to serious hazards will almost always fail
No competency evidenceState relevant qualifications, tickets (IPAF, PASMA, CSCS, gas safe registration and so on) held by the operatives doing the work
Work at height not addressed adequatelyThe Work at Height Regulations 2005 require collective protection (edge protection, safety nets, working platforms) to be considered before personal fall protection
COSHH not coveredIf you are using or generating hazardous substances, including dust, fumes, solvents or adhesives, the Control of Substances Hazardous to Health Regulations 2002 apply and your RAMS must identify the substance, the risk, and the controls
No emergency arrangementsWhat happens if someone is injured? Who calls the emergency services, where is the nearest hospital with A&E, where is the assembly point?

Revising the Document Systematically

Work through the rejection comments one by one. For each:

  1. Identify which section of the RAMS it relates to.
  2. Make the specific change needed, rather than rewriting sections that were not flagged.
  3. Cross-check that the change is consistent with the rest of the document. Adding a new hazard, for example, means you must also add controls and check the method steps reflect those controls.

Once you have made all the changes, read the whole document from start to finish as if you were the reviewer. Ask yourself: if I were a competent person who had never been to this site, would this document tell me everything I need to work safely?

Update the Version Control

Every time a RAMS is revised it must carry a new revision number or version letter, the date of the revision, and a brief note of what changed. This matters for two reasons. First, it shows the reviewer that this is a deliberate resubmission, not the same document re-sent by mistake. Second, if there is ever an incident, a clear revision history demonstrates that the document was actively managed.

Resubmitting Formally

Do not just email the file again without context. Send a short covering note that:

  • States this is a resubmission of the RAMS for the specific task and site.
  • References the revision number and date.
  • Briefly summarises the changes made in response to the rejection comments.

This makes the reviewer's job straightforward and signals that you have engaged seriously with the feedback.

Brief Your Operatives Before Work Starts

A revised and accepted RAMS only adds value if the people doing the work have read it and understood it. Get operatives to sign the RAMS to confirm they have been briefed on the method and the controls. Keep those signed copies. If the scope of work changes on site in any material way, the RAMS must be reviewed and updated before that new work begins, not after.

Rejection is part of the quality process, not a personal criticism. Treat it as useful information, address each point methodically, and your resubmission should sail through.

Need the document itself?

RAMSReady generates RAMS, risk assessments, method statements, COSHH and fire risk assessments to the correct published standard, or check your existing one free.

More from the RAMSReady library