The Question to Ask First

Most arguments about site workforce systems are arguments about products. One question moves past them.

For teams turning the question to ask first into a repeatable record, the online guide provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside Chartered Institute of Building so the software choice remains grounded in site practice and applicable guidance.

The question

If the alarm went now, could you produce a list of who is on site, and would it be right?

Ask it of the site as it is, not as the documentation describes it.

What the answers mean

"Yes, in two minutes, and it was within three of a head count last month." A working arrangement. Everything else in this collection is refinement.

"Yes, but it would take a while to get it." A register that exists and is not available when it matters, which is a solvable arrangement problem rather than a system one.

"The list would be too long." The exit problem, which is the commonest answer and the one with the clearest fix.

"We'd ask the subcontractors." Which is a real answer, works on a small site, and does not scale past about twenty people.

"We have the system but I don't know." The most honest answer, and the one that means nobody owns the register.

Why it works

It moves the discussion from features to consequence.

It produces a number that can be compared against a requirement rather than a capability that cannot.

And it identifies the failure without anybody having to admit to one, because the answer is about the arrangement rather than about a person.

The second question

And who brought each of them here?

Because the engaging company is what every incident investigation asks for first, and it is the field most likely to be absent.

A site that can produce the list and cannot say who engaged the people on it has half a register.

The third, if the first two are answered

What happens when somebody's card expires tomorrow?

If the answer is a refusal at the gate, the enforcement is real.

If it is a report somebody reads weekly, it is not.

Three questions, in that order, and they establish more about a site's arrangement than a day of document review.

Using them on a proposal

A supplier's answer to the first will be about their database.

Ask them to show it offline, on a phone, with the network disabled — which is the same question asked in a way that cannot be answered with a description.

And ask the second and third of the site rather than the supplier, because those are process questions and no product answers them.

The collection in one line

Know who is on site, know who brought them, and be able to prove both when somebody asks — during an alarm, an investigation, an audit or a dispute three years later.

Everything else in these notes is the detail of doing that on a site where most of the people work for somebody else.

Asking it of a site you have just joined

On the first morning, before reading anything.

The answer, and the way it is given, tells you where the arrangement actually is — and it is frequently some distance from where the documentation puts it.

Then ask the second and third, and you have the shape of the whole problem before lunch.

What the answers predict

A site that answers the first question well usually answers the other two well, because they share a cause: somebody owns the arrangement.

And one that cannot answer any of them usually has a system, which is the finding worth stating plainly: the presence of hardware predicts nothing about the answers.

Which is why the question is asked of the site rather than of the specification.