E911 for Remote Employees: The Address Problem Nobody Plans For

E911 for remote workers dispatches to the street address registered against that extension or number — not to wherever the device happens to be sitting. Signal registers E911 per location and per number against a validated address, and it stays registered until a person changes it. A laptop that moves does not take its 911 record with it.

How does 911 work for a remote employee on a softphone?

The same way it works for a desk phone, which is the problem.

A landline is tied to copper terminating at a known address, so dispatch knows where the call came from by how it arrived. VoIP has no such tie. When someone dials 911, the system transmits the dispatchable location on file — a validated street address, plus floor or suite where applicable — and a dispatcher acts on it.

For a phone bolted to a desk in an office you control, record and reality stay in sync by default. For a remote employee, the record is whatever someone typed when the extension was created, and the reality is wherever that person carried the laptop this morning. Nothing notices the difference: the call completes, the dispatcher gets an address, and everything looks normal until it matters.

Does a VoIP phone update its 911 address automatically?

No. This is the most common misunderstanding about E911, and it is worth stating without hedging.

An E911 address is a record you register, validate, and maintain. It is not derived from an IP address, not inferred from a network, not read from location services, and not updated when a device connects from somewhere new. E911 is never automatic. What is a dispatchable location covers what the record must contain.

Two consequences for your onboarding documentation:

• A remote employee who moves has a wrong E911 record until someone updates it. Nothing about the move triggers a change.
• A remote employee working from a hotel or a client site has a wrong record for the duration. Their extension still points at home.

Who is responsible for a remote worker's E911 address?

You are, as the employer operating the phone system. That responsibility has to land on a named person or it lands on nobody. Split it in two, because neither half works alone:

The employee reports. They are the only party who knows they moved. Make it an explicit item in your remote-work policy, with the same weight as returning a laptop: notify the administrator before working from a new address.

The administrator registers. Someone with portal access enters and validates the address. Signal validates against a real street-address database rather than accepting free text, so a typo is caught at entry instead of at dispatch. E911 locations covers creating locations and assigning extensions; E911 address problems covers a validation failure on an address that plainly exists.

Then verify on a cycle. An annual audit of every remote extension's address is a twenty-minute task that catches unreported moves.

What do Kari's Law and RAY BAUM'S Act require?

Two federal requirements apply to multi-line phone systems, and neither is waived because staff work from home.

Signal dials 911 directly with no prefix and can notify designated people whenever 911 is dialed from your account. Notification workflows covers setting that up.

The notification requirement deserves a second look in a remote context. Its original purpose was to tell the front desk to unlock the door for paramedics, and there is no front desk at an employee's house. The value shifts: it tells a manager that a colleague working alone just called for help. Send it to a person, not a shared mailbox nobody watches. Kari's Law and RAY BAUM'S Act covers the obligations in full.

The travel case

An employee at a conference or a client's office is the hardest version of this: their registered address is not merely stale, it is confidently wrong, and it will be transmitted with authority.

No configuration solves this. A policy does, and it is short:

When you are working somewhere other than your registered address, use your mobile phone for emergency calls. Do not use the softphone.

Say it in onboarding, put it in the remote-work agreement, and repeat it before travel.

For an employee genuinely relocating — a month at a second home — register the new address instead of relying on the policy. Temporary is a category that reliably outlives its own name.

A remote E911 policy that works

Six items. Written once, reviewed yearly.

1. Register a validated address for every remote extension before the person takes their first call.
2. Include unit detail. Apartment, floor, building. "The right building" is not a dispatchable location in a complex.
3. Require employees to report an address change before working from it, as a named clause in the remote-work agreement.
4. Name the administrator who makes the change, and a backup.
5. Route 911 notifications to a person, and tell them what the alert means.
6. Audit annually, reading remote extensions and their addresses against your staff roster.

The audit is the item most likely to be skipped and the one most likely to find something. Address records decay silently: nothing will tell you a record is stale, because from the system's point of view it is a perfectly valid address.

What happens when the address is wrong?

Responders go to the address on file. That is the entire answer, and it is why this article exists.

A misrouted call may also reach the wrong answering point, and inaccurate records are a compliance exposure — but the first-order risk is that someone in trouble at one address gets help sent to another, with the delay measured in the minutes it takes to resolve a confusion nobody knows is happening.

Frequently asked questions

How does 911 work for a remote employee on a softphone? The call carries the dispatchable location registered against that extension or number — a validated street address with unit detail where applicable. It reflects where the record says the phone is, not where the device is. A softphone on a laptop in another state still reports the home address on file.

Does a VoIP phone update its 911 address automatically? No. E911 addresses are registered and maintained manually, per location and per number. Nothing derives them from an IP address, a network, or location services, and connecting from a new place changes nothing. An employee who moves has a wrong record until an administrator updates it.

Who is responsible for a remote worker's E911 address? The employer operating the phone system, split between two named roles: the employee reports an address change before working from the new address, and a named administrator registers and validates it. Add an annual audit against your staff roster, because unreported moves are the normal failure.

What do Kari's Law and RAY BAUM'S Act require for remote workers? Direct 911 dialing with no prefix, notification of a designated person when 911 is dialed, and a dispatchable location precise enough to find the caller. None of it is waived for home offices. In a distributed team the notification changes purpose — it tells a manager that someone working alone called for help.

What happens if a remote employee's 911 address is wrong? Responders are sent to the address on file. The call may also reach the wrong answering point, adding transfers and delay, and inaccurate records are a compliance exposure. The consequence that matters is the first: help arrives somewhere the person is not.

If you have staff working from home and cannot say what address each of their extensions would report, that is the audit to run this week. Tell us how your remote extensions are set up and we will walk the location records with you.