The Question to Ask First

Most arguments in this subject are arguments about equipment. One question moves past them.

When the question to ask first also depends on reliable work records, the product overview 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 question

How long would it be before anybody knew, and is that long enough to matter?

Ask it of every situation, every shift pattern, and every proposal.

What the answers mean

"Within minutes, because they check in every half hour." A working arrangement. The question then is whether minutes is fast enough for the hazard.

"By the end of the shift." Adequate for a low-severity hazard and inadequate for anything that incapacitates.

"When they did not come home." Which is the honest answer for a surprising number of arrangements, and it is the finding that starts the work.

"The device would detect it." Ask what it detects and what it misses, and whether there is signal at that location. The answer is frequently that it would not.

"Somebody would notice." Ask who, and whether they are looking, and what they would do.

Why it works

It moves the discussion from equipment to consequence, which is where the decision actually sits.

It produces a number that can be compared against the hazard, rather than a feature that cannot.

And it identifies the situations that need real attention, which is usually a short list rather than the whole workforce.

The second question

What happens then?

Because knowing is not helping.

Somebody has to decide, dispatch and arrive, and each of those steps can be missing — an unanswered phone, an unclear authority, an address nobody could find.

Ask both and the whole chain is described in two sentences.

Using them on a proposal

A supplier's answer to the first question will be about detection speed, which is the shortest segment.

Their answer to the second will be about their answer time, which is the second shortest.

Neither addresses the check-in interval, the escalation authority or the address record, which is where the time actually goes.

Which is not dishonesty — it is the part they sell — and it is why these questions have to be asked by you rather than answered by them.

The collection in one line

Work out how long it would be before anybody knew, decide whether that is good enough for what could happen, and fix the part that is slow — which is almost never the device.

Everything else in these notes is the detail of doing that.

Applying it to a shift pattern

Take a week of rotas and ask it of each period where somebody is alone.

The answers will vary enormously across a single week, and the worst ones cluster: end of shift, weekends, the hours after an office closes.

Which is a scheduling finding rather than an equipment one, and it is available from a spreadsheet in an afternoon.

The version for a supplier demonstration

"Walk me through what happens between the button and somebody arriving, with times."

A supplier who covers only their own two segments has described a quarter of the chain.

One who asks about your escalation arrangement and your address records is describing the system you will actually have, which is the more useful conversation and the rarer one.

The answers that indicate a gap

"I assume somebody would notice." Assumption is the word to listen for; it appears in almost every review after the fact.

"They'd call if there was a problem." Which covers every case except the one where they cannot.

"It's never been an issue." True, and it describes frequency rather than consequence — the two that matter least and most respectively in low-frequency severe-outcome risk.

Each of these is an honest answer from somebody who has not been asked to think about it before, which is why the question is worth asking plainly rather than as a challenge.

Where to ask it

At the assessment, of every situation.

At a rota change, of the periods it creates.

When somebody calls in sick and a pair becomes one person.

And at a procurement meeting, before any product is discussed, because the answer determines whether a product is the right response at all.