A fire alarm needs a manual call point test every week, carried out by your own competent staff, plus professional servicing at least every six months by a qualified engineer. That is the short answer to one of the most common questions we are asked, and one of the most commonly misunderstood. “Testing” covers several different activities, each with its own required frequency, and conflating them is one of the easiest ways for a compliance gap to go unnoticed. This guide is for anyone responsible for a fire alarm system: building managers, landlords, facilities teams and the Responsible Person under the Fire Safety Order.
What are the two categories of fire alarm testing?
Routine user testing, which competent in-house staff can carry out, and periodic servicing and inspection, which must be carried out by a qualified engineer. Treating these as interchangeable, or assuming one covers the other, is where most compliance gaps quietly start.
How often is user testing required?
Weekly. Under BS 5839-1, the standard governing fire detection and alarm systems in non-domestic buildings, a weekly manual call point test is the baseline routine check. This typically involves activating a different manual call point each week, so that over time every call point on the system has been tested, and confirming the alarm sounds correctly across the building. The weekly test verifies that the system is functioning and audible. It is not a substitute for full system servicing and should not be treated as one.
Weekly testing should be logged. This is not box-ticking: the log is the documentation trail that demonstrates ongoing compliance if the building is ever audited or, in a worst-case scenario, if a claim needs to be investigated following an incident.
How often is professional servicing required?
At least every six months for most commercial systems, with five to seven months formally acceptable under BS 5839-1:2025. The specific frequency and scope should be confirmed against your building’s fire risk assessment and system category. A professional service visit covers considerably more ground than a user test: detector sensitivity testing, panel diagnostics, battery and standby power verification, and confirmation that the system configuration still matches the building’s current layout.
This is also where a competent maintenance contractor checks for configuration drift: situations where the building has changed (a refurbishment, a change of use, new partitioning) since the system was last formally reviewed, potentially leaving gaps in coverage that would not be obvious from a simple alarm test.
Who counts as a competent person?
Someone with the necessary training, experience and, in practice, recognised industry certification for the work being carried out. BS 5839-1 specifies that servicing must be carried out by a competent person, and this is one of the reasons accreditations like BAFE SP203-1 matter at a company level. They provide independent verification that the engineers attending your site meet that bar, rather than relying on the contractor’s own assurance.
What records do you need to keep?
A complete record of the date of each test or service, what was tested or serviced, any faults identified, and the action taken to resolve them. Gaps in this record (missed weeks, undocumented faults, unclear remediation) are consistently what auditors and insurers focus on, even when the underlying system is in good working order.
This is where paperwork usually fails, and where the Smartec Client Portal changes the picture. Every device we maintain carries its full testing history in a tamper-proof Digital Logbook, updated by the engineer during the visit, with defects photo-verified and tracked to resolution. When someone asks you to prove your testing regime, whether an inspector, your insurer or your board, the proof is a login, not an afternoon of reconstruction.
A quick checklist
To sense-check your current regime, confirm four things. Weekly user tests are actually happening and being logged, not just scheduled. Professional servicing is occurring at the frequency specified for your system category, not an informally reduced schedule. Documentation from both routine and professional testing is retained and easily retrievable. And your maintenance contractor is BAFE SP203-1 certified, or can otherwise demonstrate engineer-level competency.
Getting these basics right is the single most effective thing you can do to reduce both compliance risk and the likelihood of a system failure going unnoticed between formal service visits. If you would like a second opinion on your current testing regime, or want help establishing one from scratch, our team is happy to talk it through.