NFPA 72 document review connects the fire alarm design basis to device layouts, risers, product data, and stated system behavior. Groundbook can compare supplied PDFs and an uploaded reference to flag potential inconsistencies. The qualified designer confirms required coverage, performance, and code applicability.
Carry alarm interfaces into the building
Where the alarm releases a clean agent system, compare the releasing documents with the NFPA 2001 clean agent guide; where it starts smoke control, use the NFPA 92 smoke control guide. Follow stated HVAC signals and responses with the NFPA 90A fire and smoke interface guide. Where an opening depends on an alarm interface, connect its hardware and assembly documents using the NFPA 80 opening review.
The NFPA 101 life safety guide follows the wider occupancy, route, and protective-feature basis. Keep that basis explicit rather than inferring it from the presence of a fire alarm system.
What is NFPA 72?
NFPA 72 is the National Fire Alarm and Signaling Code. It addresses fire alarm and signaling systems, including emergency communications. NFPA’s official page identifies the 2025 edition as current when checked on September 30, 2026. See NFPA’s official NFPA 72 page for its scope and access options.
Confirm the edition and amendments that apply to the project. Record the building’s stated design basis, new and existing system boundaries, and the role of each reviewing authority. The latest published edition alone does not establish the permit requirements or which systems the building must have.
Bring the sequence of operation into the drawing review
Collect the fire alarm plans, riser, device legend and schedule, product data, sequence or cause-and-effect matrix, relevant specifications, and referenced calculation reports. Add the architectural room and ceiling plans and the sprinkler, mechanical, and electrical sheets that describe connected equipment.
Identify the governing revisions before comparing sources. Follow one initiating event from the device or system shown on the plan into the riser and the stated response. When the response depends on equipment in another package, check that the receiving discipline identifies the same interface and responsibility.
Trace six document relationships
| Review question | Documents to compare | What to resolve |
|---|---|---|
| Devices and spaces | Device layouts, legend, room plans, and ceiling information | Resolve missing identities, changed spaces, or geometry that the alarm designer needs to assess. |
| Plans and risers | Device tags, circuit references, riser, and schedules | Investigate equipment or connections that appear in only one representation. |
| System behavior | Sequence of operation, input/output matrix, and equipment descriptions | Resolve contradictory responses and unclear responsibility for connected equipment. |
| Sprinkler interfaces | Sprinkler riser, alarm interface list, and fire alarm documents | Trace named waterflow and supervisory interfaces without guessing a required response. |
| Power and calculation inputs | Panel and power-supply data, circuit schedules, and calculation reports | Check whether the documented equipment and revisions match the report inputs; refer adequacy to the designer. |
| Notification and communications | Device data, layouts, room information, and design criteria | Flag inconsistent selections and missing design evidence; drawings alone do not prove achieved performance. |
Use the fire alarm specification review to reconcile contract requirements. Where the interfaces include sprinkler or pump equipment, continue with the NFPA 13 and NFPA 20 guides.
Example: an interface has two descriptions
Hypothetical example. The sprinkler riser labels a valve supervisory connection, but the alarm input schedule uses a different equipment identifier and the sequence does not explain the relationship. A useful finding cites the riser, input schedule, and sequence and asks the designers to confirm whether they describe the same connection.
Do not silently rename the input or choose a response. The alarm and sprinkler designers must establish the intended interface and update each affected reference. Close the question only when the revised documents explain the connection consistently and the responsible reviewers have confirmed the design.
Ask Groundbook a specific review question
Upload the current drawing package and specifications, plus the applicable NFPA 72 reference from a copy you are licensed to use, where the license permits uploading it. State the edition, amendments, scope, and any excluded existing systems.
Compare the fire alarm device plans, riser, schedules, and sequence with the sprinkler and mechanical interfaces. Flag inconsistent identifiers, missing connections, and contradictory descriptions. Cite the relevant sheets and supplied reference, and distinguish missing information from a potential requirement mismatch.
Groundbook returns potential findings for your team to verify. A document review does not measure sound levels, prove intelligibility or coverage, validate battery calculations, or replace system testing. Use the cross-discipline coordination workflow to assign and resolve the document questions with the relevant designers.