A compliant weekly fire alarm test means activating one manual call point on a rotating basis, carried out by the responsible person or a nominated trained colleague, following BS 5839‑1. If the system is monitored, you notify the alarm receiving centre before and after the test, then log the result straight away. Skip any of those steps and the test does not count as compliant, even if the alarm sounded fine.
TL;DR:
- Weekly testing must include rotating manual call points during normal hours with staff present to verify alarm audibility and response.
- Notify the alarm receiving center before and after the test if the system is monitored, to prevent false alarms and ensure compliance.
- Record detailed logs of each test, including faults, responses, and notifications, and address any faults immediately to avoid system failures.
- Larger premises require more extensive rotation and supplementary tests for night-shift staff, automatic door releases, and standby power systems.
- Engaging a qualified engineer for semi-annual inspections and annual detector testing helps catch faults early and maintain full system integrity.
Table of Contents
- Why weekly testing matters for safety and legal duty
- What BS 5839-1 actually requires for weekly testing
- How to run a compliant weekly fire alarm test
- Additional considerations and common scenarios
- What to do when a test finds a fault
- What belongs in the fire alarm logbook
- What years of on-site testing actually teach you
- How CityPat supports your weekly testing routine
- Sources
Why weekly testing matters for safety and legal duty
The Regulatory Reform (Fire Safety) Order places a duty on the responsible person to keep fire detection and warning systems in efficient working order. Weekly testing is the practical way that duty gets discharged in the real world, not once a year when the servicing engineer visits, but every week, on the ground.
A weekly test does three things at once:
- Confirms the panel registers an alarm, the correct zone indicator lights, and sounders actually operate.
- Catches early faults, a failing call point, a dead zone, a sounder that has gone quiet, before they become a real emergency problem.
- Familiarises staff with the alarm tone, so nobody hesitates or mistakes it for something else during an actual evacuation.
That third point gets overlooked constantly. Staff who never hear the alarm in a controlled setting are slower to react when it matters, and slower reactions cost seconds you do not have in a real fire.
What BS 5839-1 actually requires for weekly testing
BS 5839‑1 is the British Standard covering fire detection and alarm systems in non-domestic premises, and it sets out the weekly test in fairly specific terms. Getting the detail right is what separates a genuine compliance record from a box-ticking exercise that falls apart under scrutiny.
The standard’s core requirements:
- Test one manual call point each week, working through all outstations on a fixed rotation until every point has been checked.
- Run the test during normal working hours, so staff are present to confirm the alarm is actually audible throughout the building.
- Arrange periodic servicing by a competent engineer, roughly six-monthly for general inspection, with a full functional test of every detector at least annually.
- Contact the alarm receiving centre before starting the test and again once it is finished, if the system is monitored, to stop a false call-out.
That last point trips up more sites than any other part of the process. A monitored system that triggers without warning the ARC first can send a fire engine to your building for nothing, and repeated false alarms can eventually affect your response priority with the fire and rescue service.
How to run a compliant weekly fire alarm test
Follow this sequence in order, every week, without shortcuts:
- Check your rotation list to confirm which call point is due this week. A written rotation avoids the common mistake of testing the same convenient point every time and leaving others unchecked for months.
- Warn occupants that a test is about to happen, particularly if your premises has visitors, contractors, or shift staff unfamiliar with the routine.
- Notify the ARC if your system is monitored, before you touch the call point. Loughborough University’s guidance is a good example of the wording most sites use for this call.
- Activate the call point using the correct test key, not by breaking the glass. Test keys vary between call-point ranges, so check you have the right one for your specific model on site rather than reaching for whatever is nearest.
- Confirm the panel and zone respond correctly, and check that sounders in that zone are audible from a representative location, not just the one nearest the panel.
- Reset the call point, then silence and reset the panel, restoring any isolated outputs to normal.
- Call the ARC again to confirm the system has returned to normal monitoring status.
- Log the result immediately: date, time, device location, panel and zone response, audibility check, tester name, and any fault found.
Pro Tip: Do the reset and the logbook entry back to back, in the same visit. Testers who “log it later” almost always forget a detail, usually which call point they actually tested, and that gap is exactly what an inspecting officer will spot first.
Do not skip step 5 because the panel light comes on. A registered activation with no audible sounder in a distant stairwell is still a fail, and it is precisely the kind of fault a rushed test misses.
Additional considerations and common scenarios
Larger premises need a heavier rotation. On large sites with many outstations, testing multiple call points during each test period is advisable, keeping a rotation log to ensure full coverage.
Out-of-hours staff need their own exposure to the alarm. Cambridgeshire Fire and Rescue Service recommends running additional monthly tests timed for night-shift or weekend workers, since a standard daytime weekly test never reaches them.
A few other things to fold into the weekly routine where they apply:
- Test automatic door releases linked to the alarm system during the same activation, confirming they release fully and close onto their rebates.
- Check standby power arrangements where fitted, simulating a mains failure on load periodically if you have a generator.
- Escalate to a competent engineer immediately if you find marginal audibility or a coverage gap, rather than noting it and moving on.
Rotating call points systematically does more than tick a compliance box: it is one of the few routine checks that reliably surfaces a slowly failing sounder circuit or early battery degradation before either becomes a full system fault.
What to do when a test finds a fault
A failed call point or an unresponsive panel means the test stops there. Record the fault immediately, in detail, and arrange investigation before you consider the system fully operational again. Testing the next point on your rotation as if nothing happened, and hoping someone deals with the fault later, is how small problems turn into system-wide failures.
This is where a competent person earns their place in your maintenance plan. That means an engineer with the training, equipment and experience to service, inspect and certify fire detection systems, typically visiting for a full inspection roughly every six months, with an annual functional test of every detector on the system.
Ignoring a logged fault carries real consequences:
- Enforcement action from the fire and rescue service if an inspection finds unresolved faults in your records.
- Insurance complications, since insurers can question claims where a known fault went unaddressed.
- Increased false alarm risk, which can affect your standing with the fire service over time.
What belongs in the fire alarm logbook
Your fire detection test record, or logbook, is the audit trail that proves the testing above actually happened. Every entry should capture:
- Date and time of the test.
- Call point ID and location.
- Panel and zone response.
- Audibility check result.
- Tester’s name.
- Any fault found, and the action taken.
- Who was notified, the ARC, the premises manager, or both.
Paper logbooks still work fine, but back them up if you switch to an electronic system, since a corrupted file with no paper trail behind it leaves you with nothing to show an inspecting officer. Keep records for as long as your fire risk assessor advises, and have them ready to produce for the fire and rescue service on request, without needing to dig through archives to find them.
What years of on-site testing actually teach you
Training nominated testers across dozens of sites, the same handful of issues come up again and again: a sounder that has quietly failed in a back stairwell, a call point contact that has corroded from damp, staff who have never actually heard their own alarm. Most fixes are simple once caught early.
— Gemma
How CityPat supports your weekly testing routine
Some specialist safety compliance companies offer training for nominated testers and handle periodic servicing your weekly checks can’t cover, often without long-term contracts.
If your weekly tests have started flagging recurring faults, or you’re simply not confident your rotation and logbook would survive a real inspection, that’s exactly where a competent contractor earns its keep. CityPat’s fire alarm testing and servicing covers the six-monthly inspections and annual detector checks BS 5839-1 calls for, alongside ARC liaison and logbook support so your paper trail actually holds up. Many sites bundle this with emergency lighting testing and a fire risk assessment, since they’re usually due around the same time anyway. If you’d rather have a trained engineer take the periodic servicing off your plate entirely, get a free quote and we’ll talk through what your site actually needs.
Sources
For primary guidance beyond this article: the Fire Protection Association’s testing overview summarises BS 5839-1 intervals, Cambridgeshire Fire and Rescue’s logbook template gives a ready-made record format, and Loughborough University’s guidance sets out the step-by-step procedure in plain terms.
- How often should fire alarms be tested? | Fire Protection Association
- Weekly fire alarm test guidance | Loughborough University Health and Safety Service
- Commercial fire alarm testing: weekly tests & logbook guide — Midland Fire Direct