
If the fire alarm submittal, testing, or closeout package slips, turnover can slip too.
I’d sum up NFPA 72 this way: the building code tells me when I need a fire alarm system, and NFPA 72 tells me how that system must be installed, tested, documented, and approved. For a construction manager, the main risk points are clear: early coordination, approved shop drawings, device layout, battery and voltage-drop calculations, staged testing, and closeout records.
Here’s the short version:
What this means for me is simple: NFPA 72 is not just a fire alarm contractor issue. It affects planning, trade coordination, field checks, commissioning, and final sign-off from the first phase of the job to the last day on site.
NFPA 72 Compliance Stages for Construction Managers


NFPA 72 lays out how fire alarm and signaling systems must be installed, tested, and maintained. The IBC and IFC decide when a system is required. NFPA 72 spells out how that system has to work. [7] For construction managers, that touches almost every phase of the job: design coordination, procurement, installation, testing, and closeout.
Here’s the simple split:
Project specs can also go past the code minimum. They may call for a certain brand, added system performance, or extra integration with other building systems. [7][2] That’s where teams can get tripped up. Code sets the floor, but the specs may set a higher bar.
The NFPA 72 edition that applies depends on the adopted code cycle and any local amendments. [7] That detail matters more than people think. A team might design to one edition, only to learn the AHJ is working from another. The 2025 edition adds mandatory cybersecurity requirements in Chapter 11. [4] So before final design moves ahead, confirm the adopted edition and local amendments with the AHJ.
Once the code path is clear, coordination becomes the next big pressure point. In plain terms: who designs it, who installs it, and who signs off on it?
The design professional usually owns the system design and the construction documents. The construction manager keeps the moving parts lined up, especially the fire alarm team, commissioning team, and other trades, so submittals, installation, and testing stay on track. The commissioning team checks that the fire alarm system works the way it should with HVAC, sprinklers, and elevators. [1]
The AHJ has final approval authority over both documentation and testing, so early coordination can save a lot of pain later. [1][2] Inspection delays often come from familiar problems: incomplete submittals, unresolved zone naming, annunciation location issues, and acceptance-test deficiencies. [1][9]
That’s why AHJ alignment belongs in preconstruction, not at the tail end of closeout. Waiting until the last stretch is a good way to find out a small paperwork issue has turned into a schedule problem.
Once the code path is settled, the next place jobs go sideways is preconstruction coordination. A lot of fire alarm rework starts here, while layout and interface choices are still on paper and cheap to adjust. After the wire is pulled, every change hurts more.
One early call matters more than it may seem: whether the system will be conventional or addressable. That choice affects panel size, wiring, and integration. It needs to be set before procurement starts.
Detector spacing is another spot where early coordination can save a lot of pain. NFPA 72 allows prescriptive smoke detector spacing only on ceilings 40 feet or lower. Above that, you need a performance-based analysis. It also says girders within 4 inches of a ceiling must be treated as beams for spacing purposes [4]. That changes device locations. And once device locations move, ceiling layout moves too, which can ripple into every trade working overhead.
After device locations are set, trade coordination becomes the weak point. Smoke detectors must be at least 36 inches from HVAC supply diffusers or return air openings so airflow does not interfere with detection [11]. Elevator recall, HVAC shutdown, smoke damper control, and door release functions also need to be laid out in a sequence-of-operations matrix before installation begins [8][10].
Notification appliance placement should not be treated like something the field can sort out later. It is a design task. Teams need to flag acoustically distinguishable spaces early so finishes and room acoustics do not weaken audibility [3].
Shop drawings have to clear the AHJ review path before rough-in begins [8]. So the submittal package is not just paperwork. It is a schedule gate. If the package is missing key items or has errors, review slows down and rough-in cannot move.
Here are the main submittal items construction managers should track and why each one affects the schedule:
| Submittal Item | Why It Matters |
|---|---|
| Shop Drawings / Floor Plan Layout | Coordinates device placement with HVAC, MEP, and ceiling trades |
| Riser Diagram | Verifies wiring methods and circuit integrity from panel to device |
| Battery & Voltage Drop Calculations | Confirms wire gauge and power supply adequacy; drives procurement |
| Sequence of Operations (I/O Matrix) | Establishes control logic for programming and acceptance testing |
| Equipment Data Sheets | Verifies listings and supports electrical calculations |
| System Narrative | Establishes the compliance basis for initial permit review |
Battery sizing also affects the schedule. NFPA 72 requires the system to support 24 hours of standby followed by 5 minutes of full alarm load, or 15 minutes for emergency voice or mass notification systems [10][6]. Those figures set battery size and can also decide whether the design needs a remote power supply.
Voltage-drop calculations should be finished before rough-in. On long runs, or when wire is undersized, end-of-line devices may not get enough voltage to work as intended. Catching that at the front end helps set wire gauge and shows whether remote power supplies need to be added to the design [8][6].
Once submittals clear review, the field team needs to install to the approved layout, calculations, and sequence of operations. From that point on, the work is less about design coordination and more about field quality control and testing.
Once the design gets approved, the work moves off the page and into the field. That’s where a lot of projects stumble. Most failed inspections don’t happen because the design was bad. They happen because of small install mistakes: the wrong wire gauge, weak terminations, or mixed circuit types pulled through the same conduit.
Before inspection, compare the installed system to the approved floor plans and riser diagram. Check each device against the approved type. Make sure it’s listed, mounted at the right height, and not blocked by ceilings, walls, or other building features. Panel locations also need proper working clearance and can’t be placed in prohibited rooms. Annunciators and control panel displays should be mounted between 15 and 72 inches above the finished floor [13].
One field check usually isn’t enough. After the ceiling grid and wallboard are in place, do another pass. That second review often catches conflicts that didn’t show up during rough-in.
Notification appliances need to hit the required sound and strobe levels. Voice systems bring more risk because speakers, amplifiers, zoning, and intelligibility all need to be locked in before finishes close.
If a device, pathway, or appliance issue slips through here, it usually shows up later as an acceptance-test deficiency.
Once installation clears field checks, the next pressure point is staged inspection and witness testing. Acceptance testing is not one item on a checklist. It’s a sequence. It moves through four milestones that should be built into the master schedule: plan review, rough-in inspection, above-ceiling inspection, and acceptance testing [12]. Leave float between those gates.
Before the AHJ witness test, the fire alarm contractor should run a full device-by-device pretest. Every detector, pull station, and notification appliance should be checked. Interface testing also needs to be confirmed for sprinkler water flow signals, HVAC shutdown, and elevator recall [12][1]. If anything fails during AHJ witness testing, the correction has to be documented and then re-tested.
Pretesting should also cover power. Verify secondary power, battery condition, and power-supply operation during both pretest and witness testing. For new installations, all rechargeable secondary power batteries must carry UL 1989 or UL 2054 listings [13].
As testing wraps up, the last big risk is weak turnover documentation. As-built drawings should be updated as the job moves along, not pieced together from memory at the end.
The table below shows the core closeout documents construction managers need to track before the job can close:
| Closeout Document | Producer | Delivery Timing |
|---|---|---|
| As-Built (Record) Drawings | Installing Contractor | At turnover |
| Record of Completion | Installing Contractor | Before turnover |
| Sequence of Operations (Final) | System Programmer/Installer | At turnover |
| Site-Specific Software and Access Credentials | Installing Contractor | At turnover |
| Acceptance Test Reports | Testing Personnel/Installer | Before turnover |
| O&M Manuals and Data Sheets | Equipment Supplier/Contractor | Before turnover |
| Battery and Voltage Drop Calculations | System Designer/Installer | Before turnover |
The owner also needs the system configuration files, passwords, and access instructions for future service. NFPA 72 requires record drawings to be stored in the on-site documentation cabinet as well. Before final turnover, confirm that the cabinet is installed and fully stocked.
NFPA 72 touches every stage of a project. A missed detail during preconstruction, submittals, installation, testing, or closeout can slow down AHJ approval and delay occupancy. That’s why managing NFPA 72 has to happen in the field. It can’t live only in a design review.
The failure points tend to show up in the same places: firestopping, sequence-of-operations mistakes, audibility misses, and incomplete closeout packages. Audibility needs to be checked before final acceptance, not discovered at the worst possible moment. The same goes for firestopping, circuit pathways, and battery calculations. Once finishes are in place, late changes get expensive fast. At that point, the issue isn’t just code. It’s process. And when process breaks down, people usually sit at the center of it.
Complex fire alarm work falls apart when the team handling it isn’t qualified to design or manage it. On mission-critical and commercial projects, the construction managers who deliver code-compliant fire alarm systems plan staffing around that risk. They bring in MEP leaders who understand pathway survivability, superintendents who control inspection gates, and commissioning professionals who run full functional pretests before the AHJ shows up.
For mission-critical projects, hiring people who know fire alarm code, coordination, and testing is part of compliance risk management. On complex jobs, compliance starts with the right team, not just the right code book.
NFPA 72, the National Fire Alarm and Signaling Code, sets the rules for how fire alarm and emergency communication systems should be applied, perform, be installed, documented, inspected, tested, and maintained.
It also lays out requirements for system operation and verification. That includes device placement, notification appliances, backup power, monitoring, cybersecurity, documentation, and commissioning for new systems or systems that have been upgraded in a major way.
Fire alarm coordination should start in the pre-design phase, while the consulting or engineering scope is being developed.
Early coordination with the AHJ helps line up code needs while project details, system types, and equipment assumptions are still flexible. That can cut down on redesigns, permitting delays, and scope disputes later.
NFPA 72 closeout documents show that the system was installed correctly and is working the way it was designed to work.
Key deliverables include:
Give these documents to the owner, and place a copy in the project documentation cabinet.



