Emergency Voice/Alarm Communication Systems: Code, Design, and Testing

An emergency voice/alarm communication system is a fire alarm system that replaces generic sirens with spoken instructions telling occupants what to do and where to go. The International Building Code requires these systems in high-rise buildings, large assembly venues, and certain institutional occupancies where a tone alone cannot safely guide a crowd. NFPA 72, the National Fire Alarm and Signaling Code, sets the performance rules: how loud the message is, how clearly it can be understood, how long it keeps running on backup power, and how well its wiring survives fire.

Which Buildings Require One

The IBC triggers the requirement through several sections rather than a single list. High-rise buildings are the most prominent category. The code defines a high-rise as any building with an occupied floor more than 75 feet above the lowest level of fire department vehicle access, and Section 403.4.4 requires those buildings to have an emergency voice/alarm communication system.¹ In a high-rise, the system must operate on at least the alarming floor, the floor above, and the floor below, so the building can run a staged evacuation instead of emptying every floor at once.

Group A assembly occupancies with high occupant loads commonly trigger the requirement, as do certain institutional occupancies. Group I-1 and I-2 facilities such as hospitals and assisted-living centers get a specific exception: the alarm sounds in a constantly attended area and general notification goes out over the overhead page system, rather than a full evacuation tone blasting into patient rooms. Stadiums, arenas, and grandstands with 15,000 or more fixed seats must also provide real-time or prerecorded captions alongside voice messages. The exact triggers depend on the IBC edition your jurisdiction has adopted, so confirm which version is in force locally before assuming anything.

Audibility and Voice Intelligibility

NFPA 72 sets two separate bars, and a system that clears one but not the other fails.

For audibility in public mode, notification must be at least 15 decibels above the average ambient sound level, or 5 decibels above any maximum sound level lasting 60 seconds or longer, whichever is louder.² If a mechanical room has steady background noise of 70 decibels, speakers have to hit at least 85. Private mode, used in places like hospitals where only staff need certain alerts, drops the threshold to 10 decibels above average ambient.

Intelligibility measures whether people can actually make out the words. NFPA 72 uses the Speech Transmission Index as its primary metric: 90 percent of measurement points in a space must score at least 0.45, and the overall average must reach 0.50 or higher.² Equivalent scores on the Common Intelligibility Scale are 0.65 per measurement and 0.70 average. STI accounts for echoes, reverberation, and distortion that can turn a perfectly loud message into garbled noise. Spaces with hard surfaces such as parking garages and atriums are the hardest to design for.

Message Format and Notification Zones

NFPA 72 does not leave message content to the designer’s imagination. For a full evacuation, the system plays a standardized alert tone for at least two cycles before and after the voice message.³ That alert tone follows the temporal-three pattern: half a second on, half a second off, repeated. For relocation or other non-evacuation instructions during a fire, the sequence changes to a one-to-three-second alert tone followed by the voice message, and the whole sequence must repeat at least three times.

Large buildings divide their notification coverage into zones so different floors or areas can receive different instructions at the same time. Notification zones are established through a risk analysis specific to the building, and a single undivided fire or smoke area cannot be split into multiple zones.³ When multiple speaker circuits sit within one zone, all speakers must activate or deactivate together. Enclosed stairways, exit passageways, and groups of elevators sharing a shaft each get their own separate zone, wired for manual paging so the fire department can address those areas independently.

Components and Backup Power

The voice alarm control unit is the central hub, housing amplifiers, message storage, and switching logic that routes the right message to the right zone. From there, wiring runs to ceiling- or wall-mounted speakers and synchronized strobes placed to cover every occupied space.

Backup power is where EVACS requirements diverge from ordinary fire alarms. Standard fire alarms need batteries sized for 24 hours of standby plus 5 minutes in full alarm. An EVACS needs the same 24 hours of standby but must sustain full alarm operation for at least 15 minutes, because voice messages consume far more power than simple tones.² If the building has an emergency generator, batteries are still required as a bridge in case the generator is slow to start, but they only need to provide 4 hours of standby capacity instead of 24.

Pathway Survivability

Backup power does no good if fire burns through the wires before the message reaches the speakers. NFPA 72 addresses this with four pathway survivability levels:

Level 0: no survivability protection required, used only in the simplest systems in low-risk settings.
Level 1: the building must have a full automatic sprinkler system, and all cables must run in metal raceways or use metal-armored cable.
Level 2: wiring must use two-hour fire-rated circuit integrity cable, a two-hour fire-rated cable protection system, or run inside a two-hour fire-rated enclosure.
Level 3: combines the sprinkler protection of Level 1 with the two-hour fire-rated wiring or enclosure of Level 2.

Most EVACS installations in high-rises require Level 2 or Level 3 survivability.³ Two-way in-building emergency communication wiring specifically must meet Level 2 or Level 3, with no option for lower levels.

Two-Way Firefighter Communication

EVACS handles one-way announcements from the control room to occupants. Two-way telephone communication systems handle the other direction, letting firefighters and building personnel talk back. Where a building provides a two-way telephone system, NFPA 72 requires at least one telephone station or jack at each of the following locations:³

Every floor level
Every notification zone
Every elevator cab and elevator lobby
Elevator machine rooms
Emergency and standby power rooms
Fire pump rooms
Areas of refuge
Inside each enclosed exit stairway on every floor

The system must support at least five stations operating simultaneously in a common talk mode. Wall-mounted stations sit between 36 and 66 inches above the floor, and any station accessible to the general public drops to a maximum of 48 inches.

Fire Command Center

High-rise buildings and certain large industrial occupancies must provide a dedicated fire command center where the fire department runs operations. Under IBC Section 911, the room must be at least 200 square feet or 0.015 percent of the total building area, whichever is greater, with a minimum dimension roughly equal to 10 feet.¹ The location must be approved by the fire code official and typically sits on the ground floor with direct exterior access.

The EVACS control unit is one of many required features inside the fire command center, alongside the fire department communication system, fire detection annunciator, elevator position and status indicators, air-handling and smoke control panels, stairway door unlock controls, sprinkler valve and waterflow displays, emergency power status indicators, schematic floor plans, and the building information card.¹ The point is to give the incident commander a single room where every building system can be monitored and controlled.

Visual Notification for Occupants Who Cannot Hear

Voice messages do nothing for occupants who are deaf or hard of hearing, so an EVACS is not sufficient on its own. Federal accessibility standards require synchronized strobe lights to supplement every audible notification. The U.S. Access Board specifies that visual alarm appliances be mounted 80 inches above the floor or 6 inches below the ceiling, whichever is lower.⁴ No point in any room required to have a visual signal can be more than 50 feet from that signal in the horizontal plane.

Large open spaces over 100 feet across, like auditoriums without tall obstructions, can use perimeter-mounted strobes spaced up to 100 feet apart instead of suspending units from the ceiling.⁴ Any room with more than two strobes requires synchronization so the flashing pattern is uniform. The captioning requirement for venues with 15,000 or more fixed seats adds another layer, delivering the same instructional content that comes through the speakers.

Mass Notification Integration

A traditional EVACS addresses fire emergencies. A mass notification system covers everything else: severe weather, security threats, hazardous material releases, active-threat situations. NFPA 72 Chapter 24 allows both systems to share speakers and infrastructure, but integration takes careful planning because fire and non-fire messages can conflict.

The standard does not impose a fixed priority hierarchy between the two. The building’s emergency response plan determines which type of message takes precedence in a given scenario.³ Mass notification can override fire alarm messages when the response plan specifically identifies and approves that override. When the MNS takes control, it deactivates all fire alarm audible and visible notification so occupants hear one clear instruction rather than competing messages. A distinctive indicator at the fire alarm control panel alerts the fire department that the MNS has assumed priority. Once the mass notification event ends, the fire alarm system automatically restores to normal operation or resumes its alarm sequence if a fire condition is still active.

Every MNS design must start with a risk analysis specific to the facility. NFPA 72 Section 24.3.10 requires the analysis to consider the maximum occupant load of every occupiable space, the characteristics of the occupancy, and the full range of anticipated threats, grouped into natural hazards, accidental human-caused events, intentional human-caused events, and technological failures.³ The risk analysis then drives decisions about notification zones, message priority, and how far the notification reach extends.

Design, Acceptance Testing, and Maintenance

An acoustical analysis is the foundation of every EVACS design. It models how sound behaves in each space, predicting dead zones, echo problems, and areas where reverberation will drag STI scores below the required level. From this analysis, the designer produces floor plans showing every speaker and strobe location, wiring diagrams tracing electrical pathways through each notification zone, and battery calculation worksheets proving the backup power will last the required duration. The package goes to the local authority having jurisdiction for review before permits issue.

Once installation is complete, the authority having jurisdiction schedules a mandatory acceptance test. Inspectors verify that every speaker activates, check volume and clarity at multiple measurement points, and confirm that STI scores match the levels promised in the design documents.² A battery test confirms the secondary power supply can sustain 24 hours of standby followed by 15 minutes of full alarm operation. Any speaker producing distorted audio or falling short of the required decibel levels must be corrected before the system passes. A successful test concludes with a fire alarm completion certificate.

Passing acceptance testing is not the end of it. NFPA 72 requires ongoing inspections and testing throughout the life of the system. Emergency voice/alarm communication equipment must be inspected every six months and functionally tested at least once a year. Individual speakers follow the same schedule: semi-annual visual inspection and annual performance testing to confirm they still produce clear, undistorted audio at the required volume.

Building owners must keep records of every inspection, test, and maintenance action. Routine inspection records must be retained for at least one year after the work is performed. As-built drawings, original acceptance test results, hydraulic calculations, and manufacturer specification sheets must be kept for the life of the system. Missing records create real problems during renovations or ownership transfers because the next team has no baseline to work from.

1
ICC. 2024 International Building Code Chapter 9 Fire Protection and Life Safety Systems
2
Energy.gov. Understanding ECS Risk Analysis and Voice Intelligibility
3
IFMA Central Ohio. NFPA 72 Chapter 24 Emergency Communications Systems
4
U.S. Access Board. Chapter 7 Communication Elements and Features