The four reasons ERCES inspections fail, and what they have in common

A failed ERCES inspection is rarely a surprise to the people who designed the system. It is usually the moment a decision made during design finally becomes visible, and by then the building is finished, the ceiling is closed, and the certificate of occupancy is waiting on a signature.

Across the projects we have been called into as a second opinion, the same four causes come up again and again.

The building was never tested first

Code does not require an ERCES because a building is tall or new. It requires one because the existing public-safety signal inside it fails a grid test. That test is the trigger, and it is also the baseline everything afterwards is measured against.

Skipping it means the system is designed against an assumption. When the AHJ runs their own grid test at inspection, there is nothing to compare it to, and any argument about what the building was like before is an argument you have already lost.

The design targeted coverage, not margin

The code minimum is 95 percent of general areas and 99 percent of critical areas at or above the signal threshold. A design that hits exactly those numbers on paper has no room left for anything.

Buildings move. Furniture arrives, tenants fit out, a fire door gets propped open, a rooftop unit is added. A system engineered with margin absorbs that. A system engineered to the minimum fails the re-test a year later, and the annual test is also code.

Nobody spoke to the fire marshal until the end

The AHJ is not a formality at the end of the process. They set the frequencies, the acceptable equipment, the monitoring requirements and the documentation format, and those requirements vary between jurisdictions in ways no national standard resolves for you.

Pre-approval coordination is the cheapest part of an ERCES project and the one most often skipped. Filing the permit set after the equipment is ordered is how a project discovers it bought the wrong amplifier class.

The install did not match the drawing

The last one is the most avoidable. Fire-rated pathways, correct cable, battery backup sized to the standard, fault monitoring wired back to the fire alarm panel: these are not the interesting parts of an ERCES, and they are what an inspector checks first because they are checkable.

A system that performs perfectly and cannot show a monitored, code-built installation does not pass.

What they have in common

None of these four are radio-frequency problems. They are sequencing problems. Test first, design with margin, agree the requirements with the person who signs off, and build what was drawn. In that order, an inspection is a formality.