Lone Worker Didn't Check In: What Managers Should Do

Por Syed Muhammad Daud Rizvi — Cofundador de TapOkie Work. Crea check-ins por visita y monitoreo auditable para trabajadores solitarios en equipos pequeños — sin bloqueo empresarial.

When a lone worker misses a check-in, managers should attempt contact immediately, escalate to emergency services if they cannot be reached within a reasonable window, document every action taken, and treat the response as a test of whether the escalation chain described in the lone worker policy actually works in practice.

Why the response matters as much as the monitoring

Lone worker monitoring is only as good as what happens when an alert fires. Many organisations invest in monitoring systems, write policies that describe escalation chains, and then — when an alert actually fires — discover that no one is quite sure what to do next.

A missed check-in is a time-sensitive event. Every minute spent deciding who should act, what the protocol is, or whether to wait a bit longer is a minute in which a worker who may be in genuine distress is not getting help.

This guide sets out the response process step by step. Use it to build or test your organisation's escalation procedure, and run a tabletop exercise against it before the real situation arises.

Step 1: Confirm the alert is genuine

When a missed check-in alert fires, the first check is whether it is a system or connectivity issue rather than a worker in distress. Check:

Has the worker's device lost connection? (Some monitoring apps distinguish between a session timeout and a genuine missed check-out.)
Has the app malfunctioned or sent a duplicate alert?

This check should take no more than a minute or two. Do not spend significant time rationalising the alert away. If you cannot immediately identify a technical cause, proceed on the assumption that the alert is genuine.

Step 2: Attempt direct contact with the worker

Call the worker on their mobile number immediately. If no answer, try again within two minutes. If still no answer:

Try any secondary number you have for the worker (personal mobile, office line)
If the worker was due to be at a specific location, check whether a colleague or anyone nearby can confirm their status

Document the time of each contact attempt and the outcome (no answer, voicemail, engaged).

Step 3: Escalate if contact fails

If you cannot reach the worker within your policy's stated window — typically 15 to 30 minutes for higher-risk situations, potentially longer for lower-risk lone working — escalate. Your escalation chain should include:

Primary manager: already attempting contact in Step 2. If unavailable, proceed to the backup.

Secondary contact (backup manager): a named individual who takes over if the primary cannot respond. This person should be aware in advance that they are the backup and understand the process.

Emergency services: call 999 if you believe the worker may be in danger and cannot otherwise confirm their safety. Provide the last known location, the nature of the work, and any relevant medical or risk information you hold.

The escalation chain should be written into your lone worker policy with named individuals, not just job titles. Job titles change; named backups with updated contact details are far more useful under pressure.

Step 4: Notify the client location if appropriate

If the worker was conducting a home visit, it may be appropriate to contact the client's location — but exercise judgment. In some care settings, the client or household may not be the risk. In situations where there is any possibility that a third party at the location is involved in the worker's distress, emergency services should be notified first rather than alerting the location.

For lower-risk visits (property surveys, inspection visits, delivery roles), contacting the client or site manager is usually safe and may quickly confirm the worker is fine.

Step 5: Brief whoever attends

If you have sent a colleague to check on the worker, or if emergency services are attending, brief them with:

The worker's name and physical description
The address or last known location
The nature of the work being carried out
Any relevant risk information from the risk assessment (challenging service users, medical conditions, remote access)
The time of last confirmed contact

Do not rely on emergency services already having this information. Provide it proactively.

Step 6: Document everything

From the moment the alert fires, record:

Time the alert was received
Name of the person who received and acted on it
Each contact attempt: time, method, outcome
Time and nature of escalation decisions
Outcome — when and how the worker was confirmed safe or located
Any injuries or incidents discovered

This log is your evidence that the escalation process worked as described in your policy. It is the record an HSE inspector, CQC inspector, or insurer will ask for if the incident results in a formal review.

Exportable session records from your monitoring tool — combined with a contemporaneous manager log — provide the most complete picture.

Step 7: Review after every alert

After every missed check-in alert, whether it turned out to be a genuine emergency or a false alarm, conduct a brief review:

Was the alert detected promptly?
Did the escalation chain work as designed?
Was the response within the time window specified in the policy?
Were records created correctly?

False alarms are not wasted events. They are tests of your process. A smooth response to a false alarm is evidence that your system works. A disorganised response is a warning that the policy exists on paper but not in practice — better discovered through a false alarm than through a real emergency.

When the incident is confirmed: RIDDOR

If the missed check-in reveals that the worker has suffered a reportable injury or has been involved in a dangerous occurrence as defined under the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013, you must notify the HSE.

The RIDDOR trigger is the nature of the incident — not the missed check-in itself. Report via the HSE's RIDDOR online portal at riddor.hse.gov.uk. Timeframes vary by incident type (over-seven-day injuries have a ten-day reporting window; specified injuries and fatalities must be reported immediately). Do not wait until you have all the information before making initial contact with the HSE.

Your monitoring logs and incident response record will be material to any HSE investigation that follows.

Building this into your lone worker policy

A response process only works if it is written down, known by the people who need to follow it, and tested regularly. Ensure your lone worker policy:

Specifies the escalation window for different risk levels
Names primary and backup managers with current contact details
Describes the decision to involve emergency services explicitly — including that it is not a last resort
Requires logging of all alert responses
Includes a post-incident review requirement for every alert

TapOkie Work provides timestamped session records, an email and push alert to your designated managers when a session is overdue, and exportable history for inspections — so the evidence layer of this process is handled automatically.

Preguntas frecuentes

How long should I wait before calling 999?

There is no fixed rule. For high-risk settings (remote locations, service users with challenging behaviour) escalate faster — within 15 to 30 minutes of a missed alert. For lower-risk visits, a broader window may be appropriate. Write the threshold into your policy so managers are not making judgment calls from scratch each time.

Should I call the client or visit location first?

Only if you have the number and it is safe to do so. Contacting a service user's address before confirming the worker is incapacitated may alert a third party who could be the source of the risk. Try the worker's mobile first.

Does a missed check-in always need to be logged?

Yes. Log every missed alert, the time it was received, actions taken, and the outcome — including false alarms. Cumulative records demonstrate that your monitoring process is actually used, which matters to HSE and CQC inspectors.

When does a missed check-in become a RIDDOR event?

RIDDOR applies when the missed check-in turns out to indicate a reportable injury, disease, or dangerous occurrence under the 2013 Regulations. The missed alert itself is not reportable — but the incident that caused the worker to miss may be. Report within the required timeframe once the nature of the incident is confirmed.

What if it turns out to be a false alarm?

Still log it and review why it happened. Frequent false alarms erode manager confidence and lead to slower responses over time. See whether the issue is worker training, check-in window length, or device problems — and address the root cause.