Lone Worker Safety Monitoring: From Missed Check-In to Coordinated Response
Published
Restrata Team
Lone worker safety monitoring is how an organisation knows, at any moment, that people working alone are safe, and how it acts fast when they might not be. Most organisations have the first half covered: an app, a check-in timer, a panic button. Far fewer have the second half: a defined, accountable response that starts the moment a signal goes quiet.
That second half is where lone worker safety is won or lost. An alert is not a response. A missed check-in only protects someone if a person sees it, knows where the worker actually is, understands what is happening around them, and has the authority and tools to act.
This article covers lone worker monitoring for enterprise operations - field, remote, offshore and site-based workforces in energy, maritime, infrastructure and logistics. It is not about consumer personal-safety apps.
What is lone worker safety monitoring?
Lone worker safety monitoring is the combination of technology, people and process that tracks the welfare of employees working without close supervision, and escalates when something changes. It typically brings together scheduled or automated check-ins, SOS alerts, location data and a monitoring function - in-house or outsourced - that owns the response.
Monitoring is the part that turns a lone working policy into outcomes. A device can raise an alarm. Only a monitoring capability makes sure the alarm leads somewhere.
Who counts as a lone worker, and who gets missed?
The obvious lone workers are easy to count: the engineer at an unmanned substation, the security officer on a night patrol, the inspector on a remote pipeline route. The people who drop out of the picture are usually those who are only alone some of the time:
Contractors and subcontractors who sit outside HR systems
Drivers and field teams between sites, where the risk is the journey rather than the destination
Personnel working alone in a remote area of an offshore installation or vessel
Staff making short visits to higher-risk locations
Employees working out of hours in an otherwise staffed building
If monitoring only covers people who have the app installed and switched on, coverage is defined by adoption, not by risk. The first job of any programme is an honest count of who is actually exposed, across employees, contractors and visitors.
What does the law expect from lone worker monitoring?
Most jurisdictions do not prescribe a technology. They require employers to assess the risk and put reasonable controls in place, and monitoring is one of those controls.
United Kingdom. Under the Health and Safety at Work etc Act and the Management of Health and Safety at Work Regulations, employers must assess and control risks, including those to lone workers. HSE guidance lists ways to keep in touch: supervisors visiting periodically, "pre-agreed intervals of regular contact", devices "designed to raise the alarm in an emergency which can be operated manually or automatically", and "a robust system to ensure a lone worker has returned to their base or home". Employers should also "regularly test technical solutions and all emergency procedures" (HSE, INDG73).
Australia. Regulation 48 of the model WHS Regulations requires businesses to manage the risks to remote or isolated workers and to "have systems in place to effectively communicate with workers" (Safe Work Australia).
The common thread: regulators expect a system, not just a device, and they expect it to be tested. This is general information, not legal advice. Confirm your obligations in each country where you operate.
Why do check-in-based monitoring systems fail in practice?
The alert has no owner. A missed check-in lands in a shared inbox or on a supervisor's phone at the end of a shift. Nobody is accountable for acting on it within a set time.
The location is stale. The last GPS fix was well before the alert, or the worker was assumed to be where the schedule said. Responders start by working out where to look.
There is no context. The alert says a check-in was missed. It does not say the road on the worker's route is closed, severe weather is moving in or a security incident is unfolding two streets away.
Signal disappears where risk is highest. Global coverage figures look reassuring: 4G now reaches 94% of the world's population (ITU, Facts and Figures 2026). But coverage follows where people live, not where work happens. Offshore installations, pipeline routes, mines and desert sites often sit outside it.
Escalation runs on a phone tree. Each hand-off - supervisor, duty manager, site, emergency services - adds minutes and loses detail.
What should happen when a lone worker misses a check-in?
Every lone worker programme should be able to answer this before it happens, in writing, with names and times. An escalation ladder makes the answer explicit. Set the time between stages in your risk assessment: shorter for higher-risk tasks, remote locations and poor connectivity.
Stage | Trigger | Action | Owner |
|---|---|---|---|
Stage 1 | Check-in missed | Automated prompt to the worker to confirm status | System |
Stage 2 | No response to the prompt | Direct contact attempt by phone, radio or message; last known location reviewed | Monitoring operator |
Stage 3 | Worker still unreachable | Supervisor and site notified; nearest colleague tasked to check; live threats around the location reviewed | Monitoring operator and supervisor |
Stage 4 | Worker still unaccounted for | Incident raised; emergency services contacted where required; stakeholders informed | Duty manager or incident lead |
Two rules make the ladder work. An SOS or man-down alarm skips the ladder and goes straight to response. And every step is logged as it happens, so the timeline already exists when someone asks what you knew and when.
What does good lone worker safety monitoring look like?
Good monitoring closes the gap between a signal and a decision. In practice that takes five things.
Location you can trust, not assume. No single source gives a complete picture. Restrata's Location Confidence approach combines GPS, verified check-ins, access control, itineraries and HR records, and grades each person by the quality of evidence. Responders know not just where someone is, but how sure they can be.
Context around the worker. A missed check-in means something different when a protest has blocked the road between the site and the airport. Monitoring should overlay worker locations with live threat intelligence, so the operator sees exposure, not just status.
Escalation built into response. A missed check-in or SOS should move straight into defined workflows, emergency communications and incident management, without re-keying details into another system.
Coverage when connectivity drops. Remote sites, offshore assets and long journeys are where signal fails. Offline capability, journey monitoring and overdue alerts keep people in the picture when the network does not.
An evidence trail. Every check-in, alert, call and decision recorded in one timeline, ready for regulators, clients, insurers and your own post-incident review.
This is the thinking behind resilienceOS. In High-Risk Operations, lone worker monitoring sits in the same operational picture as Personnel on Board (POB), journeys, contractors and live threats, rather than in a standalone app. When an alert becomes an incident, ROSA, the operational AI built into resilienceOS, delivers instant situational context and SITREP support.
Should you monitor lone workers in-house or use a 24/7 monitoring service?
Both models work. The question is whether you can guarantee a trained operator, around the clock, who knows your sites and your escalation plan.
In-house monitoring | 24/7 monitored service | |
|---|---|---|
Best fit | Organisations with a staffed GSOC or control room | Organisations without round-the-clock cover, or with workforces across time zones |
Who answers at 2am | Your duty operator, if the rota is covered | A trained operator, every night |
Knowledge of your sites and plans | High, if procedures are maintained | High only if the provider is briefed on your plans before go-live |
Cost profile | Staffing, training and shift cover carried in-house | Service fee, with no GSOC build |
Escalation | Your procedures, your people | Pre-agreed workflows, including supervisors and emergency services |
Main risk | Gaps at nights, weekends and holidays | A control centre seeing your plan for the first time |
The deciding factor is usually the night shift. If nobody is guaranteed to see an alert at 2am, the alert is not monitored.
Restrata's Resilience Operations Centre provides 24/7 monitoring and response as a service, separate from the resilienceOS platform. For a New Zealand public housing agency, it monitors around 900 lone workers around the clock. Workers carry mobile alert technology connected to Restrata's operators, and predefined escalation workflows bring in supervisors and emergency services where required.
How does POB visibility fit with lone worker monitoring?
On offshore installations, vessels and large remote sites, lone worker monitoring and POB answer the same question: who is here, exactly where, and are they safe? Run them as separate systems and someone ends up reconciling two lists in the middle of an emergency.
Genel Energy managed more than 2,000 people across multiple sites in Kurdistan on a paper T-card system, and mustering took up to an hour. With resilienceOS, they gained real-time visibility of every worker on site and in transit, and muster time fell by 80%, to under ten minutes. The same live picture that supports a muster supports a single worker who has gone quiet.
How do you evidence lone worker safety to a regulator, client or board?
When something goes wrong, the questions are predictable: what did you know, when did you know it, and what did you do next? Answering them should take minutes, not a week of piecing together emails and call logs.
Helmerich & Payne once had to pull data from Security, HSE, HR and Operations before it could establish who an incident affected. With automated data collection and a single operational picture, that now takes minutes rather than hours, across 30 countries and 15,000+ employees.
For lone worker programmes, hold this evidence ready:
The risk assessment and the monitoring arrangements it specified
Check-in and alert history per worker, with timestamps
The escalation timeline for every missed check-in or SOS
Test and drill records for the system and the procedures
Post-incident reviews and the changes they produced
Lone worker safety monitoring is a response capability
Lone worker safety monitoring is judged in the minutes after a signal goes quiet. The device, the app and the check-in timer matter, but only as the start of a chain: a trusted location, live context, an accountable operator, a defined escalation and a record of every step.
Restrata works with 180+ organisations across 40+ countries, including 7 of the world's 10 largest energy companies, connecting people, sites, journeys and threats in one operational picture. To test how your lone worker monitoring would hold up at 2am on a remote site, speak to our experts or see resilienceOS in action.
Frequently asked questions
What is the difference between lone worker monitoring and lone worker protection?
Lone worker protection is the whole programme: risk assessment, training, procedures and equipment. Lone worker safety monitoring is the live part of it, tracking welfare through check-ins, alerts and location data, and escalating when something changes. Protection sets the rules; monitoring makes sure someone acts on them in real time, including at night and at weekends.
How often should lone workers check in?
Set check-in intervals by risk, not habit. Higher-risk tasks, such as work at height, confined spaces or travel through an area with a live threat, justify shorter intervals or continuous tracking. Lower-risk work may only need start and end of shift check-ins. HSE guidance refers to "pre-agreed intervals of regular contact", so document the interval for each task.
What happens if a lone worker misses a check-in?
A missed check-in should trigger a defined escalation ladder: an automated prompt to the worker, a direct contact attempt, notification of the supervisor and site, then an incident with emergency services if needed. Each step needs a named owner and a time limit. An SOS or man-down alarm should skip the ladder and go straight to response.
Is lone worker monitoring a legal requirement?
Most jurisdictions require employers to assess and control risks to lone workers rather than mandating a specific technology. In the UK the duty comes from the Health and Safety at Work etc Act and the Management of Health and Safety at Work Regulations. In Australia, WHS Regulation 48 requires systems to communicate effectively with remote or isolated workers. Confirm local obligations with your advisors.
How do you monitor lone workers with no mobile signal?
Plan for no signal before work starts. Options include satellite devices, radios, agreed check-in windows when workers return to coverage, and journey plans with overdue alerts that fire if someone does not arrive. Platforms with offline capability keep the operational picture working at disconnected sites. Decide in advance what happens when a worker goes quiet in a known dead zone.
What is a man-down alarm?
A man-down alarm is a device or app feature that raises an automatic alert when it detects a fall, a sudden impact or no movement for a set period. It matters most where a worker could be injured and unable to call for help. Like any alarm, it only protects people if a monitoring operator receives it and acts on it.
Should contractors be included in lone worker monitoring?
Yes. Contractors often carry out some of the highest-risk lone work, yet they are the group most likely to sit outside HR systems and lone worker apps. Monitoring should cover anyone working under your control, whether employee, contractor or visitor, with the same check-in rules, escalation and records. If they are not in the picture, they cannot be accounted for.
How do you choose a lone worker monitoring system?
Look beyond the device. Ask how the system establishes location when GPS is unavailable, how it shows threats near a worker, how alerts escalate into incident response and communications, whether it works offline, and what evidence it produces afterwards. Then ask who answers an alert at 2am, and how they already know your sites and plans.