Lone worker incident response time: a UK checklist for check-call escalation

Lone worker incident response time is the gap between a missed check call and a named person taking action. No published UK standard sets a figure for that gap, so this article does not offer one. Instead it explains what the law expects employers to have in place, how ShiftTracker escalates a missed check call with its default settings, and how to set your own target from your risk assessment. It covers what a response procedure should say, how to test the escalation path, and which records show whether it worked. Where a detail could not be confirmed from ShiftTracker's documentation or an official source, we say so and list it at the end for a demo, so you can test it before relying on it in a client contract. The checklist suits security, cleaning and facilities operators who run lone workers on site, on patrol or in empty buildings.

What does the law expect for lone worker response?

UK employers must manage risks before anyone works alone and keep in touch with lone workers. The Health and Safety at Work etc. Act 1974 sets a general duty of care, and the Management of Health and Safety at Work Regulations 1999 require a suitable and sufficient risk assessment. Neither source sets a response time in minutes.

HSE's employer guidance states: 'As an employer, you must manage any health and safety risks before people can work alone.' Its monitoring page adds: 'You must monitor your lone workers and keep in touch with them.' It also asks employers to regularly test emergency procedures so lone workers can be contacted. This is a summary of process guidance, not legal advice. Check your position with a health and safety adviser for your sites and contracts.

Is there a published UK benchmark for lone worker response time?

No. We did not find a published UK standard or official dataset that gives acknowledgement or response times for lone worker check calls, so this article gives no benchmark figure. Set your target from your own risk assessment and your own records, and label it as an internal standard.

Be cautious with any figure described as typical or industry standard. Ask for the source, open it, and check that it covers your sector and your risk level. If you cannot find one, record in your procedure that the target is an internal figure.

How does ShiftTracker escalate a missed check call?

ShiftTracker marks a check call as missed if nothing is logged before its window closes. By default the window opens 15 minutes before the call is due and stays open for 30 minutes. If Auto-Escalate Missed Calls is on, administrators are alerted once the 15-minute escalation delay has passed. An administrator can press Escalate to send the alert sooner.

The documentation is explicit about what a missed call does not change: 'The shift keeps its status, the person is not marked absent, no call is placed to them, and no cover is arranged.' Your procedure must cover each of those steps yourself.

These are the organisation-wide defaults. A service or site pattern can override them, and the documentation lists the order in which settings apply, with the first match winning. For the full settings, see the check-call pattern settings guide.

The Check Calls settings page, where the order of precedence for check-call patterns is shown.

What should a lone worker response procedure include?

A response procedure names who acts, what they do first, when emergency services are called and who records the outcome. ShiftTracker sends the alert, but it does not contact the worker or emergency services, so the procedure must cover both steps and the handover between them.

• Who receives the alert, and who covers when they are off shift.

• How the worker is contacted, including how many attempts are made and in what order.

• The point at which emergency services are called, and who makes the call.

• Who decides whether cover is arranged, since ShiftTracker arranges none.

• Where the outcome is recorded. An Admin or Manager can log a call taken by phone on the Check Calls board.

Keep the procedure to one page that a supervisor can follow without the software open.

How do you set a response target for each role?

Start from your risk assessment. Group lone-worker roles by the risk each one carries, then choose a check-call interval, window and escalation delay for each group. Record the target for each group as your internal standard, and review it when a role or client site changes.

A service can carry its own check-call pattern, so a higher-risk role can have a shorter interval than the site default. The recurring shift patterns guide explains how to assign one.

A shorter escalation delay sends the alert sooner, but it may also raise alerts for short lapses that a worker would have resolved. Choose the delay from your own test results, not from a figure in this article.

A site's check-call summary, which shows the schedule its staff see.

How do you test the escalation path?

Test it before you rely on it, and repeat the test after any change to patterns, notification settings or staffing. A test shows whether the alert reaches the right people and how long it takes against your target. HSE guidance asks employers to test emergency procedures regularly.

• Choose a test shift that is not live, or tell the people involved beforehand.

• Let its check-call window close without logging a call, and note the time.

• Note when the alert appears and who receives it.

• Check each recipient's notification settings. Each person chooses which channels they receive, so an alert can be missed if a channel is switched off.

• Compare the timings with your target, fix any gap, and repeat the test.

What records show the response worked?

ShiftTracker records each book-on, check call and miss on the shift timeline, with a timestamp. Missed calls on running shifts stay on the Unconfirmed tab of the Check Calls board until someone acts on them. The check-call compliance report gives a record for a past period, and it exports as CSV.

A record shows that the welfare system ran as documented. It does not show that the worker was safe. Keep a separate incident log for outcomes, and link it to the timeline entry for each missed call. When a client asks for evidence, export the compliance report for the period in question, so the file shows the figures recorded at the time rather than figures rebuilt later from memory.

How we checked this and what to confirm

We rewrote this article from ShiftTracker's documentation and from the HSE and legislation.gov.uk pages linked above. We removed the benchmark figures because we could not open a source for them. The points below need a demo or a written answer before you publish or rely on them.

• Automatic escalation recipients. The documentation says administrators at the site are alerted. Whether Control users or Managers also receive the alert needs confirming.

• The organisation notification email. The documentation lists missed check-call alerts among organisation emails, but confirm it fires for check calls in your account.

• The panic button. It appears on the pricing page only, so this article does not describe it.

• A separate Lone Worker module. The documentation we checked does not describe one.

Next steps: run the test above, confirm the points in this list in a demo, and write the procedure before you go live.