Implementation Guidance

How to encourage staff to use lone worker safety devices

Issuing a device or discreet panic alarm is not enough. Staff need confidence, permission and practice so they can activate support early, especially when pressure, embarrassment or the freeze, flight or fight response may affect decision-making. The strongest systems treat technology, training and management follow-up as one safety arrangement.

Reception staff member preparing to use a discreet alarm during a difficult public-facing interaction

Why devices go unused

Most adoption problems are behavioural, not technical

Staff may understand the technology but still hesitate to use it in a real situation. That hesitation should be treated as a training and culture issue, not a staff failure.

The device is not carried

Devices get left in drawers, vehicles or lockers when staff do not see them as part of the job. Carrying the device has to become as routine as carrying keys, ID or a work phone.

The device is not ready

Flat batteries, missed software updates, forgotten passwords and apps that have not been opened all turn a purchased control into a weak control.

The activation method is uncertain

Staff may know they have a device but still hesitate because they have not physically practised the button press, app sequence, code word or escalation process.

False activations feel embarrassing

If false alarms are treated as failure, staff learn to delay. They need permission to activate early and confidence that a cautious alert will be reviewed constructively.

Features are poorly understood

Check-in, GPS, discreet alarm, fall detection, satellite connectivity and Stay With Me functions only help when staff know what each feature is for and when to use it.

Managers do not close the loop

Usage data, missed tests, false activations and genuine alerts need review. Without visible management follow-up, the system loses credibility.

Muscle memory

Practise the moment of activation

In a freeze, flight or fight situation, staff may not follow a written procedure unless they have practised it. Features that guide or reassure the user can help, but the organisation still needs regular realistic practice.

Practise where the device, button or app is located.
Practise when to activate and what to say afterwards.
Practise how colleagues acknowledge and respond to an alert.
Practise staying engaged with support rather than freezing.

Daily competence

Build device use into the working routine

A lone worker device should not be something staff remember only after a difficult incident. Competence is built through small, repeated checks before lone visits, field work, evening appointments or public-facing tasks.

Carry the device or work phone before leaving base.

Check battery level, signal and app access before the visit or shift.

Confirm the correct user profile, escalation contacts and location settings.

Test the agreed practice mode or check-in process at the required interval.

Know the difference between check-in, Stay With Me support and emergency activation.

Report faults, missed tests, forgotten passwords or configuration issues immediately.

Lone worker holding a phone while feeling unsafe during an evening street visit

Stay with me support

Use a virtual buddy when staff feel unsafe but are not ready to raise an emergency alarm

Some lone worker systems include a monitored call, check-in or “Stay With Me” style feature. This gives staff a live support presence while they leave an area, approach a visit or wait for the situation to settle.

Training should make clear when to use this option, what the monitoring centre or colleague will do, and when the worker should move from supported check-in to a full alert.

Dynamic risk assessment

Teach staff to act before the situation deteriorates

Device training should sit alongside practical decision-making: early intervention, de-escalation, safe withdrawal, incident recording and learning from what happened. The aim is not simply to press a button, but to recognise when support should be brought in before the risk escalates.

What has changed since the visit, task or journey was planned?
Is the worker still in control of time, distance, exit route and communication?
Would an early check-in, Stay With Me call or colleague update reduce the risk now?
Is it safer to withdraw, delay the task or request support before contact continues?
If an alert is raised, does the worker know what to say and what happens next?

Departmental indicators

Measure confidence and readiness, not blame

Performance indicators should help managers spot where the safety system needs support. They should not discourage staff from using the device or reporting concerns. Repeated refusal to carry, check or use a required device may become a performance or disciplinary matter, but only after clear instruction, support and reasonable management steps.

Percentage of staff inducted on device or alert use.

Percentage of staff completing monthly practice activation.

Number of test activations completed by department.

False alarms reviewed constructively.

Missed check-ins or missed tests reviewed.

Staff confidence score before and after training.

Internal response time to alerts.

Percentage of incidents where escalation procedure was followed.

Device availability, charge and readiness checks.

Repeated non-use managed through supervision, performance review or disciplinary action where appropriate.

Management responsibility

Keep the safety system active after the device is issued

UK employers need suitable arrangements for managing foreseeable lone working risk. In practice, that means checking whether the control is working, whether staff are competent to use it and whether incidents are driving improvement.

Make device use part of the lone working risk assessment and safe system of work.
Audit whether staff carry, charge, test and understand the device in normal conditions.
Review genuine alerts, false activations and missed check-ins without blame.
Keep escalation contacts, user profiles, monitoring instructions and configurations current.
Schedule refresher practice so competence does not fade after initial issue.
Use incident learning to improve procedures, training and supplier configuration.
Treat device readiness as a performance indicator because it forms part of the safe system of work.
Escalate deliberate or repeated non-compliance only after instruction, support and reasonable management steps.

Team champion

Use a champion to keep the system alive

A lone worker safety champion or device champion can help bridge the gap between policy and everyday behaviour. The role should be practical, supportive and clearly linked to managers. The champion supports adoption, but managers remain accountable for supervision, performance indicators and formal action where repeated non-compliance creates risk.

Support new staff with device confidence.

Normalise routine testing and practice activation.

Spot barriers that stop staff using the system.

Feed practical concerns back to managers.

Help review false alarms without blame.

Reinforce escalation procedures in team briefings.

Act as the first local contact when colleagues are unsure how to use a feature.

Encourage staff to raise faults, configuration issues and confidence gaps early.

Supplier-neutral implementation

Compare features by how staff will use them under pressure

Common UK systems may include smartphone apps, dedicated devices, discreet buttons, check-in functions, GPS, monitoring centre support, satellite options and fall detection. Supplier choice matters, but staff adoption depends on whether those features are understood, configured and practised.

Ask how staff practise activation without creating live alarms.
Check whether Stay With Me, check-in and emergency alert routes are clearly different.
Review what reports managers receive on use, testing and missed check-ins.
Confirm how supplier configuration will match your escalation procedure.

Where this connects to supplier choice

When comparing suppliers, ask what reporting, training support, practice mode, alert acknowledgement and management data are available. These features matter because adoption is not only a hardware issue.

View supplier index