Michigan MI
Michigan has detailed MLTS requirements tied to building size, number of devices, floors, buildings, contiguous/separate properties, and implementation timing.
What matters before you deploy or audit E911 in Michigan
- Michigan 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
Michigan's law is especially useful for facilities teams because it thinks in physical plant terms: square footage, floors, buildings, properties, and device counts. That maps well to enterprise E911 design.
Autoridad 911 y modelo de enrutamiento
MLTS operators should classify sites by size and layout before choosing an emergency-location model. A single office suite, a warehouse, a multi-building campus, and a small branch may not need the same level of ERL granularity.
Enfoque de entrega de ubicación
Dispatchable location should be designed around how responders search a facility. Building, floor, suite, wing, room, entrance, and access-control notes may be more useful than a generic billing address.
Área de ubicación despachable / regla de pies cuadrados
Michigan defines 'specific location' as a room, unit, room name, or equivalent unique area that is not more than 7,000 sq ft. Many obligations turn on whether MLTS workspace exceeds 7,000 sq ft, and there are limited exemptions tied to buildings under 20,000 sq ft with fewer than 20 communications devices until new-system triggers apply. For larger or multi-floor/multi-building environments, identify the specific location of each communications device, including floor and unique building identifier where applicable.
State-specific differences
Michigan's special issue is threshold logic. The PDF describes different obligations for larger facilities, multi-floor or multi-building environments, separate properties, and systems with fewer than 20 communications devices.
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.