NFPA 72
National Fire Alarm and Signaling Code
NFPA 72 is a standard issued by National Fire Protection Association covering fire alarm systems, initiating devices, notification appliances, and emergency communications.
Read it at National Fire Protection Association
Affixure supplies artifacts and hosts records. We do not interpret this standard on your behalf and we do not certify compliance with it. The link above goes to the issuing authority so you can read the text yourself.
Who enforces this, and how it reaches you
Adopted by reference into building and fire codes. Enforcement is usually triggered by an event rather than a schedule: a false alarm history or an incident brings scrutiny that routine inspection does not.
How this differs from the neighbouring standards
Covers the alarm system as a system. Individual device testing frequencies vary by device type, which is what makes the inspection record longer than people expect.
What you have to be able to show
Fire alarm work under NFPA 72 produces two distinct kinds of document and they are frequently confused. The first is the record of completion, generated when a system is installed or materially modified, describing what was actually built. The second is the ongoing inspection, testing and maintenance record, produced on recurring frequencies for the life of the system. What has to be provable is both: what the system is, and what has been done to it since. Devices within a single system are also not uniform - detectors, notification appliances, and the panel itself carry different testing obligations - so the evidence is device level, not panel level.
What the record adds that the tag cannot
A fire alarm system is the clearest case on this site where the equipment substantially outlives the people who know about it. Panels stay in service for decades. The technician who commissioned it, the company that installed it, and the record of completion describing what was built are routinely all gone before the system is. Binding a record to the panel means the next person to open it can see the testing history without locating a company that may not exist. Serialisation also handles the device level problem: a system with hundreds of initiating devices cannot be evidenced by one date on one tag, and a record that resolves per device is the only way a missed device becomes visible rather than being averaged into a system that reads as tested.
The mechanics are the same for every standard, and they are set out on how inspection records work.
Why this is a different purchase from ordering the same item printed
The service tag on an alarm panel is a low value item that nobody thinks about at the point of purchase, and that is precisely why it is worth reconsidering. It is the only thing physically attached to a piece of equipment that will be in the building longer than most of its occupants. Ordering it as a serialised artifact rather than as printed card costs the same order and produces something the building still benefits from in twenty years. A printer cannot offer that because a printer's product ends at the loading dock.
Choosing a substrate for this environment
Alarm panel tags have the easiest physical environment on this site and the longest service expectation, which inverts the usual trade-off. The panel is indoors, climate controlled and rarely touched, so almost any substrate survives. What matters instead is that the tag is still legible in fifteen years, and the thing that fails over that span is not the material but the ink under fluorescent or LED lighting. Choose for print permanence rather than for toughness, and mount inside the panel door rather than on the outer face where cleaning and casual contact reach it.
Substrate and rating are stated on every product page. If you are not sure, compare the options or order the hundred unit minimum and see how it survives before committing a fleet to it.
Equipment this applies to
Questions people ask about NFPA 72
Does this cover the record of completion as well as testing?
The record holds the ongoing inspection and testing history. The record of completion is a document produced at installation by the installing contractor and is normally retained with the system. What serialisation adds is that the panel itself points at the ongoing history, so the two are findable from the equipment rather than from a filing system. We do not generate or certify a record of completion.
Can individual devices be tracked, or only the panel?
Individual devices. A system with hundreds of initiating devices cannot be honestly evidenced by a single date on the panel, because that date says nothing about which devices were reached. Per device records mean an untested device shows as untested instead of disappearing into a system level pass.
What if the installing contractor is no longer in business?
The record does not depend on them. It is bound to the equipment and readable from the QR on it by the building owner or the authority having jurisdiction without an account. This is the failure mode that motivates the design: alarm systems routinely outlive the companies that installed them, and a history held only in a contractor CRM is a history that ends when the contractor does.