Spreadsheets vs a fire safety compliance platform: when is it actually time to switch?

There's nothing inherently wrong with managing fire safety records in a spreadsheet. For a single building or a small handful, a well-maintained spreadsheet can genuinely do the job — it's cheap, flexible, and everyone already knows how to use it. The question worth asking isn't whether spreadsheets are bad, it's recognising the specific point where they stop being adequate for the portfolio they're being asked to cover.

Where spreadsheets genuinely hold up

For one or two buildings with a single person responsible for keeping records current, a spreadsheet tracking FRA review dates, actions and basic servicing history can be entirely workable. The discipline required is real but manageable at that scale, and there's a reasonable argument that adding a dedicated platform for such a small portfolio is more overhead than it's worth.

The signs a spreadsheet has stopped working

The breakdown tends to follow a recognisable pattern rather than happening suddenly: more than one person needs to update records and versions start to diverge; the portfolio grows past a size where any one person can hold the full picture in their head; review dates and outstanding actions start getting discovered late rather than tracked proactively; and producing a clean report for an insurer or auditor starts requiring real manual effort rather than a quick export.

• –More than one person edits the same records, and versions have started to conflict or diverge
• –The number of buildings has grown past the point where any one person can hold the full picture from memory
• –Review dates or overdue actions are being discovered late, rather than flagged proactively
• –Producing a report for an auditor, insurer or new managing agent takes real manual effort each time
• –Photo evidence for defects and completed actions is scattered across emails and phone galleries rather than attached to a record
• –A change of staff member or agent risks losing institutional knowledge the spreadsheet never actually captured

The migration question people avoid asking

A common reason to delay switching, even once the signs above are obvious, is the fear of losing existing records in a messy migration. In practice, a reasonable platform should be able to import historical review dates, building details and outstanding actions from an existing spreadsheet as a starting point, rather than requiring everything to be rebuilt from scratch — that's worth asking about directly, and is one of the questions worth putting to a vendor before committing.

What actually gets easier after switching

The genuine gain isn't usually that a platform does anything a well-run spreadsheet couldn't, in principle — it's that the platform makes the disciplined behaviour the default rather than something that depends entirely on one person's diligence. Review dates get surfaced automatically. Actions can't be quietly forgotten because they're not sitting in a cell nobody's scrolled to in months. That shift from "depends on someone remembering" to "the system surfaces it" is the real value, more than any individual feature.

Where the spreadsheet stops being defensible

A spreadsheet can hold assessment dates and action lists perfectly adequately for a small number of buildings. Where it becomes genuinely difficult is evidence: showing not just that an action was closed but when, by whom, on what basis, and with what supporting document — and showing that the record has not been altered since. A cell can be changed by anyone with access and it leaves no trace.

For most operational data that is an acceptable risk. For a record that may be read after an incident by someone assessing whether duties were discharged, the absence of any audit trail is a different kind of exposure, and it is usually the argument that actually decides the switch.

Common mistakes

• –No audit trail, so a change cannot be traced or dated
• –Evidence held separately from the action it supports
• –Multiple copies with no agreed master
• –Renewal and review dates with no notification attached
• –Waiting for a visible failure when the failure mode is quiet inaccuracy
• –Comparing a licence cost against zero rather than against the exposure it reduces