NFPA 13, 14, 25, 72 overview.
2
hours
0.2
CEUs
Codes and Standards
1.7.3
NFPA 13, 14, 25, 72 overview.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamUnderstand NFPA fire protection standards and their I-Code references
The National Fire Protection Association is a standards-development organization, not a code-writing body in the same sense as the International Code Council. It publishes and maintains hundreds of consensus standards covering fire and life-safety topics in a level of technical and installation detail that a general building or fire code was never meant to carry on its own. Rather than duplicating that detail, the I-Codes incorporate the relevant NFPA standards by reference: the adopting code names the standard, and the standard's own requirements become part of what is enforced. This platform's course on referenced standards works through that legal mechanism in depth — the short version for fire protection is that once an NFPA standard is invoked, an inspector or plan reviewer is not weighing a "best practice" against the code. The standard's own text has already become the code, for the piece of it the reference actually covers.
That reference is never open-ended. NFPA standards are revised on their own periodic cycle, and the code that references one names a specific edition, fixed at the point that code cycle was adopted. A newer edition published afterward is not automatically enforceable just because it exists; it becomes binding only once the jurisdiction's adopted code, or the standard reference within it, is updated to point to it. This is the same discipline covered from the jurisdiction's side in this platform's course on understanding your adopted jurisdiction: confirming exactly what has been adopted, and by which edition, before assuming any requirement applies. For NFPA standards specifically, the correct question is never simply what a standard requires in general, but what the edition of that standard actually referenced by this jurisdiction's adopted code requires.
A code official does not need to memorize every NFPA standard in existence, but recognizing the handful that recur constantly is close to a professional requirement. NFPA 13 governs the design and installation of automatic sprinkler systems. NFPA 72 governs fire alarm and signaling systems: detection, notification, and monitoring. NFPA 25 governs the inspection, testing, and maintenance of water-based fire protection systems once they are in service, functioning as the standard that keeps NFPA 13 systems trustworthy for the life of the building. NFPA 101, the Life Safety Code, provides an alternative or companion life-safety framework used alongside the I-Codes in some jurisdictions and occupancy types. NFPA 30 addresses the storage and handling of flammable and combustible liquids. NFPA 70, the National Electrical Code, is referenced for electrical installation safety generally. NFPA 80 governs fire doors and other opening protectives. NFPA 92 governs smoke control systems. None of these substitutes for another, and naming the correct one for a given system is the first move in any review that touches fire protection.
A plan reviewer opens a submittal for a mixed-use building that shows an automatic sprinkler system, a fire alarm and detection system, and a first-floor storage room for flammable solvents used in an attached shop. Rather than treating the fire-protection portion of the review as one undifferentiated task, the reviewer separates it into three distinct questions: is the sprinkler design consistent with the standard that governs sprinkler design, is the alarm and detection design consistent with the standard that governs alarm and detection, and is the flammable-liquids storage consistent with the standard that governs that specific hazard. Each question points to a different NFPA standard, and each standard has its own referenced edition to confirm against the jurisdiction's adopted code before the reviewer looks at a single drawing detail.
A common error is treating "NFPA" as a single undifferentiated body of fire-safety guidance rather than a family of separate standards, each with its own scope and its own role. A related mistake is confirming that a design cites an NFPA standard without confirming it cites the correct one for the system in question, or the edition the jurisdiction has actually adopted. A third is assuming that the newest edition available from NFPA is automatically the enforceable one. The correction is the same discipline in every case: identify the specific system or hazard, identify the specific standard that governs it, and confirm the specific edition the adopted code references before evaluating compliance.
Code Reference: NFPA 13, 14, 25, 72 - These standards are incorporated into the I-Codes by reference and become part of the enforceable code to the extent each is invoked, for the specific systems and hazards they each govern.
Apply sprinkler system design requirements from NFPA 13
Sprinkler systems, like fire alarm systems, are rarely designed by the architect or general engineer of record. NFPA 13 design is specialty work, typically performed by a fire protection engineer or a qualified sprinkler contractor who works out hazard classification, water demand, and pipe sizing for the specific building and its contents. Because that design work often is not finished when the rest of the construction documents are submitted, it is common for sprinkler and alarm drawings to be filed as deferred or delegated submittals: packages the code official agrees to review later, before that portion of the work begins, rather than holding up the whole permit. The arrangement is a normal, code-recognized pathway, not a way to avoid review. It simply changes when the review happens.
When that submittal arrives, the plan reviewer's job is not to reproduce the fire protection engineer's calculations. It is to confirm that the design was actually built on the standard the adopted code requires: the correct referenced edition of NFPA 13, applied to the correct hazard classification for each area of the building, with the scope of what NFPA 13 governs, and does not govern, clearly understood. Reading a referenced standard this way is a specific skill: locating the edition in force, confirming what the code's reference actually pulls in, and treating the result as binding text rather than a design suggestion. A reviewer who verifies that the documented basis of design matches the referenced standard has done the job. One who tries to re-derive the engineering from scratch is duplicating work that the referenced standard, backed by the specialty designer's stamp, already exists to handle.
Once a system like this clears review and goes into the building, keeping it trustworthy for the rest of the structure's life becomes a separate, ongoing question: the subject of this platform's course on IFC fire protection systems inspection and testing, which picks up almost exactly where this module leaves off.
A plans examiner reviewing a new assembly building finds the architectural and structural drawings complete, while the sprinkler and fire alarm packages are noted as deferred submittals to follow from the specialty contractor. The general contractor asks whether the permit can be issued now, with sprinkler and alarm approval to follow later. The examiner confirms that the deferral is properly documented, that the deferred packages will still require full review and approval, checked against the referenced editions of NFPA 13 and NFPA 72, before that work is installed, and that the building permit itself does not authorize installing fire protection systems ahead of that approval.
A frequent mistake is treating a deferred submittal as a lower-scrutiny formality rather than a full review that simply happens on a different schedule. Another is a reviewer trying to independently verify hydraulic calculations or head placement in detail, well past what confirming standard-compliance actually requires, rather than confirming the documented design basis is sound and correctly referenced. A third is approving a system because it looks complete without confirming which edition of NFPA 13 the design was actually built on. The correction: treat deferred submittals as full reviews on a later timeline, confirm the referenced edition and hazard-classification basis, and verify compliance with the standard rather than re-performing the specialty design.
Code Reference: NFPA 13, 14, 25, 72 - Sprinkler and fire alarm design is commonly submitted as a deferred or delegated submittal, reviewed against the specific referenced edition before that portion of the work is installed.
Understand standpipe and fire alarm system standards
Standpipes and fire alarm systems answer different questions than the sprinkler system discussed in the previous module, even though all three are frequently reviewed together. A standpipe is not aimed at occupants; it exists so fire crews have a ready water supply inside the building instead of dragging hose up a stairwell from a truck outside, and its governing design standard is NFPA 14. A fire alarm and signaling system, governed by NFPA 72, is doing something different again: sensing a fire condition, notifying occupants, and getting a signal to a point where someone will respond, three separate jobs that each have to keep working independently. Neither system substitutes for the other, and neither substitutes for the sprinkler coverage discussed previously. A code official evaluating a building's fire protection has to confirm each system against its own governing standard rather than treating fire protection as a single line item.
Design and installation are only half of what NFPA 14 and NFPA 72 govern. Both standards, like NFPA 25 for water-based systems generally, also carry the ongoing inspection, testing, and maintenance obligations that apply for as long as the system remains in service. A standpipe that was correctly installed years ago and a fire alarm system that passed its acceptance test at construction have both told a code official something about the past. Whether either one still performs today is a separate question, answered only by confirming that the required ongoing testing and maintenance, under the applicable standard, is actually happening and documented.
Occasionally a design detail or field condition seems to sit between what the adopted code says directly and what a referenced NFPA standard says about the same point. The general operating principle a code official applies is straightforward: the adopted code's own text controls where the two are in direct conflict, since a referenced standard exists to supply technical detail within the code's framework rather than to override it, and where the code is silent on a point the standard addresses, the more restrictive reading is the safer and more defensible one to apply.
During a fire inspection of an existing high-rise, an inspector reviews recent standpipe and fire alarm maintenance records alongside the building's permit history. The building's most recent alarm system upgrade was completed using an edition of NFPA 72 the contractor described as current, but the inspector confirms that the jurisdiction's adopted code actually references an earlier edition, and that the installed notification arrangement was designed to assumptions from the newer, uninstalled edition rather than the one legally in force. Because the inspector treats the referenced edition as binding rather than a formality, the mismatch surfaces during a routine record review instead of going unnoticed until an actual emergency exposed it.
The most consequential mistake in this area is assuming a standpipe or alarm system that was compliant at installation remains compliant indefinitely without ongoing, documented testing and maintenance under the applicable standard. A closely related mistake is a contractor or building owner treating an NFPA standard's requirements as optional best practice once the system is up and running, rather than as adopted, binding text. A third is confirming that some NFPA standard was used without confirming it was the specific edition the adopted code actually references. The correction: verify current, documented inspection, testing, and maintenance against the correct standard, and confirm the referenced edition explicitly rather than accepting a general claim of compliance at face value.
Code Reference: NFPA 13, 14, 25, 72 - Standpipe and fire alarm systems each carry both design and installation requirements and ongoing inspection, testing, and maintenance obligations under their respective referenced standards.
NFPA standards function as the enforceable technical backbone behind a large share of fire and life-safety review, not as background reading. The I-Codes incorporate them by reference, which means an official's real job runs in two directions: confirming, during plan review, that a design was built on the correct standard and its correctly adopted edition, and confirming, during inspection, that the installed and maintained system still meets that same standard over time. NFPA 13 and NFPA 72 govern how sprinkler and alarm systems are designed; NFPA 25, together with the maintenance provisions carried within NFPA 14 and NFPA 72, governs how those systems and standpipes are kept trustworthy afterward; and standards such as NFPA 101, NFPA 30, NFPA 70, NFPA 80, and NFPA 92 fill specific roles elsewhere in the same framework. None of it is optional once referenced and adopted, and none of it substitutes for identifying the correct standard, for the correct system, at its correct edition, every time.