The Device Is the Smallest Part

Lone worker safety is sold as devices. What actually protects anybody is what happens after the device does its job.

When the device is the smallest part also depends on reliable work records, www.monitask.com 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.

The chain

Something happens, or fails to happen.

The device or app raises it — a button pressed, a check-in missed, a fall detected.

An alert reaches somebody, who is awake and looking.

That person decides whether it is real, which takes seconds and requires information.

Somebody responds, which may mean a phone call, a colleague, or an emergency service.

And somebody reaches the worker, which requires knowing where they are.

Six links. The device is the first, and every vendor demonstration is about that one.

Where these systems fail

Not in the hardware, which mostly works.

In the link that has nobody in it at three in the morning.

In the escalation list that was written when three of the five named people still worked there.

In the location that was accurate to the building but not to the floor.

And in the alert that fired so often that the responder stopped looking.

The test that matters

Press the button at two in the morning on a Sunday and time what happens.

Most organisations have never done this.

And the ones that have almost always find something: an unanswered phone, an out-of-date list, a responder who did not know they were on it.

Run it before buying anything more, because a better device does not shorten that time.

What lone working actually covers

More people than the phrase suggests: care workers in homes, engineers on site, retail staff opening and closing alone, cleaners at night, drivers, social workers, agricultural workers, anyone in a remote or isolated part of a large building.

And people who are alone intermittently rather than by job title, which is the group most often missed in a risk assessment.

What this collection covers

The response chain, end to end, which is where the failures are.

Check-in arrangements and escalation.

Devices, honestly, including what each cannot do.

The legal duties, which are about risk assessment rather than about equipment.

And the situations where the answer is not to have people working alone at all, which is a legitimate finding that no product will suggest.

Timing each link

The chain is only as fast as its slowest link, and the slow one is rarely where people expect.

Detection to alert is usually instant for a button press and can be thirty seconds or more for automatic detection, because most systems wait before declaring a fall — deliberately, to reduce false alarms.

Alert to answered is the contracted figure a monitoring supplier quotes, and it is the only one anybody measures. It is also the shortest.

Answered to decision depends entirely on what the operator can see. An alert with a name, a schedule and an address is decided in seconds. One with a coordinate and nothing else becomes a series of phone calls.

Decision to dispatch is where authority matters. An operator who must obtain permission before calling emergency services adds the length of a phone call to a manager who may be asleep.

Dispatch to arrival is outside your control and is frequently the longest — but the preceding four are entirely within it, and in most organisations they add up to more than anyone assumes.

The arithmetic nobody does

Add the four controllable links and compare the total against the hazard.

A fall from height or a cardiac event needs minutes.

An aggressive situation needs whatever time the situation allows, which is unknowable.

A slip in a plant room with a broken ankle needs hours before the delay itself becomes the injury.

Most organisations discover their controllable total is twenty to forty minutes, which is adequate for the third case and not for the first. That finding is the whole business case, and it costs one test to produce.

Why the device gets all the attention

It is the visible part. A supplier can demonstrate it, a manager can hold it, and a purchase order can describe it.

It has a price. The rest of the chain has a cost — somebody's evenings, a duty rota, a monitoring contract — and costs are harder to approve than prices.

And it feels like the answer. Handing somebody a device is a complete-feeling action, which is precisely why it substitutes for the incomplete-feeling work of arranging a response.

This substitution is the central failure in this subject, and it recurs in almost every note that follows.

What a working chain looks like in one sentence

Somebody raises an alarm, a person who is awake sees it within seconds with enough context to decide, and somebody with authority dispatches help to an address rather than a coordinate.

Every element of that sentence is a design decision. None of them is a device.

How to read this collection

The notes are grouped by where in the chain they sit. The response section covers check-ins, escalation, monitoring and location — the links that fail. The equipment section covers devices, honestly, including what each cannot do. The sector notes cover the situations where the chain has to be arranged differently: home visits, retail, remote work, nights.

Two notes are worth reading before any purchase decision: the risk assessment, because it determines whether equipment is the right control at all, and the note on what these systems cannot do, because a system believed to do more than it does produces worse decisions than none.