pstn switch off 2027 checklist leeds businesses — 6 checks

Stick to a simple outcome: move voice off analogue to SIP/VoIP, validate emergency services mapping and replace any analogue-dependent kit before Ofcom’s 2027 PSTN switch-off. Start with a site inventory and a pilot cutover — allow 4–8 weeks for complex multi-site estates such as hospitals or legal offices. (More here: our it support leeds guide.)

Check 1 — How quickly can you cut over?

Speed matters because a phased migration reduces business risk, but rushing causes missed devices and broken services. Ask suppliers how many concurrent cutovers they can reliably handle and whether they use staged testing (SIP trunk to PBX, handset provisioning, then service verification). In our experience that sequence prevents surprises during busy switch windows — it’s what separates a clean migration from one that requires expensive rollback work.

Operational target: a single-site office with standard handsets and no bespoke alarms should be able to cut over in a day; multi-site organisations, offices with digital reception systems, or sites in the LS1–LS11 legal/finance/digital triangle commonly need a multi-week schedule. Where your estate overlaps with the Park Square legal cluster or the Wellington Place / South Bank financial hubs, plan cutovers outside peak client hours to avoid customer-facing disruptions.

Ask for a trial SIP trunk on a non-critical line first.
Require a documented runbook showing the step-by-step cutover and rollback triggers.
Confirm availability windows and on-site technicians for the first 72 hours after cutover.

For logistics-heavy teams that rely on mobile coordination around the M62/M1/A1 freight nexus, verify the provider’s ability to sequence changes across depots and offices without breaking line-of-business integrations.

Check 2 — What happens to alarms, EPOS, fax and life-safety lines?

Analogue devices are the usual hidden failures in migrations. EPOS terminals, existing fax machines, door entry, patient-call systems in clinics, and some fire/medical alarm panels still expect a PSTN line. If you don’t find and remediate these before 2027 you risk compliance breaches and operational downtime.

Inventory first. Use port-level discovery and a physical walkthrough of sites in complex estates like Leeds General Infirmary or St James’s Hospital where life-safety systems are in scope. Where wiring runs or equipment are old, you’ll often need either an adapter (analogue-to-SIP gateway) or a device replacement. Both options have trade-offs:

Analogue gateways preserve equipment but add a single point of failure and sometimes require battery-backed power.
Device replacement (e.g. replacing a fax with secure email-to-fax or a cloud fax service) improves long-term resilience but needs configuration and staff retraining.

Practical test: schedule a failover test for each critical device type in a non-business hour and document the observed behaviour. Where services sit inside the University of Leeds Innovation District or Nexus-managed labs, coordinate with estates teams to avoid test clashes with research equipment.

Check 3 — What are the commercial terms, SLAs and audit evidence?

Commercial detail matters more than headline price when a migration risks regulatory audits or client contract clauses. Get written answers to: restoration SLA for voice and data, response times for on-site engineers, charges for number porting, and penalties for missed cutover windows. Demand a clear statement on how your numbers and caller ID will be preserved and on whom bears the cost if a number transfer fails.

We support businesses across Harrogate (HG1-HG5) from our Leeds base — the 30-minute proximity means on-site visits are same-day when required, with no travel-time premium on our SLAs. That local capability matters when your provider must be on-site quickly to meet an SLA or to carry out an emergency rollback.

Ask for audit-ready documentation. For regulated sectors — legal firms clustered around Park Square or finance teams in Wellington Place — you’ll need a migration log that records testing, IP addresses assigned, incident tickets, and confirmation that emergency-calling information (Caller Location) was signed off. If your contracts require evidence of continuity, add a clause that requires the supplier to produce that migration log within 48 hours of request.

Insist on a restoration SLA expressed in minutes/hours, not vague terms.
Confirm who is responsible for number portability costs and timeline.
Request a sample migration log before you sign any long-term contract.

Check 4 — How resilient and compliant must your replacement be?

Replacing PSTN with SIP/VoIP changes failure modes. IP voice is resilient when designed well — redundant SIP carriers, multiple outbound routes, and power/backhaul diversity are key. Avoid single-provider single-path designs for sites that must be always-on: think hospitals near St James’s (Jimmy’s), law firms handling urgent client calls, or Channel 4’s HQ-linked teams on the South Bank who need media-grade uptime.

Design checklist: ensure at least two independent SIP providers or two distinct network paths, battery or UPS protection for any gateway or on-prem device, and a tested fallback to mobile or hosted SBC (session border controller) services. For remote locations or sites near Leeds Bradford Airport where travel disruption affects on-site teams, confirm remote provisioning capabilities so changes can be applied from a central operations room without waiting for a flight-based site visit.

Regulatory compliance: emergency calling (caller location) rules change with IP. Link your readiness questions to the NCSC or Ofcom guidance where appropriate; for high-assurance services consider an external audit of the configuration. If you choose hosted telephony, confirm encryption in transit and at rest if your calls carry sensitive client information.

Check 5 — Who owns the inventory and ongoing monitoring?

Migrations fail when nobody owns the inventory. Make one team responsible for the equipment list, wiring diagrams, handset models, and device owners. That single source of truth should feed into monitoring that alerts on SIP trunk failures, call quality degradation, and device offline alarms.

Operationally, decide whether your IT team, an external provider, or a hybrid model manages monitoring. In the manufacturing belt up the Aire Valley toward Bradford, sites often rely on local IT teams who combine remote monitoring with occasional site visits; document escalation paths and response windows, particularly for VoIP call-quality issues that impact operations (order taking, telematics, automated dispatch).

Keep the inventory live — update it within 48 hours of any hardware change.
Set QoS and monitoring thresholds, and agree on alert-to-response timelines.
Run quarterly simulated failovers and keep the results in your audit folder.

Check 6 — How will you compare suppliers on these criteria?

When comparing bids, score each supplier against the same four decision criteria above: cutover speed, device remediation, commercial terms & audit evidence, and resilience/compliance. Use a weighted checklist — for example, give higher weight to resilience if you serve healthcare or finance clients. Ask for references from organisations in Leeds with similar estates (multi-site legal practices, university research labs, or hospitality groups on the South Bank) and insist on seeing a migration runbook for at least one completed local project.

Request fixed-price pilots rather than open-ended time-and-materials work. That forces suppliers to show they can scope accurately and manage risk. Include a short acceptance window where your team signs off the migration log and a separate warranty period during which any migration-related faults are rectified at no charge.

Finally, check local capability. Pick a supplier that can deliver same-day on-site response without travel premiums — that local presence is invaluable across Harrogate (HG1-HG5) and central Leeds. If you want an independent technical review, arrange a 90-minute audit that maps critical lines and produces a remediation plan you can take to three suppliers for fixed bids.

How to apply these checks when choosing an option

Make a short RFP that forces bidders to answer the six checks above in plain language, with attachments: runbook sample, SLA wording, migration log example, and two local references. Score each answer, visit a completed migration site in Leeds where possible, and weight resilience and device remediation higher for regulated or safety-critical operations.

Your immediate next step is a 30–60 minute scoping call to confirm the inventory and any obvious analogue dependencies. That gives you a firm fixed-price pilot and a timeline that preserves numbers and client trust. A clear pilot delivered quickly buys you time and reduces overall cost compared with an open, reactive migration.

Contact a supplier that can prove local responsiveness, documented SLAs and tested failover paths — you’ll save time, protect revenue and keep client confidence intact.