Minnesota MN
Minnesota's 911 statutes are broad and state-administered, with local operational variation and 911 planning considerations.
What matters before you deploy or audit E911 in Minnesota
- Minnesota has one of the clearest MLTS square-foot frameworks.
- Business MLTS calls must result in ALI for each ERL, adequate alternative direction, or connection to a designated on-site individual.
- The state differentiates single-floor, multi-floor, shared residential, hotels/motels, and schools.
How detailed should the dispatchable location be?
Minnesota: one ERL may be enough for a single-floor workspace under 40,000 sq ft, a multi-floor workspace under 7,000 sq ft on one contiguous property, or a single-public-entrance single-floor facility.
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.
Minnesota business MLTS
Minn. Stat. § 403.15, subd. 5(a)“automatic location identification for each respective emergency response location”
Map enterprise phones to ERLs unless an approved alternative response workflow is maintained.
Minnesota square-foot exceptions
Minn. Stat. § 403.15, subd. 5(c)“less than 40,000 square feet, located on a single floor”
Single-floor workspaces under 40,000 sq ft may need only one ERL, but multi-floor sites drop to the 7,000 sq ft threshold.
911 context
Minnesota combines statewide 911 coordination with local public-safety operations. Enterprise readiness depends on how each office, school, clinic, plant, or remote-work population reaches the correct PSAP with the right callback and location data.
911 authority and routing model
The state framework should be paired with provider testing and local PSAP coordination where complex sites are involved. Multi-tenant buildings and shared campuses deserve special attention.
Location delivery approach
Location delivery should distinguish fixed phones, nomadic VoIP, wireless users, and softphones. For cloud voice, do not rely on a default headquarters address for all users.
Dispatchable location area / square-footage rule
Minnesota uses practical single-ERL thresholds. Only one emergency response location is required where an employer workspace is under 40,000 sq ft on a single floor and one contiguous property, under 7,000 sq ft across multiple floors on a single contiguous property, or a single-public-entrance, single-floor facility on one contiguous property. Larger or more complex sites should plan multiple ERLs or an approved alternative method.
State-specific differences
Minnesota's special issue is operational discipline across many site types. The law may establish the 911 framework, but compliance work lives in address validation, moves/adds/changes, provider records, and recurring test governance.
Regulatory references
Privacy and records considerations
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.