(Why early ERCES planning helps architects, contractors, life-safety trades and inspectors avoid late-stage disruption)
Architects rarely intend to create problems downstream. Yet ERCES issues often appear late in a project, long after thoughtful design decisions are made, drawings are issued, and the building is nearly finished. When that happens, ERCES feels intrusive, costly, and at odds with the architecture.
The irony is that most ERCES problems aren’t caused by poor systems. They’re caused by delayed planning.
What ERCES Really Is (From a Design Perspective)
Emergency Responder Communication Enhancement Systems (ERCES) are designed to ensure that first responders can communicate reliably inside buildings where radio signals are weak or otherwise blocked by modern construction materials.
From an architectural perspective, ERCES is not just a gadget or an add-on. It is an integral part of the infrastructure. Similar to fire sprinklers, fire alarm pathways, or smoke control systems, ERCES directly influences key architectural decisions such as floor layouts, stairwells and shafts, ceiling systems, equipment rooms, pathway routing, and exterior components like roofs and facades.
When ERCES is addressed early, it integrates quietly into the building. When it is addressed late, it competes for space and attention.
Why ERCES Causes Problems When It’s Deferred
ERCES requirements are often identified during plan review or during late-stage testing. By that point, ceiling heights are fixed, shafts are full, rated pathways are already defined, and architectural finishes are complete. The result is rarely better safety. More often, it is redesign, rework, and visual compromise. What could have been a coordinated infrastructure decision becomes a series of field fixes.
The Role of An ERCES Preliminary Design
A preliminary ERCES design does not constitute a commitment to install a system. It serves as a risk-management step during the design phase. Typically, a preliminary ERCES design assesses the building’s size, use, and construction type; identifies areas that may pose radio challenges, such as basements, stairwells, and elevators; considers potential equipment locations; reviews pathway and survivability implications; and highlights coordination points with architecture and other trades.
The goal is straightforward: make sure the building can support an ERCES if later testing indicates it is necessary.
How This Helps Architects
Addressing ERCES during design helps architects prevent unexpected plan-review issues, protect ceiling heights and clean lines, avoid ad-hoc equipment placement, reduce last-minute coordination meetings, and preserve architectural intent.
In short, it stops ERCES from turning into a design problem after the design is finished.
Why IBWS Recommends Preliminary ERCES Design
IBWS works with architects and design teams early to evaluate ERCES risk before it turns into a construction problem.
Our initial design approach emphasizes assessing whether ERCES is likely needed, defining infrastructure requirements without overbuilding, collaborating early with architectural constraints, and recording assumptions for discussions with the Authority Having Jurisdiction.
This enables design teams to proceed with clarity, regardless of whether a system is ultimately installed.
The Key Takeaway
Early ERCES planning works best when architects, general contractors, and life-safety trades share a clear understanding of the system’s infrastructure requirements. A preliminary ERCES design provides that common reference point, allowing each stakeholder to coordinate purposefully rather than reactively.
ERCES is easiest to handle when it remains invisible, which only happens through early planning. A preliminary ERCES design doesn’t complicate architecture; it protects it. If your project involves dense construction, below-grade spaces, or public occupancy, addressing ERCES during the design phase is not extra work. It serves as insurance against disruptions late in the project.