TECHNOLOGY
THE DATA PROBLEM IN DUTY OF CARE
When nothing goes wrong, how do you prove you managed the risk? Here, Peoplesafe suggests why evidencing duty of care depends less on policy, and more on the data your systems generate.
It’s a familiar scene in H&S reviews: a board asks how confident the organisation should feel about lone worker safety. Nothing has gone wrong this quarter. No incidents, no near-misses on record. But “nothing happened” isn’t the same as “we can prove we managed the risk”. Increasingly, that’s the question being asked.
With an estimated 22% of the workforce working alone in the UK at some point in their working day, this isn’t a niche concern. It’s a live exposure for most H&S teams.
The problem is that most lone worker processes were built to manage risk in the moment, not to evidence that management after the fact. A sign-in sheet, an informal WhatsApp check-in, a verbal handover between shifts – none of it survives scrutiny six months later. There’s no timestamp, no verification that a check actually happened, nothing retrievable when a regulator, insurer, or claimant’s solicitor comes asking.
“THE PROBLEM IS THAT MOST LONE WORKER PROCESSES WERE BUILT TO MANAGE RISK IN THE MOMENT, NOT TO EVIDENCE THAT MANAGEMENT AFTER THE FACT.”
Evidencing duty of care properly means the record has to be a by-product of the safety process itself: generated automatically, continuously, and in a form that can be pulled up on demand rather than reconstructed from memory after an incident.
THE RISK HIDING IN WHAT GOES UNRECORDED
Incident figures rarely tell the whole story. Verbal abuse, a threatening encounter, a close call on a lone visit; much of this goes unreported, normalised as 'part of the job' rather than logged. That leaves employers with a partial risk picture, and a gap in the evidence base that opens long before anything serious happens.
Closing that gap means giving workers a way to flag concern before it escalates and capturing it when they do – not relying on someone deciding, after the fact, that an incident was serious enough to write up.
This is precisely where technology earns its place in the conversation. At Peoplesafe, this thinking sits behind two parts of the service.
SINGLE SOURCE OF TRUTH AND AUDIT TRIAL
Nexus is where that evidencing data lives. Every check-in, alert, location ping, and escalation across an organisation’s lone worker population is captured and housed in one place. Rather than a patchwork of logs across shifts and systems, H&S managers get a single, retrievable dataset. When the question is 'how do you
28
WWW.TOMORROWSHS.COM
know your people were safe today?’, the answer isn’t a policy document; it’s data.
Every live alarm is handled by a trained Alarm Controller, and Peoplesafe’s proprietary Lighthouse software logs every action that controller takes during the call in real time. The result is a complete, timestamped record of exactly what was done, by whom, for every alert that comes through– not just the ones that became incidents.
Together, they turn “we have a lone worker policy” into something far more defensible: a continuous, automatically-generated record that shows the system working, alert by alert, day by day regardless of whether anything ever goes wrong.
BUILT FOR MORE THAN EMERGENCIES
This is where the design of the technology matters. A lone worker service isn’t reserved for active incidents. A worker can raise an alarm the moment they feel threatened or unsafe, giving visibility of risk that would otherwise go unspoken.
For higher-risk lone tasks, activity timers add a further layer: an automatic countdown that triggers a check if a worker doesn’t confirm they’re safe in time, creating a built-in safety net without waiting for someone to ask for help. Both generate a record simply by existing, whether or not help was ever needed.
Proving a negative is never going to be easy. But with the right technology in place, it doesn’t have to be guesswork.
https://peoplesafe.co.uk
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44
