Fire alarm inspection report template (NFPA 72)
An NFPA 72 report names the panel, devices tested, deficiencies, sign-off, and next due date. Download the Word or PDF layout, then store the signed file.
A fire alarm inspection report shows the building and panel, which initiating devices and notification appliances were inspected or tested, any supervisory or interface tests, the deficiencies in plain language, who signed, and the next due date. The fire alarm file pack for that report is the blank Word template, the filled example, the Letter and A4 PDFs, and the field guides. NFPA 72 does not publish one official PDF. It sets the inspection and test work by component. The 2022 edition summary used here separates visual checks and functional tests, so an annual test line does not stand in for a shorter battery or device row. The files below are editable layouts, not an official NFPA form. Use the form your authority having jurisdiction names when it names one.
Download the fire alarm report pack
Grab the layout before the tech leaves the shop. Each file opens with a note that it is not an official NFPA form. Use your AHJ or licensed contractor form when they name one. The general multi system pack, including extinguishers and sprinklers, stays on the fire inspection report. Every blank is also listed from templates.
- Fire alarm blank Word template
- Filled example Word
- Letter PDF (US)
- A4 PDF
- Field guide Letter PDF and A4 guide
Get an email before the next inspection is due. 1 site free, no card.
The Word file uses tables for control equipment, initiating devices, notification appliances, supervisory inputs, deficiencies, and sign-off blocks. The PDF copies mirror the same sections for printing on site. The filled example is sample data for training, not a report you should submit.
Need extinguisher or sprinkler layouts too? The fire inspection report template page lists every system pack in one place.
What a fire alarm inspection report must prove
Inspectors and owners care about evidence, not branding. A usable fire alarm inspection report shows who was on site, which system was tested, which devices were exercised, what failed, who signed, and when the next test is due. Missing any of those fields turns the PDF into a story nobody can audit six months later.
Site identity belongs on page one: legal property name, street address, and panel or account number the central station recognizes. Room nicknames alone do not survive staff turnover.
Scope should state whether the visit was an annual, a quarterly device sample, a monthly owner visual, or a deficiency follow-up. Mixing scopes on one form without labels confuses the next tech.
Device detail means more than "100 percent tested." List counts or locations for smoke, heat, pull stations, duct detectors, waterflow and tamper switches, horns, strobes, speakers, and any emergency control functions you exercised. Your licensed contractor may use proprietary software; the owner still needs a readable export.
Deficiencies need plain language. "Strobe blocked by storage in Suite 204" beats "see notes." Each open item should say who will repair it and by when.
Sign-off requires the licensed technician or responsible party allowed in your jurisdiction. Electronic signatures are fine when your program accepts them.
Next due dates should match the intervals in your contract and NFPA 72 tables for the adopted edition. If the footer says annual but the body only covered half the initiating circuits, fix the report before upload.
How the report ties to NFPA 72
NFPA 72 does not sell a single universal PDF. It defines what to inspect and test and how often by component. Your report should show that the work listed on the ticket matches the table rows your vendor quoted.
Visual inspections from Table 14.3.1 and functional tests from Table 14.4.3.2 run on different calendars. An annual functional test does not prove semiannual battery marking happened. Split tasks on separate report sections or separate visits when your program tracks them independently.
The annual fire alarm inspection schedule page embeds the same 2022-edition table summary used on the NFPA 72 inspection checklist. Cross-check due dates on the report footer against those rows before you confirm reminders in software.
Sensitivity testing, heat-detector rotation, and generator monthly runs are easy to skip on a busy route. If the standard requires them for your occupancy, the report should name the method used, not a generic "system OK."
FireCert Clock does not interpret NFPA for you. It stores the file and the dates you confirm after a qualified person signs the report.
When your AHJ requires its own form or online filing
Some authorities having jurisdiction require their own report form or an online submission. Check with the local fire marshal before you file a generic template. The notes below are only rules confirmed on the official site named in each note.
California
The California State Fire Marshal enforces fire and life safety in state-owned buildings, specified state-occupied buildings, and state institutions. That office says it is not the authority having jurisdiction for local projects, and that its code interpretations do not replace the local authority (https://osfm.fire.ca.gov/what-we-do/code-development-and-analysis/code-interpretations, checked 30 Oct 2026). When the State Fire Marshal inspects a state building, a representative of the owner or manager signs the inspection report in a GOVmotus account (https://osfm.fire.ca.gov/what-we-do/fire-and-life-safety, checked 30 Oct 2026). Ask your local fire marshal which form or portal applies to a private building.
New York City
FDNY publishes its own fire alarm inspection forms, including Fire Alarm Inspection B-45. Effective 11/7/2025, follow-up inspections and cancellations for the Fire Alarm Inspection Unit must be requested online through FDNY Business. Initial inspection requests are completed in person on the current B-45 (https://www.nyc.gov/site/fdny/business/inspections/request-inspection.page, checked 30 Oct 2026).
Owner visuals versus contractor tests
Building staff often own weekly or monthly panel visuals between vendor visits. The licensed fire alarm contractor still owns most functional tests. When both groups use one form, label who performed each block so the fire marshal does not assume the annual covered a monthly battery row.
Owner entries might cover trouble log review, primary power indicator, and obvious damage to devices in public corridors. Contractor entries cover smoke entry tests, pull-station operation, notification appliance activation, and interface tests with elevator or HVAC partners present.
Two assets in FireCert Clock, two owners or two technicians, keeps monthly owner work from hiding the licensed annual on one due date.
After the visit: upload and confirm dates
A report that stays on a phone camera roll does not help the next shift. When the PDF is final:
- Open the site in FireCert Clock and select the fire alarm asset (or split assets if you track batteries separately).
- Upload the PDF on the visit record.
- Confirm last service and next due on Starter and above when AI reads the footer, or type them when the layout is nonstandard.
- Let email notices run at 30, 14, 7, 3, and 1 day before due, plus overdue visibility when someone misses a walk.
Free is $0 a month for 1 site and 25 assets with mail to you. Starter is $39 a month for client emails and AI date reading on many contractor PDFs. Pro adds your logo on the owner-facing site export. See pricing.
Log a visit only when the work passes, since logging moves the next due date.
Central station and monitoring paperwork
Many sites receive a separate central-station test summary. Store that PDF on the same asset or a child asset labeled monitoring so an auditor sees both the field report and the station acknowledgment.
If the station report disagrees with the field report on time or device count, reconcile before you confirm dates. Reminders follow what you save in the product, not what was true on the truck if the office typed the wrong year.
Deficiency follow-up reports
When the annual finds open troubles, the follow-up visit deserves its own PDF or a clearly labeled addendum. Closing a deficiency without a written record leaves the original annual looking incomplete.
Photograph blocked strobes or missing detector covers when photos are part of your quality program. Reference image filenames in the deficiency table so the PDF narrative stays coherent.
Multi-building and campus programs
Campuses often share one contractor letterhead but need per-building reports. Duplicate the site in FireCert Clock when each building has its own AHJ file number or separate panel.
Sample testing plans for heat detectors should note which devices were tested this year so rotation records survive staff changes. The report footer can reference an attachment with device IDs when the main table only has counts.
What FireCert Clock does not do
The product is a due-date register and file cabinet. It does not pull points from the panel over the network, does not replace your licensed alarm contractor, and does not auto-fill a proprietary NFPA form your vendor sells.
You produce the inspection report in the field with these templates, your existing forms, or your contractor software. FireCert Clock stores the finished PDF, shows overdue assets, and exports a site compliance PDF for owners.
Cross-links for the same visit week
Alarm work rarely stands alone. The annual fire inspection checklist covers extinguishers, sprinklers, emergency lights, and doors on the same marshal walk. Sprinkler intervals live on the sprinkler inspection schedule page. Keep each system on its own assets so one overdue row stays visible.
Use the NFPA inspection frequency lookup when you need a quick row for another system before you add assets.
FAQ
Is this download an official NFPA form?
No. It is an editable layout. Your AHJ or insurer may require a specific format. Use theirs when named.
Can we edit the Word template with our logo?
Yes. Add letterhead in Word before you send the file to techs. Export to PDF when the client wants a fixed layout.
Why keep both Word and PDF?
Some teams draft in Word and print to PDF for signatures. Others mark up PDF on a tablet. Offer both so nobody retypes tables in the parking lot.
Does uploading change asset due dates automatically?
You confirm dates on save. Starter can suggest dates read from the upload. Correct wrong years before reminders send.
What if the contractor already uses their own software?
Export their PDF and upload it. These templates are for teams that want a starting layout or a sample for new hires.
Can the building owner get the same reminders?
On Starter and above, add the client contact email on the site. They receive the same notice schedule you do.
Do we need a separate report for monthly owner checks?
Use a short owner log or the same template with the scope labeled "owner visual." Upload so the site PDF tells one story.
Where do intervals come from if we do not read the code?
Start with the schedule and checklist tables for NFPA 72 (2022), then confirm with your vendor and AHJ.
Make the report habit stick
Print the filled example in the shop. New techs copy section headings before they copy shortcuts. When every truck returns the same blocks, the office spends less time fixing PDFs and more time booking the next quarter.
Download the pack above. Finish the visit. Upload once. Let the inbox tell you when the next test is due.
The printable set and the calculator sit on Templates.
Support and Terms. Calculator.