Mass Notification and ECS for Georgia K-12 Schools

The two systems people confuse: voice evac vs. mass notification

A fire alarm voice evacuation system is one-way audio that delivers a pre-recorded or live fire-instruction message to building occupants, typically following a single sequence: alarm tone, voice message, alarm tone, voice message. Voice evac is well-defined by NFPA 72 Chapter 18 (notification appliances) and Chapter 23 (protected premises). The audience is everyone in the building; the message is uniform; the trigger is a fire signal.

A mass notification or emergency communications system is a broader animal. It is governed by NFPA 72 (2022 Edition) Chapter 24, titled Emergency Communications Systems. Chapter 24 covers in-building ECS, wide-area ECS (campus and outdoor), and distributed-recipient ECS (SMS, app push, email). The audience can be targeted (a single corridor, a single building, a single grade level); the message can vary by event type; the trigger can be fire, weather, lockdown, intruder, hazardous materials, or operator-initiated.

Districts often start a project assuming they need voice evac and end up needing ECS. Knowing the difference at programming saves a redesign at submittal.

What NFPA 72 Chapter 24 actually requires

Chapter 24 is built around the concept of a risk analysis. Section 24.3 requires that an ECS be designed based on a documented risk analysis that identifies the threats the system must address, the populations it must reach, and the acceptable failure modes. For a Georgia K-12 school, a typical Chapter 24 risk analysis covers:

• Fire. Always required when the building has a fire alarm.
• Severe weather. Tornado watch and warning, lightning shelter-in-place, severe thunderstorm. Georgia sits in a tornado-prone climate and schools are designated shelter locations for surrounding communities.
• Lockdown and intruder. Active assailant, suspicious person on grounds, perimeter breach.
• Medical emergency. Cardiac event, mass-casualty incident requiring directed lockdown of unaffected areas.
• Hazardous material release. Chemical, biological, radiological, or large-scale chemical spill (most common in science wings and bus garages).
• Utility failure. Power loss with extended evacuation, gas leak.

The risk analysis output drives system design. A school where the risk analysis identifies active-shooter response as a critical scenario needs an ECS architecture that can target specific zones (lockdown a single wing while evacuating others), broadcast different messages by zone, and recall the system from a fire-alarm-initiated full-building evac if the actual event is a lockdown rather than a fire.

Chapter 24 also requires:

• Survivable pathways. ECS signaling line circuits must survive fire conditions long enough to deliver the emergency message. Two-hour-rated cable or Class A pathways are the typical solutions.
• Secondary power. ECS must operate on secondary power for the full required notification duration.
• Distinct alert tones and pre-alert tones that are not the standard NFPA 72 fire signal.
• Trained operators. The system must include credentialed operator interfaces, and the district must train staff on operator use.
• Documentation. Risk analysis, design narrative, sequence-of-operations matrix, training records, and annual inspection records under Chapter 14.

How Georgia school standards and funding shape the choice

Georgia school construction is funded primarily through SPLOST (Special-Purpose Local-Option Sales Tax), a county-level sales tax authorized by referendum, and through state capital outlay funds administered by the Georgia Department of Education facilities office. Both funding streams have facility-standard expectations, and ECS is increasingly a baseline scope item rather than an option.

Several Georgia districts now specify combined fire alarm plus ECS architecture as the default for new construction and major renovations. The driver is partly cost (one common infrastructure is cheaper than two) and partly operational (a single user interface for office staff is more reliable in an emergency than two separate panels).

The Georgia Department of Education's facility planning guidelines reference NFPA 72 by edition, and updates flow through the state-adopted edition under Rule 120-3-3-.04. As of the 2022 Edition adoption, ECS expectations in Georgia school plans have aligned with Chapter 24 requirements, including the risk analysis requirement.

Active shooter, weather, and lockdown overlay

The decade since the 2018 IFC adoption has reshaped how Georgia districts think about school security. ECS systems are no longer optional for districts that take an honest look at their threat profile.

Active-assailant response on an ECS architecture typically includes:

• Pre-recorded lockdown announcement that overrides ongoing fire alarm signaling and directs occupants to shelter rather than evacuate. The override sequence is critical: a fire alarm activated by a perpetrator to drive occupants into a hallway must be defeatable from the operator console.
• Zone-targeted messaging. Lockdown a single wing while continuing normal operations in others when the threat is localized.
• Two-way communication with classroom-level intercom or wireless panic devices, so staff can confirm status without leaving secured rooms.
• Integration with parent and staff notification. SMS to parents, email to staff, integration with district-level emergency management.

Severe weather overlay typically includes:

• NWS alert integration. Automatic activation on county-level tornado warning when configured.
• Pre-recorded shelter-in-place announcement that overrides routine paging.
• Integration with weather radio as a redundant trigger.

A combined fire alarm plus ECS architecture handles all of this from one back-end. A separate-systems approach (fire alarm on one panel, ECS on another, lockdown buttons on a third) requires manual coordination during an event, and manual coordination during a stress event is unreliable.

Survivable pathways and other Chapter 24 technical details

NFPA 72 Chapter 24 requires survivable pathways for ECS messaging in many configurations. The intent is that the system must keep working long enough for occupants to receive and act on the emergency message, even if a fire damages some circuits. Two implementation paths:

1. Class A signaling line circuits and Class A notification appliance circuits. A short or open on a single conductor does not disable the circuit.
2. Two-hour-rated fire-resistive cable. Cable assembly rated for two-hour exposure per UL 2196 or equivalent, protecting circuits through fire-rated walls and ceilings.

Most Georgia schools use a hybrid: Class A on signaling lines, two-hour-rated cable for risers and critical pathways. The design choice is driven by building geometry, cost, and Chapter 23 protected-premises requirements that intersect with Chapter 24.

Other Chapter 24 details that come up routinely in Georgia school designs:

• Audibility and intelligibility. Chapter 18 audibility tables apply to ECS, plus Chapter 24's intelligibility requirements. STI-PA measurement is the field-test method most inspectors expect to see.
• Coverage. All occupiable spaces, including outdoor athletic fields and parking areas if the risk analysis identifies them. Outdoor coverage often drives wide-area ECS speakers.
• Secondary power. Generator backup with NFPA 110 (2025 Edition) Type 10 Class 1.5 minimum. Battery-only backup is rare on schools because the required operating duration is long.

IP paging, marquee signs, SMS, and parent notification

Modern ECS integrates with the digital infrastructure already on a school campus. Typical integrations:

• IP paging. Cisco, Singlewire InformaCast, or similar platforms tie classroom phones, ceiling speakers, and the ECS together over the school network.
• Marquee signs. Outdoor LED marquees flip to emergency messaging on ECS activation.
• SMS to parents. District-level emergency notification platforms (Blackboard Connect, ParentSquare, SchoolMessenger) integrate with the ECS through API or middleware.
• Staff app push. Mobile alerting for staff who are off-campus or in transit.
• Public address override. ECS announcement overrides routine intercom paging without manual intervention.

The integration layer is where most school ECS projects either deliver value or stall. A well-integrated system reduces operator load during an event from "remember to activate four systems" to "press one button." A poorly integrated system multiplies operator load.

The case for combined ECS plus fire alarm vs. separate systems

JB Technologies recommends combined architecture for almost every Georgia K-12 project. The reasons:

• One panel, one operator interface. Fewer points of failure under stress.
• Shared infrastructure. One set of speakers, one cable plant, one set of survivable pathways.
• Lower lifecycle cost. One annual ITM contract, one set of spare parts.
• Cleaner Chapter 24 risk analysis. Documented integration is easier to audit than documented separation.
• Cleaner submittal. The combined system is reviewed once under NFPA 72 (2022 Edition), not as two separate code packages.

The case for separate systems is narrower than districts often assume. It comes up mainly when a district has an existing fire alarm with significant remaining useful life and wants to add ECS as an overlay rather than replace. Even then, the overlay should be integrated at the operator interface, not left as two parallel panels.

Inspection, testing, and maintenance under Chapter 14

ECS systems are inspected and tested under NFPA 72 (2022 Edition) Chapter 14 just like fire alarm systems. The intervals are similar: 100 percent of devices at acceptance, then annual functional testing thereafter. Batteries are tested semi-annually under load. Voice intelligibility is verified at acceptance and at any major change.

Schools have an additional operational layer: drills. Georgia requires regular fire drills, and many districts run additional lockdown and severe-weather drills annually. The ECS is the audible backbone of those drills, and the drill schedule itself becomes an informal test of the system. Districts should document drill performance in the same record book as the formal ITM inspections; AHJs sometimes ask to see both.

Procurement and vendor selection notes for districts

A few notes for district facility managers evaluating ECS proposals:

• Ask for the Chapter 24 risk analysis up front. A vendor who proposes equipment before documenting the risk analysis is proposing a hardware list, not a designed system.
• Confirm Georgia fire alarm contractor licensure. ECS work integrated with fire alarm requires the same Georgia low-voltage fire alarm license, including the fire alarm specialty designation.
• Confirm NICET-credentialed designers. NICET Level III or IV in Fire Alarm Systems is the de facto standard for the designer of record on Georgia school projects.
• Ask how the system integrates with existing IT infrastructure. District IT has opinions about VLAN placement, multicast, and network resilience; involve them at design.
• Ask about training and operator credentials. Chapter 24 requires trained operators, and training must be documented.
• Ask about lifecycle support. Annual ITM, software updates, and parts availability for 10 to 15 years are real considerations on a system the district will own for two decades.

A district that asks those questions in vendor RFP responses filters out the proposals that will not survive an actual emergency, regardless of how good the brochure looks.

A note on funding integration

SPLOST referendums in Georgia counties typically run on five-year cycles, and ECS retrofits are commonly bundled into broader school facility modernization line items. Districts planning ECS upgrades benefit from sequencing the design work to land in the SPLOST cycle window, which means starting design eighteen to twenty-four months before construction. JB Technologies has supported district planning teams on that sequencing, providing design-phase deliverables that align with the SPLOST funding referendum and the subsequent construction schedule.

For Georgia K-12 districts evaluating mass notification, ECS retrofits, or combined fire alarm and ECS for new construction, call (770) 637-2094 or email sales@jbtecknologies.com. JB Technologies designs to NFPA 72 (2022 Edition) Chapter 24 and integrates with the IP paging, marquee, and parent-notification platforms most Georgia districts already run.