Lone Worker Safety Centre

Manager Implementation Toolkit

A lone worker system becomes effective when managers configure it, explain it, test it and review it. This toolkit sets out the practical stages between procurement and working control.

Training courses Discuss your training needs

Practical recommendationNo obligationUK-wide delivery

Training courses Discuss your training needs

Practical recommendationNo obligationUK-wide delivery

Implementation sequence

Build the control before relying on the device

The stages are ordered deliberately: define the risk first, then decide who responds, configure the service, train users and review the evidence once the system is live.

01Implementation focus

Define the risk

Identify who works alone, where they work, what foreseeable harm exists and where current controls are weak.

Manager check: Map roles, locations, visit types, out-of-hours work, signal gaps and current reporting arrangements.

Evidence: Risk profile, existing controls, worker groups and priority gaps are recorded before any supplier decision.

Decide who responds

Choose external, internal or hybrid monitoring based on realistic responder availability and urgency.

Manager check: Confirm who receives each alert first, what happens if they do not answer and how out-of-hours escalation works.

Evidence: Monitoring responsibilities, escalation steps and responder availability are documented and understood.

Set the service up

Set user profiles, contacts, locations, task notes, escalation rules, test routes and management access.

Manager check: Build the system around real teams, live contact details, task notes, test arrangements and management permissions.

Evidence: User records, escalation contacts, test routes and manager access have been checked before launch.

Train staff and managers

Practise preparation, check-ins, concern-stage support, emergency activation, cancellation and post-incident reporting.

Manager check: Practise device checks, timed sessions, discreet activation, cancellation, false alarms and responder actions.

Evidence: Staff can explain when to use the system and managers can explain what happens after an alert.

Review evidence

Monitor false activations, missed check-ins, test calls, incident records, staff confidence and supplier performance.

Manager check: Review missed check-ins, incident reports, test history, false activations, training gaps and supplier performance.

Evidence: Findings lead to updated profiles, escalation instructions, refresher training or supplier challenge where needed.

Open related guidance

Manager duties

Implementation is not complete when devices are issued

Managers should be able to evidence that staff know what to carry, how to test it, when to use concern-stage support, how to activate an alarm and what happens afterwards.

Record team-specific lone worker arrangements.
Keep contact details and escalation instructions current.
Review failed tests and false activations constructively.
Refresh training after incidents, role changes and system changes.

Ownership and review

Set a routine that keeps it up to date

Before launch: Approve the risk profile, response model, privacy position, worker consultation, configuration, fallback arrangements, competence assessment and go-live evidence. Record any unresolved limitation and the person authorised to accept or correct it.
Weekly during early adoption: Review faults, unanswered contacts, user access, carrying problems, false activations, missed tests and staff questions. Correct profiles and procedures quickly before workarounds become normal practice.
Monthly operational assurance: Compare use, readiness, alarm handling, missed check-ins and incidents by team, shift, role and location. Sample whether escalation contacts remain available and whether completed actions have evidence.
Event-driven review: Review after a serious incident, failed response, material near miss, role or location change, supplier change, system update, significant staff concern or relevant legal and official-guidance change.
Scheduled strategic review: At least annually, reconsider whether lone work remains necessary, whether prevention controls can be strengthened and whether the technology, monitoring, contract, training and governance remain suitable.

Minimum management record

Evidence the decision, not paperwork volume

Keep records that allow another competent manager to understand the arrangement and act when the usual owner is absent.

Scope

People and work

Roles, tasks, locations, risk groups, work periods, exclusions and the reasons different controls apply.

Response

Contacts and decisions

Alert routes, escalation thresholds, responder availability, fallback arrangements and authority to stop or change work.

Assurance

Tests and improvements

Training evidence, system tests, incidents, faults, staff consultation, actions, owners, due dates and completion evidence.

Evidence and limits

The toolkit supports management judgement

It does not determine whether a particular arrangement satisfies legal duties or whether work should be performed alone. Use competent health and safety, HR, safeguarding, procurement, data-protection or legal advice where those decisions are material.

Related resources

Lone Worker Safety CentreReturn to the centre for the wider lone worker control framework.Staff device readiness guidanceCheck staff readiness before relying on device or app controls.Incident evidence and reporting guideUse incident records and near misses to improve the system.Lone Worker SafetySupport managers and staff with practical implementation training.