How to Test and Inspect a Fire Alarm System (NFPA 72)

If you’re working toward your NICET certification or you’re just starting out in the fire alarm industry, test and inspection is one of the most important topics you’ll ever learn. A lot of technicians think test and inspection is just checking boxes on a form. It isn’t. This is how you actually tell whether a system is going to pass or fail, where inspectors catch mistakes, and where NICET pulls exam questions straight from real-world field experience.

This guide walks you through how to properly test and inspect a fire alarm system, what NFPA 72 is actually looking for, what inspectors require in the field, and how this shows up on your NICET Level I exam. It’s field-accurate and code-driven.

Inspection vs. Testing: They Are Not the Same Thing

The very first thing to understand is that inspection and testing are not interchangeable terms. NFPA 72 (Chapter 14, Inspection, Testing, and Maintenance) separates them deliberately.

• Inspection is visual. It answers the question: Is this device installed correctly?
• Testing is functional. It answers: Does this device operate the way it is supposed to?

During an inspection you are not activating anything. You are taking a visual look to confirm device placement is correct, that there’s no dust or dirt inside the smoke detectors, that nothing looks out of order — a broken horn/strobe, batteries that are seven years past date, anything physically wrong with the system.

During a test, you’re actually activating the devices to confirm functionality. For example, if you have a smoke detector in an elevator lobby, you want to confirm the relay activates so the elevator recalls the way it’s designed to.

Common exam trap: “Does a visual confirmation prove the operation of a strobe?” The answer is no. Only testing can prove the operation of any fire alarm device.

NFPA 72 draws this line on purpose — not to confuse you, but to make sure you understand the difference.

What Inspectors Look for in the Field

During the visual inspection portion, an inspector — and you — should be checking:

• Device placement and spacing. Are detectors, pull stations, and horn/strobes at the correct mounting height, especially in corridors? Is spacing correct per NFPA 72 Chapter 17 (initiating devices) and Chapter 18 (notification appliances)?
• Clean smoke detectors. Not painted over, not clogged, no dust or dirt on the sensing chamber.
• Remote LEDs for concealed devices. Duct detectors above the ceiling grid or in plenum/ductwork need a remote LED indicator so you know there’s a device up there providing protection that can be tested.
• Correct labeling. A remote annunciator should be labeled “Fire Alarm Remote Annunciator.” A control panel should read “Fire Alarm Control Panel,” and a booster panel “Fire Alarm Booster Panel.” If the annunciator sits at the fire department’s first point of entry, it should also identify where the fuse/disconnect is located.
• Accurate descriptors. If you test a device on the third floor and it reports “second floor,” or the descriptor is simply wrong, mark it down so the programmer can correct it. NFPA 72 wants the exact message, description, and location for every device.

Labeling isn’t just about passing — clean wire labels are what let you get in and out of a building fast when you’re troubleshooting.

Testing for Functionality

Testing verifies what actually happens when a device activates. When you pull a station or trigger a detector, you need to confirm the correct outputs fire:

1. Pull station / general alarm: correct message on the panel, trouble/alarm signal sounds, horns and strobes activate, door holders release and doors close.
2. Area smoke / duct detectors: fans and air handlers shut down.
3. Elevator lobby detectors: in addition to shutting down fans, the elevators recall (drop) and any associated functions execute.
4. Special systems: verify smoke-control/purge functions, stair pressurization, and damper positions (open, closed, or partial) where applicable.

You also have to prove the system stays reliable in an emergency. That means confirming the batteries can sustain the system with no AC present — sealed batteries should be within 5 years of manufacture per NFPA 72 Chapter 14 and 10.6.

Every off-premises signal has to be verified too — alarm, supervisory, and trouble, plus telephone/communicator lines, data loss, and any connected signal — and you must confirm each one actually reaches the central station.

If you have CO detectors, make sure the central station will dispatch the fire department on a CO event. It may only be a supervisory signal and sound bases rather than horns and strobes — but the response still has to happen.

Common Reasons a System Fails Inspection

• A pull station with a broken box or a missing glass rod. A missing glass rod doesn’t fail the whole system, but it’s a documented problem you have to return and correct.
• Horn/strobes mounted incorrectly, wrong candela setting, or a broken lens or cover.
• Dust accumulated inside the fire alarm control panel.
• Batteries out of date (past 5 years).
• Maintenance fault on an addressable device. On a networked system, a maintenance fault typically means the detector is around 80% dirty and can no longer be compensated — that device must be replaced, not just cleaned, and it will hold a trouble until it is. Until replaced, it may not go into alarm.

Pro move: pull a sensitivity/contamination report. Run it for detectors below 20% and above 80% so you know which smokes need cleaning versus which need replacement.

Documentation and the Inspection Report

The report is part of the job — done on site, not at home. Document:

• Everything that did not work and everything that did.
• Devices out of order, abandoned wires, and abandoned devices.
• The total device count so you can check off every device (smoke detector first floor, second floor, third floor, and so on).

If your company installed the system, you should be able to pull the device list from the loop card or loop controller, or have the office/programmer send it. Some companies use building reports with serial numbers you scan to prove every device was tested. This is what NFPA 72 Chapter 7 and 14 documentation requirements — and the record of completion / inspection and testing forms — are built around.

How This Shows Up on the NICET Level I Exam

NICET isn’t testing whether you can memorize the entire code book. It’s testing whether you truly understand the difference between testing and inspection. Once you separate the two in your mind, you can read the question and see which direction they’re pointing you.

Expect focus on:

• Signal types: alarm, supervisory, trouble, monitor.
• Who is qualified to test and inspect the system.
• The visual-vs-functional distinction (inspection confirms it looks right; testing confirms it works).

How Fire Code Mastery Fits Into This

Understanding the test-versus-inspection distinction is exactly the kind of concept that separates techs who pass from techs who guess — and it’s precisely what Fire Code Mastery is built to drill.

• 3,450+ exam questions covering inspection, testing, maintenance, signal types, and device functionality, written to mirror how NICET actually asks.
• 10+ calculators for battery/standby load, notification appliance spacing, candela, and voltage drop — so the numbers behind your field decisions become second nature.
• Flash cards to lock in the NFPA 72 chapter and section references (Chapters 7, 14, 17, and 18) that show up on the exam.
• Case studies built from real-world scenarios — the same kind inspectors and NICET pull from.
• Mock tests that simulate exam pressure so you walk in ready.

Master the concept, then prove it with the questions. Study smart, test with confidence, and pass the first time.