What Belongs in a Fire Alarm Inspection Report (and What Doesn't)

A fire alarm inspection report has two jobs. It proves the system was inspected and tested the way the code requires, and it tells the owner exactly what needs attention. A report that does the first job but not the second is a stack of paper. A report that does neither is a liability for everyone who signed it.

I have read thousands of these, ours and other companies’, on service takeovers and at fire marshal meetings. Here is what belongs in a fire alarm inspection report, and what does not.

Who Actually Reads the Report

Before the checklist, remember the audience.

• The building owner or property manager reads the first page and the deficiency list. They want to know if the system passed, what is wrong, and what it will take to resolve it.
• The fire marshal reads for proof. Was every device tested? Was the supervising station notified and were signals received? Who did the work, and are they qualified?
• The next technician reads for history. What failed last year? What batteries are in the panel and when were they installed?

A good report serves all three without making any of them dig.

What Belongs in a Fire Alarm Inspection Report

Property and system information

The top of the report should identify the property, the address, the customer, the date and time of the inspection, and when the system was restored to normal. It should identify the fire alarm control unit by manufacturer, model and location, plus the monitoring arrangement: supervising station, account number and means of transmission.

Code edition

State which edition of NFPA 72 the inspection was performed under. That should be the edition adopted by your AHJ. When the edition is missing, a fire marshal has no way to tell whether the frequencies and methods in the report are the right ones.

Notifications made before testing

Who was notified before testing started: the supervising station, the AHJ where required, building management and occupants. Include names or contacts and times where you have them. This is basic, and it is often missing.

Test methods

For each device type, the report should show how it was tested. Smoke detectors tested with listed aerosol or other approved methods, heat detectors by the method appropriate to the type, waterflow by flowing water through the inspector’s test connection. “Tested” by itself is not a method.

Device-by-device results

Every initiating device and notification appliance should appear on its own line with:

• Device type
• Address or zone
• Location in plain language (“2nd floor corridor outside 204,” not “2C”)
• Result: pass, fail, or not tested, with the reason if not tested

This is the heart of the report. Summary statements like “all devices tested” do not tell the fire marshal anything and do not help the next technician find the one detector that failed.

Control unit and power supply checks

Control unit condition, indicators, trouble signals, ground fault monitoring, supervision of circuits, and any remote power supplies or notification appliance panels. Each of these should have its own result.

Battery information

For each battery set: location, type, size, install date, and the test results. Batteries are where systems quietly fail, and a battery line that just says “OK” is not enough to plan a replacement.

Supervising station signal verification

Record that alarm, supervisory and trouble signals were transmitted and received at the supervising station, with the time and the person who confirmed. A system that works at the panel but does not report off premises is not doing its job.

Deficiencies, with location and description

Every deficiency should say what device, where it is, what is wrong with it, and what should be done. I go deeper on this in a separate post, but the short version: write it so someone who has never seen the building can walk to the device and know what to do.

Photos

A photo of a damaged device, a painted-over detector, or a blocked pull station ends arguments. Photos of the panel and the batteries help the next technician come prepared.

Technician name and qualifications

The report should name the technician who performed the work and list their qualifications. In Connecticut, NICET credentials are what fire marshals expect to see.

Signatures and dates

Technician signature, date, and the owner’s or representative’s acknowledgment where your process includes it. An unsigned report is a draft.

What Doesn’t Belong in a Fire Alarm Inspection Report

Pages of N/A

A small office with a conventional panel and twenty devices does not need four pages of voice evacuation, elevator recall and fire pump questions marked N/A. Those pages make the report longer, hide the results that matter, and train readers to skim. A report should ask about the systems the building actually has.

Vague deficiency language

“Bad detector.” “Needs repair.” “Panel issue.” None of these tell the owner what to approve or tell the next technician what to bring. Name the device, the location, the condition and the recommended action.

Unsupported pass statements

“System passed” with no device list behind it is not proof of anything. A pass is only as good as the line items that support it.

Boilerplate that contradicts the results

A cover letter that says “the system is in good working order” on top of a deficiency list with three failed notification appliances is a problem waiting to happen. Let the results speak.

How This Connects to Reading Your Report

If you are a building owner trying to make sense of a report you already have, start with our post on how to read and understand your fire safety inspection report. This checklist is the other side of the same coin: what the report should have contained in the first place.

How We Build Reports at Titan

At Titan we run inspections on CodeGreen ITM, the software I co-founded because the tools we had did not fit the way an inspection shop works. The inspection only asks what the building has, so there are no pages of N/A to scroll past. Devices come in from a panel point report, results are recorded device by device, deficiencies carry before and after photos, and the report goes out with our logo, our license number and the technician’s qualifications. Multiple services on one visit go out as one combined report. You can see more on our fire alarm inspection software page.

Frequently Asked Questions

Is there a required fire alarm inspection form?

NFPA 72 includes sample inspection and testing forms, and many contractors base their reports on them. Your AHJ may require a specific format or specific content. What matters most is that the report contains the information the code and your AHJ require for the edition they have adopted.

How long should I keep fire alarm inspection reports?

NFPA 72 sets minimum record retention requirements, and some AHJs and insurers want more. Keep them at least as long as your AHJ requires, and keep the current report with the system documentation.

What should I do if my report has no device list?

Ask your contractor for the device-by-device results. If they cannot provide them, it is fair to ask how the inspection was performed.

Get a Report You Can Actually Use

Connecticut building owners: Titan Fire Protection performs fire alarm inspections and testing across Connecticut with reports built device by device. Request a quote or call 860-322-9028.

Fire alarm contractors nationwide: see how CodeGreen ITM builds inspection reports, or start a 60-day free evaluation at app.codegreenitm.com/signup. No credit card needed.