Por Syed Muhammad Daud Rizvi — Cofundador da TapOkie Work. Constrói check-ins por visita e monitorização auditável para trabalhadores isolados em pequenas equipas — sem lock-in enterprise.
A usable lone worker policy defines who it covers, how visits are risk assessed, how workers check in and escalate, who responds to alerts, training requirements, and how you keep records. Keep it short enough to follow daily, then map tools — including monitoring apps — to those written steps so practice matches paper.
Why a written policy matters
A lone worker policy is not a formality. It is the document that ties together your risk assessment, monitoring controls, escalation chain, and training into one place. When an HSE inspector, CQC inspector, or insurer asks how you manage lone workers, a written policy that you can hand over immediately carries far more weight than an explanation of what you generally do.
The Health and Safety at Work Act 1974 requires employers to ensure, so far as is reasonably practicable, the health, safety, and welfare of their employees. The Management of Health and Safety at Work Regulations 1999 require significant findings to be recorded in writing for employers with five or more employees. A lone worker policy is not legally mandated by name, but if you do not have a written document covering this area and something goes wrong, its absence is conspicuous.
What a lone worker policy should cover
A good lone worker policy is not long. Five to eight sections covering the key elements is usually enough. Here is what those sections should address.
Section 1: Scope and purpose
State who the policy applies to. Include employees, bank staff, contractors under your direction, and volunteers where relevant. Be specific about roles. A vague "all staff who sometimes work alone" is less useful than listing domiciliary care workers, outreach coordinators, lone-opening staff, and any other specific roles in your organisation.
State the purpose clearly: the policy exists to meet your duty of care under the Health and Safety at Work Act 1974 and the Management of Health and Safety at Work Regulations 1999, and to provide workers with a documented process for working safely alone.
Section 2: Lone worker risk assessment
Reference your organisation's risk assessment for lone working and summarise its key findings. You do not need to reproduce the full assessment in the policy, but the policy should acknowledge it exists and link to it.
If you do not yet have a formal risk assessment, the policy should note that it will be completed by a named date. An incomplete policy that acknowledges its gaps is more honest and legally defensible than one that implies a process exists when it does not.
Key risk areas to summarise: violence or aggression from third parties, medical emergencies without immediate assistance, accidents at remote or unfamiliar locations, and failure to detect an incident in time.
Section 3: Monitoring process
Describe how lone workers are monitored. This is the operational heart of the policy and should be specific enough that a worker or manager reading it knows exactly what to do.
Include: how workers confirm they are starting a lone working period, how workers confirm they have ended a lone working period, what the expected check-out window is for different types of work, and how the system detects a missed check-out.
Avoid vague language like "workers should check in regularly." Instead: "Workers start a session in the TapOkie Work app when they begin a visit. They end the session on departure. Sessions have a maximum duration matching the scheduled visit length. If a session is not ended within [X] minutes of the expected end time, the monitoring dashboard alerts the designated manager."
Section 4: Escalation chain
Name who gets notified when a check-out is missed, and in what order. A two-tier escalation chain is minimum: a primary manager and a backup. Include out-of-hours coverage if your workers operate outside business hours.
Write this as a named list, not just job titles. Job titles change; named individuals with named backups make the process more robust. Review and update the escalation chain when staff change.
Section 5: Emergency procedures
Cover what workers should do if they feel unsafe during a lone working period. This should include how to raise an SOS or immediate alert, who is contacted when one is raised, and what workers should not do (for example: not to put themselves at greater risk trying to continue a visit).
Cover what managers should do when an SOS or missed check-out alert is received: attempt contact with the worker, contact emergency services if they cannot be reached, record the incident and response.
Section 6: Training and induction
State that lone working procedures are covered in induction for all roles that include lone working, and that refresher training is provided when the policy is updated or when workers raise concerns about the process. Record attendance.
Section 7: Policy review
State when the policy was last reviewed, who is responsible for reviewing it, and on what schedule. Annual review is typical; more frequent if you have incidents, near-misses, or significant changes to roles or working patterns.
A policy with a review date and a named owner is materially more credible than one that appears to have been written once and not touched since.
Employer obligations checklist
Before you circulate the policy, check:
- Does it cover all roles that involve lone working, including temporary and episodic situations?
- Does it reference a risk assessment?
- Does the monitoring process described match what you actually use?
- Is the escalation chain named and up to date?
- Is out-of-hours coverage addressed if relevant?
- Does the SOS procedure tell workers and managers what to do in concrete terms?
- Is there a review schedule?
If you answer no to any of these, address it before circulation. A policy with known gaps is better addressed now than when it is tested by an incident.
Making the policy usable
A policy that workers cannot find or do not understand is not working. Keep it short. Put it somewhere accessible, such as your staff handbook, intranet, or shared folder. Brief all new starters on it during induction and get a signature or acknowledgement.
Review worker feedback on the monitoring process itself. If workers find the check-in process difficult and are quietly not using it, your policy describes controls that do not exist in practice. That is the most common failure mode in lone worker monitoring, and it is entirely preventable.
Related reading
- What is a lone worker? UK definition explained
- Lone worker risk assessment for small teams
- UK lone worker legislation: employer duties explained
- Lone worker compliance hub
- Features: how TapOkie Work supports your policy
Perguntas frequentes
What sections should a policy include?
Scope, definitions, risk assessment, equipment and apps, check-in and escalation, supervision, training, reporting incidents, and review dates are the usual core.
How long should it be?
Prefer a clear 4–8 page working document over a generic template nobody reads. Link detailed appendices for high-risk procedures only.
Who signs it off?
A named senior manager with health and safety responsibility. Workers should acknowledge they have read the version that applies to them.
How often update it?
After major incidents, service redesign, tool changes, or at least annually. Version-control the document managers and inspectors will see.