Property-by-property remediation never converges.

Each property makes a reasonable decision. The portfolio ends up with no answer to the only question that gets asked at corporate level.

Why it does not converge

Every property in a portfolio runs a multi-line telephone system, so every property carries the obligation. Handled locally, each site assesses its own position, selects its own approach and schedules its own remediation.

The result is a set of individually defensible decisions that do not add up to a portfolio position. Sites drift at different rates, general managers rotate, and the estate is never in a single known state at a single point in time — which is exactly what a corporate-level question requires.

The exposure, meanwhile, is not local. A failure at one property becomes a group-level federal, civil and reputational event, because the obligation attaches to the organization operating the systems rather than to the building where the call was placed.

What property-level handling produces

Remediation costs more in aggregate, because each property procures and configures independently rather than against one standard.
No portfolio-wide answer exists at any moment, so the question from an insurer or a franchise agreement cannot be answered directly.
Mixed estates compound the problem — Cisco at some sites, Avaya at others, Teams at the newest — with each platform handling location differently.
Ageing systems raise compliance risk and support risk simultaneously, and the two get budgeted separately.
Where properties are franchised, nobody has established where the obligation actually sits for each one.

What corporate-level scoping looks like

The shape that works inverts the sequence. One assessment covers the full portfolio and produces per-property findings, and deployment is then phased by site against a single standard rather than negotiated site by site.

The important detail is what gets standardized. It is the compliance outcome, not the phone system — a mixed Cisco, Avaya and Teams estate does not need to be unified to reach one compliance position, and attempting that turns a compliance programme into a platform migration.

One assessment across the portfolio, with findings recorded per property
A single corporate contract, with deployment phased by site on a priority order
Priority usually set by property size and system age, so the largest exposure closes first
Location database build and PSAP connectivity testing with acceptance sign-off per site
Annual testing and change-control governance covering the whole estate, not each building separately
One technical contact accountable for the estate rather than a relationship per property

Questions that scope a portfolio properly

These four establish whether the problem is compliance, inventory or ownership — three different engagements that look identical from a corporate office.

Does anyone hold a current inventory of which system is deployed at which property?
Which properties have changed phone systems in the last five years, and did anyone re-verify location data afterwards?
Which properties are franchised, and where does the obligation actually sit for each?
When a guest dials 911 from a room, who at the property is notified — and has that been tested this year?

If the first question has no answer, the assessment is partly an inventory exercise and should be scoped as one. That is a common and unembarrassing starting position; discovering it midway through a deployment is the expensive version.

Where to go next.

Who We Serve

Get one answer for the whole portfolio.

The free multi-site assessment reviews every property under both statutes and produces per-property findings. There is no scoped project attached.

Claim your free multi-site assessment →Email us