Office Move Done? Retest Every UCaaS Emergency Location Before Renewal

The office move is finished. Phones work. Numbers ported. Users can call customers.

That does not prove an emergency call will carry the right location.

A cloud phone system can look healthy while an old address, retired floor, reused subnet, reassigned device, or stale notification contact remains buried in the emergency calling configuration. The normal call test passes because normal calls do not have to prove which building, floor, suite, or security desk owns the event.

Before you renew the UCaaS agreement, test emergency calling as its own workflow. Do not accept a screenshot of one headquarters address as evidence for every site and device.

Start with the locations the business uses now

Pull the current site list from facilities, HR, real estate, network operations, business continuity, and the UCaaS administration portal. Those records often disagree after a move, consolidation, acquisition, hybrid-work change, or temporary office closure.

Create one row for every in-scope operating location:

Field	What to record
Civic address	Street address used for emergency calling
Dispatchable detail	Building, floor, suite, room, wing, or other needed detail
Site status	Active, moving, temporary, closing, acquired, or retired
UCaaS location ID	Platform record tied to the address and place
Network identifiers	Public IP, subnet, switch, switch port, wireless access point, or other platform input
Users and endpoints	People, common-area phones, rooms, soft clients, remote users, and analog devices
PSTN path	Calling plan, operator service, direct routing, carrier, SBC, or emergency routing provider
Notification owner	Security, reception, facilities, IT, or another current responder
Test evidence	Date, endpoint, detected location, callback number, route result, and exception
Decision	Keep, correct, retire, retest, or investigate

Do not begin with the renewal proposal. The proposal tells you what the vendor wants to sell again. The location register tells you what the business needs to protect.

Know what the federal rules are trying to accomplish

This is not legal advice, and your obligations depend on the system, installation date, device type, location, and applicable federal, state, and local requirements. Get counsel or a qualified emergency-services specialist involved when the scope is unclear.

The federal baseline still matters for the buying conversation.

The FCC guidance page, as archived August 4, 2026, says Kari’s Law requires covered multi-line telephone systems to support direct 911 dialing without an added prefix or access code. It also describes a notification requirement for covered systems: the call should trigger notice to a central location on-site or off-site where someone is likely to see or hear it, without delaying the 911 call.

The FCC also explains the dispatchable-location rules adopted under Section 506 of RAY BAUM’S Act. A dispatchable location includes the validated street address plus information such as a suite, apartment, floor, or similar detail needed to identify the caller’s location. The technical treatment differs for fixed, non-fixed, and off-premises devices.

That is why an office move is more than an address edit. You may need to update the location record, network mapping, routing treatment, device assignment, user treatment, and notification path. A correct street address with the wrong floor is not a clean result. Neither is a correct location that alerts a security inbox nobody watches.

Map the full emergency calling workflow

Ask the provider to draw the path from the endpoint to the emergency service, then name who owns each step.

For a fixed desk phone, the system may use a statically assigned address or a location associated with the device or network. A soft client moving among offices may depend on network discovery. A remote user may need location sharing, an entered address, or another supported treatment. Direct routing may introduce an SBC and a separate emergency routing provider. Other PSTN options may place more of the routing work with the carrier.

Do not let “the platform supports E911” close the discussion. Support is a product statement. You need an environment-specific result.

Your workflow map should answer:

How does this endpoint learn or receive its location?
Which record supplies the street address and in-building detail?
Which network identifier wins when several identifiers match?
Which carrier, SBC, or emergency routing service handles the call?
Which callback number is presented?
Who receives the internal notification, and by which channel?
What happens when the user is remote or the client cannot determine a location?
What evidence can the provider and your team export after a controlled test?

Microsoft’s current Teams documentation is a useful example of why this gets complicated. Teams can associate emergency locations with network identifiers such as wireless access points, switch ports, switches, and subnets. Its documented matching order uses the first match among those inputs. Microsoft also notes that PSTN connectivity choices change how emergency calling is configured, and some network-setting changes can take up to four hours to reach clients.

That is one platform’s design, not a universal rule. The lesson is broader: your UCaaS provider, network, carrier path, and endpoint behavior have to agree.

Audit every change that can break the location

An office move is the obvious trigger, but it is not the only one.

Retest after changes to:

Street addresses, suite numbers, floors, rooms, or building names
Public IP addresses, subnets, VLANs, switches, switch ports, or Wi-Fi access points
Internet carriers, PSTN providers, SBCs, or emergency routing providers
Calling plans, direct-routing policies, emergency policies, or security notifications
Desk phones, common-area devices, room systems, soft clients, or analog adapters
User assignments, remote-work status, hot desks, or shared spaces
Acquired, closed, temporary, or consolidated sites
Reception, security, facilities, help desk, and escalation contacts

Watch for reused infrastructure. A subnet copied from a former site, a phone moved without its record, or a wireless access point installed under an old name can create a location mismatch that looks normal in an inventory export.

Pair the location work with the shared-phone license audit. A warehouse phone, lobby phone, conference room, and receptionist position may use different licenses and workflows, but each still needs the right emergency calling treatment for its role.

Test without creating a public-safety problem

Do not place an uncoordinated 911 call just to see what happens.

Use the provider’s documented test service and process. Microsoft, for example, documents 933 as a test number for eligible Calling Plan, Operator Connect, and Teams Phone Mobile users in the United States and Canada. The test service can read back the calling line ID, emergency address or location, and routing treatment. Microsoft tells Direct Routing customers in the United States to coordinate testing with their emergency routing service provider.

For any platform, confirm the current test method with the provider before dialing. If a live 911 test is required, coordinate it with the appropriate provider and public-safety authority and follow their instructions.

Build a sample that covers the risk, not the easiest phone to reach:

One fixed desk phone at each changed site
One device on each material network path or location-detection method
One common-area or shared phone
One room or conference device if it can place external calls
One soft client inside the office
One supported remote-user scenario
One Direct Routing or carrier path where the architecture differs
One notification path for every responsible team or location

Record the endpoint, client, user, device identity, network connection, detected address, in-building detail, callback number, routing response, notification recipient, timestamps, and result. Save screenshots or exports where appropriate, but do not expose sensitive call or location data more broadly than necessary.

A test passes only when the expected location, route, callback information, and notification behavior all match the approved design. “The call connected” is incomplete evidence.

Make the renewal decision from the exception list

Give every site and endpoint population one status:

Verified: The current configuration and controlled test match the approved location and workflow.
Corrected: A stale or wrong record was fixed and retested.
Retired: The old site, address, network identifier, device, or notification route is removed under a documented change.
Limited: The platform or client has a documented restriction that the business has accepted with a defined treatment.
Open: The owner, configuration, carrier path, address, or test result is unresolved.

Then ask the incumbent and any competing provider to respond to the same requirements. Require written answers for configuration ownership, location-management tools, supported endpoint types, remote-user treatment, test services, carrier dependencies, support escalation, reporting, implementation work, and contract responsibility.

Renew as proposed only when the current platform still fits and the emergency calling workflow has current evidence across the in-scope environment.

Renew with corrections when the platform works but addresses, network mappings, policies, notification contacts, devices, service scope, or documentation need to change.

Use a short bridge when material locations remain untested and a longer term would reduce leverage before the work is complete. Put the remediation owner, test date, provider obligation, and exit right in writing.

Compare alternatives when the provider cannot explain the routing model, support the required location methods, produce useful test evidence, or assign responsibility across the platform and PSTN path.

Use the UCaaS migration checklist if the review exposes broader cutover, network, number, device, or adoption risk. Work backward from the notice deadline with the IT contract renewal calendar so testing happens while you still have options.

The buying standard is simple: every in-scope location needs a current record, an accountable owner, a supported routing path, a working notification, and dated test evidence.

If your UCaaS agreement is approaching renewal after an office move, site consolidation, network change, or remote-work shift, request a Contract and Spend Risk Review. Bring the agreement, proposal, site list, emergency location export, network map, device inventory, PSTN design, notification list, and test records. Catch Advisors will help you identify what to correct, retest, require in writing, or compare before you sign.