How should missed lone worker check-ins be escalated?

A missed lone worker check-in is a prompt to act, not a completed response. Control rooms and managers need a clear sequence: see the miss, decide the next contact, take the action your procedures require, and leave a record of what happened. NightWarden can surface the alert, offer configured escalation contacts and log actions against the shift. People and procedures still decide what to do next.

The feature detail is on the lone worker monitoring software page. Use the steps below as operational guidance for an active Lone Worker session, not as a replacement for your written escalation procedure.

Confirm monitoring is actually running

Escalation only works if a Lone Worker session has started. Opening the Lone Worker screen in the Field app without starting a session does not begin monitoring. When an officer starts a Lone Worker session, the countdown uses the check-in interval already configured for that site or shift. Managers and control set and override those intervals. Field staff confirm check-ins when prompted and do not choose the interval in Lone Worker. (Staff-set intervals belong to the separate Lone Protect module.)

If you cannot see the session in Lone Worker Compliance or Check-in History, treat that as a setup problem as well as a welfare risk. Do not assume the control room is watching someone who never started monitoring.

See the miss early in Control Room

Keep the Control Room view open during operational hours so overdue check-ins are visible without ringing round. NightWarden's control room lone worker dashboard shows active field officers with countdown timers and colour-coded overdue status. Missed check-ins are flagged on active sessions. Panic alerts, where raised, are shown prominently and should be handled under your emergency procedure.

Amber and red severity tiers help you prioritise consecutive misses. They are not a reason to wait before acting under your procedures. If welfare is already in doubt, escalate immediately rather than waiting for the next colour change.

Use the site's Lone Worker Escalation settings

Before a busy night, check that each relevant site has Lone Worker Escalation contacts and numbers configured under Clients, Client Management and the site record. Available channels depend on your subscription and site configuration.

In NightWarden, Step 1 push, Telegram or SMS notifications can be sent as soon as a check is missed. A configured Step 1 phone call has a minimum five-minute grace after the miss. Later steps follow their configured delays. Treat those timings as the system's contact schedule, not as permission to delay a welfare decision. If someone may be injured or trapped, follow your emergency escalation procedure rather than waiting for the next automated step or for technical support.

In-app reminders and push notifications to the officer are separate from external Telegram, SMS or phone-call escalation to site contacts. Confirm both sides when something looks wrong: officer connectivity and app notifications, and the external contacts you expect to ring or message.

Act, then log what you did

An alert going out is not the same as someone responding. Your procedure should say who calls first, who is backup, when to involve a supervisor, and when to contact emergency services.

NightWarden logs escalation actions against the shift record, including calls, messages and decisions taken for post-incident review. Alerts acknowledged in the Control Room are logged with timestamp and user. A failed check-in can also open a pre-structured incident report template so the response is documented while events are fresh. Use those records after the incident. Do not restart or edit an overdue live session merely to test the system; preserve the original timeline for investigation.

Read location carefully

Check-ins can store GPS for compliance reporting. Map positions include the time last received. A stale timestamp is the last known position, not proof of where the officer is now. Connectivity, battery restrictions and location permissions can delay updates. After a missed check, background location can briefly help an escalation, but it is still only a last-known point.

If welfare is in doubt, follow your emergency procedure rather than relying on a map timestamp alone.

Aftercare and client proof

When the officer is safe, review the session in Lone Worker Compliance and Check-in History so check-ins, timestamps and GPS are available for internal review. Where a client asks for lone worker arrangements, monthly lone worker monitoring compliance reports through the client portal can support that conversation. Reporting helps show what happened. It does not guarantee legal compliance, audit success or prevention of every incident.

Field staff can also send an ad-hoc check-in outside a scheduled Lone Worker session when they need to confirm contact without waiting for the next prompt. That is useful operationally. It does not replace a properly started session when lone working is required.

Offline and coverage limits

The Field app can store drafts and pending work during connectivity loss and sync when online again. Do not assume the control room has live visibility while a device is disconnected. Build weak-signal and basement sites into your risk assessment and say what control should do when the dashboard goes quiet.

Suitability of phone-based check-ins still depends on assessed risk and working conditions. A separate lone-worker device may still be appropriate for higher-risk tasks or poor coverage. Software and alerts can support the response. They do not replace human judgement, risk assessment or the procedures your control room follows.

Wider operations picture

Lone worker escalation sits alongside scheduling, run sheets and live site visibility. If your team already uses security guard software for shifts and field tasks, keep lone worker alerts in the same operational picture rather than treating them as a separate add-on.

NightWarden is software for field operations. It does not supply guards or attend sites for you.

Next step

Write down who owns first-line response for each site, which contacts are Step 1 and backup, and when your team must call emergency services. Then check NightWarden's Lone Worker Escalation settings and Control Room view against that written procedure. Review the capability on the lone worker monitoring software page, or start from the NightWarden homepage if you want a demonstration against your escalation process.