I once inherited an annual report where every single line said "Yes." Every device, every circuit, every battery. One of the notification appliances on that report was sitting behind a fresh coat of paint, lens and all. Nobody had tested it, and the form said somebody had.
That's the whole reason this form exists. It's the paper that says what you actually did.
First, which form are you holding?
"NFPA 72 form" is a bit of a trap search, because NFPA 72 ships more than one. The two you'll meet on a job:
- Record of Completion. Done once, when a new system or a major change is finished. It describes what was installed. I covered it already in the Record of Completion article, so I won't repeat it here.
- Inspection and Testing Form. Done on a schedule, over the life of the system. It describes what you checked and what you found. This is the one most techs mean on the second Tuesday of a service contract.
Rule of thumb: new or changed system, Record of Completion. Existing system, periodic visit, Inspection and Testing Form. Acceptance testing of new work leans on the first, and your annual lives on the second.
One honest caveat. NFPA publishes these forms, and I'm not going to reproduce them here. They're copyrighted, they change between editions, and plenty of AHJs have their own version or want a specific edition. Some want the NFPA layout, some want their own cover sheet stapled on front, some accept a software-generated report as long as it carries the same information. Call or check the local requirement before you build anything.
What the Inspection and Testing Form asks for
The sections shift a bit by edition, but the shape is stable. Roughly:
Property and system info. Who owns it, who's the contact, what the building is, what panel, who monitors it. Boring, and it's where a surprising number of reports get bounced, because the address doesn't match what the AHJ has on file.
Who did the work and for whom. The service company, the person testing, the inspection type and date. Some forms ask for the inspection frequency too.
Control equipment and power. Panel checks, supervisory and trouble operation, primary power, and the battery. The battery line wants a real number, not a check mark. If you need a refresher on what the number should be, the secondary power article covers it.
Initiating devices, notification appliances, and signaling. Smoke and heat detectors, pull stations, waterflow and tamper switches, horns and strobes, speakers, the communicator or DACT, and the ancillary stuff like fan shutdown and door holders.
Results, deficiencies, and sign-off. What passed, what failed, what's impaired, and who signs.
Who signs
Usually two parties. The person who performed the inspection and testing signs for the service company, and the owner or their representative signs as received. Check your AHJ and your contract on whether a license or certification number has to go next to the signature. Some places want it, some don't care, and I've seen both in the same county.
What people leave blank
Here's a made up but very typical annual on a mid sized office building. One system, 214 devices.
| Device group | Installed | Tested | Passed | Failed or not accessible |
|---|---|---|---|---|
| Smoke detectors | 118 | 118 | 116 | 2 (one dirty, one removed) |
| Pull stations | 9 | 9 | 9 | 0 |
| Horn/strobes | 62 | 62 | 61 | 1 (strobe dead) |
| Duct detectors | 6 | 5 | 5 | 1 (roof access locked) |
| Waterflow/tamper | 19 | 19 | 19 | 0 |
Look at the duct detector row. That's the one that gets fudged. Six installed, five tested, one behind a locked roof hatch. The lazy version writes "6 tested" and moves on. The honest version writes the five, lists the sixth as not accessible, and puts it in the deficiency section so somebody has to go get the key.
Other things I see left blank all the time:
- Battery readings. Techs write "OK" where the form wants a voltage and a load figure.
- The monitoring company's name and the time the signal was received.
- The "not tested" reason. If you skipped something, say why.
- The date of the last inspection, which the next tech needs.
Blanks are fine if they're explained. Blanks with nothing next to them look like you skipped it.
What happens to deficiencies
Short version: they don't live on the form forever. The form records that something failed. What happens next is a separate trail.
You tell the owner, in writing, and the owner decides to fix it. If it's something that takes part of the system out of service, that's an impairment, and your local rules probably say who has to be notified (the fire department, the monitoring company, the insurance carrier, depending on where you are). The repair happens, the item gets retested, and the follow up gets documented against the original report so the next reader can see it closed.
What I do not do is quietly mark a failed device "pass" after fixing it on the same visit without noting the original failure. Some AHJs don't mind. Some read it as hiding history. Write it down both ways.
Keep the records
The owner is supposed to hold onto these, and you should keep your own copies too. How long varies, so check your AHJ and your contract. Mine live next to the as builts, and the first thing I open on any service call is last year's report.
Full disclosure, I built FireDeck because retyping the same device list into every report by hand ate more of my evenings than the testing did, so I'm biased. The form is the form either way.