NFPA 25 (2026) Expands What Counts as an Impairment

NFPA 25 Expands What Counts as an Impairment
NFPA 25 Expands What Counts as an Impairment

Two changes in the 2026 edition of NFPA 25 look like wording cleanups and aren't. One lowers the threshold for declaring a sprinkler system impaired. The other closes a gap that let emergency impairments go unreported.

Both land in the same place: what you have to be able to prove afterward.

From "frozen" to "contain ice"

The impairment classification itself isn't new — a frozen system was already an impairment. What changed is the test for getting there.

The second draft shows the edit in markup. Section 4.1.2.6.1 previously applied where piping was "found to be frozen"; the 2026 language applies where it is found to "contain ice," with the existing consequence intact: "the system shall be considered impaired." Section 4.1.2.6.2 moved the same way, from "frozen system" to "system components found to contain ice shall be completely thawed out or replaced and the system restored to service" (NFPA 25 Second Draft Report).

That's a lower and more objective bar. A technician no longer has to judge whether a system is frozen in some overall sense. Ice in the piping is the test, and ice is a thing you either find or don't.

In practice this pulls a familiar cold-climate situation across a line. Where a technician previously had room to judge that partial ice in a section of dry-system piping didn't amount to a frozen system, the 2026 language removes that room: ice found in the piping means the system is impaired, which means the full impairment procedure in Chapter 15 applies. Impairments carry obligations that deficiencies don't.

Not everyone reads the change the same way. IFSA describes systems with ice in the piping as "now classified as impaired, not merely deficient" (IFSA), which reads the classification itself as new. The draft markup doesn't support that — "shall be considered impaired" is text that was already there — but it's a fair signal of how the change is landing in the field.

Emergency impairments now explicitly require notification

The list of who gets notified did not change. Section 4.1.4 already required the property owner or designated representative to notify the authority having jurisdiction, the fire department where required, and the alarm-receiving facility when an impairment is identified or before testing or shutting down a system. The 2026 edits to that sentence are punctuation and a swap of "if required" for "where required."

The substantive addition is 4.1.4.1: "The notification of an impairment shall be required for both preplanned and emergency impairments."

That closes a real gap. A preplanned impairment has a work order behind it and someone at a desk who knows the drill. An emergency impairment is a technician finding ice in a dry system at 4pm on a Friday — the exact circumstance in which a three-party notification is most likely to become one phone call and a note to self. The standard now says both count.

Section 4.1.4.1.1 adds that "additional information required by 15.5.2 as applicable shall be included in the notification," so the content of an impairment notification is governed by Chapter 15, not by the shorter list in 4.1.4.2. That list — purpose, the system or component involved, the estimated time, and the expected duration — applies to notification of a system shutdown or test.

Either way, "we called it in" is not evidence. A dated record naming who was notified, when, and what they were told is.

Deficiencies run on your AHJ's clock

Section 4.1.5.2 applies where impairments, critical deficiencies or noncritical deficiencies are identified, and requires two things: "Deficiencies shall be corrected or repaired in a time frame approved by the AHJ," and until impairments are corrected, "an approved impairment program shall be implemented in accordance with Chapter 15." Corrections and repairs must be performed by qualified personnel (4.1.6.2).

This is worth stating carefully, because secondary coverage of the 2026 edition sometimes reports fixed correction windows — 30 days for critical deficiencies, 90 for noncritical. Those numbers do not appear in the mandatory text. Treat any specific day count as annex guidance or a local rule until you've confirmed it against your own jurisdiction.

The operational consequence is arguably worse than a fixed rule would be: your correction deadlines are jurisdiction-specific, so you can't run one clock across a multi-jurisdiction portfolio.

Other changes worth knowing

Section text below is from the NFPA 25 Second Draft Report except where noted.

Qualified personnel (4.1.1.3). The 2023 edition's detailed list of qualification methods gives way to a requirement that personnel be qualified for the specific tasks performed. Per IFSA, the prescriptive criteria move to the annex as recommended guidance, and local jurisdiction licensing requirements take precedence over the national standard.

Corrosion mitigation (4.1.5.3, 4.1.5.4). Two different triggers, worth keeping straight. Under 4.1.5.3, where the corrosion mitigation system "is not replaced in accordance with NFPA 13 to maintain the increased C value," the dry pipe or preaction system has to be hydraulically calculated and modified. Under 4.1.5.4, where that system is found deficient or impaired and 4.1.5.3 isn't met, it has to be repaired or replaced.

Escutcheons and cover plates (5.2.1.1.5). Replacement required where escutcheons are found to be missing, or show physical damage, detrimental corrosion, loading or paint — and under 5.2.1.1.5.1, where one has been adhered or attached to the ceiling or wall.

Dwelling unit sprinklers (5.3.1.1.1.7). Where sprinklers have been installed for 50 years in dwelling units, they must be replaced with fast-response models, or representative samples tested to confirm a Response Time Index not exceeding 65 (m·s)^½. The clock runs on time in service, not date of manufacture — so what you need on file is an installation date, not a sprinkler's age.

FDC piping (13.8.5.2). Fire department connection piping of 10 feet or less that can be inspected visually, internally and externally, does not require the hydrostatic test (Chesapeake Sprinkler) — one of the few changes that removes work rather than adding it.

What this asks of your records

The through-line is that this edition is less about what you look at and more about what you can reconstruct six months later.

An impairment now needs a defensible trail: what triggered it, when it started, who was notified, what they were told, and when it cleared — for emergency impairments as much as planned ones. A deficiency needs a correction deadline sourced from a specific AHJ and tracked to closure. A dwelling-unit sprinkler needs a documented installation date or an RTI result. Qualification needs evidence tied to local licensing rather than a national checklist.

None of that is difficult on its own. All of it is difficult to assemble after the fact from a PDF and someone's memory, which is how a large share of ITM records still work.

Two moves worth making before this edition reaches your jurisdiction. Make impairment notification a structured field set rather than free text — recipients, required details, timestamps. And attach the governing AHJ and its correction timeframe to the site rather than the customer, since one customer's portfolio will span jurisdictions with different answers.

On sourcing. The section text above comes from the NFPA 25 second draft report and, where noted, trade summaries — not the published standard. Confirm specifics against the printed 2026 edition. More importantly, confirm what your jurisdiction has adopted — a new edition binds you when it's adopted into law, not when NFPA publishes it.

If your impairment records are free text and your correction deadlines live in email, this is the edition that breaks that. Joyfill lets you build inspection forms with the fields each jurisdiction actually requires, complete them in the field, and keep every record in one place you control.

fire protection

NFPA

NFPA 25

author's photo

Written by John

Get started - It's free forever!

Join thousands of field teams already saving hours on every job.

Free forever

No credit card required

Cancel anytime

Support included

Get started - It's free forever!

Join thousands of field teams already saving hours on every job.

Free forever

No credit card required

Cancel anytime

Support included

Get started - It's free forever!

Join thousands of field teams already saving hours on every job.

Free forever

No credit card required

Cancel anytime

Support included