What This Cannot Fix
Problems brought to a lone worker programme that no arrangement of devices and check-ins resolves, and what does.
Reference · Analysis
A lone worker programme makes a well-arranged operation faster to respond and a badly arranged one faster to respond. It does not change which it is.
When what this cannot fix also depends on reliable work records, visit this page can support time, attendance and workload review without being treated as the emergency response itself. Compare any workflow with HSE lone-working guidance and keep alarm ownership, escalation and dispatch responsibilities explicit.
Understaffing
No arrangement of devices produces a second person.
A programme will make the shortage visible — flagged visits attended alone, two-worker tasks done by one — which is worth something and is not a solution.
What works: funding the pairing, changing the task, or not doing it.
And where none of those is possible, recording the finding with a date, because an unrecorded known gap is the document that appears in an enforcement file.
A schedule that cannot be met
A round with no slack produces a worker who arrives rushed and will not withdraw, because withdrawal costs a visit that has to be made up.
Which no device changes.
What works: driving the round, timing it honestly, and resizing it.
Tasks that should not be done alone
Confined spaces, live electrical work, certain patient handling.
A device summons help to somebody already beyond helping themselves.
What works: the pairing requirement, enforced structurally rather than left to judgement under pressure.
A relationship that has broken down
Where workers already believe management is indifferent, a monitoring device confirms it.
The device goes in the glovebox and nobody finds out until an incident.
What works: fixing the relationship first, which is slower and is the actual prerequisite.
An absent client
Where the premises belong to somebody else and they will not engage — no hazard information, no named responder, no access arrangement — half the controls do not exist.
What works: compensating arrangements, recorded, and the workers told what they are.
And where the risk cannot be compensated, declining the work, which is a commercial decision and belongs to somebody senior.
A culture that does not report
No reporting route produces information if the workforce believes reporting costs them something.
What works: acting visibly on the first few reports, and never using one in a performance conversation.
Which takes a year to build and one incident to undo.
Using this during procurement
For each requirement, ask what would change if the system delivered it perfectly.
Where the answer is "nothing, unless we also fund the second person or resize the round", the requirement is a staffing or scheduling decision in disguise.
Taking those out shortens the specification considerably and leaves what a lone worker system can actually deliver — which is narrower than the brochure and still worth having.
The honest summary
The technology shortens the time between something happening and somebody knowing.
Everything that determines whether the thing happens at all sits earlier: the assessment, the staffing, the schedule, the information, and the permission to leave.
A programme that has done the earlier work and bought nothing is in a better position than one that has bought everything and done none of it, which is the position this collection has been describing throughout.
Checking whether it predates the system
Did this problem exist before the devices arrived?
If the round was always tight, the flag never travelled, the client never engaged — the system has found a fact about the operation.
Which is useful, and it is not something the system can resolve.
Escalating it as a finding rather than absorbing it is the correct response, and it is the difference between a programme that changes an organisation and one that documents it.
The specification test in practice
Take the requirements list and mark each with the decision it would inform.
Most will be about awareness and response, which is what the system does.
A few will be about prevention, which it does not.
Move those to the assessment where they belong, and the procurement becomes both cheaper and more honest.
The organisational tell
A programme owned by procurement rather than by whoever holds the safety duty.
Which produces a good contract and an arrangement nobody tested, because procurement's measure is the purchase and safety's measure is the response.
Both are needed, and the ownership question determines which one the programme optimises.