Competent Person Sign-Off for RAMS: Who, What & How

A signature at the bottom of a RAMS document means nothing unless the person who placed it there was genuinely competent to judge what they reviewed. Yet across UK construction sites, RAMS are countersigned by supervisors who have not read them, managers who lack the relevant task knowledge, and occasionally by the same person who wrote the document in the first place. This page dismantles the rubber-stamp habit by giving you a precise framework: who holds sign-off authority under the CDM 2015 duty structure, what competence actually means in that context, and what a defensible sign-off record must contain.

---

What 'Competent Person Sign-Off' Actually Means in the Context of RAMS

Signing off RAMS is a gate, not a formality. The person countersigning is asserting — to their client, their principal contractor, and if necessary to an enforcement authority — that the document has been reviewed by someone with sufficient knowledge, skill, and experience to confirm it accurately describes the hazards, controls, and safe working method for the specific task at hand.

The Construction (Design and Management) Regulations 2015 (SI 2015/51) is the primary UK regulatory framework for construction health and safety. CDM 2015 links competence to skills, knowledge, experience, and — where an organisation rather than an individual is in scope — organisational capability. No single threshold of years in industry, no single card scheme, and no specific qualification — not NEBOSH, not IOSH membership, not any CSCS card level — is mandated by CDM 2015 as a prerequisite for signing off RAMS. Competence is task-specific and evidence-based, which means the burden falls on you to demonstrate it, not simply to claim it.

Key principle: Competent person sign-off is not a credential — it is a documented judgement, made by someone who can show why they were qualified to make it.

---

The Legal Duty Structure: Which CDM 2015 Duty Holders Are Involved in RAMS Approval

CDM 2015 (SI 2015/51) establishes a layered duty structure. Understanding where RAMS approval sits within that structure prevents misattribution of responsibility.

• Client — Responsible for ensuring that suitable arrangements are in place for managing the project, including the allocation of sufficient time and resources.
• Principal Designer — Holds duties relating to health and safety coordination during the pre-construction phase, including ensuring pre-construction information is prepared and communicated.
• Principal Contractor — Holds overarching responsibility for coordinating health and safety across the site during the construction phase. This includes satisfying themselves that contractor method statements and risk assessments are adequate before work begins. The principal contractor does not author every RAMS document, but they must ensure a competent review occurs.
• Contractor — Responsible for planning, managing, monitoring, and coordinating construction work carried out by that contractor, including preparing RAMS for their own activities.
• Worker — Has a duty to cooperate and follow the health and safety directions they are given, including those contained in RAMS.

RAMS approval therefore operates at the contractor level (internal sign-off that the document is correct and complete) and at the principal contractor level (external gate confirming the document is adequate before work starts on a shared site).

---

Defining Competence for RAMS Sign-Off: Knowledge, Skills, Experience, and Behaviours

CDM 2015 uses competence as a multi-dimensional concept. For RAMS sign-off, industry-accepted practice translates this into four components that the signer must be able to evidence:

Component	What it means for RAMS sign-off
Knowledge	Understanding of the specific hazards associated with the task (e.g. excavation near live services, working at height, confined space entry). Familiarity with relevant legislation, guidance, and safe systems of work.
Skills	Ability to read and critically evaluate a RAMS document — identifying omissions, unrealistic controls, or generic content that does not reflect site conditions.
Experience	Demonstrable track record of working with or managing the type of work being described. Not necessarily on an identical site, but with the same hazard profile.
Behaviours	Willingness to reject a RAMS document that does not meet the required standard; independence from commercial pressure to approve inadequate documents; awareness of when specialist input is needed.

No specific credential makes someone automatically competent for every RAMS sign-off. A person with a NEBOSH Certificate but no experience of groundworks is not competent to approve excavation RAMS. A site manager with fifteen years of groundworks experience and sound practical knowledge may be. The combination matters; the label does not.

---

Who Can Sign Off RAMS — Role Authority Matrix

This matrix applies to a project where a principal contractor is appointed. Conditions on sign-off authority are noted in the right-hand column.

Role	Author RAMS?	Internal review?	Formal sign-off authority?	Conditions
Client	Rarely	No	No (unless also a contractor)	Clients set management arrangements; they do not typically hold task-level RAMS competence.
Principal Designer	No	Pre-construction phase only	No	Role ends at construction phase start for most RAMS purposes.
Principal Contractor	For own direct work	Yes — all contractor RAMS	Yes — mandatory counter-sign before work starts	Must have competence in the task type being approved. Cannot delegate this gate to an incompetent nominee.
Contractor (subcontractor)	Yes	Yes — own RAMS	Internal sign-off only	Own supervisor or manager may internally approve, but this does not replace PC counter-sign on shared sites.
Contractor's supervisor	Can contribute	Yes	Internal sign-off only	Competence must be evidenced for the specific task. Author and sole approver should not be the same person.
Worker	Can contribute content	No	No	Workers inform RAMS through toolbox talks and task briefings; they do not hold sign-off authority.

---

The Independence Principle: Why the RAMS Author Should Not Also Be the Sole Sign-Off Authority

A RAMS document is a control document. Its purpose is to manage risk. When the same person writes it and signs it off without independent review, two failure modes emerge: blind spots in the original drafting are not caught, and commercial or time pressure on a single individual is unresisted.

Industry best practice — and CDM 2015's coordinated duty structure — supports separating RAMS authorship from review wherever practicable. Where a principal contractor is appointed, their review provides an external coordination check against the construction phase plan and site rules. On smaller projects without a PC, the contractor should designate a reviewer who was not the primary author. This does not need to be a different company; it needs to be a different, genuinely critical eye.

---

What a Competent Person Must Check Before Countersigning: The 12-Point Review Gate

This checklist is a best-practice framework derived from CDM 2015 duty-holder logic and established RAMS practice. It is not a statutory checklist. Use it as Part B of your sign-off process — Part A (competence verification) is covered in the evidence log below.

Part B — Document Review Gate (run before countersigning)

• 1. Task scope match — Does the RAMS title and scope exactly match the task being authorised? Generic or mismatched documents must be returned.
• 2. Hazard completeness — Are all significant hazards for this task identified, including those arising from site-specific conditions (proximity to services, other trades, public)?
• 3. Risk rating credibility — Are likelihood and severity ratings realistic, not systematically underscored to make the task look lower risk than it is?
• 4. Control hierarchy — Do controls follow the recognised hierarchy (eliminate, substitute, engineer, administrative, PPE)? PPE-first documents without engineering controls must be returned.
• 5. Control specificity — Are controls specific (named equipment, named procedure, specific permit number) rather than generic ("follow safe working practices")?
• 6. Residual risk acknowledged — Is residual risk identified after controls are applied, and is it at an acceptable level for the task to proceed?
• 7. Competence of operatives — Does the RAMS reference the training, qualifications, or experience required of the people doing the work?
• 8. Emergency arrangements — Are emergency procedures named, site-specific, and realistic (nearest hospital with A&E, site emergency contact, rescue procedure for confined space etc.)?
• 9. Environmental and third-party risk — Are impacts on adjacent workers, the public, or the environment considered?
• 10. Legislation and standards referenced — Where specific legal duties or technical standards apply (e.g. Schedule 3 of CDM 2015 lists work involving particular risks including excavations and work near high-voltage power lines), are these acknowledged?
• 11. Briefing evidence — Is there a mechanism for workers to confirm they have read and understood the RAMS (signatures, toolbox talk record)?
• 12. Review and version control — Does the RAMS include a version date, a review trigger (change of method, near miss, change in site conditions), and the name of the author?

Any failed gate item must be resolved before sign-off is granted. Annotate which items were queried and how they were resolved.

---

Records You Must Keep to Evidence Competent-Person Sign-Off

A signed RAMS page proves only that someone wrote their name. To make sign-off defensible, you need a Competence Evidence Log attached to or filed with the RAMS. Here is the minimum content:

Competence Evidence Log — Template

Field	Content to record
Signer's full name and role	e.g. "J. Smith, Site Manager, XYZ Groundworks Ltd"
Relationship to the work	Author / Reviewer / PC counter-signatory (circle one)
Relevant experience	e.g. "12 years managing excavation operations on civil engineering projects"
Relevant training/qualifications held	List with dates — note these are evidence of competence, not legal prerequisites
Specific task knowledge basis	e.g. "Reviewed and managed CAT scanning and trial holing procedures on 6 comparable projects in the last 3 years"
Date and version of RAMS reviewed	Must match document header
Gate items queried	List any Part B items that prompted a query, and how resolved
Sign-off decision	Approved / Approved with conditions / Returned for revision
Date of sign-off

File this log with the RAMS document. Both must be retained for the duration of the project and for a period appropriate to the nature of the work.

---

Worked Example: Excavation RAMS on a Notifiable Project

Scenario: A groundworks subcontractor (Greenfield Groundworks Ltd) is appointed by a principal contractor (BuildCo) on a notifiable project. Greenfield submits RAMS for a 2.5-metre excavation adjacent to a live gas main and a live electrical distribution cable — work that falls within Schedule 3 of CDM 2015, which lists work putting workers at risk of burial under earthfalls and work near high-voltage power lines as involving particular risks.

Step 1 — Greenfield authors the RAMS. The document is drafted by the groundworks supervisor, covering hazard identification, shoring specification, CAT and Genny scanning protocol, and emergency procedures.

Step 2 — Greenfield's internal review. The company's health and safety advisor (not the authoring supervisor) runs through the 12-point gate. Item 5 (control specificity) is queried: the document says "service avoidance measures to be followed" without naming the specific permit-to-dig procedure. The document is returned to the supervisor for amendment. Revised version resubmitted.

Step 3 — PC review. BuildCo's designated competent person — a construction manager with eight years of groundworks project management and a current first aid at work certificate — receives the revised document. They complete their own 12-point review. They note Schedule 3 applies, confirm the shoring specification matches the ground conditions described in the pre-construction information, and verify Greenfield's operatives hold the required training (EUSR water hygiene card holders are not relevant — the log confirms two operatives hold CPCS plant tickets and the supervisor holds SHEA Gas). All 12 gate items pass. BuildCo's construction manager records acceptance for coordination purposes and completes a Competence Evidence Log recording their eight years' experience and the specific basis for competence.

Step 4 — Audit trail. The signed RAMS, the Competence Evidence Log, the Part B gate record (including the initial query on Item 5 and resolution), and the worker briefing record are filed together. If HSE or an insurer later asks who approved this work and on what basis, every step is documented.

---

Common Failure Modes: Rubber-Stamp Sign-Off and How Regulators and Clients Detect It

Generic language throughout. A RAMS document that uses phrases like "ensure safe working" and "comply with all relevant legislation" without task-specific controls signals that neither the author nor the approver engaged with the actual risk. Investigators look for this immediately.

Mismatched signer credentials. A signatory whose Competence Evidence Log shows no relevant task experience — or no log at all — cannot sustain a claim of competence under challenge. Signing off excavation RAMS when your background is office fit-out is not defensible.

Same person as author and sole approver. Where a PC is appointed, the absence of any PC review or acceptance record is a red flag because the RAMS may not have been checked against the construction phase plan and site rules. On smaller projects, a single-person sign-off without any independent review record is difficult to defend if the RAMS contained an error that led to an incident.

Date anomalies. Sign-off dated after work started is evidence that the gate did not function. Always record the sign-off date, and ensure it precedes the start date on the site permit or programme.

---

How ramsdocs Automates Competent-Person Sign-Off, the Audit Trail, and Evidence Capture

ramsdocs is built around the principle that RAMS sign-off should be a documented process, not a last-minute signature.

• Structured sign-off workflow routes each RAMS through the correct review sequence — internal author review, then PC counter-sign — so the independence principle is enforced by the platform, not by memory.
• Competence Evidence Log is captured digitally at the point of sign-off: the reviewer records their role, experience basis, and task-specific knowledge before the countersign is accepted.
• 12-point gate checklist is presented to the reviewer on-screen, with mandatory annotation for any item queried. The resolution record is stored against the document version.
• Automatic audit trail timestamps every action — document creation, internal review, query raised, revision submitted, PC counter-sign granted — and exports as a single PDF alongside the RAMS for submission to the client or retention in the health and safety file.
• Version control flags any document amended after sign-off and triggers a re-review workflow, so a revised RAMS cannot be used on site under an approval that applied to an earlier version.

The result is a sign-off record that is PC review-ready from the moment it is generated — designed to reduce RAMS rework and demonstrate that competent-person sign-off was a genuine gate, not an afterthought.

---

Frequently Asked Questions

Who legally qualifies as a competent person to sign off RAMS in the UK? CDM 2015 (SI 2015/51) does not prescribe a named qualification or credential. Competence is assessed on the combination of knowledge, skills, experience, and — where an organisation is involved — organisational capability relevant to the specific task described in the RAMS. The person must be able to demonstrate why they were qualified to make the judgement they made.

Is a formal qualification required to sign off RAMS? No. No specific qualification — including NEBOSH, IOSH membership, or any CSCS card level — is mandated by CDM 2015 as a legal prerequisite for RAMS sign-off. Qualifications are evidence of competence, not a substitute for it. Demonstrated, task-relevant experience and knowledge carry equal weight.

Can a subcontractor's supervisor sign off their own RAMS? A supervisor can perform an internal review. Where a principal contractor is appointed, the RAMS should also be submitted for PC review before the work starts because the PC must coordinate work against the construction phase plan and site rules. The supervisor's internal sign-off does not replace that coordination gate. On projects without a PC, the contractor should still separate the authoring and reviewing functions where possible.

What must a competent person actually check before signing? Use the 12-point review gate above. In summary: task scope match, hazard completeness, credible risk ratings, control hierarchy followed, specific (not generic) controls, residual risk acknowledged, operative competence referenced, site-specific emergency arrangements, third-party risk considered, relevant legislation/standards acknowledged, briefing mechanism confirmed, and version control in place.

What records prove competent-person sign-off occurred? The signed RAMS document plus a completed Competence Evidence Log (signer identity, role, relevant experience, task-specific knowledge basis, gate items queried and resolved, sign-off decision, and date). Both must be retained and filed together.

What happens if RAMS are signed off by someone who is not genuinely competent? If an incident occurs and the sign-off cannot be shown to have been made by a competent person, the individual who signed and the organisation behind them face significantly increased exposure under CDM 2015 and, depending on the circumstances, under criminal law. Rubber-stamp sign-off is not a defence — it is an aggravating factor that demonstrates the safety management system was not functioning.

If site conditions change materially after RAMS have been signed off, who is responsible for initiating a review and re-sign? The contractor who owns the RAMS carries primary responsibility for identifying when a change in conditions — such as unexpectedly encountered services, altered ground conditions, adjacent trade activity, or a near-miss — renders the existing document inadequate. Where a principal contractor is appointed, they also hold a coordination duty and should flag condition changes that affect individual contractor RAMS during site inspections and audits. The reviewed document must go back through the same competent-person sign-off gate before affected work resumes; a verbal update or annotation without a formal re-sign does not constitute an adequate control record. Treating the original sign-off as still valid when conditions have materially changed is a recognised failure mode that undermines the entire safe system of work.

Does a change in scope or method always trigger a full re-sign, or only when the risk profile shifts? The practical test is whether the change introduces hazards, controls, or interfaces not covered by the signed document — if it does, a re-sign is required; if the existing RAMS genuinely still describes what will happen and how risk is controlled, a documented review confirming no change is needed is sufficient. Minor administrative amendments (correcting a name, updating a date) do not require full re-sign provided they do not alter any risk or control content. Where doubt exists, re-signing costs far less than defending an unreviewed document at an incident investigation, so err towards the formal gate rather than away from it.

How does competent person sign-off on RAMS function as evidence of competence in SSIP, CHAS, and Constructionline pre-qualification submissions? Pre-qualification schemes such as SSIP, CHAS, and Constructionline assess a contractor's health and safety competence through documentary evidence rather than on-site observation, and RAMS are routinely scrutinised as part of that assessment. Assessors look at whether documents are task-specific, identify realistic hazards and controls, and carry a traceable sign-off by a named, identifiably competent person — generic templates with blank or unidentifiable signatures typically score poorly or prompt requests for additional evidence. Submitting RAMS that show clear authorship, a named competent reviewer, and version control demonstrates the organisational capability that CDM 2015's duty-holder framework expects contractors to evidence.

Should RAMS submitted for tender or pre-qualification be live project documents or purpose-prepared examples? Either can serve the evidential purpose, but live project RAMS — with real site-specific hazards, named controls, and a dated competent-person sign-off — carry more weight than documents that appear to have been produced solely for the submission. If you use previous project RAMS as examples, ensure they accurately reflect the type of work tendered and that any client-confidential information has been appropriately redacted; submitting an obviously generic or lightly adapted document risks signalling the rubber-stamp habit that assessors are specifically trained to identify.

---

Disclaimer: This page and all checklists, templates, and frameworks within it must be reviewed and adapted to your specific site, task, and contractor arrangements by a competent person before use. Nothing on this page constitutes legal advice, and no template or checklist is a substitute for site-specific assessment. ramsdocs documents are designed to be PC review-ready and to reduce RAMS rework; they do not guarantee acceptance by any client, principal contractor, or enforcement authority, and they do not remove the need for competent review and adaptation.