Utah passed its version of Alyssa’s Law in 2024 through House Bill 84, and it wrote the requirement more broadly than almost any other state: Utah public and charter schools must have emergency communication systems. Not just a button. A communication system, codified in Utah Code around Section 53G-8-805. That wording choice matters, because it means Utah compliance is not a single-device purchase; it is a question of whether your campus can detect an emergency, alert the right people, and coordinate a response, all in seconds. This guide covers what HB 84 requires, why the communication-system framing changes the buying decision, and how Utah districts build compliance on hardware many of them already own.
What HB 84 Requires
HB 84, passed in the 2024 session, requires Utah public and charter schools to have emergency communication systems as part of the state’s school safety framework. The law arrived in a package of Utah school safety legislation that also tightened requirements around armed security presence and safety planning, and it applies to charter schools alongside traditional districts, a coverage detail some states skipped. The bill record and code language are on the Utah Legislature’s site.
The named inspiration is the same as everywhere else: Alyssa Alhadeff, killed at Marjory Stoneman Douglas High School in 2018, whose family has carried this legislation state by state. Utah became one of the mandate states, the group that requires capability rather than merely asking schools to consider it.
Why “Emergency Communication Systems” Is a Bigger Requirement Than a Panic Button
Most Alyssa’s Law states wrote their statutes around the alert: a silent signal that reaches law enforcement. Utah’s language reaches further. A communication system implies the full chain: the trigger that starts it, the notification that reaches responders, and the communication that reaches the people inside the building while the emergency is unfolding. A button that only dials out satisfies the first two links and leaves the third, the one that actually moves students behind locked doors, to improvisation.
That is worth sitting with, because it changes what a compliant purchase looks like. The strongest reading of Utah’s requirement is a campus where one activation does three jobs at once: alerts dispatch, notifies staff, and drives the response through the systems every school already uses all day, bells, PA, and displays. That is the difference between owning a panic button and owning a school lockdown system, and Utah’s statute language leans toward the second.
Building Compliance on Hardware Utah Schools Already Own
Here is the practical good news: most Utah campuses already own most of a compliant communication system. The PA that reads morning announcements, the bells that move a thousand students on schedule, the displays in the gym and cafeteria: that is emergency communication infrastructure running non-emergency traffic. Compliance work is largely connecting a silent trigger to it. Fixed panic buttons for schools provide that trigger at the room level, mounted stations that need no charging, no pairing, and no staff member’s personal phone to be on and in signal at the worst moment. Wired into wireless PA and paging systems and existing bells, a single press becomes a campus-wide, pre-programmed response, which is the communication system Utah’s statute describes rather than the bare alert some vendors sell against it.
Districts weighing device classes for the trigger layer should read the fixed vs. wearable panic buttons comparison. The short version for a statute like Utah’s: wearables serve the staff member, fixed stations serve the room, and a communication-system requirement is fundamentally about the building.
Geography sharpens the argument. Utah districts range from dense Wasatch Front campuses minutes from responders to rural schools where arrival is measured in tens of minutes, and the communication-system framing serves the rural case most: when help is far away, the system’s job during the gap, ordering the building into lockdown, moving students behind doors, telling staff what is happening, is the part that protects people. A requirement written around communication rather than a single dial-out is Utah’s legislature acknowledging that the first responder on scene is, for several minutes, the school itself.
Deadlines, Documentation, and the Charter School Question
Utah’s requirement is in force, which means the question for a district or charter board is not when the state expects action but whether your buildings would pass an audit today. The documentation habit that serves mandate-state schools everywhere applies here: record what systems exist per building, how activation works, who responds, and when it was last drilled. Charter schools should note they are inside the requirement, not adjacent to it; smaller campuses and single-building charters are exactly where a wireless installation makes compliance a season project instead of a construction project.
The walkthrough that settles the question takes an afternoon per building and asks five things. Where would an emergency be detected first, and is there a silent trigger within reach of that spot? Does activation reach dispatch without a phone in the loop? Does the same activation tell the people inside the building anything? Which of the systems already installed, PA, bells, displays, can carry that message today? And who owns the drill calendar that proves all of it works under stress? A board that can answer all five in writing is compliant in substance; a board that cannot has its project plan written for it in the gaps.
Paying for It in Utah
The federal funding path runs through the COPS School Violence Prevention Program, whose purpose areas include technology for expedited notification of law enforcement during an emergency, with awards up to $500,000, a microgrant tier up to $100,000 with the local match waived for smaller and rural districts, and FY26 applications due August 11, 2026. Utah’s rural district profile fits the microgrant tier well. State safety funding cycles and local capital budgets stack on top, and an owned system with no recurring subscription fees fits every one of those funding shapes better than a permanent annual platform fee does. The full map, with deadlines, is in Alyssa’s Law funding and grants.
Where Utah Sits on the National Map
Thirteen states now carry Alyssa’s Law style legislation: mandates like Utah, Texas, Oklahoma, and New Jersey; consider states that require the question to be weighed in safety planning; and authorize states that empower boards without compelling them. Utah’s communication-systems framing is arguably the most complete of the mandates, because it legislates the whole response chain rather than one device on the wall. The full landscape is in the state-by-state breakdown, and if your board wants to know what closing the gap would cost for your specific buildings, get a quote for your campus with the building count in hand.
Frequently Asked Questions
What does Alyssa’s Law require in Utah?
HB 84, passed in 2024, requires Utah public and charter schools to have emergency communication systems. The framing is broader than a panic button alone: it points to the full chain of alerting responders and communicating with the building during an emergency.
Does Utah’s law apply to charter schools?
Yes. HB 84’s requirement covers public and charter schools alike, which makes it one of the more complete coverage frameworks among the Alyssa’s Law states.
Can existing PA and bell systems count toward Utah compliance?
They are the backbone of it. A compliant emergency communication system connects a silent trigger to the notification and communication infrastructure a campus already runs daily, which is why most Utah schools are closer to compliance than a vendor pitch suggests.
