Colorado CO
Colorado has E911/MLTS policy history, while current deployments must be read against the federal MLTS baseline and local 911 authority requirements.
What matters before you deploy or audit E911 in Colorado
- Colorado 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
Colorado's legislative notes focus on the difficulty of delivering precise callback and location from wireless and MLTS calls. That is exactly the modern enterprise problem: users move, buildings are larger, and cloud voice separates phone numbers from physical desks.
Autoridad 911 y modelo de enrutamiento
Local 911 authorities and state policy shape routing. Enterprise teams should map sites to PSAPs, verify civic addresses, and test provider routing after major changes such as new floors, new network subnets, or office moves.
Enfoque de entrega de ubicación
Direct dialing is now the minimum expectation. Dispatchable location is the operational measure: address plus usable detail such as suite, floor, room, wing, or building identifier when needed for responders.
Área de ubicación despachable / regla de pies cuadrados
No state-specific square-foot maximum was identified in the reviewed state-law source. Treat the federal dispatchable-location rule as the floor and use square footage as responder-search risk: review spaces over 7,000 sq ft, multi-floor sites, campuses, hotels, schools, healthcare areas, warehouses, and any large single room or public area. The location sent with a 911 call should be specific enough for responders to find the caller, using room, suite, floor, building, wing, entrance, dock, alarm zone, or similar detail where a street address alone is not enough.
State-specific differences
Colorado's older law addressed instructions where an access digit was required. That is now a legacy risk signal: if any location still depends on an outside-line prefix, the voice environment needs modernization or documented remediation.
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.