Fire Alarm Routine Testing, Servicing & Logbooks | BS 5839 Compliance UK

Fire Alarms: Routine Testing, Servicing, and Record Keeping — Meeting Regulatory Standards

A building can look finished long before it is safe. The ceilings are closed, the corridors painted, the signage hung. But the life-safety systems sit behind the surfaces, waiting to be needed at the worst possible moment. A fire alarm system is not “installed and done”. It is a maintained condition.

Routine testing and disciplined record keeping are where that condition is kept alive. Not as admin. As evidence that the system you are relying on is still the system that was commissioned.

The duty sits with the Responsible Person

UK fire safety law places the duty on the Responsible Person to take general fire precautions and to maintain fire precautions in an efficient state, efficient working order, and good repair under the Regulatory Reform (Fire Safety) Order 2005. 

You can contract out servicing. You cannot contract out accountability.

Where buildings are higher-risk, or where building safety regimes demand traceability, maintenance records become part of the building’s auditable story — the practical end of the “Golden Thread” mindset: decisions, inspections, defects, and close-out. 

Routine user testing: small acts, done without drama

BS 5839-1 sets expectations for routine attention by the user. The point is simple: prove the system can raise an alarm, the indication is correct, and faults are noticed early. 

Weekly test discipline (typical BS 5839-1 approach)

• Test at roughly the same time each week, during normal occupancy, so staff recognise the routine and any out-of-hours variations stand out. 

• Operate a different manual call point each week so every device is tested over time, not just the convenient one near reception. 

• Confirm the alarm operates correctly (sounders/visuals where provided), the panel shows the correct zone/device, and any remote signalling behaves as intended. 

• Reset properly, and record the result immediately.

If your fire alarm interfaces with other life-safety functions — door releases, shutters, plant shutdown, smoke control signals — incorporate those checks into the weekly routine where applicable, because interface failure is a real failure. 

Planned inspection and servicing: the interval is not negotiable

User tests confirm the system still “speaks”. Servicing confirms it still means what it says.

BS 5839-1 guidance is widely referenced in UK compliance practice for non-domestic systems. A key point: the period between successive inspection and servicing visits should not exceed six months. 

That six-monthly visit is not a box-tick. It is where a competent engineer verifies performance across devices and functions, checks standby power arrangements, investigates recurring faults, and tests more deeply than a weekly call point activation ever can. 

Some risk profiles justify more frequent attention (care environments, complex cause-and-effect, high false alarm burden). Treat the building’s use and behaviour as part of the system. 

Record keeping: the logbook is the building’s memory

If you cannot prove the system was tested, serviced, and faults managed, you are functionally relying on hope.

Government fire risk assessment guidance explicitly supports keeping a log book of maintenance and testing, because it is how you demonstrate ongoing control. 

Fire and rescue services publish log book templates for exactly this reason: consistent entries, consistent evidence. 

What a credible fire alarm record looks like

Keep entries short, factual, and complete:

• Date and time of test or event

• Device tested (call point reference/location)

• Result (pass/fail) and what was observed (panel indication, sounders, signalling)

• Any faults present before/after test

• Action taken (reset, isolate, engineer called, temporary measures)

• Name and signature (or accountable identifier) of the person conducting the test

• Engineer visit records: scope, tests completed, defects, parts replaced, certificates, follow-up actions

• False alarm log: cause, location, classification, corrective action and trend notes 

The logbook should live where the panel is — not in someone’s inbox. A log you can’t reach during an audit is theatre.

Common compliance failures that look “minor” until they aren’t

1. Testing the same call point every week because it is convenient. That is not a rotation; it is a ritual. 

2. No evidence trail: verbal assurances, missing pages, undated entries, no engineer reports. 

3. Fault tolerance: a panel in fault becomes “normal”. That is how defects become building culture.

4. Unmanaged false alarms: repeated unwanted signals ignored instead of corrected, until someone ignores the real one. 

5. Interfaces not verified: doors that do not release, signals that do not transmit, cause-and-effect that is assumed rather than tested. 

Competence, traceability, and what “good” looks like

Routine testing is simple. That’s the point. It should survive staff turnover and busy weeks. Servicing requires competence and proper reporting. Between the two sits the discipline of records.

A compliant fire alarm system is not just a collection of devices. It is a maintained narrative: routine checks, bounded intervals, managed faults, and evidence that an enforcing authority can follow without guesswork. Under the Fire Safety Order, that is what “maintained” means in practice

FIRE ALARM MANUAL