Last Updated: October 28, 2026
Quick Summary
A fire alarm logbook is a written record of every test, inspection, fault and repair carried out on a building’s fire alarm system. It is the single document that proves your system was checked, and checked on time, when an auditor or fire officer asks. An auditor does not test your alarm; they read your records and spot-check your building against them.
- A logbook entry should capture six core fields: date and time, item checked, result, tester, signature and corrective action.
- The weekly test should cover one manual call point or detector on rotation, with the next device noted in each entry.
- Fire alarm testing records must name the person who did the work and carry their signature, or they prove nothing.
- Keep historical safety records for at least three to five years to show a consistent pattern of compliance.
- Never leave a fault entry open without a follow-up date, as auditors read it as an unresolved defect.
Table of Contents
- Why a Fire Alarm Logbook Is Your Best Compliance Evidence
- What Belongs in a Fire Alarm Logbook Template
- Fire Alarm Testing Frequency and the Weekly Test Routine
- Fire Alarm Testing Records: What to Write Down and Who Signs
- Recording False Alarms, Faults and Corrective Actions
- Digital Fire Alarm Logbook vs Paper: Audit Trails and Backups
- Common Record-Keeping Mistakes That Weaken Your Compliance Case
- Book Your Fire Alarm Testing and Get Audit-Ready Records
- Frequently Asked Questions
Why a Fire Alarm Logbook Is Your Best Compliance Evidence
A fire alarm logbook is a written record of every test, inspection, fault and repair carried out on a building’s fire alarm system. It is the single document that proves your system was checked, and checked on time, when an auditor or fire officer asks.
The testing gets done. The paperwork does not. Then an audit arrives and the whole compliance case rests on memory and a folder of loose invoices.
That gap matters because the importance of fire alarm logbook record keeping is not about tidiness. It is about evidence. Preventive measures research from the National Center for Biotechnology Information found that systematic documentation of risk management is critical to reducing fire-related injuries. Records are part of the safety system, not an afterthought.
Here is what most guides miss: an auditor does not test your alarm. They read your records and spot-check your building against them. Weak records fail audits even when the system is sound.
Below, we break down exactly what to write, who signs it, and how to keep it inspection-ready.
What Belongs in a Fire Alarm Logbook Template
A fire alarm logbook template should capture six core fields for every event: the date and time, the item checked, the result, the person carrying out the check, their signature, and any corrective action taken. Miss any one of these and the entry is hard to defend.
The practical structure looks like this:
- Date and time of every test, inspection or fault
- System or device covered, by zone or location
- Test results recorded as pass, fail or defect
- Person carrying out the check, printed name and signature
- Corrective action and the date it was completed
- Next scheduled service date
Keep the logbook on site and in one place. A folder split across three cupboards is not a logbook, it is a scavenger hunt.
For a field-by-field walkthrough of each entry, see our guide to fire safety logbook documentation tips.
Fire Alarm Testing Frequency and the Weekly Test Routine
Fire alarm testing frequency is a key part of maintaining records. The weekly test is the one most sites get wrong, because it looks simple and gets skipped.
A clear split of who does what keeps the schedule honest:
| Routine | Who carries it out | Typical interval | Where it is recorded |
|---|---|---|---|
| Weekly test | Trained staff member or site caretaker | Weekly | Logbook, signed by the tester |
| Monthly inspection | Responsible person or delegated staff | Monthly | Logbook, with any defects noted |
| Six-monthly service | Licensed fire technician | Every six months | Service report filed in the logbook |
| Annual service and certification | Licensed fire technician | Annually | Annual certificate and service report |
Your weekly routine should take minutes, not hours. A worked example of a defensible entry looks like this:
- Test one manual call point or detector on rotation, for example Zone 4, Level 2 east stair lobby
- Confirm the alarm sounds and the panel registers the correct zone
- Check the panel shows no outstanding faults
- Record the result, date, time and your signature
- Log any fault and report it the same day
A completed weekly entry might read: “Zone 4 manual call point tested at 09:15. Alarm sounded and panel registered Zone 4. No outstanding faults. Tested by J. Nguyen (signature). Next device on rotation: Zone 5.” That entry tells an auditor what was tested, when, by whom, and what comes next.
Those service reports belong in the same logbook, filed against the date of attendance, so the full history sits in one place.
Rotate the weekly test device in a fixed sequence and note the next device in each entry. It proves the whole system is being covered over time, not just the same call point every week.
For the full AS 1851 breakdown and a maintenance checklist, read our commercial fire alarm maintenance guide.
Fire Alarm Testing Records: What to Write Down and Who Signs
Fire alarm testing records must name the person who did the work and carry their signature. An unsigned entry proves nothing, because nobody can be held to it.
Write the entry so a stranger could understand it. “Tested, all good” tells an auditor nothing. Instead, note the zone, the device, the result and the action taken.
Who signs what:
- Weekly in-house tests: the staff member who ran the test signs
- Six-monthly and annual servicing: the licensed technician signs, with their licence details
- Faults and repairs: whoever attended signs, plus the date the repair was verified
The responsible person for the premises should review and countersign periodically. That review is itself evidence of premises management oversight.
Recording False Alarms, Faults and Corrective Actions
Every false alarm, fault and defect needs its own entry, with the corrective action and the date it closed out. This is the section auditors read hardest, because it shows whether you fix problems or just note them.
A recurring fault with no repair record is a red flag. It suggests the system is unreliable and nobody acted. Guidance on retaining historical safety records recommends keeping records for at least three to five years so a consistent pattern of compliance can be shown. Failing to maintain this documentation leaves building owners vulnerable to severe legal safety consequences that extend well beyond fire systems into other critical areas of facility management.
For each event, record:
- What triggered the alarm, if known
- Which zone or device was involved
- The fault or defect found
- The corrective action taken
- The date the repair was completed and verified
A consistent incident workflow is what turns a list of events into evidence of corrective action:
- Log the event on the day it happens, with the time, zone and device
- Classify it as a false alarm, fault, defect or damage
- Assign an owner and a target date for the fix
- Record the corrective action when the work is done, with the technician’s name and licence details where relevant
- Verify and close out the entry, with the date the repair was confirmed working
- Review the pattern at each service visit to spot repeat faults in the same zone or device
A worked example of a closed-out entry: “14 March, 22:40. Zone 7 smoke detector activated, no fire found. Classified as false alarm, likely cooking smoke from adjacent kitchen. Detector cleaned and sensitivity checked by licensed technician on 18 March. Verified clear on retest 18 March. Closed out 18 March.” That entry shows the event, the cause, the action and the verification in one place.
Never leave a fault entry open without a follow-up date. An open entry with no close-out reads to an auditor as an unresolved defect, even if the repair was done and simply not written down.
Our breakdown of common fire alarm faults in commercial buildings covers the issues most likely to show up in your log, so you can log and resolve them properly.
Digital Fire Alarm Logbook vs Paper: Audit Trails and Backups
A digital fire alarm logbook can provide audit trails and backups. Paper is another record-keeping format.
Modern digital systems timestamp every entry, track who changed what, and store records off site. Compliance record-keeping guidance from CalmCompliance notes that logbooks are increasingly built to track maintenance, training and corrective actions against rising regulatory scrutiny.
Where paper falls down:
- Entries go missing or get rewritten
- One spill or fire destroys the whole history
- No proof of who edited what, or when
- Hard to search when an auditor asks for zone 4
Where digital falls down:
- Poor systems with no export or backup
- Staff who log in under a shared account, killing the audit trail
If you are weighing the switch, our article on automated fire safety compliance software covers how audit trails and backups actually work in practice.
Common Record-Keeping Mistakes That Weaken Your Compliance Case
Treating the logbook as admin rather than evidence can weaken a compliance case. Gaps, vague entries and missing signatures can make records harder to assess.
Watch out: back-filling entries weeks later can undermine confidence in the records. An auditor who spots a page filled in one sitting with the same pen may question the entries.
Common record-keeping mistakes include:
- Gaps in the weekly test record with no explanation
- Vague results like “checked” or “OK”
- No signature or an illegible one
- Faults logged but never closed out
- Separate folders for tests, repairs and service reports
- No fire extinguisher or emergency lighting records in the same system
Fire safety equipment records matter as much as alarm records. Extinguishers, fire doors, exit signs and emergency lighting all need their own entries, on their own schedule.
If your last audit went badly, our guide to why fire safety reports fail audits walks through the defects auditors flag most.
Book Your Fire Alarm Testing and Get Audit-Ready Records
Paperwork is one part of preparing for an audit.
Fyrepower is fully insured and QBSA-licensed, and we work to Australian standards including AS 2444 and AS 1851. We provide professional testing services across residential, commercial and industrial properties. Our team also runs on and offsite fire training, so your staff know what to do when an alarm sounds.
Get in touch with Fyrepower and get audit-ready records in place before the next inspection lands.
Frequently Asked Questions
Why is it important to keep a fire alarm logbook?
A fire alarm logbook records testing, servicing and repairs. Without records, you may have done the work but cannot prove it when it counts.
How often should a fire alarm system be tested and recorded?
A clear testing schedule with named responsibilities can help keep records organised.
What should you do if a fire alarm test or inspection identifies a fault?
Record the fault immediately, including the date, time, what failed and who found it. Then log the corrective action taken, the repair date and the signature of the person who completed it. An inspection-ready record shows the fault was found and fixed, not just noted. Recurring faults can be tracked separately.
Can fire alarm maintenance records be kept digitally?
Digital fire alarm logbooks are one possible record-keeping format.
