Fire alarm servicing: what to expect and how often it should happen

A fire alarm system that hasn't been properly serviced can look completely normal for a long time — the panel shows green, the sounders test fine, nobody notices anything wrong — right up until it's called on to do its actual job. Servicing exists precisely to catch the slow degradation that a casual glance at the panel won't reveal.

What routine servicing generally involves

The relevant British Standard for fire detection and alarm systems in non-domestic premises sets out recommended inspection and servicing routines, typically involving a mix of more frequent checks carried out in-house and periodic professional servicing by a competent engineer. A professional service visit generally includes testing detector and call point operation, checking battery condition, verifying sounders and any linked systems function correctly, and reviewing the system log for recurring faults.

How often professional servicing is generally expected

Guidance under the relevant British Standard commonly points towards periodic professional servicing visits, often discussed as at least twice yearly for many system types, alongside more frequent weekly and monthly checks that can be carried out by a trained in-house person rather than a specialist engineer. The exact frequency and scope depend on the system type, its complexity, and any manufacturer-specific requirements — the standard itself and the system installer's recommendations are the definitive reference, not a general figure.

• –Weekly: a manual test point activated to confirm the system responds correctly, rotated around different call points
• –Monthly: emergency lighting linked to the fire alarm (where fitted) and any standby batteries visually checked
• –Periodic professional service: full functional testing of detectors, call points, sounders and system logic by a competent engineer
• –After any fault or false alarm: investigation of the root cause, not just a reset of the panel
• –Whenever the building changes: a review of whether detector coverage and zoning still reflect the current layout

The gap between 'serviced' and 'serviced well'

Not every service visit is equal. A rushed visit that confirms the panel powers on and a couple of devices respond is technically a service, but it's a much weaker one than a thorough visit that actually works through the full test regime and genuinely investigates any recurring faults in the log rather than clearing them and moving on. Asking a servicing contractor what their visit actually covers, and checking the resulting paperwork reflects that, is a reasonable and fair question to ask.

Why the paperwork matters as much as the visit

A servicing certificate that just says "system serviced, no faults found" tells you very little on its own. More useful records note what was actually tested, any faults found and how they were resolved, and any recommendations for follow-up — the same principle covered in our broader piece on record-keeping requirements. Across a portfolio with multiple alarm systems on different service contracts, having servicing dates and outcomes visible in one place, rather than scattered across separate contractor portals and email inboxes, is often the difference between noticing a missed service quickly and discovering it a year later.

The service visit and the things around it

A service visit is one part of a wider picture that includes routine in-house testing, the log of events between visits, and what happens when the panel shows a fault at eleven on a Sunday night. Organisations frequently have the service contract well in hand and the surrounding routine much less so — a weekly test that has quietly lapsed, a log with a six-month gap, or no agreed procedure for an out-of-hours fault other than silencing the panel.

The out-of-hours question is worth settling explicitly, because it is answered under pressure by whoever is present. Someone silencing a panel without anyone being told is how a system ends up impaired for days with no record that anything happened.

Common mistakes

• –Holding a service contract while the routine in-house testing has lapsed
• –Gaps in the log nobody has noticed or explained
• –No agreed procedure for a fault outside working hours
• –Silencing a panel without recording the event or escalating it
• –Not tracking whether faults found at service were actually rectified
• –Assuming the servicing contractor is monitoring the system between visits

This is a general orientation, not a servicing schedule to follow directly — the specific requirements for any given system should come from the relevant current British Standard and the system manufacturer or installer's own guidance.