Massachusetts MA
Massachusetts has detailed MLTS rules for new or substantially renovated systems, including facility categories, ERLs, off-premises users, updates, waivers, and PSAP testing.
What matters before you deploy or audit E911 in Massachusetts
- Massachusetts requires new or substantially renovated MLTS to provide the same level of enhanced 911 service as others in the Commonwealth.
- The statute delegates implementation details and possible exemptions to regulations.
- Substantial renovation, cloud migration, PBX replacement, and campus redesign should all trigger review.
How detailed should the dispatchable location be?
No state square-foot threshold was found in Mass. Gen. Laws ch. 6A, § 18J. Use federal dispatchable-location rules and Massachusetts regulations/exemptions for specific facilities.
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.
Massachusetts MLTS service level
Mass. Gen. Laws ch. 6A, § 18J“same level of enhanced 911 service”
Do not assume a business PBX can provide weaker location/callback behavior than ordinary E911 service.
Massachusetts trigger
Mass. Gen. Laws ch. 6A, § 18J“new or substantially renovated multi-line telephone system”
Treat major UCaaS, PBX, SIP, building, or campus changes as E911 compliance checkpoints.
911 context
Massachusetts is a strong state-profile example because the law and 560 CMR rules distinguish business, government, hotel/motel, school, and shared residential settings. The rules are meant to make a caller's in-building location actionable, not merely route a call somewhere.
911 authority and routing model
MLTS operators should define emergency response locations, support direct inward dialing where required, and account for off-premises users. PSAP testing and waiver processes may be relevant for complex deployments.
Location delivery approach
Location data should include address plus ERL-level information. The PDF summary describes updates within one business day after new or substantially renovated MLTS work, which should be reflected in change-management procedures.
Dispatchable location area / square-footage rule
Massachusetts uses a tighter 22,500 sq ft workspace rule for business/entity and government MLTS. Buildings at or below 22,500 sq ft generally need at least one ANI and ERL identifier per building; buildings over 22,500 sq ft need at least one ANI and one ERL identifier per 22,500 sq ft of workspace. Certain small systems, including business/government workspaces under 7,000 sq ft on one contiguous property, may not need more than one ERL.
State-specific differences
Massachusetts differs from generic federal guidance by being facility-specific. Schools, hotels, shared residential buildings, government buildings, and offices can have different operating expectations and documentation needs.
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.