The Paper Trail: Every Document Your Building Needs to Prove ERCES Compliance

An Emergency Responder Communication Enhancement System (ERCES) is designed to keep first responders connected when building materials, distance, or structural conditions weaken public-safety radio signals. But reliable performance is only one part of compliance.

The other part is documentation.

During plan review, commissioning, a Certificate of Occupancy process, or a fire marshal inspection, building owners may be asked to prove that the ERCES was properly designed, installed, tested, monitored, and maintained. If critical records are missing, outdated, or inconsistent with the installed system, an otherwise functional system can still create delays.

A complete compliance file should clearly connect the design intent, installed equipment, test results, backup power, fire alarm interface, and ongoing maintenance history. Requirements vary by jurisdiction, adopted code edition, and Authority Having Jurisdiction (AHJ), so always confirm the local process before finalizing a project.

The following document checklist provides a practical framework for building owners, facility managers, developers, and government agencies.

1. System Design and Permit Documents

The paper trail begins before installation. The design and permit package establishes what the ERCES is intended to do and which standards govern the work.

A typical submittal package should include:

Project name, building address, owner, and occupancy information
Installing contractor and system designer information
A written design narrative
Applicable code and standard editions
Floor plans and reflected ceiling plans
Public-safety radio coverage predictions
Donor antenna location and orientation
BDA or headend equipment locations
Indoor antenna locations
Coaxial cable, fiber, riser, and pathway routes
One-line diagrams and point-to-point wiring details
Equipment schedules and manufacturer cut sheets
Frequency and channel information
Equipment listings and certifications, where required
Fire alarm interface details
Backup power and battery calculations
Planned test-grid layouts
Initial or pre-installation signal survey data

Establish the code basis

The design narrative should identify the standards used for the project. Depending on the jurisdiction, this may include IFC Section 510, NFPA 72, NFPA 1225, applicable local amendments, and equipment requirements such as UL 2524.

The International Code Council’s IFC overview explains that the International Fire Code is a model code adopted and amended by individual jurisdictions. That means the code edition and local amendments matter. A document package that passes review in one city may require additional information in another.

Show the system: not just the equipment

A list of BDA model numbers is not enough. The drawings should allow an AHJ to understand how the full system operates, including the relationship between the donor antenna, BDA, DAS cabling, indoor antennas, power supplies, batteries, monitoring panels, and fire alarm control unit.

2. Initial Coverage Survey and Grid Test Data

Before a BDA or public-safety DAS is designed, the building should be evaluated for existing radio coverage. This baseline is commonly documented through a pre-installation grid test or initial determination coverage test.

The report should identify:

Building areas tested
Floor-by-floor grid layout
Test-point locations
Radio bands and channels evaluated
Signal strength measurements in dBm
Test equipment used
Equipment calibration status
Building conditions during testing
Critical areas requiring special attention
Areas that failed to meet the applicable threshold

A pass/fail statement without measurement data is often insufficient. The actual readings provide the technical evidence needed to justify system design decisions.

Typical critical areas may include:

Exit stairs and exit passageways
Fire command centers
Fire pump rooms
Elevator lobbies
Standpipe and sprinkler valve locations
Basements and parking structures
Areas identified by the local fire marshal

Grid dimensions and signal thresholds are jurisdiction-specific. Some AHJs use 20-point grids, while others require a different layout. Likewise, signal requirements may distinguish between general and critical areas. The design file should state the exact test method and acceptance criteria used.

3. Battery Calculations and Emergency Power Records

An ERCES must continue operating when normal building power is interrupted. The compliance file should therefore include clear documentation for the system’s secondary power supply.

Battery documentation should show:

Connected equipment and current draw
Standby and alarm-load calculations
Required operating duration
Battery capacity
Voltage and amp-hour ratings
Allowable derating factors
Environmental or installation considerations
Calculated reserve margin
Battery cabinet and power-supply locations
Generator or alternate power connections, if applicable
Battery installation date and replacement schedule

The calculation should match the equipment actually installed. If the design originally listed one amplifier, power supply, or fiber unit but the final installation includes another, the battery calculation must be updated.

During annual service, records should also document battery condition, charger operation, supervisory signals, and any runtime or load verification performed. A battery that looks acceptable during a visual inspection may still fail under load.

4. Acceptance Test and Commissioning Report

The acceptance test report is one of the most important documents in the ERCES file. It demonstrates that the installed system performs according to the approved design and the AHJ’s acceptance criteria.

A complete report generally includes:

Project and building information
Testing date and personnel
Test procedures and applicable standards
Test equipment and calibration records
Final equipment inventory
BDA gain and programming information
Donor signal measurements
Downlink and uplink readings
Floor-by-floor grid data
Critical-area test results
DAQ or audio-quality results, if required
Isolation and oscillation test results
Fire alarm interface testing
Battery and emergency power verification
Supervisory signal verification
Failed points and corrective actions
Final pass/fail summary
Acceptance signatures and AHJ comments

Grid data should show the individual measurement at every test point. Heat maps can make results easier to review, but they should supplement: not replace: the underlying readings.

If a test point fails, the report should not hide the failure. It should identify the corrective action, such as antenna relocation, cable repair, gain adjustment, filtering, or system redesign, followed by documented retesting.

5. Fire Alarm Interface and Monitoring Records

ERCES equipment commonly reports trouble and supervisory conditions through the building’s fire alarm system. The documentation must show how those signals are generated, transmitted, annunciated, and tested.

Maintain records for:

Fire alarm interface drawings
Point-to-point wiring
Control logic
Signal descriptions and labels
BDA fault conditions
AC power failure
Battery trouble or low-battery conditions
Amplifier failure
Donor or antenna path faults
Fiber or cable faults
Remote annunciator locations
Fire alarm panel programming
NFPA 72 functional testing
Corrective actions and retesting

An inspector needs to verify that a fault will be recognized by the monitoring system: not merely displayed locally at the BDA cabinet.

6. As-Built Drawings and Closeout Package

The final system is rarely identical to the first design. Field conditions may require equipment relocation, cable rerouting, antenna changes, or approved substitutions. Those changes must be reflected in the as-built drawings.

As-built documents should show:

Final BDA, headend, and remote-unit locations
Final donor antenna location and azimuth
Final indoor antenna locations
Cable and fiber pathways
Equipment-room details
Power sources and disconnects
Battery cabinets
Grounding and surge protection
Fire alarm interface points
Monitoring panels and annunciators
Equipment model numbers and serial numbers
Approved deviations from the original design
Final coverage-grid locations

The closeout package may also include equipment manuals, warranties, programming files, frequency coordination documents, permits, approval letters, and the final Letter of Compliance or Certificate of Completion, where applicable.

As-built accuracy matters. When a future technician arrives for annual testing, the drawings should help locate every critical component without opening walls or tracing undocumented cabling.

7. Annual Inspection and Maintenance Records

ERCES compliance is not a one-time event. Building renovations, new construction, damaged cables, failed batteries, and changes to surrounding structures can affect radio performance.

Annual records should document:

Date and location of inspection
Technician and company information
Visual inspection results
BDA operational status
Antenna and cable condition
Grounding and surge protection
Battery and charger condition
Fire alarm supervisory testing
Remote annunciator operation
Alarm and trouble signal verification
Representative RF measurements
Required full grid testing, when applicable
Repairs and component replacements
Corrective-action completion
Final certification or service report

The UL Solutions ERCES overview describes ERCES components such as repeaters, signal boosters, remote annunciators, power supplies, and battery charging systems. Each component should be accounted for in the inspection and maintenance history.

Keep records in a centralized location: both digitally and, where required, at the system headend. A fire marshal should be able to review the latest annual report, prior deficiencies, and corrective actions without searching through disconnected contractor files.

Build a Compliance File That Is Ready Before the Inspection

A strong ERCES documentation package answers five questions:

What was designed?
What was installed?
Did it pass acceptance testing?
Will it operate during a power failure?
Is it still being inspected and maintained?

When those answers are supported by organized records, building owners gain more than inspection readiness. They gain visibility into the life-safety system protecting occupants and first responders.

Global Network LLC provides ERCES and Public Safety DAS design, installation, commissioning, compliance testing, and annual maintenance support. From initial grid testing to final as-built documentation, the objective is clear: 0% Missed Deadlines. 0% Documentation Gaps. Reliable communication when it matters most.

For a compliance consultation, contact Global Network LLC: