The Last Copper Mile: Assuring Telecare Before the Analogue Retirement

The retirement of the UK's analogue telephone network is often described in the language of infrastructure: copper cables, exchange equipment, fibre-to-the-premises. For assistance providers, the more useful language is operational. A telecare pendant is not a telephone. It is an alert device that happens to use a telephone line. When Openreach completes the withdrawal of the Public Switched Telephone Network, scheduled for January 2027, the households that depend on that line will not simply lose a dial tone. They will lose a route to help.

The Assistance Lens on a Telecoms Deadline

Much of the public commentary treats the switch-off as a broadband migration story. That framing understates the risk. A household can have fibre broadband installed and still have a pendant connected to a copper line, or a fall alarm that dials out through an analogue port on a router that has never been tested with the alarm receiving centre. The presence of fibre is not evidence of telecare readiness. Assistance providers should therefore treat the analogue retirement as a service continuity programme, not a telecoms procurement exercise.

Verified Migration, Not Reassuring Paperwork

Assistance providers should insist on verification rather than attestation. A letter from a telecoms provider confirming that a line has been upgraded says nothing about whether a pendant can raise an alarm end-to-end. Verified migration means a tested alarm transmission from the device to the alarm receiving centre, with the receiving centre confirming receipt and the customer record updated. It means recording the device make and model, firmware version, transmission path, battery backup duration and the date of the last successful test. It also means distinguishing between a device that is technically compatible and one that is operationally proven in the home where it will be used.

A Register That Works on the Night Shift

Vulnerable-customer registers are familiar in financial services and utilities, but they are too often treated as a compliance artefact. In telecare, the register is an operational instrument. It should flag households with no broadband, no mobile signal at the property, no nominated contact, cognitive impairment or a history of falls. It should record the agreed fallback route and the maximum tolerable time to response. Most importantly, it should be visible to the night shift, not buried in a spreadsheet owned by a project team. Consent, accuracy and review cadence need to be designed in from the start, with data-sharing arrangements agreed before the register is used across organisational boundaries.

Fallback Protocols for the Silent Line

An analogue line fails in a way that is easy to miss: no dial tone, no alarm, no obvious symptom. Digital systems fail differently, often with a router reboot or a power cut. Fallback protocols must therefore be layered. A dual-path device with a SIM is useful, but only if mobile coverage at the property has been checked. Battery backup is essential, but only if its duration is known. A nominated responder can fill a gap, but only if that person has agreed to the role and knows what to do. The protocol should specify what happens when the primary path is down: who calls the customer, how quickly, and when the case is escalated to adult social care or the housing provider.

The Joint Working Imperative

Telecare is rarely delivered by one organisation. Local authorities commission services, housing associations own sheltered schemes, alarm receiving centres handle calls, and device manufacturers supply the hardware. The switch-off cuts across all of them. A joint working group with a shared risk register is more useful than a series of bilateral assurances. Migration schedules should be shared with alarm receiving centres so that test calls are not lost in a queue. Housing associations should confirm that communal equipment and warden-call systems have been migrated, not just individual dwellings. Data-sharing agreements should be reviewed before the register is shared, not after.

A Readiness Checklist for 2026

Operations and compliance teams should be able to answer the following questions with evidence, not confidence:

• Have all telecare devices, including dispersed alarms and communal systems, been inventoried and risk-tiered?
• Has each device been tested end-to-end to the alarm receiving centre, with the result recorded against the customer account?
• Has the fallback route been confirmed for every priority-one household, including mobile coverage and battery duration?
• Is the vulnerable-customer register current, consented and visible to front-line responders?
• Is there an outage playbook that sets out proactive welfare calls and escalation thresholds?
• Have contractual assurances been obtained from telecoms providers, housing associations and device suppliers?
• Have customers received clear, plain-English communications about what will change and what they need to do?
• Are migration metrics reported to the board alongside customer outcomes, not just project milestones?
• Has a post-migration assurance sample been planned for the first quarter after switch-off?
• Are incident logs reviewed for near misses, not only for completed alarms?

The Clock Is Not the Only Measure

January 2027 is a fixed date, but readiness is not a single event. It is a service design discipline that should outlast the copper retirement. The pendant on the bedside table is a promise that help will arrive. The fibre line is now part of how that promise is kept. For CPP Group and the wider assistance sector, the test is whether migration is treated as an IT project or as a continuity of care problem. The organisations that choose the latter will be better prepared for the next change, whatever form it takes.