What happens if a subcontractor turns up without a RAMS?

If a subcontractor arrives on site without a RAMS for the work they're due to carry out, a principal contractor is entitled — and, in terms of their own CDM 2015 duties, arguably obligated — to refuse them site access until it's in place.

How this actually plays out at the gate

In practice, it's rarely a dramatic confrontation. A subcontractor turns up, the person checking them in asks for their RAMS for that day's task, and it either isn't there, doesn't match the work they're actually about to do, or is an old version that's been superseded by a change in site conditions. Whoever's doing the checking then has a genuinely awkward decision in front of them: hold the subcontractor at the gate, with the crew standing around and the programme slipping, or let them through and sort the paperwork out later. The entire value of the RAMS requirement rests on that person making the harder call.

What "valid" actually means here

It's worth being precise about what counts as a missing RAMS, because it's not always a binary of "has one" versus "doesn't." A RAMS that exists but describes a different task, references equipment that isn't actually on site, or was written for a different set of site conditions is functionally the same problem as no RAMS at all — it hasn't actually assessed the risk of the work that's about to happen. Treating an outdated or mismatched RAMS as "good enough because there's a document" defeats the purpose just as thoroughly as skipping the check altogether.

The programme-pressure trap

The practical pressure runs the other way, though: a subcontractor turned away means a delay, which under schedule pressure creates a strong temptation to let them start anyway on the promise that the paperwork will follow later that day. That's exactly the pattern that erodes the requirement over time — a document that can be supplied after the fact isn't really controlling risk before work starts, which is the entire point of having one. Once it becomes known on a project that this rule bends under enough pressure, subcontractors learn that showing up without a RAMS and letting the site team feel the time pressure is a viable way to skip the review entirely.

Is there ever a genuine exception?

Genuine emergency work — responding to an immediate danger, rather than routine work running behind schedule — is a different category, and dealt with under separate emergency procedures rather than the standard RAMS gate. The distinction matters because it's tempting to stretch "this is urgent" to cover ordinary schedule pressure. If a piece of work can wait an hour for a RAMS to be reviewed, it's not the kind of emergency that justifies bypassing the check — and treating routine urgency as an exception is how the exception stops meaning anything.

Consistently enforcing this, even when it's inconvenient, is also what keeps the requirement credible with subcontractors themselves — an occasional exception signals that the rule is negotiable, which tends to produce more requests for exceptions, not fewer.

Supporting the person who has to make the call

Whoever is actually responsible for checking RAMS at the gate — often a site manager or a gate marshal with far less seniority than the subcontractor's own management — needs to feel genuinely backed when they refuse access. If that person turns someone away and then gets overruled by a more senior manager under programme pressure an hour later, they'll learn quickly that the rule is only real when it's convenient, and stop enforcing it consistently themselves next time. Making sure refusals are supported, not quietly reversed, is as much a management decision as writing the policy in the first place.

What this costs versus what it prevents

It's worth being honest that refusing access has a real, immediate cost — lost time, a frustrated subcontractor, a schedule slip that someone above the site manager will likely ask about. That cost is visible and easy to point to. The cost of letting unassessed work start is harder to see because, most of the time, nothing goes wrong and the risk that was skipped never becomes obvious. That asymmetry — visible cost now versus invisible risk later — is exactly why this rule needs to be enforced as a matter of policy rather than left to a judgement call made under pressure in the moment, when the visible cost will always feel more urgent than the invisible one.

How to prevent it happening in the first place

The best way to avoid this scenario is to catch it before the subcontractor is even travelling to site — confirming RAMS is submitted and reviewed the day before work is due to start, not the morning of. A simple pre-arrival check, built into how work is scheduled rather than left to whoever's on the gate, catches most of these situations early enough that nobody has to have the awkward conversation at the entrance at all. This is a much easier problem to solve upstream, with a bit of planning discipline, than to manage in the moment once a crew is already standing at the gate with tools in hand.

Common mistakes

• –Accepting an outdated or mismatched RAMS on the basis that "they have something"
• –Making a one-off exception under programme pressure without recognising it sets a precedent for the next subcontractor
• –Not distinguishing genuine emergency work from ordinary work running late
• –Leaving the decision to refuse access to whoever happens to be on the gate that day, without backing them when they make the harder call
• –Treating a verbal promise that "the RAMS is coming" as equivalent to actually having reviewed one
• –Overruling a refusal under programme pressure, which teaches the person enforcing the rule not to bother next time