When a “Like-for-Like” Fire Alarm Repair Is Not Code-Compliant!
Fire alarm repairs are often assumed to be simple: remove the failed device and replace it with the same model. While this approach may work in limited cases, many “like-for-like” repairs are no longer code-compliant under current standards or local AHJ interpretations.
Understanding why helps owners, contractors, and facility managers avoid costly rework and inspection delays.
What Is a “Like-for-Like” Fire Alarm Repair?
A like-for-like repair typically means replacing a failed device, panel component, or appliance with what appears to be the same or equivalent product — without modifying the rest of the system.
The problem is that fire alarm codes evolve, while systems often remain in service for decades.
Why Simple Swaps Can Create Code Issues
1. Obsolete Devices and Discontinued Models
Many older devices are no longer manufactured. Replacement models may look similar but:
Have different sensitivity
Different spacing rules
Different electrical characteristics
Installing them without evaluating code impact can create non-compliant conditions.
2. Changes in Code Requirements
Fire alarm systems installed years ago were compliant at the time. Since then, changes to NFPA 72 and local amendments may affect:
Detector spacing
Notification appliance coverage
Mounting heights
Power and survivability requirements
A repair can expose these differences.
3. Performance Differences Matter
Even if a device is “listed as compatible,” it may:
Change candela output
Affect audibility levels
Alter detector response characteristics
AHJs often evaluate performance, not just product labeling.
4. Programming and Documentation Conflicts
Replacing a device without updating:
Point labels
Sequences of operation
Shop drawings
Records of completion
can result in inspection findings — even if the hardware works.
5. AHJ Interpretation and Enforcement
AHJs have authority to require corrections when a repair:
Modifies system behavior
Affects coverage or performance
Conflicts with approved documentation
What was once acceptable may no longer be.
When Is Like-for-Like Usually Acceptable?
Like-for-like repairs are more likely to be acceptable when:
The device model is still supported
Code requirements have not materially changed
The repair does not affect coverage or performance
Documentation is updated appropriately
Even then, verification is critical.
Why Repairs Should Be Evaluated — Not Assumed
Fire alarm repairs should be approached with the same care as design decisions. A small change can have system-wide implications.
Evaluating repairs for:
Code impact
Performance
Documentation alignment
protects both safety and compliance.
How Capitol City Fire Protection & Life Safety, LLC Helps
We assist facilities by:
Evaluating repair scope and code impact
Coordinating with AHJs when required
Preventing unnecessary rework
Updating documentation correctly
Restoring systems confidently and compliantly
Our goal is to ensure repairs solve problems — not create new ones.
📞 (225) 242-9215
🌐 www.capitolcityfire.com
Capitol City Fire Protection & Life Safety, LLC
Repairing fire alarm systems the right way.