Learning outcomes
What this guide will help you do
- Identify whether the written policy reflects how lone working is actually planned, supervised and reviewed.
- Test check-in, withdrawal, reporting and training arrangements against real work.
- Include harassment, third-party behaviour and vulnerable lone working situations in the review.
- Create a prioritised improvement record rather than simply issuing a revised policy date.
Legal anchor: lone working is a management duty, not a document
The Health and Safety at Work etc. Act 1974 places a broad duty on employers to protect employees, so far as is reasonably practicable. The Management of Health and Safety at Work Regulations 1999 require suitable and sufficient risk assessment. HSE guidance on lone working is clear that employers must manage health and safety risks before people work alone. A lone worker policy therefore needs to show how risk is assessed, controlled, supervised, reviewed and evidenced in real work.
Worker Protection Act: why it matters for lone workers
The Worker Protection (Amendment of Equality Act 2010) Act 2023 added a proactive duty to take reasonable steps to prevent sexual harassment at work. EHRC guidance links this to practical risk assessment, action planning, reporting routes, staff communication and regular review. For lone workers, the connection is clear: isolated work, working alone with third parties, customer-facing duties, travel between sites and night work can all increase exposure to harassment. A policy review should therefore check whether harassment by clients, customers, service users or members of the public is assessed, whether staff know how to report it, and whether managers act on patterns before harm becomes normalised.
1. The risk assessment happens after the risk
A visit plan completed safely back at the office is an accurate record of a missed opportunity. The useful decisions happen before the door opens: Is the location known? Has anything changed? Who is expecting the check-in? What would make the worker leave? If the process is too slow or awkward to use at that moment, redesign it. A good dynamic risk assessment helps someone choose to proceed, pause, call for support, change the plan or withdraw while those options still matter.
2. A missed check-in produces no response
The real test of a check-in system is not whether staff remember to call; it is what happens when they do not. A reliable arrangement gives one named person responsibility for noticing missed contact, sets a clear time for action and provides an escalation route they can follow without improvising. Casual calls, rotating buddies and unanswered alerts create the appearance of a control, but none of the protection.
3. The warning signs live in chats and inboxes
A shaken phone call to a manager may provide support, but it does not create an organisational record. Near misses, verbal abuse, harassment, threats and unsettling encounters need a reporting route that is quick, visible and consistently used. Otherwise each event looks isolated, repeat locations and people go unnoticed, and managers lose the evidence needed to strengthen controls before a more serious incident occurs.
4. Staff can leave in theory, but hesitate in practice
Permission to withdraw must survive contact with targets, waiting clients and managerial pressure. Workers need recognisable stop signals, simple words for ending a visit and confidence that a sensible decision will be supported afterwards. Rehearse the awkward moments: the atmosphere changes, an unexpected person arrives or the agreed controls are missing. If staff still wonder whether leaving will count against them, the policy has not given them practical permission to act safely.
5. Everyone passed the training, years ago
An induction certificate shows that training happened once; it does not show that people can use today's systems under pressure. Refresh the learning when roles, routes, technology or legal expectations change, and after incidents or near misses expose uncertainty. Short scenario practice is especially valuable: can staff recognise harassment risk, report clearly, withdraw from a visit and trigger the right escalation without searching for a forgotten procedure? That is the competence the policy depends on.
Try the two-minute reality check
Ask a worker and a manager, separately, to explain the visit plan, check-in route, missed-contact response, withdrawal rule and incident-reporting process. Then compare their answers with the written policy and the available records. Add device or app use, harassment reporting, post-incident learning and the date of the last meaningful review. Any gap between the document, the explanation and the evidence is a practical place to begin.