8.1 Impairment Programs & AHJ Notification
Key Takeaways
- An impairment is any condition that takes a required fire alarm system, zone, or function out of service—planned work and unresolved troubles both count
- NFPA 72 expects a written impairment program: tags, owner/AHJ/supervising-station notification, duration tracking, and restoration verification
- A trouble or off-normal condition not restored within about 24 hours is handled as an impairment under standard NFPA 72 impairment concepts
- Fire watch and other temporary alternative measures are compensations for lost protection—they do not replace restoring the listed system
- Never leave an occupied building with silent, untagged, unreported downtime; coordinate with the owner and occupants before and after the outage
8.1 Impairment Programs & AHJ Notification
Quick Answer: When a required fire alarm system (or any required portion of it) is out of service, treat it as an impairment. Use a written impairment program: tag impaired equipment, notify the owner, AHJ, and supervising station as required, track duration, provide fire watch or other temporary measures when needed, verify correct operation before return to service, then remove tags and report restoration. Unresolved troubles that persist roughly 24 hours are handled as impairments—not “just a trouble light.”
Maintenance domain 2.2 is roughly one-third of NICET FAS Level II. Periodic testing (Chapter 7 of this guide) finds problems; this section covers what you do when protection is actually down. Level II technicians often own the field side of impairments during ITM, renovations, and emergency repairs. Doing the electrical fix without the impairment process is a common exam and field failure.
What Counts as an Impairment
NFPA 72 impairment concepts address conditions where the system or a portion of the system is out of service or cannot perform a required function. That is broader than “the FACU is powered off.”
Examples of impairments or impairment-equivalent downtime:
- FACU, NAC booster, or power supply intentionally powered down for service
- SLC, NAC, or initiating circuit disabled, jumpered, or open so coverage/notification is lost
- Detection or notification intentionally bypassed for construction in an area that still needs protection
- Elevator recall, HVAC shutdown, door release, or suppression interface disabled while still required by design
- A trouble or off-normal condition that remains unrestored long enough that formal impairment handling applies (commonly taught as the 24-hour threshold for treating an unrepaired trouble as an impairment)
Examples that are not automatically full-system impairments by themselves:
- A single device under active, short-duration functional test with the rest of the system normal and supervised
- A routine software/firmware update performed under a controlled plan with continuous monitoring and immediate restoration (still may require notifications if functions are offline)
- A supervisory signal for a sprinkler valve that is being tested under a sprinkler impairment program (coordinate—two systems, one building risk)
| Condition | Typical handling |
|---|---|
| Planned FACU swap tomorrow | Planned impairment with written plan |
| Storm damage opens SLC at 02:00 | Emergency impairment — notify and protect first, document as you go |
| Open SLC left unrestored overnight into the next day | Trouble becomes formal impairment handling if not restored within the code’s duration concept (~24 h) |
| Annual detector sensitivity test, system restored same visit | Testing procedure, not a multi-day impairment—if coverage is down, still control notifications and duration |
Exam trap: “Nothing is required if the impairment is under 8 hours.” Duration can affect fire-watch decisions and urgency, but it does not erase tagging, owner coordination, and required notifications. Short outages still need control.
Planned vs Emergency Impairments
Planned (preplanned) impairments
Use when you know protection will be offline: panel upgrade, major rewire, phased renovation, battery replacement that drops standby, scheduled interface work with elevators or HVAC.
Before work:
- Written impairment plan — what is down, why, start/stop times, who is responsible, how the building is protected meanwhile, who to call.
- Notify the property owner/manager, the AHJ when required by code/AHJ policy, and the supervising station so central station/proprietary/remote operators do not treat expected troubles as ignored alarms.
- Tag impaired equipment and, where practical, the control unit or affected zones so other techs and building staff see the status.
- Stage temporary measures — fire watch, temporary detection/notification, area evacuation plans, or heightened occupant awareness as the AHJ/owner requires.
- Coordinate occupants — elevators, noisy testing, door magnets dropping, and HVAC shutdowns surprise people if you do not warn them.
Emergency impairments
Use when failure is sudden: cable damage, water in a panel, device failure that forces a circuit offline, accidental disable during other trades’ work.
Priorities shift:
- Life safety first — if the building is occupied and detection or notification is lost, establish compensatory protection immediately (fire watch, evacuate if directed by owner/AHJ, isolate only what is necessary).
- Notify owner and supervising station promptly; notify the AHJ per local policy and NFPA 72 impairment expectations (do not wait for “business hours paperwork” while the building is dark to fire).
- Document as soon as practical—tags, log entries, time stamps—even if the written plan is completed after the initial emergency steps.
- Repair and restore on a priority basis; convert the emergency into a tracked impairment until full service returns.
Tag Out and Visual Control
Impairment tags (or equivalent controlled labels) mark equipment or zones that are out of service. Good practice:
- Place tags at the FACU and at field equipment that is intentionally disabled when accessible.
- Record system name, impaired portion, date/time, company, technician, and expected restoration.
- Do not remove tags until the impaired portion is verified operational and restoration notifications are complete.
- Never leave a silent bypass, lifted conductor, or software disable with no tag—the next shift will not know what is broken on purpose.
Tags are communication tools for AHJ inspectors, other trades, and night staff, not decorations for the job folder.
Fire Watch and Temporary Alternative Measures
When required protection is impaired, the AHJ or adopted requirements may mandate a fire watch or other temporary measures. Level II technicians should understand the concept even when the owner hires the watch:
- A fire watch is continuous or scheduled human surveillance of impaired areas to detect fire and initiate occupant notification and emergency response.
- It compensates for lost automatic detection or notification—it does not equal a working listed system.
- Scope, training, and documentation of the watch are often set by the AHJ or facility policy (routes, interval, radios, log sheets).
- Other temporary measures can include temporary smoke detection, horns/strobes on temporary power, restricting hot work, or limiting occupancy in the impaired area.
| Temporary measure | When it helps | Limit |
|---|---|---|
| Fire watch | Occupied building with lost detection/notification | Labor-intensive; must be real continuous coverage |
| Temporary appliances | Renovation zones still occupied | Must still warn occupants; not a permanent substitute |
| Hot-work ban / extra permits | Construction impairments | Does not detect accidental fires elsewhere |
| Partial evacuation / area closure | High-risk outage | Operational impact; needs owner decision |
Scenario: A hospital wing SLC must be offline for four hours to clear water-damaged cable. The impairment plan includes AHJ/owner notification, supervising-station “test/repair” status, corridor fire watch, no hot work in the wing, and a hard stop time with full restore and tag removal before night shift. That is Level II impairment control. Pulling the circuit “real quick” with no notice is not.
AHJ Notification Thresholds and Who Else Gets Called
NFPA 72 impairment procedures emphasize notification of parties who must know protection is reduced:
- Authority Having Jurisdiction (AHJ) — fire department, fire marshal, or other designated authority, especially for impairments that leave required systems out of service or when local rules require notice for any impairment.
- Property owner / owner’s designated representative — ultimately responsible for building safety and for authorizing fire watch or occupancy limits.
- Supervising station — so operators know expected troubles, do not dispatch inappropriately, and resume normal response after restore.
- Occupants / facility staff as needed — security, nurses’ stations, front desk, and after-hours contacts.
Local amendments matter. Some jurisdictions want notice for any impairment of a required system; others focus on duration or extent (whole building vs one floor). On the exam, prefer answers that notify the AHJ and supervising station and tag the system over answers that “fix the owner only if convenient.”
Duration tracking
Log:
- Impairment start date/time
- Portion impaired (system, circuit, zone, function)
- Reason and responsible party
- Temporary measures in place
- Target restoration time and actual restoration time
- Who was notified and when (including restoration calls)
Duration tracking supports AHJ expectations, owner risk decisions, and proof that you did not abandon an open trouble for days.
Restoring the System
Returning to normal service is part of the impairment program, not an afterthought:
- Complete the repair or planned work.
- Verify that the impaired portion operates correctly (functional check appropriate to what was down—not a paperwork-only clear).
- Confirm related supervision (troubles clear, devices report, NACs drive loads, interfaces actuate if they were part of the impairment).
- Notify the AHJ and supervising station that the system is restored (and the owner/representative).
- Remove impairment tags.
- File the impairment record with ITM documentation for the site.
Leaving tags on after restore confuses the next inspector. Removing tags before verification creates a false “all clear.”
Coordinating with Owner and Occupants
Impairments are building-operations events:
- Schedule planned work for lowest risk periods when the owner allows (often nights for assembly or health care, but follow the facility—not your convenience alone).
- Explain what signals occupants may hear/see (troubles, disabled LEDs, door release).
- Keep egress clear; do not stage ladders and open panels in a way that blocks exits during reduced protection.
- For multi-tenant buildings, identify who can authorize fire watch and who holds the monitoring account passwords/contacts.
Exam Focus
When a stem describes a system “down for repair,” “bypassed for construction,” or “in trouble since yesterday,” look for the answer that implements a written impairment approach: tag, notify AHJ/owner/supervising station, track time, provide temporary protection when required, verify before restore, and remove tags. Reject options that treat short duration as a free pass or that restore service by clearing a trouble without functional verification.
Per NFPA 72 impairment concepts commonly tested at Level II, a trouble condition that is not restored within approximately which duration is treated as an impairment requiring formal impairment handling?
A planned FACU replacement will take a required protected-premises system out of service for six hours in an occupied building. Which package best matches NFPA 72 impairment expectations?
After repairing an impaired NAC riser, what must be completed before the system is returned to normal service and tags are removed?
Which statement best describes the role of a fire watch during a fire alarm impairment?