How Often Should RAMS Be Reviewed on Site in the UK?
Introduction
If you are asking “how often should RAMS be reviewed”, you are usually trying to avoid two common failures on site: using an old method statement that no longer matches the work, or updating documents but not briefing people properly. RAMS should be treated as a working control, not a one-off upload. In practice, you review RAMS at a sensible baseline interval, then you review again whenever something changes that could affect risk or controls.
This guide gives you a simple rule you can apply on UK sites, plus the change triggers to watch for, who should do the review, and what to record so you can evidence control. For a full end-to-end overview of how RAMS fits into planning, briefing, and change control, see the ultimate guide to RAMS in construction.
Quick Answer..
There is no single fixed legal time interval that applies to every RAMS pack. A practical UK rule is to review RAMS at least annually, and also whenever anything significant changes. HSE guidance on risk assessment review commonly points to an annual review as a sensible baseline, with additional reviews triggered by change.
When should RAMS be reviewed in practice?
Use a two-part rule:
-
Baseline review: at least once every 12 months for recurring activities and standard task types, even if nothing obvious has changed. This aligns with typical HSE guidance that an annual review is a sensible guide for risk assessments.
-
Event-driven review: immediately when a change could affect hazards, risk level, or controls. This is the part that matters most on construction sites, because the programme and interfaces change constantly.
If you only follow the baseline review, you will still miss high-risk drift.
The change triggers that should force a RAMS review
Treat these as non-negotiable review triggers:
-
Scope change: new tasks, changed sequence, new work faces, temporary works introduced or removed
-
Method change: different technique, new access, different containment, new lifting plan, different isolation approach
-
Plant and equipment change: different excavator, attachment, MEWP type, lifting accessory, electrical tools, temporary power setup
-
People change: new subcontractor, new supervisor, new operatives, competence gaps identified, change in supervision ratio
-
Interface change: increased public interface, new trades working nearby, new delivery routes, changed segregation
-
Site condition change: ground conditions, weather exposure, lighting, access constraints, adjacent live services, confined spaces
-
Incident learning: near miss, damage event, nonconformance, enforcement visit feedback, or a trend from inspections
-
Document dependency change: updated permit requirements, updated lifting plan, changed traffic management plan, changed emergency arrangements
If any one of these occurs, you are not just updating paperwork. You are updating the control model for the task.
Who should review RAMS and who should approve changes?
A simple role split that works on most UK sites:
-
Supervisor or works manager: owns the day-to-day task reality and initiates the review when the job changes
-
HSQE or competent reviewer: checks that hazards and controls remain suitable and sufficient, and that site rules and company standards are met
-
Principal contractor or contractor management: ensures the site has a working system for plan, manage, monitor, and update arrangements across the project
-
Operatives: must be re-briefed on changes and should be able to explain the controls back in practical terms
If your RAMS forms part of wider project planning, CDM places an ongoing duty to keep the construction phase plan reviewed and updated through the project. This reinforces the principle that construction controls must remain current as the project evolves.
What a good RAMS review record should include
For auditability, record the minimum that proves control:
-
Version number and date
-
What changed and why
-
Who reviewed it and who approved it
-
What sections were impacted: hazards, controls, method steps, PPE, permits, plant, interfaces
-
Who was briefed and when: attendance and sign-off
-
Superseded versions: clearly marked, archived, and not accessible as “live” documents
If you want a practical model for briefing and sign-off, see contractors RAMS briefings.
Download Your Free Briefing & Attendance Template
Ready-to-Use Briefing Sheet
Track attendance, signatures, and daily safety briefings with a free HSE-aligned record sheet for toolbox talks, inductions, and site audits.
Common mistakes and the controls that prevent them
Mistake: Reviewing the RAMS but not checking the method steps against the live programme
Control: Tie review to daily or weekly planning and permit conditions
Mistake: Changing controls without re-briefing
Control: “No brief, no start” rule on changed tasks
Mistake: Multiple PDFs and WhatsApp versions
Control: One source of truth, controlled access, and automatic version supersession
Mistake: Only reviewing after an incident
Control: Trigger reviews from leading indicators such as unsafe condition reports, inspections, and interface changes
For version control and governance concepts, see <a href="https://paperlessconstruction.co.uk/2025/01/17/site-rams-compliance/">site RAMS compliance</a> and <a href="https://paperlessconstruction.co.uk/2025/02/08/digital-site-rams/">digital site RAMS</a>.
Practical example: review cadence for a UK groundworks package
Imagine a groundworks subcontractor doing drainage and external works over 10 weeks.
-
Baseline: schedule a formal RAMS review at week 1 and then again if the package extends beyond 12 months, which it will not
-
Event-driven triggers in reality:
-
week 2: route changes and a new pedestrian interface
-
week 4: different excavator and lifting attachments
-
week 6: temporary works added for a trench box arrangement
-
week 8: night shift introduced with new lighting and fatigue controls
-
In this scenario, the baseline review is not the control. The event-driven reviews are.
Frequently Asked Questions
Do RAMS need to be reviewed daily?
If the task conditions and method are stable, RAMS do not usually need a full daily rewrite. What you do need is a daily check that the work still matches the RAMS and that controls are in place. If conditions or scope change, trigger a RAMS review and re-brief.
Is there a legal requirement to review RAMS annually?
I cannot confirm a single legal rule that states “RAMS must be reviewed annually” for every situation. HSE guidance commonly uses annual review as a sensible baseline for risk assessments, with additional reviews when change occurs.
What counts as a “significant change” that forces a review?
Any change that could introduce new hazards, increase risk, or weaken controls. Common examples include changed sequence, new plant, new access, changed interfaces with other trades, or changed site conditions such as ground stability or public interface.
Who should sign off an updated RAMS?
The person with authority for the work should approve the change, and a competent reviewer should check the hazards and controls remain suitable and sufficient. On many sites this means supervisor initiated, HSQE reviewed, and contractor management approved, then briefed to the workforce.
A simple rule you can enforce across every site
Review RAMS at least annually, and immediately when the job changes in any meaningful way. Keep it controlled with one live version, clear approvals, and a recorded re-brief after changes. If you can evidence what changed, who approved it, and who was briefed, you are far better placed for compliance and for real-world risk control. For the full process including planning, briefing, and change control, return to the ultimate guide to RAMS in construction.
Want a cleaner way to manage RAMS reviews, briefings, and version control?
Use RAMS and safety briefings to keep one live version, capture sign-off, and evidence your audit trail.
Using ChatGPT for RAMS?
Draft Faster. Review Site Risks Properly.
Get access to our free RAMS generator now.
