California CA
California 911 modernization is active; enterprise details should be verified by county, Cal OES program information, and provider route.
What matters before you deploy or audit E911 in California
- California’s AB 911 history is important for MLTS operators even where current compliance is driven by federal rules.
- The operational idea is precise location, one-business-day updates after changes, and annual accuracy review.
- California sites should be designed by facility type: high-rise, campus, warehouse, hotel, hospital, school, or temporary structure.
How detailed should the dispatchable location be?
California AB 911 used a 7,000 sq ft one-ERL concept. For enterprise planning, treat larger or more complex California facilities as needing multiple dispatchable locations even when federal rules are the direct baseline.
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.
California MLTS update concept
California AB 911, proposed Pub. Util. Code § 2883(e)“within one business day of the record of completion”
Use one-business-day update timing as a practical control after phone moves, remodels, floor changes, or provider updates.
California small-building exception concept
California AB 911, proposed Pub. Util. Code § 2883(j)“7,000 square feet or less”
Small sites may need only one emergency response location, but large or multi-building sites should use finer ERLs.
911 context
California 911 routing is shaped by state coordination, local PSAP operations, wireless routing, seismic and wildfire continuity planning, and a large enterprise/cloud-calling footprint.
911 authority and routing model
State-level coordination works with local jurisdictions and service providers. Enterprises should validate site records, security-desk notifications, emergency call routing, and remote-user workflows county by county.
Location delivery approach
Wireless calls rely on carrier and handset-derived location. Enterprise VoIP calls depend on validated dispatchable location and provider routing records; softphones and remote users need active location update procedures.
Dispatchable location area / square-footage rule
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
California's special issue is operational diversity: a downtown high-rise, film lot, school district, hospital, warehouse, and wildfire-prone rural site need different response-location detail and continuity assumptions.
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.