A fire alarm log book is the running record, on paper or in a file, of everything that happens at the panel: real and false alarms, trouble messages, devices disabled and returned to service, and every test or maintenance visit. The inspection report is a different document: the maintenance contractor issues it after each periodic visit to show what was inspected, what passed and what is still open. This article explains what goes into each one and gives a field-by-field template for a periodic fire alarm report, based on the structure of the NFPA 72 inspection and testing form. Both are part of what a facility receives under AZEIDK annual maintenance contracts.
Key Takeaways
- The log book is kept daily on site; the inspection report is issued after each maintenance visit.
- Every log entry needs the date and time, event type, device address and location, cause, action taken and the name of the person recording it.
- Any disabled detector or zone is logged with the reason, who approved it, the interim measure and when it went back into service.
- A useful inspection report lists the result for every device by address, not just a device count, and ends with uncorrected deficiencies signed by the owner.
- The panel event memory helps with review, but it does not replace a written log that explains causes and actions.
In this article
- What Is a Fire Alarm Log Book, and How Is It Different from the Inspection Report?
- What to Record in a Fire Alarm Logbook
- Does the Panel Event Memory Replace a Written Log?
- Disablements and Isolations: The First Entry Inspectors Look For
- Fire Alarm Inspection Report Template: Core Fields (Non-Official Sample)
- How Long Should Fire Alarm Records and Reports Be Kept?
- Using the Log to Reduce False Alarms
- Common Mistakes in Fire Alarm Logs and Reports
- What a Maintenance Contract Provides
- Frequently Asked Questions
- Summary
What Is a Fire Alarm Log Book, and How Is It Different from the Inspection Report?
Facilities often mix up three documents. The first is the building’s overall fire safety log, which covers every system from sprinklers and fire pumps to extinguishers; we covered it in Fire Safety Log Book and Maintenance Records. The second is the fire alarm log book, which covers only the panel and its devices and is filled in by the building’s security or maintenance staff whenever something happens. The third is the inspection and testing report written by the maintenance contractor after each visit.
In practice, the log answers “what happened to the system this month?” and the report answers “did every device work as it should on the day of the test?”. Read together, they show the owner where problems keep coming back and which devices need repair or replacement.
What to Record in a Fire Alarm Logbook
There is no unified, published Saudi form for a fire alarm panel log. The entries below cover what inspectors, consultants and maintenance contractors usually ask for:
| Entry type | When it is written | Required details |
|---|---|---|
| Fire alarm | Every alarm activation | Date and time, device address and location, real fire or false alarm, likely cause, reset time |
| Fault / trouble | Whenever a trouble message appears | Message text as displayed, circuit or address, time reported to the contractor, time repaired and by whom |
| Supervisory signal | Signal from a monitored valve, fire pump or interfaced system | Source, cause, action, time restored to normal |
| Disable / isolate | Before any device, zone or output is disabled | Device or zone, reason (hot work, painting, maintenance), who approved, interim measure, time re-enabled |
| Test or maintenance visit | Every periodic or corrective visit | Contractor and technician, visit type, attached report number, open items |
| Programming or device change | When a device is added, moved or the cause-and-effect changes | What changed, who did it, test result after the change, drawing updates |
| Mains power failure | When the panel switches to batteries | Duration, panel status after power returns, any messages shown |
The rule that makes a log useful: every open entry is closed by a matching one. An alarm has a reset time, a fault has a repair time, and a disablement has a re-enable time.
Does the Panel Event Memory Replace a Written Log?
Modern addressable panels store events internally. For example, AZEIDK’s page for the Context Plus Single Loop 16 Zone panel, one of the addressable fire alarm panels AZEIDK supplies, lists event monitoring and an event memory among its features. It is very useful during review because it records times and addresses precisely.
It is not enough on its own, for three reasons. The panel records what happened, not why: it cannot know that an alarm was caused by kitchen steam or dust from fit-out works. Memory capacity is limited according to the model’s datasheet, and older events may be overwritten. And the panel does not record who approved a disablement or what interim measure was in place. The practical approach is for the building manager to review the event memory regularly against the written log, and for the technician to check the panel clock and date at every visit, because a wrong clock makes the entries impossible to compare.
Disablements and Isolations: The First Entry Inspectors Look For
The most dangerous condition in any alarm system is a disabled device everyone has forgotten. It often happens after welding, painting or tenant fit-outs: a detector or a whole zone is isolated to avoid nuisance alarms, the work ends, and the isolation stays. A fixed procedure helps:
- No device is disabled without written approval from the building manager, and the entry is made before the disablement, not after.
- The interim measure is stated, such as periodic patrols of the area or an extinguisher close to the work.
- An expected re-enable time is set and checked at the end of every shift.
- The panel display is checked at the end of the day to confirm no device or zone is left disabled.
During a maintenance visit the technician usually pulls the list of disabled points from the panel and compares it with the log. Any disabled device with no log entry appears in the report as a deficiency.
Fire Alarm Inspection Report Template: Core Fields (Non-Official Sample)
NFPA 72 has a documentation chapter (Chapter 7), added in the 2013 edition, which covers the Record of Completion and the Record of Inspection and Testing. The table summarises the sections of the NFPA 72 (2013 edition) inspection and testing form as published by the City of Columbus, Ohio. It is a non-official sample to agree with your contractor, not an official form issued by Civil Defense or any Saudi authority:
| Section | Fields |
|---|---|
| Visit details | Inspection start and completion date and time, supplementary sheets attached |
| Property information | Name, address and description of the property; owner’s representative and contact details |
| Testing and monitoring organisations | Maintenance contractor details; remote monitoring organisation, if any, and means of transmission |
| Documentation | On-site location of system record documents and site-specific software |
| System description | Control unit manufacturer and model, firmware revision, primary power, secondary power, battery type and calculated capacity |
| Notifications before testing | Who was notified and when: monitoring organisation, building management, occupants, authority having jurisdiction |
| Test results | Control unit and related equipment (indicators, display, fuses, trouble and supervisory signals, remote panels), batteries (condition, load voltage, charger test), initiating devices and notification appliances on attached sheets, interface equipment, supervising station signals |
| Notifications that testing is complete | Same parties with time |
| System restored to normal | Date and time |
| Certification | Technician signature, name, organisation, qualifications and date |
| Deficiencies not corrected | List of uncorrected defects, with acknowledgement signed by the owner or representative |
The Device Results Sheet
This is what separates a real report from a paper exercise. One line per device: address or circuit number, device type (smoke detector, heat detector, manual call point, sounder or strobe, input or output module), location, type of check (visual or functional), result and remarks. For which devices are tested at each visit and how often, see our fire alarm maintenance checklist.
How Long Should Fire Alarm Records and Reports Be Kept?
It depends on the reference:
- In the 2010 edition of NFPA 72, inspection and testing records were covered in section 14.6.2; from the 2013 edition, documentation and records retention moved to Chapter 7 (section 7.7). Published summaries of these requirements state that inspection and testing records are kept until the next test and for one year after, on a medium that lasts for that period. Check the exact period and clause in the NFPA 72 edition adopted for your project.
- The fire and life safety maintenance plan for municipal facilities (document EOM-ZM0-PL-000046-AR, 2020) issued by EXPRO, the Saudi Authority for Spending Efficiency and Government Projects, which applies to municipal facilities, requires all records to be kept on site for at least three years, and recommends a dedicated fire protection log as the single reference for all safety system activities.
- The Record of Completion and as-built drawings are normally kept for the life of the system because every later change refers back to them; the 2010 edition of NFPA 72 (10.18.2.1.2.5) requires a copy of the Record of Completion at the fire alarm control unit or another approved location.
In practice, keeping all fire alarm reports on site for at least three years is the simplest approach, because older reports are the only way to spot recurring faults.
Using the Log to Reduce False Alarms
When false alarms are logged with device addresses and causes, patterns appear within a few months: a smoke detector near a kitchen that goes off at cooking times, a zone that throws faults after rain, or an old detector that alarms with no visible cause. These patterns drive the technician’s decision to change the detector type, relocate it, clean it or replace it. Common causes and fixes are covered in our article on fire alarm false alarm causes.
Common Mistakes in Fire Alarm Logs and Reports
- A visit report that just says “system OK” with no device list and results.
- A disablement entry with no re-enable time, or a disablement never logged at all.
- Resetting the panel after an alarm without recording which device triggered it.
- A panel clock that is wrong, so event memory times do not match the log.
- Programming changes or added devices without updating the Record of Completion and drawings.
- Reports kept only by the contractor, with no copy on site for the owner.
What a Maintenance Contract Provides
Under AZEIDK periodic maintenance contracts, the owner receives a report after each visit with findings, remarks and recommended corrective actions, plus an updated maintenance log that can be presented at inspection or licence renewal. The fire systems maintenance contract covers fire alarm, fire fighting and related safety systems; CCTV and low current systems normally sit under a separate maintenance contract, and one contract never combines the two groups. For the periodic tests themselves, see Fire Alarm Maintenance: Periodic Inspection and Testing Under NFPA 72 and SBC 801.
To be clear: the technical report required on the Salamah platform is issued by engineering consultancy offices, not by AZEIDK. Under its Civil Defense approval support service, AZEIDK issues the safety equipment installation certificate. Well-kept maintenance reports and a clean fire alarm log make the consultant’s and the inspector’s work easier.
Frequently Asked Questions
Who fills in the fire alarm log book?
The building’s security or maintenance staff record daily events such as alarms, faults and disablements. The maintenance contractor adds an entry for each visit and attaches its report.
Is there an official fire alarm report sample in Saudi Arabia?
We found no unified published form for fire alarm panels. The structure of the NFPA 72 inspection and testing form is a sound basis, agreed in the maintenance contract.
Is an electronic log acceptable instead of a paper book?
Yes, as long as it is kept in a way that lasts for the retention period and can be shown at inspection. The EXPRO plan for municipal facilities accepts paper or electronic records.
What should I write after a false alarm?
Record the time, device address and location, likely cause and reset time, and tell the maintenance contractor if the same device alarms again.
How often should a fire alarm inspection report be issued?
After every periodic or corrective visit. The maintenance contract sets the visit schedule according to the system and the devices to be tested.
Does AZEIDK issue the Salamah technical report?
No. Engineering consultancy offices issue the technical report. AZEIDK issues the safety equipment installation certificate and provides maintenance reports and logs under its contracts.
Summary
The fire alarm log book tells the day-to-day story of the system, and the inspection report proves the condition of every device on the day of the visit. Close every open entry with a matching one, ask your contractor for a result per device and address, and keep copies on site for at least three years. That turns the log into a tool for cutting faults and false alarms, not paperwork prepared the night before an inspection.
Need regular maintenance reports and an up-to-date fire alarm log for your facility? Send us the panel type, device count and site location, and our team will prepare the maintenance scope and visit schedule. Contact the AZEIDK team
