Washington WA
Washington has MLTS-related statutory language and active E911/GIS considerations; verify state and local program status.
What matters before you deploy or audit E911 in Washington
- Washington’s cited law focuses on enhanced 911 for private shared residential and business services.
- Business service must provide automatic location identification for each emergency response location, subject to exceptions.
- For enterprise sites, apply federal MLTS rules and validate local PSAP expectations.
How detailed should the dispatchable location be?
Washington’s cited business/residential sections should be paired with current state rules and federal dispatchable-location obligations. Use 7,000 sq ft as a practical review trigger unless local counsel confirms a different state-specific threshold.
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.
Washington residential E911
RCW 80.36.555“automatic location identification for each residential unit”
Shared residential environments should not collapse multiple living units into one vague E911 location.
Washington business E911
RCW 80.36.560“automatic location identification for each emergency response location”
Business MLTS planning should identify ERLs that are meaningful to responders and local PSAP workflow.
Contexto 911
Washington includes dense urban campuses, ports, hospitals, rural communities, islands, and remote geography. Emergency calling design should consider both ordinary office calls and disaster/failover operations.
Autoridad 911 y modelo de enrutamiento
State law and local PSAP operations both matter. Businesses should document provider routing, callback, location fields, and internal notifications for every site.
Enfoque de entrega de ubicación
Location delivery must cover fixed phones, softphones, remote users, Wi-Fi/network-based hints, and failover numbers. Multi-building campuses should use emergency response locations that responders recognize.
Área de ubicación despachable / regla de pies cuadrados
Washington follows the NENA model-style 7,000 sq ft exception: workspaces under 7,000 sq ft on a single level and single contiguous property are not required to provide more than one ERL. Larger areas should use additional ERLs, and logical boundaries should not exceed fire alarm zones; fire/smoke/sprinkler zones are good starting points.
State-specific differences
Washington's special issue is operational resilience. Routing and location should be validated under normal service, power/network disruption, and alternate carrier paths where feasible.
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.