How Often Should RAMS Be Reviewed? Legal Triggers & Intervals Explained

Most contractors have heard "review your RAMS annually." Few can say where that figure comes from — because it does not come from statute. There is no fixed legal interval written into UK legislation. What the law does specify is a set of conditions under which the risk assessment must be reviewed, regardless of when you last looked at the document. This page separates that legal reality from the folklore, explains the different review obligations that attach to the two distinct instruments bundled inside a RAMS document, and gives you a practical trigger matrix to build a defensible review policy around.

---

What Does 'Reviewing RAMS' Actually Mean — and Why the Distinction Matters

"Reviewing" is not the same as "rewriting." A review is a structured assessment of whether the existing document remains valid for the task, site conditions, and workforce as they currently exist. It may conclude that nothing needs to change — and that conclusion is itself a legitimate outcome, provided it is recorded.

The reason the distinction matters legally is that RAMS bundles two instruments with different legal characters:

1. The risk assessment — a document whose production and maintenance is driven by statutory duties under general UK health and safety law.
2. The method statement — a procedural document describing how work will be carried out safely, required either by contract between parties or by a principal contractor's site rules; it does not carry identical statutory standing to the risk assessment.

Treating them as a single homogeneous document when deciding review obligations leads to under-review of the risk assessment and unnecessary bureaucracy around the method statement. The sections below deal with each in turn.

---

What UK Law Says About Review Frequency (CDM 2015 and General Health and Safety Law)

CDM 2015 — the Construction (Design and Management) Regulations 2015 — is the primary statutory instrument governing health and safety management on UK construction projects, imposing duties on clients, principal designers, principal contractors, and contractors (CDM 2015). The Regulations address the construction phase plan, the health and safety file, and the duties of each duty-holder, but they do not prescribe a specific numeric review interval for RAMS.

The duty to review risk assessments flows from general UK health and safety legislation. That legislation requires employers to review their risk assessments when there is reason to believe they may no longer be valid, or when there has been a significant change in the matters to which they relate. No fixed statutory interval — such as "every 12 months" — is mandated. Annual review is widely adopted industry practice, not a legal minimum. If your risk assessment remains fully valid after six months, you are not in breach by not rewriting it. If it becomes invalid after six weeks, you are in breach by not reviewing it.

Key legal principle: The review obligation is condition-triggered, not calendar-triggered.

---

The Two Instruments Inside RAMS: Different Review Obligations

Instrument	Legal character	What drives the review obligation
Risk Assessment	Statutory document — production and maintenance required by general UK health and safety law	Law requires review when the assessment may no longer be valid or after significant change
Method Statement	Procedural document — required by contract terms, site rules, or principal contractor pre-start requirements; does not carry the same statutory standing as a risk assessment	Contract terms, principal contractor requirements, or a change in work sequence

Practical consequence: If a personnel change affects competence but does not alter the risk profile of the task, the method statement may need updating (names, induction records) while the risk assessment itself remains valid. Conversely, a change in the substance of risk — new hazards introduced, control hierarchy altered — triggers a risk assessment review even if the work sequence in the method statement is unchanged.

---

Scheduled Review Intervals: Setting a Defensible Periodic Cadence

Because statute does not set a fixed interval, your periodic cadence should be proportionate to:

• Task risk level — high-hazard activities (excavation, work at height, confined spaces, demolition) warrant a shorter default interval than low-risk tasks.
• Project duration — on a project running longer than three months, a review at each phase gate is a recognised baseline.
• Rate of change on site — a dynamic site with multiple subcontractors, shifting layouts, and sequential trades changes faster than a single-trade fit-out.

A commonly adopted industry baseline is to review RAMS at each project phase gate, and at no less than every three months on continuous high-risk operations, regardless of whether a specific trigger has occurred. This is not a statutory requirement; it is a proportionate policy position that demonstrates ongoing due diligence.

Note on accreditation schemes: CHAS, SSIP schemes, and similar accreditation bodies may impose their own minimum review frequencies as a condition of registration. These are scheme rules, not statute, and must be read as such.

---

RAMS Review Trigger Matrix

The matrix below identifies the conditions that require action, the urgency of that action, and the responsible party under common CDM 2015 duty-holder roles.

Trigger Type	Example	Required Action
Significant change to work method	Sequence of operations altered; new technique introduced mid-project	Immediate review — before work resumes
New or altered plant / equipment introduced	Different excavator model with different reach/load; new temporary works system	Immediate review — before the plant is put to work
Near-miss or incident on the task	Worker almost struck during lift; trench collapse narrowly avoided	Immediate review — suspend affected work until the assessment and method are reviewed, updated where needed, and re-briefed
Change in site conditions or layout	Adjacent excavation opened; overhead cable rerouted; ground conditions differ from survey	Immediate review — before work continues in affected area
Personnel change affecting competence	Operative with specific certification leaves; untrained replacement assigned	Immediate review of competence controls; risk assessment reviewed if control hierarchy is affected
Regulatory or guidance update	New HSE guidance issued; approved code of practice revised	Scheduled review — within a reasonable period; immediate if the change invalidates a current control
Project phase change	Moving from ground works to above-ground structure; handover between subcontractors	Scheduled review at phase gate — before new phase commences
Post-incident investigation findings	Root-cause analysis identifies a hazard not addressed in RAMS	Immediate review — RAMS updated to reflect corrective action
Scheduled periodic interval	End of monthly/quarterly cycle; organisation's internal review date	Scheduled review — confirm validity or update as required
No material change since last review	Same task, same crew, same conditions, same controls	No immediate action required — record that review confirmed continued validity

---

Who Is Responsible for Initiating a RAMS Review Under CDM 2015 Duty-Holder Roles

CDM 2015 distributes responsibility across named duty-holders. Responsibility for task-specific RAMS sits primarily at the contractor level — the organisation actually carrying out the work is responsible for ensuring that its own risk assessments and method statements remain valid.

Where a principal contractor is appointed (required where a project involves, or is likely to involve, more than one contractor), CDM 2015 places duties on the principal contractor to manage the overall construction phase, coordinate the activities of contractors, and ensure that arrangements for managing the project are maintained. In practice, this normally includes receiving and reviewing RAMS submitted by subcontractors before high-risk work begins, and requesting updated RAMS when site conditions change in ways that affect a subcontractor's scope.

In practice:

Action	Responsible party
Identifying that a trigger has occurred	Site manager / supervisor (contractor's representative on site)
Initiating the RAMS review	Contractor (the employing organisation)
Reviewing updated RAMS before work resumes	Principal contractor (where appointed)
Signing off the revised document	Competent person within the contractor organisation
Briefing the workforce on changes	Supervisor / site manager — documented via toolbox talk or pre-start briefing

---

Worked Scenario: Reviewing RAMS Across a 9-Month Groundworks Project

Scenario: A groundworks subcontractor is appointed on a mixed residential development running from January to September. Their initial RAMS cover bulk excavation, drainage installation, and slab preparation.

Month 1 — Mobilisation RAMS submitted to the principal contractor before work commences. Principal contractor reviews and confirms acceptance. Version 1.0 issued.

Month 2 — Phase gate (bulk excavation complete; drainage commences) The subcontractor's site manager identifies that the drainage phase involves confined-space entry into inspection chambers — a hazard category not covered in the original RAMS. Trigger: project phase change + new significant hazard. Action (contractor): Immediate review. New confined-space section added. Version 1.1 issued. Principal contractor re-reviews before drainage work begins. Workers briefed via toolbox talk. Briefing recorded.

Month 4 — Near-miss incident An operative is struck by the bucket of a 360° excavator during backfill operations. No injury, but a near-miss report is filed. Trigger: near-miss on the task. Action (contractor): Work suspended. RAMS reviewed the same day. Exclusion zone distances and signalling protocols revised. Version 1.2 issued. Principal contractor notified and updated RAMS accepted. All operatives re-briefed before work resumes. Version 1.1 destroyed and replaced on site.

Month 6 — Equipment swap The 5-tonne excavator is replaced with a 13-tonne machine to address harder ground conditions. Trigger: new plant introduced. Action (contractor): Immediate review. Swing radius, exclusion zones, and ground-bearing capacity checks updated. Operator CPCS card checked and recorded. Version 1.3 issued before machine is put to work.

Month 8 — Scheduled periodic review No specific trigger has occurred since Month 6. The contractor's internal policy requires a review every three months on active high-risk operations. Action (contractor): Review conducted. Conditions unchanged. RAMS confirmed valid. Version 1.3 remains current. Record signed and filed.

Month 9 — Project completion RAMS Version 1.3 archived as part of the health and safety file.

---

What a Compliant Review Record Must Contain

A RAMS review that is not recorded is a RAMS review that did not happen — at least as far as enforcement and litigation are concerned. The record below captures the minimum evidence a competent person should produce each time a review is carried out.

---

RAMS Review Record — Template

Field	Entry
Document title
Current version number
Date of review
Reviewer name and job title
Trigger for this review	(e.g. phase change / near-miss / scheduled interval / equipment change)
Was the risk assessment amended?	Yes / No
Was the method statement amended?	Yes / No
Sections amended	(list section headings changed, or "None")
New version number issued
Previous version withdrawn from site?	Yes / No / N/A
Sign-off by competent person	Name / Signature / Date
Workers briefed on changes?	Yes / No
Briefing method	(e.g. toolbox talk / pre-start briefing / individual sign-off)
Names of workers briefed	(attach sign-in sheet if group briefing)
Principal contractor notified?	Yes / No / N/A
PC acceptance confirmed by	Name / Date
Next scheduled review date

---

Common Review Failures — and How They Expose Contractors to Enforcement Action

The following failures appear repeatedly in HSE investigation reports and civil litigation following construction incidents:

1. Original RAMS used throughout a project despite material changes. A document that was valid on day one is not automatically valid nine months later. Where conditions have changed and RAMS have not, the gap between document and reality is direct evidence of a failure to manage risk.

2. Review conducted but not recorded. A verbal "we looked at it and it was fine" cannot be evidenced. An unrecorded review provides no defence.

3. Workers not briefed on revised controls. Updating a document that remains in the site manager's folder while operatives continue working under superseded controls defeats the purpose of the review entirely.

4. Method statement updated but risk assessment left unchanged. Where the method has changed in a way that introduces new hazards or alters the control hierarchy, the risk assessment must be reviewed in parallel.

5. Version control absent. Where multiple versions of a RAMS document are in circulation on site simultaneously, it cannot be demonstrated that workers were operating under the correct controls. Previous versions must be formally withdrawn.

---

FAQ

Is there a legally specified interval for reviewing RAMS under UK law? No. UK law does not prescribe a fixed numeric interval. The legal duty is to review when there is reason to believe the assessment may no longer be valid, or when there has been a significant change. Annual review is industry practice, not a statutory minimum.

What events must trigger an immediate, unscheduled RAMS review? A significant change to the work method, introduction of new or altered plant, a near-miss or incident on the task, a change in site conditions affecting the risk profile, or a personnel change that undermines a competence-based control. See the Trigger Matrix above.

Does the review obligation differ between the risk assessment and method statement parts of RAMS? Yes. The risk assessment is a statutory document whose review is required by general UK health and safety law when it may no longer be valid. The method statement is a procedural document required by contract or principal contractor instruction — it does not carry the same statutory standing, and the triggers for updating it may differ from those that require a risk assessment review.

Who is responsible for initiating and signing off a RAMS review? The contractor employing or controlling the workforce is responsible for initiating the review. Sign-off should be by a competent person within that organisation. Where a principal contractor is appointed under CDM 2015, the updated RAMS should also be submitted through the PC's review/acceptance process before affected work resumes.

What evidence should be recorded to show a review has taken place? As a minimum: date of review, reviewer name and role, trigger for the review, sections amended, new version number, sign-off by a competent person, and a communication log confirming workers were briefed on any changes. Use the Review Record template above.

Does CDM 2015 impose specific review duties on principal contractors or other duty-holders? CDM 2015 places duties on principal contractors to manage the construction phase and coordinate contractor activities. In practice this includes requiring and reviewing RAMS before high-risk work begins and requesting updated documents when site conditions change. The Regulations do not specify a review interval; the duty is to maintain effective management arrangements throughout the construction phase.

How should RAMS be reviewed when a task is long-running across multiple phases? At each project phase gate as a minimum, plus whenever a specific trigger occurs. The worked scenario above illustrates this across a 9-month groundworks project. High-risk continuous operations warrant a scheduled periodic review regardless of whether a specific trigger has occurred.

---

How ramsdocs Supports RAMS Review Management

ramsdocs generates construction RAMS that are structured for straightforward review and version control, with clear section delineation between the risk assessment and method statement components. Review scheduling, trigger flagging, and version history are built into the platform so that your review obligations are visible rather than buried in a folder.

All documents produced must be reviewed and adapted to the specific site, task, and contractor by a competent person before use. ramsdocs output is designed to reduce RAMS rework and support PC review-ready submissions — it does not remove the need for site-specific assessment or professional judgement.

Frequently Asked Questions

When RAMS are revised mid-project, must workers re-sign the updated document? There is no statutory provision that prescribes re-signing as a specific legal formality, but the purpose of the original sign-off — confirming that workers have understood the safe system of work — applies equally to any revised version. In practice, issuing a revised RAMS without re-briefing affected operatives and capturing their acknowledgement of the changes means the document no longer reflects what workers have actually been instructed to do, which undermines the control. Each revision should carry its own date and version reference, and evidence of the re-briefing (signature, digital acknowledgement, or toolbox talk record) should be retained alongside the superseded version.

Does a client request count as a formal trigger to review and revise RAMS? A client request is a recognised and legitimate prompt to review RAMS, even where no other trigger condition has yet been met. Under CDM 2015, clients hold duties to make suitable arrangements for managing a project and to ensure those arrangements are maintained and reviewed throughout the project; where a client identifies that site conditions, scope, or programme have shifted in a way that may affect the validity of existing RAMS, raising that with the contractor is consistent with those duties. The contractor remains responsible for assessing whether a revision is warranted and, if so, for producing the updated document, re-briefing the workforce, and recording that process before affected work continues.