Every finding on a sprinkler inspection is not created equal. A missing spare-head wrench and a seized-shut control valve will both show up on the report, but one is a housekeeping note and the other means the building's fire protection does not work. NFPA 25 formalizes that difference into three tiers — and for the worst tier, it prescribes an entire procedure with its own chapter.
Getting the classification right matters for two reasons: it drives how fast the correction has to happen, and misclassifying an impairment as a mere deficiency is the kind of finding that ends up in litigation after a loss.
The three tiers
Noncritical deficiency. Something needs correction, but it doesn't materially affect how the system performs in a fire. Documentation gaps, a missing sign, the spare-head cabinet short a wrench. It goes on the report and gets fixed in the normal course of business — commonly by the next scheduled visit.
Critical deficiency. If left uncorrected, it has a material effect on the system's ability to do its job — but the system still partially functions. A painted-over sprinkler head, an obstructed spray pattern, a dry system with chronic air-pressure loss. This is prompt-correction territory: quote it, schedule it, close it.
Impairment. The system, or a portion of it, is out of order — it will not function in a fire event. A closed control valve, a failed fire pump, a drained system, a break in the main. The moment a finding crosses this line, you're not in track-and-quote mode anymore; you're in Chapter 15.
One nuance worth knowing: NFPA 25 itself deliberately does not attach day-count deadlines to deficiency correction — timing is left to the owner and the AHJ. The 30-day and 90-day windows you'll see in service software (including ours) are industry-practice defaults, not code citations. What the standard is explicit about is the impairment procedure.
Chapter 15: what actually has to happen
Impairments come in two flavors — preplanned (you're shutting the system down to work on it) and emergency (you found it broken). The procedure is the same; emergencies just run it as fast as feasible.
1. Someone owns it. The standard requires an impairment coordinator — by default, the building owner. In practice, the sprinkler contractor ends up driving the checklist.
2. Tag it out. An impairment tag goes on the system control valve and the fire department connection, so an arriving crew knows the system is down before they hook in.
3. Notify everyone with a stake:
- The fire department / AHJ
- The building owner or their representative
- The insurance carrier
- The alarm monitoring company
- Supervisors in the affected areas (who inform occupants)
4. Mitigate for long outages. Where the system will be out more than 10 hours in a 24-hour period, the coordinator must do one of: evacuate the affected portion, post an approved fire watch, rig a temporary water supply, or run an approved hazard-mitigation program (control ignition sources and fuel loads). (You may have heard 4 hours — that's the International Fire Code's threshold, not NFPA 25's. Florida follows the NFPA track, but your AHJ always gets the last word.)
5. Restore and verify. When the work is done: test the system back into service — trip test, main drain, alarm verification, whatever the repair touched — then notify the same list you notified going down, and pull the tags. An impairment isn't over when the wrench stops turning; it's over when the system is verified operational and everyone knows.
Why this belongs in your tracking system, not a clipboard
The failure mode with impairments is never the repair — it's the paper trail. Six months later, someone asks: when did the system come out, who was told, was there a fire watch, when was it verified back? If the answer lives in a tech's memory, you don't have an answer.
The way we built it into FireDeck's Inspections & Compliance module: a field finding marked impairment automatically opens an impairment record — emergency type, linked to the system and the finding — with the Chapter 15 checklist on it: tag posted, fire watch, owner, fire department, insurer, monitoring. The office checks items off as notifications go out, and "mark restored" stamps the verified return to service. The record is permanent, which is exactly what you want when the question gets asked.
However you run it, the discipline is the same: classify honestly, tag physically, notify everyone, mitigate long outages, and verify the restoration. That's the whole chapter — and it's the part of NFPA 25 most likely to matter after the worst day.