How long before anybody knows?
A lone worker system is a chain that ends with somebody driving to a location. The device raises the alarm; everything that determines whether help arrives happens after that, and most of it is free.
When how long before anybody knows? also depends on reliable work records, Monitask 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.
Software guides
Detailed comparisons for lone-worker alerts, workforce check-ins and field communication.
All 50 notes
The subjects stay in view on the left while the list scrolls, because the sections are deliberately uneven — most of this collection is about the response chain and very little about equipment, which is roughly the opposite of how the money usually gets spent.
The device is the first link of six. Most of what protects anybody is decided before it is ever pressed.
The links that actually fail: the one with nobody in it at three in the morning, the list with a wrong number, and the alert nobody believes any more.
Chosen last, after the chain exists, and by the people who will wear it. Comfort is not a preference here; it determines coverage.
The same chain arranged differently. Home visits are the largest group and the least controllable environment.
Scheduling is the most powerful control in this subject and is rarely treated as one. Testing is the only way to know whether any of it works.
- Near Misses and the Things Not Reported
- Training That Changes Anything
- What It Costs and What It Saves
- Involving the People It Is For
- Testing the Whole Chain
- Where to Start
- How These Programmes Fail
- Who Owns the Arrangement
- Small Organisations
- Scheduling as a Safety Control
- The Policy Document
- The First Ninety Days
- The Numbers Worth Watching
- The Thing You Are Spending
The duty is to assess and control, not to buy equipment. The absence of an assessment is the finding in most enforcement action here.
Almost all of them substitute something visible for something structural: a device for staffing, a document for a tested chain.
Where the controls that work sit furthest from the device, and where the organisation's own arrangements frequently produce the risk.
The end state as a checklist, the limits stated plainly, and the five arrangements that cost nothing.
What this is
Fifty notes on lone worker safety, written from the response backwards.
Independent product comparisons are kept in dedicated guides and assessed against operational requirements.
Four things that hold
The device is the first link of six. Something happens, an alert is raised, somebody sees it, somebody decides, somebody is dispatched, and somebody arrives. Every vendor demonstration is about the first link.
The failures are in the links with nobody in them. An escalation tree with a wrong number, monitoring that covers office hours for work that happens at night, an alert nobody takes seriously any more.
The strongest controls sit before the incident. Not working alone, a schedule that can be met, information that reaches the person before they arrive, and a withdrawal permission that costs them nothing.
Five arrangements cost nothing and deliver most of the protection: the assessment, the tested escalation tree, the check-in, the withdrawal statement, and telling people how it all works.
Where to start
Nothing exists yet: who counts as working alone, then the assessment.
Devices exist and nobody has tested the response: the escalation tree, then testing.
A purchase is proposed: the question to ask first.
Your situation is specific: the sector notes.
What this is not
Not legal advice. Duties around risk assessment, reporting, monitoring and data protection differ substantially by jurisdiction.
It does not describe how to enable continuous tracking quietly, how to use safety data for timekeeping, or how to present a device as a control for a hazard it cannot address. Those appear only in the notes explaining why they should not be done.