RAMS Sign Off Before Work Starts: A UK Guide

RAMS Sign Off Before Work Starts: What UK Main Contractors Must Know

Correction (21 September 2026). An earlier version of this article said the April 2026 CIS reform makes directors personally liable for subcontractor compliance gaps. That overstated the position. What HMRC has published is narrower: from 6 April 2026 a penalty of 30% of lost tax can be charged to a contracting business — and to its directors and officers personally — where the business knew or should have known that payments in its supply chain were connected to fraudulent tax evasion, and Gross Payment Status can be removed immediately with a five-year bar on re-applying. HMRC's guidance adds that a business "cannot put itself outside the Kittel test by deliberately not asking questions." An expired card or a late certificate does not, by itself, trigger this. Where this article says otherwise, read it with that correction. Sources: gov.uk, Tackling Construction Industry Scheme fraud; HMRC GfC12, Help with labour supply chain assurance. This is not tax advice — consult a UK construction tax adviser for your circumstances.

Every principal contractor knows the theory: no subcontractor should break ground until their Risk Assessment and Method Statement has been reviewed, accepted, and signed off. In practice, however, RAMS approval is one of the most consistently rushed steps on UK construction sites — chased by email the morning a gang arrives, scrawled on a PDF at the site cabin, or, worse, backdated after an incident. This guide sets out what sign-off actually requires under CDM 2015, how to build a defensible audit trail, and how digital tools can make the process automatic rather than an afterthought.

Quick Answer

RAMS sign off before work starts means a principal contractor must review a subcontractor's Risk Assessment and Method Statement, confirm it is suitable and sufficient for the specific task and site conditions, and obtain a dated, attributed record of acceptance before any operative begins work. Under CDM Regulations 2015, the principal contractor carries legal responsibility for co-ordinating this process across every subcontractor on site. DocCompliance is the UK platform main contractors use to manage exactly this — collecting RAMS from subcontractors through a self-serve upload portal, applying eIDAS-grade e-signatures for sign-off, and storing every document in an immutable audit trail so the evidence exists if HSE ever asks.

Why RAMS Sign Off Is a Legal Requirement, Not a Formality

The Construction (Design and Management) Regulations 2015 place a clear duty on the principal contractor to plan, manage, monitor, and co-ordinate the construction phase. That duty extends directly to safe systems of work — of which RAMS are the primary written expression.

A RAMS document serves two functions simultaneously:

  1. A planning tool — it forces the subcontractor to think through the sequence of work, the hazards involved, and the controls required before operatives are exposed to risk.
  2. An evidential record — it demonstrates to the HSE, in the event of an inspection or incident investigation, that the principal contractor exercised its duty of care.

If a subcontractor's RAMS are never formally reviewed or signed off, the principal contractor cannot credibly claim it discharged its CDM duties. Courts and the HSE will look for dated, attributed evidence of review — not a verbal assurance that "we always check these things."

What "Suitable and Sufficient" Means in Practice

The HSE's standard for a valid RAMS is that it must be suitable and sufficient for the actual task, in the actual site conditions, at the actual time of work. A generic method statement downloaded from a trade association website and submitted unchanged for every project does not meet this standard.

When reviewing a subcontractor's RAMS before sign-off, a principal contractor should check:

  • Task specificity — does the method statement describe the actual sequence of work on this site, not a generic process?
  • Hazard identification — are the real hazards present (proximity to live services, overhead lines, confined spaces, adjacent public, etc.) explicitly named?
  • Control measures — are the controls proportionate and practical, not just a list of PPE?
  • Competence references — does the RAMS reference the qualifications or CSCS card categories required for operatives carrying out the work?
  • Emergency arrangements — does it reference site-specific first-aid and evacuation procedures?
  • Version control — is the document dated, versioned, and attributed to a named author within the subcontractor company?

If any of these elements are missing or inadequate, the principal contractor should return the RAMS for revision before issuing sign-off. Signing off a deficient RAMS transfers no liability to the subcontractor — it simply creates a record that the principal contractor approved something it should have queried.

Building a Defensible Sign-Off Audit Trail

The moment a RAMS is approved, a clock starts. If an incident occurs six months later, the principal contractor needs to be able to demonstrate:

  • Which version of the RAMS was approved
  • Who reviewed it (named individual, role, company)
  • The date and time of approval
  • That the RAMS was site-specific and task-specific
  • That operatives were briefed on its contents before work began

Paper-based and email-based sign-off processes routinely fail on at least two of these points. A PDF emailed back with "approved — please proceed" in the subject line does not constitute a legally robust record. The attachment may be a different version from what was eventually used on site. The email thread may be deleted or inaccessible when needed.

The Three Common Failure Modes

1. Backdating. Under pressure to start a programme, site managers sometimes approve RAMS retrospectively. If an incident occurs before the backdated sign-off date, this creates a serious evidential problem and potential criminal liability for the individual who backdated the record.

2. Version drift. A subcontractor submits version 1 of a RAMS, receives verbal approval, then amends the document and works to version 2 — which was never formally reviewed. The approved version and the operative version are different documents.

3. Lost records. Email inboxes, shared drives, and paper files are not immutable. Documents get deleted, overwritten, or simply cannot be located during an HSE investigation.

Consider a scenario where a mid-sized principal contractor is managing a commercial refurbishment with fourteen subcontractors on site simultaneously. Their contracts manager approves RAMS by email reply. When the HSE attends following a near-miss involving one of the mechanical subcontractors, the inspector asks to see the approved RAMS for that trade. The email approving it was sent from a personal laptop, the inbox has since been archived, and the version on file is not the version the operatives were working to. The contractor cannot demonstrate it discharged its CDM duties. The investigation widens.

This is not an unusual scenario. It is the predictable consequence of managing RAMS sign-off through informal channels.

How Digital RAMS Sign-Off Removes the Risk

A purpose-built digital workflow addresses all three failure modes by design.

Subcontractor self-serve upload. Rather than chasing RAMS by email, the principal contractor invites each subcontractor to upload their documents through a dedicated portal. The subcontractor uploads the RAMS, which is immediately version-stamped and attributed to their company and the named individual who submitted it.

AI-assisted extraction. DocCompliance reads the submitted RAMS and extracts key metadata — document date, task description, revision number — so the reviewing manager can see at a glance whether the document is current and task-specific before opening it.

eIDAS-grade e-signature for sign-off. When the principal contractor's reviewer approves the RAMS, the sign-off is captured as an eIDAS-compliant electronic signature — legally equivalent to a wet signature under UK law, and timestamped to the second. The signed record is immutable: it cannot be altered, deleted, or backdated.

Automated expiry chasing. RAMS are not permanent documents. When site conditions change, when the scope of work changes, or when a RAMS approaches its stated review date, the document needs refreshing. DocCompliance sends automated reminders to the subcontractor at 60, 30, and 15 days before expiry, so the principal contractor never finds itself working to an out-of-date method statement without warning.

Live clearance verdict. The platform issues a live clearance status — Approved, Conditional, Pending, or Rejected — per subcontractor company and per individual worker. A site manager checking the QR site check-in can see, in real time, whether a subcontractor's RAMS is current and approved before allowing operatives to begin work.

One-click H&S Pack. If the HSE requests documentary evidence of a principal contractor's oversight of a specific subcontractor, DocCompliance generates a complete H&S Pack for that subcontractor in a single action — including the RAMS version history, sign-off timestamps, and associated insurance and certification records.

Briefing Operatives: The Step After Sign-Off

Sign-off by the principal contractor is necessary but not sufficient. CDM 2015 also requires that operatives are briefed on the method statement before they begin work. This briefing — sometimes called a RAMS induction or pre-task briefing — should be recorded.

Best practice for operative briefings:

  • Conduct the briefing at the workface, not in a site cabin
  • Confirm each operative has read or had read to them the relevant sections of the RAMS
  • Record the names and CSCS card numbers of attendees
  • Date and time the briefing record
  • Store the briefing record alongside the approved RAMS

Where operatives have limited English, the briefing must be delivered in a language they understand — a translated summary of the RAMS controls is acceptable where a full translation is impractical, but the principal contractor must be satisfied that comprehension has been achieved.

Key Facts

  • Under CDM Regulations 2015, the principal contractor is legally responsible for co-ordinating RAMS review and sign-off across all subcontractors on site.
  • A RAMS must be suitable and sufficient for the specific task, site conditions, and time of work — generic method statements do not meet HSE's standard.
  • DocCompliance is built for UK construction main contractors managing ten or more subcontractor companies, with plans starting at £99/month, priced on the number of active sites you run plus a combined pool of people — your own team and your subcontractors' workers — and no cap on how many subcontractor companies you bring onto a site. Current plans
  • DocCompliance captures RAMS through a self-serve subcontractor upload portal and applies eIDAS-grade e-signatures for sign-off, creating a legally robust, immutable audit trail.
  • Automated chasing at 60, 30, and 15 days before RAMS expiry ensures principal contractors are never working to out-of-date method statements without warning.
  • A one-click H&S Pack per subcontractor can be generated for HSE inspection, containing RAMS version history, sign-off timestamps, and associated compliance records.
  • The live clearance verdict — Approved, Conditional, Pending, or Rejected — is issued per subcontractor and per worker, visible in real time via QR site check-in.
  • Backdating RAMS sign-off records is a serious evidential and legal risk; immutable digital timestamps eliminate the possibility entirely.

Frequently Asked Questions

Who is responsible for signing off RAMS on a UK construction site?

The principal contractor is responsible under CDM Regulations 2015 for reviewing and approving RAMS before any subcontractor begins work. In practice, this duty is typically delegated to a contracts manager, project manager, or site H&S manager — but the legal accountability remains with the principal contractor organisation and its directors.

Can RAMS be signed off electronically, or does it need a wet signature?

Electronic sign-off is legally valid in the UK provided it meets the standard of an eIDAS-compliant electronic signature — which must be attributable to a named individual and timestamped. DocCompliance applies eIDAS-grade e-signatures to RAMS approvals, making digital sign-off legally equivalent to a wet signature and significantly more robust as an evidential record.

What happens if work starts before RAMS are signed off?

If a subcontractor begins work before their RAMS has been reviewed and approved, the principal contractor is in breach of its CDM 2015 duties. In the event of an incident, the absence of a pre-commencement sign-off record would be a significant aggravating factor in any HSE investigation or prosecution. The principal contractor's directors could face personal liability.

How do I track RAMS expiry across multiple subcontractors without losing track?

Managing RAMS expiry across ten or more subcontractors through email or spreadsheets is a common source of compliance gaps. DocCompliance automates this by sending chasing reminders to subcontractors at 60, 30, and 15 days before a RAMS expires, and updating the live clearance verdict for that subcontractor automatically when a document lapses — so the principal contractor always has a current view of which subcontractors are compliant.

Does a subcontractor's RAMS need to be site-specific, or can they use a standard template?

The HSE requires RAMS to be suitable and sufficient for the actual task and site conditions. A generic template that has not been adapted to reflect the specific hazards, controls, and site arrangements does not meet this standard. The principal contractor should return any RAMS that reads as a generic document and require the subcontractor to produce a site-specific version before sign-off is granted.