Learning outcomes
What this guide will help you do
- Match the device and response model to foreseeable work risks rather than buying from a feature list.
- Test usability, connectivity, privacy and escalation arrangements before roll-out.
- Build staff and manager competence through practical activation and response exercises.
- Use adoption, alert and incident evidence to review whether the control works in practice.
Start with the risk, not the product
A device cannot remove the hazards created by an isolated location, violent behaviour, unsafe travel, a medical event or a poorly planned task. Begin by identifying who works alone, the work they do, the harm that is reasonably foreseeable, existing controls and the point at which communication or assistance may fail.
Define the required outcome before comparing products. The need may be a discreet duress alarm, timed welfare check, fall alert, two-way audio, location support or a lower-threshold monitored call. Different roles may need different controls, even within the same organisation.
- Map tasks, places, times, people and known incident patterns.
- Identify when a worker can speak, reach a phone or activate discreetly.
- Decide who must respond, how quickly and with what information.
- Retain non-technical controls such as paired work, changed appointments or withdrawal where technology cannot reduce the risk sufficiently.
Choose a usable device and response model
Dedicated devices can offer a simple physical button and consistent carrying position. Managed smartphone applications can support timers, check-ins and location functions where phones are routinely carried and maintained. Satellite-capable services may be relevant in remote areas, but capability, coverage and response arrangements still require field testing.
The response model matters as much as the handset or app. Alerts may go to an Alarm Receiving Centre, an internal manager or a hybrid arrangement. Employers must confirm who acts first, what happens if a responder does not answer, how out-of-hours cover works and what information can be provided to emergency services.
Test the service in real working conditions
Coverage maps and supplier statements are useful starting points, not proof that a service works inside a particular building, basement, rural estate, vehicle or plant area. Test the approved carrying position, activation method, audio, location quality, cancellation route and responder instructions in representative locations and shifts.
Record expected limitations and the fallback action. If the worker enters a known no-signal area, the control may need a pre-entry check, timed escalation, satellite device, paired working or a decision not to proceed. Staff should never be encouraged to assume that GPS or network roaming guarantees precise location or continuous connection.
- Test indoors, outdoors, in vehicles and at known coverage boundaries.
- Include silent activation and inability-to-speak scenarios.
- Confirm how stale, delayed or uncertain location data is displayed.
- Retest after software, network, building, role or supplier changes.
Design the daily safe system
The worker needs a routine for carrying, charging, testing and using the device before they become isolated. User profiles, task notes, escalation contacts and temporary changes must remain current. Managers need a fault route that can authorise alternative controls rather than leaving staff to decide alone whether work continues.
Define thresholds for ordinary check-in, active support and emergency activation. Staff should have permission to act at the concern stage, not only when an incident has already become dangerous. Procedures should explain false activations and cancellation so fear of embarrassment does not delay genuine use.
- Pre-use: identity, battery, signal, profile, carrying position and task notes.
- During work: check-ins, changes in plan, concern-stage support and withdrawal.
- After work: close sessions, report faults, preserve incident information and recharge.
- Manager oversight: missed checks, unavailable responders, non-use patterns and overdue training.
Practise worker and manager competence
A quick demonstration shows where a button is. Competence requires the worker to prepare the service, choose the right activation, use it under pressure, communicate with the responder where safe and complete the post-incident process. Practice should use the actual approved device, app and local escalation route.
Managers and internal responders also need rehearsal. They should be able to interpret an alert, use location and task information, contact the worker safely, follow missed-contact steps, escalate and document decisions. A strong worker activation can still fail if the receiving side is unavailable or uncertain.
Manage privacy, location and recorded evidence
Location history, audio, call recordings, incident notes and user profiles may contain personal information. The employer should define why each type is processed, who can access it, how long it is retained, how workers are informed and what the supplier does on the employer's behalf. Monitoring should be necessary, proportionate and transparent.
Do not promise that audio, transcripts or GPS history will always be available after an incident. Availability and retention vary. Procurement and contract review should identify the evidence required, access method, response time, export format and any additional cost before an incident occurs.
Review whether the control is working
Issue numbers and licence counts do not establish effectiveness. Review carrying and check-in behaviour, test completion, false activations, genuine alerts, missed contacts, responder availability, faults, staff confidence and incident outcomes. Look for differences between teams, roles, shifts and locations.
A rise in early support calls may show improved confidence rather than worsening risk. Conversely, very low use may indicate that the system is inaccessible or distrusted. Combine system data with staff consultation and incident review before reaching conclusions.
- Monthly operational review: faults, contacts, tests, false alerts and profile accuracy.
- Post-incident review: activation, response, location, communication, support and evidence.
- Scheduled system review: suitability, adoption, supplier performance, privacy and training.
- Event-driven review: serious incident, role change, new location, product change or material guidance change.
Use the full implementation guide
This article provides the decision framework. SST's Personal Safety Devices and Lone Worker Technology guide contains detailed device types, response models, contract questions, implementation stages, scenarios, sector guidance and downloadable tools.
Use the wider Lone Worker Safety Centre where the question concerns risk assessment, policy, monitoring, incident reporting or manager governance rather than the technology alone.


