Fire alarm weekly testing log template
A ready-to-use weekly fire alarm test log template, what each column records, how to use it correctly, and what to do when the test identifies a problem.
The weekly fire alarm test log is the written record that proves your testing regime is being carried out. Under BS 5839-1, all test results must be recorded in the fire alarm log book — a missing or incomplete log is evidence of non-compliance during an inspection. This template gives you everything you need to record tests correctly from day one.
Weekly Fire Alarm Test Log
Copy or print the template below and keep it in your fire alarm log book. Complete one row for each weekly test.
| Date | Time | Call point tested (No. / location) | Panel responded correctly? | Sounders audible? | ARC notified? | Any faults noted | Tested by (print name) | Signature |
|---|---|---|---|---|---|---|---|---|
| Yes / No | Yes / No | Yes / No / N/A | ||||||
| Yes / No | Yes / No | Yes / No / N/A | ||||||
| Yes / No | Yes / No | Yes / No / N/A | ||||||
| Yes / No | Yes / No | Yes / No / N/A | ||||||
| Yes / No | Yes / No | Yes / No / N/A |
How to fill it in
Completing Each Column Correctly
| Column | What to record |
|---|---|
| Date | The date the test was carried out — not the date it was planned or the date the log was written up. Tests should be recorded on the day they are carried out |
| Time | The time the alarm sounded. BS 5839-1 recommends testing during normal working hours when the building is occupied |
| Call point tested | The number or location of the specific call point tested. Each call point should have a reference number — use the zone plan or device schedule. Rotating through all call points ensures every device is tested over time |
| Panel responded correctly? | Yes if the panel showed an alarm in the correct zone or with the correct device address. No if there was no alarm, the wrong zone alarmed, or the panel showed a fault instead of an alarm. Any No answer requires immediate investigation |
| Sounders audible? | Yes if the alarm was clearly audible throughout the areas it should cover. No if any area was identified as having poor or no audibility. Any No requires investigation and must be reported to the maintenance contractor |
| ARC notified? | Yes if you called the ARC before and after the test. N/A if your system is not monitored. Never start a test on a monitored system without notifying the ARC first — failure to do so can result in an unnecessary emergency response |
| Faults noted | Any fault indications on the panel before, during, or after the test; any sounder that appeared not to activate; any visible damage to devices noted during the test walk. Write “None” if there are no faults — do not leave blank |
| Tested by | Full printed name of the person carrying out the test. This creates an accountable record of who performed each test |
Call point rotation
Rotating Through All Call Points
BS 5839-1 requires that call points are tested on rotation so that every call point is tested at regular intervals. A simple way to manage this is to number all call points on a building plan and keep a separate rotation schedule showing which call point to test each week. The schedule and the log together provide clear evidence that every call point receives regular testing.
If your building has twelve call points, each one will be tested approximately once per quarter on a weekly rotation. If your building has four call points, each will be tested approximately once a month. The goal is that no call point goes more than a few months without a functional test.
What Happens if You Miss a Weekly Test
Missing occasional weekly tests is not uncommon — holidays, building closures, and staff absences happen. What matters is that missed tests are acknowledged in the log book (note the date and reason) and that the testing resumes promptly. A log book showing weeks or months of missing entries, with no explanation, is a clear indication to an inspector that the testing regime has broken down. An honest record with occasional documented gaps is far better than a log with no entries at all.
What to do when problems are found
Acting on Test Results
The weekly test is only valuable if problems identified during testing are acted on. The immediate actions for common test outcomes are:
- Panel did not alarm — record in log, call maintenance contractor immediately; this is a Category 1 fault
- Wrong zone alarmed — record in log, call maintenance contractor; the zone labelling or wiring may need correction
- Sounders not audible in part of building — record in log, call maintenance contractor; check whether a sounder circuit fault is indicated on the panel
- Panel showing pre-existing fault — check whether this was previously recorded; if not, record it now and contact contractor
- Call point test key not working — record, investigate whether key is wrong type for the call point; contact contractor if key cannot be made to work
Every fault identified during a weekly test should be followed up until it is resolved, with the resolution recorded in the log book. See our guide to common fire alarm faults for more detail on fault types and responses.
Common questions
Frequently Asked Questions
Yes — BS 5839-1 permits electronic records provided they meet the same requirements as a paper log: all required information recorded promptly, accessible on the premises, and available for inspection. A spreadsheet, dedicated maintenance app, or building management system log are all acceptable. The key practical requirement is that the record can be accessed and printed at any time — not just by the person who created it.
No — the weekly call point test is an operational check carried out by building staff. It is not a substitute for the six-monthly professional service visit required by BS 5839-1, which covers detector testing, battery testing, wiring inspection, and a full service report. The weekly test and the professional service visits serve different purposes and both are required.