Lone Worker Connectivity FAQ

These are the questions we hear most often about how lone worker connectivity works: where it can fail, what BS 8484 covers, and what the 2G and 3G sunset means for devices already in the field. Each answer is short by design, with a link to the relevant section of our white paper for the longer case. For the underlying argument and evidence, follow the white-paper links.

Companion to: Lone Worker Connectivity in 2026: Specifying the Protection Chain, a CSL Group white paper that sets out the full case for moving from device assurance to protection-chain assurance.

Why does a lone worker device show full signal but no alarm gets through?

The device’s radio attachment to the network is healthy, but the alarm path depends on layers above the radio. The operator core that carries the data (and the voice call layered over it), and the ARC’s ability to receive and act on the alarm, both sit upstream of the radio bars. Any one of them can fail without the device’s modem or signal display knowing. The dashboard “online” status reflects one layer; the protection chain is five layers, and only the full chain decides whether an alarm reaches the ARC.

See The protection chain has five layers, and the dashboard shows one in the white paper.

Is multi-network the same as multi-core?

No. Multi-network means the SIM can attach to more than one operator’s radio access network, which handles radio-side failures such as a local mast going down or coverage degrading across an area. Multi-core means the SIM routes through two independent operator cores, each with multi-network capability, together with autonomous switching if the active core fails. A multi-network SIM with a single core still has a single point of failure at the core layer. The white paper sets out the three architectures side by side: single-network, multi-network single-core, and dual-core.

See Multi-network is not multi-core in the white paper.

If a SIM is multi-network, can it survive an operator-core failure?

Only if it routes through more than one operator core. A multi-network SIM that uses a single operator core has nothing to switch to when the core fails: the radio is healthy, so reselection has no benefit, and the break is upstream of where the device can act. The device waits for the operator to restore the core, and recovery time is whatever the operator’s recovery time turns out to be. A dual-core SIM detects the failure and switches to the second operator core autonomously, in a bounded delay rather than an open-ended wait on operator repair.

See What recovery looks like when a core fails in the white paper.

Do I need dual-core, or is multi-network enough?

It depends on risk tier. Multi-network is the right baseline for many lone worker estates: it handles the most common failure modes (radio and coverage) and is exactly the right answer for many devices. Dual-core earns its place at the higher-risk end, where an operator-core failure would mean alarms unable to reach the ARC for the duration of the operator’s recovery. Many mature estates run multi-network broadly and introduce dual-core where a core failure would carry the most serious consequences, often piloting it on that tier first to build the evidence before any wider decision.

See Specifying with a connectivity partner in the white paper.

Does a multi-network SIM guarantee that voice calls to the ARC will work too?

No, not on its own. On 4G, voice is delivered as VoLTE (Voice over LTE), which depends on IMS support, device configuration, and interoperability between visited and home networks. Successful data roaming doesn’t prove voice roaming works. A device can roam onto a visited network, pass its location data, show green on the dashboard, and still drop the voice call to the ARC. For higher-risk lone worker deployments where voice matters, the provider should evidence and support VoLTE interoperability across every network the SIM is expected to roam onto.

See Voice is a separate failure mode in the white paper.

When does 2G actually switch off in the UK?

EE has announced that 2G switch-off will begin from May 2029, and VodafoneThree has announced that Vodafone UK 2G will be switched off during 2030. In practice, that makes 2G unreliable as a primary safety bearer for lone worker estates beyond this period, especially for services that depend on roaming. The 2033 outer ceiling that Ofcom has confirmed for all UK MNOs would only extend that for a device on a single-operator SIM, which few higher-risk lone worker services would want to take at the cost of multi-network resilience. For roaming-SIM estates, that puts the effective planning horizon at 2029-2030. Roaming SIMs also face an earlier milestone: O2 withdrew 2G/3G inbound roaming access from 1 October 2025.

See The 2G and 3G sunset in the white paper.

My devices run on 2G or 3G. Do I have to migrate now?

No. 3G is already gone (Virgin Media O2’s final shutdowns to the end of February 2026 completed the picture), but the 2G timeline through 2029 and 2030 sets a migration calendar, not an emergency. For service providers with substantial 2G estates, the practical task is a planned, risk-tiered transition aligned with device refresh cycles, starting with the highest-risk deployments and the earliest roaming-SIM milestones, not a wholesale rebuild. The right conversation with a connectivity partner is which devices and sites move first, what device refresh cycles allow, and how to phase the change without disrupting what is working.

See Specifying with a connectivity partner in the white paper.

What is BS 8484, and what does it cover?

BS 8484 is the British Standard for lone worker device services. It sets requirements covering the provider organisation, the device, the alarm receiving centre (which is required to comply with EN 50518), and the police-response process, including the Unique Reference Number that allows the ARC to request police action directly. For higher-risk lone worker deployments, BS 8484 accreditation is the baseline service standard, and any reputable provider will be able to evidence current accreditation.

See The protection chain has five layers in the white paper for how BS 8484 sits alongside the wider connectivity assurance picture.

Does BS 8484 cover the connectivity path?

Not fully. BS 8484 sets requirements covering the provider, device, ARC and police-response processes that an accredited service should already meet. What it does not currently reach is the connectivity path above the radio: which operator cores the SIM routes through, how the device behaves when an operator core fails, and whether VoLTE voice will work across every network the SIM roams onto. Those are the layers that decide whether an alarm reaches the ARC in the first place, and they need to be specified and evidenced separately.

See The protection chain has five layers in the white paper.

Why doesn’t a high battery state-of-health guarantee a full shift?

State-of-health measures the proportion of a battery’s original capacity that remains. It is a useful aging metric, but not on its own a guarantee of operational endurance. Cycle aging, cold weather, livestream load, polling overhead, and continuous GNSS use all consume battery during a real shift. A bodycam reporting a high state-of-health figure can still fail to deliver its required ten-hour shift. The operational test is the runtime remaining at end of shift in real conditions, not the percentage the battery reports on a dashboard.

See Polling cadence is a battery decision in the white paper.

Will satellite replace cellular for lone worker protection?

Not on its own. Direct-to-device satellite has moved from trial toward early commercial service in the UK and US over the last year, and for lone worker protection it is becoming a genuine resilience layer, particularly for workers operating in poor cellular coverage or remote sites. But satellite is a layer to add to a resilient cellular baseline, not a wider-coverage replacement for one. Bandwidth, latency, and indoor reception are still cellular’s strengths, and a serious lone worker service needs both.

See Satellite adds reach, not resilience on its own in the white paper.

CSL helps lone worker service providers specify connectivity across the protection chain, from multi-network IoT SIMs through to rSIM dual-core, and runs the managed service layer above it. Talk to us about your estate, your risk tiers, and the questions you’re trying to answer.

Contact CSL: https://www.csl-group.com/contact-us/

Lone Worker Connectivity FAQ. CSL Group, May 2026. Companion to the white paper Lone Worker Connectivity in 2026: Specifying the Protection Chain.

About CSL: a UK connectivity provider for critical alarm and safety applications, including life-critical connectivity, alarm signalling, lone worker, fire, security, and assisted living.