Utah UT
Utah has statewide public-safety communications governance and local emergency service operations; verify current 911 program and county details.
What matters before you deploy or audit E911 in Utah
- Utah sites should start with the federal MLTS baseline: direct 911 dialing, no delayed emergency call, notification where technically feasible, and dispatchable location.
- The most important enterprise question is whether responders can find the caller inside the actual facility, not whether the billing address is correct.
- For larger offices, campuses, healthcare facilities, schools, hotels, warehouses, and shared buildings, review floor, suite, room, wing, entrance, zone, and callback behavior.
How detailed should the dispatchable location be?
No state-specific square-foot threshold was identified in the currently reviewed sources. Treat 7,000 sq ft as a practical audit trigger and apply federal dispatchable-location rules with local PSAP/provider validation.
Exact law callouts
Short excerpts are included for orientation. Follow the links for the complete statutory or regulatory text.
Direct 911 dialing
47 C.F.R. § 9.16(b)(1)“without dialing any additional digit, code, prefix, or post-fix”
Covered MLTS environments should support plain 911 dialing from every station with dialing capability. Old PBX habits such as 9-911 are a compliance red flag.
On-site or responsible-party notification
47 C.F.R. § 9.16(b)(2)“must not delay the call to 911”
Security desk, reception, facilities, or crisis teams can be notified, but notification cannot hold or reroute the emergency call before it reaches public safety.
Dispatchable location for MLTS
47 C.F.R. § 9.16(b)(3)“conveying the dispatchable location of the caller to the PSAP”
The enterprise has to maintain usable location records, not merely a billing address or main switchboard number.
Contexto 911
Utah's terrain, fast-growing cities, campuses, ski/tourism areas, and rural communities make accurate location and routing important. Enterprise systems need to handle offices, hospitality, public venues, and mobile workforces.
Autoridad 911 y modelo de enrutamiento
The state framework should be paired with local PSAP/ECC knowledge. For complex sites, document who is notified internally when 911 is dialed and what responders will see.
Enfoque de entrega de ubicación
Location data should be maintained across fixed phones, softphones, Wi-Fi/network hints, and mobile users. Change control is the difference between a correct dispatchable location and stale records.
Área de ubicación despachable / regla de pies cuadrados
No square-foot maximum was identified in the reviewed source. Utah-oriented enterprise designs should still define dispatchable locations by floor, room, building, entrance, or operational zone where a street address would leave responders searching.
State-specific differences
Utah's special issue is geography and growth. New offices, redeveloped campuses, and temporary/event spaces should be added to the emergency-location process early, not after phones are installed.
Referencias regulatorias
Privacidad y registros
911 location records, callback numbers, test-call results, and site inventories should be treated as sensitive safety data. Limit access, keep change history, and align retention with state public-records rules, customer contracts, and incident-response needs.