Why RAMS Get Rejected by Principal Contractors (And How to Fix It)

Your RAMS came back. Again. No work starts, your operatives are standing by, and a terse email from the PC's site manager says "insufficient — please resubmit." If you don't know exactly what failed or why the PC could not accept it, the second submission is likely to hit the same wall.

This page maps every common rejection reason to the PC coordination duty or contractor planning duty it compromises — so you understand you are not dealing with personal preference or bureaucratic box-ticking. It then shows you, with a concrete worked example, what "site-specific" actually looks like on paper, and gives you a resubmission cover note you can adapt immediately.

---

The Principal Contractor's Legal Position: Why They Cannot Simply Wave RAMS Through

Principal contractors reject RAMS because accepting a deficient document creates obvious coordination and enforcement risk. CDM 2015 places duties on the principal contractor to plan, manage, monitor and coordinate the construction phase, including ensuring that workers carry out work in accordance with the construction phase plan (CDM 2015). CDM 2015 also requires the principal contractor to ensure that all contractors are provided with the parts of the construction phase plan that are relevant to the work they are to carry out (CDM 2015).

If a PC accepts RAMS that describe no dust suppression for silica-generating work, no emergency procedure, or controls that plainly do not match the site conditions, it becomes difficult to show that the work was properly coordinated against the construction phase plan and site rules. Rejection, therefore, is the PC protecting workers and maintaining a defensible management process — not a stylistic preference.

At the same time, CDM 2015 requires that every contractor plan, manage and monitor construction work carried out either by the contractor or by workers under the contractor's control, to ensure it is carried out without risks to health and safety so far as is reasonably practicable (CDM 2015). The RAMS document is the usual evidence submitted to show that duty is being addressed. A generic or incomplete document does not demonstrate it — it undermines it.

---

The 10 Most Common RAMS Rejection Reasons — Mapped to What They Breach

The table below is the core of this page. Each rejection reason is named, the duty or review concern it compromises is stated, and the minimum fix is given. Use it as a pre-submission audit before you click send.

#	Rejection Reason	Why the PC Is Likely to Reject It	Minimum Fix Required
1	No site address or project reference	The document cannot be matched to the construction phase plan for this specific project, undermining the PC's coordination duty under CDM 2015.	Add the full site address, project name, and PC's contract reference on the cover page.
2	Hazard list copied verbatim from a template with no site context	Generic hazards that bear no relationship to the actual site conditions mean the contractor has not planned the specific work — a direct gap in the contractor's own CDM 2015 duty.	Walk the specific site. Replace or annotate each hazard entry to reflect actual conditions: proximity to live services, existing structures, public access, etc.
3	Controls listed at PPE only (no hierarchy)	PPE is the last resort in the hierarchy of control. A list of controls that jumps straight to "wear RPE / hearing protection" without addressing elimination, substitution, or engineering controls shows the risk assessment has not been properly conducted.	Work through the hierarchy: can the task be eliminated or substituted? What engineering controls (LEV, wet suppression, barriers) apply before PPE is reached?
4	No named operatives or competency evidence	The PC needs evidence that the people carrying out the work are competent. A RAMS signed only by the company director, with no reference to the operatives who will be on site, provides no such assurance.	Name each operative (or role), state relevant task-specific training or competence evidence (e.g. MEWP operator training where a MEWP is used, abrasive wheels training, asbestos awareness), and confirm CSCS/card evidence where the PC requires it.
5	No reference to site-specific emergency procedures	CDM 2015 requires the PC to ensure appropriate site induction and emergency arrangements are in place (CDM 2015). A RAMS that states "follow site emergency procedures" without naming them gives the PC nothing to cross-reference.	State the site muster point, the site emergency contact number, the nearest hospital with A&E (named, with address), and the first-aider on site for your works.
6	Task description is activity-generic, not task-specific	"Groundworks" or "civils works" tells the PC nothing about the actual operations, sequence, or hazards. The contractor's CDM 2015 duty to plan the specific work is visibly not met.	Break the work into discrete tasks (excavate, shore, lay, backfill). Each task needs its own hazard and control entry.
7	COSHH substances listed by category, not product	"Cement-based products may be used" gives no basis for the PC to assess whether adequate controls are in place.	List each product by name, reference the SDS sheet, and state the specific control measures derived from it (e.g. WEL for the substance, required RPE filter class).
8	No briefing / toolbox talk record section	A RAMS that cannot be shown to have been communicated to the operatives is functionally useless at inspection. The PC may also need evidence of briefing to satisfy their own audit requirements.	Include a briefing record table: operative name, signature, date briefed. This can be a blank table in the document completed before work starts.
9	Method statement contradicts the construction phase plan	If the construction phase plan specifies a one-way traffic system and your RAMS makes no mention of it, the PC cannot confirm that your work aligns with site rules — a failure of their coordination duty.	Obtain the relevant sections of the construction phase plan from the PC (they are required to provide them) and cross-reference your RAMS against site-specific rules before submitting.
10	Document version / revision control absent	If RAMS are updated mid-project and the revision history is unclear, the PC cannot confirm which version operatives are working to.	Add a version table: version number, date, summary of change, author. Even V1.0 on the first submission provides a baseline.

---

The 'Generic Document' Problem: What Site-Specific Actually Means in Practice

"Generic" is the most common reason RAMS are rejected, and the least well-explained. Here is a worked example for a single task — cutting concrete kerbs with an angle grinder — showing the difference between a document that will be returned and one that gives the PC enough to work with.

⚠️ Worked Example: Cutting Concrete Kerbs with an Angle Grinder

---

GENERIC VERSION (likely to be rejected)

Task: Cutting works. Hazard: Dust, noise, vibration, blade contact. Controls: Operative to wear appropriate PPE including dust mask, ear defenders, gloves and eye protection. Ensure blade is fitted correctly. Follow manufacturer instructions. Emergency: Follow site emergency procedure.

Why it fails: No site address. No operative named. No specific dust suppression method. RPE filter class not stated. No noise exposure context. No reference to silica (the specific hazard in concrete cutting). No first-aider named. Emergency procedure referenced but not described. Controls go straight to PPE with nothing above them in the hierarchy.

---

SITE-SPECIFIC VERSION (PC review-ready)

Site: Riverside Quarter Phase 2, [Full Address]. PC: [Name]. Contract ref: [Ref]. Task: Cutting concrete kerb units to line using 230mm angle grinder (Makita GA9020) fitted with diamond blade. Duration: approximately 4 hours on Day 3 of programme. Operative: J. Smith. Abrasive wheels certificate held (issued [date], copy attached). CSCS card: Skilled Worker, card no. [number]. Daily HAV exposure reviewed by supervisor against manufacturer-stated trigger value.

Hazard 1 — Respirable crystalline silica (RCS): Concrete cutting generates RCS, a hazardous substance. Controls in hierarchy order: — Engineering: Wet suppression via integrated water feed (blade water-feed kit fitted and checked before task). LEV not required where wet suppression achieves adequate control, confirmed by supervisor pre-task check. — Administrative: Task duration limited to 4 hours continuous; rotation of operative where task extends beyond this. Exclusion zone of 3 m established; signage erected. — PPE: FFP3 disposable respirator (3M Aura 9332+) worn throughout. Operative face-fit tested; record held by company (date: [date]).

Hazard 2 — Noise: Angle grinder at source approximately 100 dB(A). Upper exposure action value (EAV) under the Control of Noise at Work Regulations 2005 is 85 dB(A) LEP,d; this task will exceed it. Controls: EN352-rated ear defenders (SNR 28 dB minimum) worn throughout. Task duration managed. Hearing protection zone marked.

Hazard 3 — Contact injury / blade failure: Diamond blade inspected against manufacturer specification before fitting. Guard in place and checked. No-one within 3 m exclusion zone during cutting. Angle grinder SWL confirmed by supervisor.

Emergency: Site muster point: car park entrance, east gate. Site emergency number: [number]. First-aider for these works: [Name], EFAW certificate held, located in site welfare cabin. Nearest A&E: [Hospital name and address]. If operative shows signs of injury: stop work, call [number], escort to welfare cabin.

Why it passes: The task is specific. The operative is identified. The principal hazard (RCS/silica) is named with engineering controls leading the hierarchy. PPE is specified by product and filter class. Noise exposure is contextualised. The emergency section is actionable, not a cross-reference to an unknown procedure.

---

Missing Competency Evidence: Why Signing the Document Is Not Enough

A RAMS bearing only the company director's signature tells the PC nothing about the person holding the angle grinder on Tuesday morning. Practical competency evidence that PCs expect to see includes:

• Named operative(s) carrying out the task, not just the company signatory
• Relevant competence evidence referenced by name, issuing body/training provider where applicable, and expiry date where applicable (e.g. MEWP operator training category where a MEWP is used, abrasive wheels, asbestos awareness)
• CSCS card class where the PC's site rules require it — note this is a scheme-based expectation, not a direct statutory requirement, but PCs routinely enforce it as a site rule
• Tool-specific authorisations where relevant (e.g. PA shot firer's certificate, chainsaw NPTC unit)

Where operatives change mid-project, the RAMS must be updated and re-briefed. A document naming an operative who has left site is as problematic as one that names nobody.

---

Inadequate Emergency and First-Aid Arrangements: The Section Most Subcontractors Leave Blank

CDM 2015 requires the principal contractor to ensure that all persons working on the site have been provided with appropriate site induction (CDM 2015). Emergency arrangements form part of that induction, and your RAMS must align with them. PCs flag an empty or cross-referenced emergency section immediately because it signals the subcontractor has not engaged with the site at all.

At minimum, state: the muster point by name and location; the site emergency telephone number; the name (or role) and location of the first-aider covering your works; the nearest A&E hospital with its address; and any task-specific emergency actions (e.g. for confined space work, the rescue procedure and rescue equipment location).

---

The RAMS Briefing Record: Why an Unread RAMS Is as Bad as No RAMS

A PC reviewing your RAMS at a health and safety audit will ask two things: "Where is the RAMS?" and "Can you show me it was briefed?" If the operative cannot produce a signed briefing record, the document might as well not exist. Include a briefing log as a standard section:

Operative Name	Role	Date Briefed	Signature

This table is completed before work starts and held on site. Where a new operative joins mid-task, they must be briefed and sign before starting — do not simply hand them the document at the start of a shift and assume it counts.

---

How to Resubmit and Cut the Rejection Cycle

A bare resubmission with no explanation forces the PC to re-read the whole document to spot what changed. A short cover note referencing specific changes cuts review time and signals professionalism. Adapt the template below:

---

RAMS Resubmission Cover Note

To: [PC Health & Safety Manager / Site Manager name] From: [Your company name] Project: [Site address / contract reference] RAMS document ref: [Doc title, version number] Date of resubmission: [Date]

Further to your rejection comments dated [date], the following changes have been made to the above RAMS:

1. Site details added — cover page now includes full site address and your contract reference.
2. Hazard list revised — generic template entries replaced with site-specific hazards identified during site visit on [date]. Specific changes: [list, e.g. "proximity to live overhead line at grid ref X added; public footpath exclusion zone described"].
3. Control hierarchy completed — engineering controls (wet suppression, LEV assessment) now precede PPE entries for silica and noise hazards.
4. Operative competency — J. Smith named as task operative; abrasive wheels certificate (copy attached) and CSCS card details added.
5. Emergency section completed — site muster point, emergency number, first-aider name and nearest A&E now stated.
6. Briefing record table added — section 9 now includes signature log for pre-task briefing.

The revised document is version [V2.0], dated [date]. Please confirm receipt and advise of any further queries.

[Your name, role, contact number]

---

RAMSdocs: How the Platform Structures Documents to Reduce Rejection

RAMSdocs builds RAMS documents around the structure that PC reviewers check against. Each section in the platform maps to a reviewable duty: task description, hazard identification by hierarchy, named operatives, COSHH substance entries with SDS reference fields, emergency arrangements with named first-aider fields, and a briefing record built into the document output. Version control is automatic. The result is a document structured for review — not a blank template where critical sections can be left empty without being noticed.

Review and adapt every output to your specific site, task, and contractor before submission.

---

Frequently Asked Questions

Can a PC reject RAMS with no written explanation? In practice, yes — CDM 2015 does not prescribe the format of a rejection. However, most PC-subcontractor contracts include a provision for written feedback. If yours does not, ask for specific written comments before resubmitting; guessing at the failure costs time.

How long should a PC take to review RAMS? CDM 2015 does not set a statutory review period. Turnaround expectations are contractual and vary by PC. Best practice on most projects is to allow five working days before the planned start of the relevant task, and to submit earlier on larger programmes. Agree the expected turnaround in writing at mobilisation stage.

What does 'generic' mean when a PC uses it as a rejection reason? It means your document could describe any site, any operative, any project. The hazards, controls, and emergency arrangements are not identifiably connected to the specific location, task duration, or conditions on this project. See the worked example above for the concrete difference.

What happens if work starts before RAMS are accepted? Starting work without accepted RAMS where the PC requires them is a significant risk for both parties. The PC's coordination duties under CDM 2015 are undermined if a contractor begins work under a document the PC has not reviewed against the construction phase plan. The subcontractor's own CDM 2015 duty to plan and manage the work is also undermined. In practice, the PC may stop the works and the contractor may face contractual consequences.

Can a PC be held liable if they accept a deficient RAMS? Yes, depending on the facts. Acceptance of a RAMS that plainly fails to address a foreseeable hazard — and where injury subsequently occurs — may support an allegation that the PC failed to plan, manage, monitor and coordinate the construction phase under CDM 2015. This is precisely why rejection, not rubber-stamping, is the prudent response to a poor document.

What is the minimum a RAMS must contain to be ready for PC review? At minimum: site address and project reference; specific task description with sequence; hazards identified for this site and task; controls in hierarchy order (not PPE-first); named operative(s) with competency evidence; COSHH substances by product name; site-specific emergency arrangements; and a briefing record section. A document missing any of these elements is likely to be returned.

Does poor formatting or an unprofessional layout actually cause RAMS to be rejected by principal contractors? Yes — presentation quality is a documented rejection trigger, not just a compliance issue. A document with inconsistent fonts, cluttered layouts, or an obviously unedited generic template signals to a PC reviewer that the same lack of care likely runs through the content itself, making them more likely to scrutinise and return it. In practice, a clean, consistently formatted document that is easy to navigate makes it straightforward for a reviewer to locate the site address, hazard controls, and emergency details quickly — reducing the friction that leads to rejection. Formatting will not rescue a substantively deficient RAMS, but it can prevent a substantively sound one from being dismissed on first impression.

Can RAMS be rejected at tender or pre-qualification stage, before any site access question even arises? RAMS submissions are increasingly required as part of PQQ or tender returns, and a missing, incomplete, or obviously generic document at that stage can result in a bid being downgraded or disqualified outright — affecting contract award, not just site entry. Where a tender asks for both a generic service RAMS demonstrating standing capability and a separate site-specific RAMS for the tendered scope, failing to provide both is treated as a mandatory documentation failure by many procurement teams. Contractors should check tender requirements carefully: submitting only one where two are requested, or submitting a generic document where site-specific content was specified, is a separate and earlier failure point from the in-project submission process this page otherwise addresses.

---

All RAMS documents must be reviewed and adapted to the specific site, task, and working conditions by a competent person before submission or use. Nothing on this page constitutes legal advice or removes the need for site-specific professional review.