RAMS Approval Software and CDM 2015: A Worked Example for Principal Contractors

An Illustrative Worked Example, Not a Customer Story

This is an illustrative worked example, not a customer story. DocCompliance is a new product and we don't publish case studies we can't evidence. The contractor described below is invented and unnamed, and nobody is quoted — there is no operations director behind this article, and we are not going to invent one.

The duties, the failure modes and the reasoning are genuine. That is what the article is for.

The Scenario (Our Premises)

Assume a principal contractor operating across the East of England, delivering commercial fit-out, residential new-build and light industrial projects. Assume it carries between 35 and 55 active subcontractors across its live portfolio at any given time — enough that RAMS management is a standing operational undertaking rather than a background task.

Assume RAMS are managed through email, shared network drives and a manually maintained spreadsheet, with approval given by whichever site manager is closest to the package.

These are chosen premises, not findings. What follows is what breaks in that arrangement, and why the breakage is a legal problem rather than merely an administrative one.

What the Duty Actually Requires

Worth being precise here, because "RAMS" is industry shorthand rather than a statutory term.

Two duties combine. Under regulation 3 of the Management of Health and Safety at Work Regulations 1999, an employer must make a suitable and sufficient assessment of the risks to which employees and others are exposed — and, where five or more people are employed, record the significant findings. Under CDM 2015, the principal contractor must plan, manage and monitor the construction phase and coordinate matters relating to health and safety so that work is carried out without risks to health or safety so far as is reasonably practicable.

Put those together and the practical position is clear. It is not enough to have collected a method statement. The principal contractor needs the relevant risk assessment and method statement to have been reviewed and found suitable before the work activity begins — and to be able to show it.

That word "before" is doing an enormous amount of work, and it is where manual processes tend to fail.

The Challenges

Challenge 1 — Version Control Is Where Email-Based RAMS Fail

With dozens of subcontractors submitting documents in different formats, at different times, to different members of the team, the question "which version is current" becomes genuinely difficult to answer.

The characteristic failure runs like this. A site manager reviews a method statement and approves it by email. The subcontractor subsequently revises it — perhaps for good reasons, perhaps at the site manager's request — and sends a new version to a different contact. Work proceeds. Two versions now exist, one of which was approved and one of which is being worked to, and they are not necessarily the same document.

From a legal standpoint that is not a filing inconvenience. The approval attaches to a version, and if you cannot say which version was approved, you cannot demonstrate that the work being done was the work that was assessed.

Challenge 2 — Approval Before Mobilisation Is Inconsistently Achieved

In principle, no operative attends site until the RAMS for their activity are approved. In practice, under programme pressure, that sequence inverts more often than most operations teams would like to admit.

A subcontractor mobilises while their method statement is "being finalised". Sign-off exists as an informal email acknowledgement rather than a considered approval. The work is probably being done safely — but the control that was supposed to establish that has been bypassed, and there is no record of a decision to bypass it, because nobody made one.

This is not a discipline problem to be solved with reminders. A gate that depends on somebody refusing a request under schedule pressure will fail intermittently and unpredictably. Gates need to be structural.

Challenge 3 — The Administrative Load Produces a Fragile Output

Chasing, reviewing and filing RAMS across a large subcontractor base consumes a substantial share of a compliance coordinator's week — hours of it, every week, indefinitely.

The frustrating part is what all that effort produces: a folder structure that one person fully understands, no automated tracking of which documents need revisiting, and no way to assemble a consolidated pack quickly. High effort, fragile result. And when that person is on leave or leaves the business, the structure becomes considerably less navigable.

The Solution

Three things are needed: one versioned record per document, an approval that is bound to a specific version and a named approver, and a gate that mobilisation cannot route around.

Stated as capability rather than as anyone's result, DocCompliance is built to:

  • Hold a single versioned record per RAMS document, so the current version is unambiguous and superseded versions remain visible in history rather than being overwritten.
  • Bind approval to a version, so what was approved is a matter of record rather than reconstruction.
  • Provide e-signature approval with an audit trail, giving sign-off evidential weight rather than the status of an email acknowledgement.
  • Enforce a pre-start gate, so a subcontractor cannot be marked ready to mobilise until their RAMS are submitted, reviewed and formally approved. This is the control that addresses the most significant exposure.
  • Route submissions through a subcontractor portal, giving subcontractors one clear destination instead of an email chain.
  • Produce a consolidated compliance pack covering approvals, approvers, dates and version histories, without manual retrieval.

A Sensible Order of Work

No timeline promised — how long this takes depends on your existing documentation, which we cannot see.

  1. Configure the requirement by trade. Decide what RAMS and supporting documents each trade must submit. Trades differ substantially here and a generic list serves nobody.
  2. Set the approval routing. Decide who approves what, and at what level. Ambiguity in routing is a common reason approvals stall or get given by someone without the standing to give them.
  3. Bring subcontractors onto the portal. Give subcontractors one clear destination for submission, with the requirements visible to them, rather than an email chain they have to navigate.
  4. Turn the pre-start gate on. This is the substantive change. Everything before it is preparation.
  5. Spot-check by exporting a pack. Pick a live project, produce the full approval record, and read it as though you were an inspector.

What This Would Give the Contractor

Not a percentage. A different position:

  • An unambiguous current version for every RAMS document, with superseded versions retained rather than lost.
  • Approvals bound to a version and a named approver, which is what makes sign-off evidence rather than correspondence.
  • A mobilisation gate that holds under programme pressure, because it is structural rather than a matter of individual resolve.
  • A compliance pack available on request, rather than assembled from drives and inboxes when someone asks.

We are not going to publish a reduction in administration hours or a pack-production time. We do not know your baseline, and any figure we quoted would be invented.

Key Takeaways

  1. RAMS sign-off is a legal obligation, not an administrative courtesy. The duty is to have assessed the risk and established a safe method before work starts, and to be able to show it. A document collected after mobilisation does not discharge that, however good the document is.

  2. Version control is the most common point of failure. Email-based management makes approving a superseded document almost inevitable given enough revisions. If approval is not bound to a specific version, the approval cannot tell you what was actually authorised.

  3. Audit-readiness should be a continuous state rather than a fire drill. Evidence that exists only when someone assembles it is evidence you might not have. A system that records approvals as they happen produces the pack as a by-product.

Conclusion

The contractor in this article is invented, but the gap it describes is one that many principal contractors would recognise: the distance between believing you are on top of RAMS and being able to prove it to somebody who arrives without notice.

Closing that gap does not require an operational overhaul. It requires replacing an informal approval process with one where the version is unambiguous, the approver is named, the timestamp is automatic, and the gate does not open early.

Plans start at £99 per month, priced on active sites plus a combined people pool covering your own team and your subcontractors' workers, with no cap on the number of subcontractor companies. See doccompliance.io/pricing.

Book a demonstration of DocCompliance to see the RAMS approval workflow in practice.

The contractor in this article is invented and the article is an illustrative worked example, not a customer case study. No outcome described is a claim about results achieved by any contractor, and no individual is quoted. This is general information about CDM 2015 duties, not legal advice.