Skip to main content
SwiftCase
PlatformForward-deployedSwitchboardFeaturesSolutionsCase StudiesFree ToolsPricingAbout
Book a Demo
SwiftCase

Workflow automation for UK service businesses. Created in the UK.

A Livepoint Solution

Platform

  • Platform Overview
  • Workflow Engine
  • Case Management
  • CRM
  • Document Generation
  • Document Extraction
  • Context Graph
  • Data Model
  • Integrations
  • Analytics

Switchboard

  • Switchboard Overview
  • Voice AI
  • Chat
  • Email
  • SMS
  • WhatsApp

Features

  • All Features
  • Claims Operations
  • High-Volume Operations
  • Multi-Party Collaboration
  • Contract Renewals
  • Compliance & Audit
  • Pricing
  • Case Studies
  • Customers
  • Why SwiftCase

Company

  • About
  • Our Team
  • Adam Sykes
  • Nik Ellis
  • Implementation
  • 30-Day Pilot
  • Operations Pressure Map
  • For Your Role
  • Peer Clusters
  • Engineering
  • Careers
  • Partners
  • Press
  • Research
  • Tech Radar
  • Blog
  • Contact
  • SwiftCase Signal

Resources

  • Use Cases
  • Software
  • ROI Calculator
  • Pressure Diagnostic
  • Pilot Scope Estimator
  • Board Case Builder
  • Free Tools
  • Guides & Templates
  • FAQ
  • Compare
  • Best Practices
  • Changelog
  • Documentation
  • Help Centre

Legal

  • Privacy
  • Terms
  • Cookies
  • Accessibility

Stay in the loop

Cyber Essentials CertifiedGDPR CompliantUK Data Centres

© 2026 SwiftCase. All rights reserved.

  1. Home
  2. Guides
  3. Fire Safety
  4. How Often Must a Fire Risk Assessment Be Reviewed?
Article 9Review Cycles

How Often Must a Fire Risk Assessment Be Reviewed?

The law does not give a number, which is why practices get asked the question so often. This guide sets out what the Order requires, what triggers a review, and how a practice keeps hundreds of review cycles running without one slipping.

8 min readLast updated 2026-08-22Last verified 2026-08-22

The Law Says Regularly, and Leaves the Rest to Judgement

Article 9(3) of the Regulatory Reform (Fire Safety) Order 2005 requires the fire risk assessment to be reviewed regularly so as to keep it up to date, and in particular where there is reason to suspect it is no longer valid or there has been a significant change in the matters to which it relates. There is no statutory interval. The Responsible Person has to decide what regular means for their premises, and most of them ask their assessor.

In practice a cycle has grown up around the duty: an annual review to confirm the assessment still stands, a full reassessment every few years or when the building changes, and a review straight away after anything that could invalidate it. Those are conventions rather than law, and the right interval for a small office is not the right interval for a care home or a block of flats over 11 metres, where the Fire Safety (England) Regulations 2022 add their own recurring checks.

For the practice, the operational problem is scale. A consultancy holding five hundred clients has five hundred review dates, each with its own cycle, its own history of change and its own Responsible Person who may or may not respond. A missed review is an assessment that quietly stops being valid, and it is the practice's name on the last one issued.

Review Cycles as a Managed Book, Not a Diary

Treat every issued assessment as the start of a cycle rather than the end of a job. The review date is set at issue, on the case, and the case carries the cycle: when the next review is due, what kind of review it is, what changed since, and what the outcome was. The practice then has a book of review cycles it can see across, rather than a diary that one person keeps.

The cycle needs two kinds of trigger. The scheduled one is the review date, driven by the building's risk profile and the interval the practice has set for that class of premises. The event-driven one is a change at the premises: a change of use, an alteration, a change in occupancy, a fire or near miss, an enforcement notice. Those arrive from the client, so the client needs an easy way to report them and the practice needs them to land on the right case.

A review that concludes the assessment is still valid is itself a record, and it should be kept as one. The Responsible Person's file should show that the assessment was reviewed on a date, by whom, what was considered and what was decided. An annual review that confirms nothing has changed is evidence of a duty discharged; a review that never happened is the opposite.

Every issued assessment carries its own review date and cycle, so nothing depends on a spreadsheet
Review intervals are set per class of premises and applied consistently across the book
Reminders go to the client and the practice automatically as the date approaches
Changes reported by the client land on the right case and can trigger an early review
Reviews that confirm the assessment still stands are recorded as evidence, not lost as non-events
The practice can see the whole book: due, overdue, reviewed, reassessed, declined

How to Run Review Cycles Across a Whole Client Book

Follow these steps to turn review dates from a diary into a managed cycle that the practice controls and can evidence.

1

Set the review date at issue, on the case

When the assessment is issued, set the review date on the same case, according to the interval the practice has decided for that class of premises. The date is part of the record of issue, not a separate note.

Print the review date on the report. It tells the Responsible Person what the practice expects and makes the next conversation easier.
2

Decide intervals by class of premises, and write them down

Define the review interval and reassessment interval the practice applies to each class: low-risk commercial, sleeping accommodation, care premises, residential blocks by height, and so on. The decision is the practice's professional judgement and it should be recorded so it can be explained and applied consistently.

Review the intervals themselves once a year. Guidance moves, and so does the practice's view of risk.
3

Automate the reminders, to the client and to you

As the review date approaches, the case should prompt the practice and write to the client. A first notice, a follow-up, and an escalation if there is no reply, each recorded against the case. The practice should never discover an overdue review by accident.

Send the reminder from the case so the reply comes back to it. A reply in someone's personal inbox is a review that will be forgotten.
4

Give clients a way to report change

The event-driven triggers depend on the client telling you. A simple form or a line in the annual reminder asking whether the building, its use or its occupancy has changed, whether there has been a fire or an alarm activation, and whether the fire service has visited, brings those triggers in. A yes should create a review task on the case straight away.

Ask the questions in the client's language. Has anything been built, knocked through, rewired or changed hands will get an answer that a clause reference will not.
5

Decide review or reassessment, and record why

Not every review needs a site visit and not every change needs a new assessment. Record the decision on the case: reviewed remotely and confirmed, reviewed on site and updated, or reassessed in full, and the reason. That record is what shows the Responsible Person acted regularly and with judgement.

Make the decision a required field. A cycle that ends without a recorded outcome is indistinguishable from one that was missed.
6

Record the outcome, even when nothing changed

A review that confirms the assessment is still valid gets recorded with the date, the reviewer and what was considered. The next review date is set from it. Over time the case holds the whole history of the premises: every assessment, every review, every change reported and what was done about it.

That history is the handover record the Order expects when a Responsible Person changes. Keep it where it can be produced in one go.

Best Practices

Treat the review book as a product, not an afterthought

Many practices find that the review cycle is their steadiest line of work once it is managed. A client who is reminded reliably, told what has changed and offered the right level of review stays a client.

Distinguish review from reassessment in the offer and in the record

Clients understand an annual check and a periodic full assessment when the difference is explained. Offer both, price both, and record which one happened.

Chase in writing, from the case

Every reminder and every reply is part of the record. If a client declines a review, the practice should be able to show that it was offered, when, and what the client said.

Tie reviews to the action plan

The review is the natural moment to ask what became of last year's actions. An assessment whose findings were never addressed is not one the practice should simply re-date.

Watch the higher-risk buildings separately

Residential buildings over 11 metres carry recurring checks under the 2022 Regulations, and higher-risk buildings over 18 metres or seven storeys sit in the Building Safety Act regime. Their cycles are shorter and more scrutinised, and they deserve their own view.

Report on the book monthly

Due this month, overdue, reviewed, reassessed, declined. A practice that can see those five numbers can manage the book; one that cannot will find out about the gaps from a client or a fire officer.

Implementation Checklist

Review date set on the case at issue and printed on the report
Review and reassessment intervals defined per class of premises and recorded
Reminder sequence to client and practice automated from the case
Client has a way to report change, and a report creates a review task
Review or reassessment decision recorded with the reason
Outcome recorded even when the assessment is confirmed unchanged
Next review date set from the outcome
Declined reviews recorded with the client's response
Higher-risk and over-11-metre residential buildings visible as their own group
Monthly view of due, overdue, reviewed, reassessed and declined
Free Tool

SLA Builder

Set turnaround targets for write-up, QA and issue, and timings for review reminders.

Try It Free

Frequently Asked Questions

Related Guides

fire safety

Fire Risk Assessment Workflow: From Instruction to Issued Report

A fire risk assessment is a legal record as much as a piece of advice. This guide sets out a workflow that takes a practice from instruction to an issued, defensible report, at the volume a working practice has to handle.

fire safety

Tracking Fire Risk Assessment Actions Through to Completion

An assessment is only as good as what happens to its findings. This guide sets out how to turn the action plan into tracked work with owners, dates and evidence, across every client the practice holds.

fire safety

Handing Over Fire Safety Information When the Responsible Person Changes

Buildings change hands, managing agents change, and the fire safety record is supposed to go with the building. This guide sets out what has to pass over, and how a practice that holds the record makes itself the continuity.

Further Reading

Timeline: Every review, reminder and reply on the case, in order, with a summary on top.Workflow engine: Reminder sequences and escalations that run from the review date without anyone chasing.Property inspection scheduling guide: Scheduling recurring inspections across a portfolio.SLA Builder: Set the reminder and escalation timings for your review cycles.

Never Find Out About an Overdue Review From a Client

Bring us your client list and we will show you what it looks like as a managed book of review cycles, with the reminders, the change reports and the records running from the case.

Book a Discovery CallSee how reminder cycles run themselves