What the System Cannot Tell You

Access data is precise about a narrow thing: that a credential was presented at a place and time. Most questions asked of it need more than that.

For teams turning what the system cannot tell you into a repeatable record, the feature page 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.

Whether the work was done

Presence is not production.

A gate record showing twelve bricklayers for eight hours says nothing about whether the scaffold was ready, the materials arrived or the drawing was right.

Where to look instead: the site diary and the progress measurement, which is what a delay claim actually turns on.

Who was actually there

Unless the reader is biometric, it shows that a card was presented.

Which is sufficient in normal operation and insufficient in a dispute, where card sharing is the first thing raised.

Where to look instead: supervision, and the fact that a foreman knows his gang.

Where people were on site

The gate knows the boundary, not the interior.

A person who entered at seven could be anywhere within the hoarding.

Which matters for an incident in a specific area and for an evacuation of part of the site.

Where to look instead: the permit system, which records who is authorised where, and supervision.

Whether somebody is competent

It knows a card is valid.

A valid card is evidence of training, not of competence on this machine, in this configuration, on this day.

Where to look instead: familiarisation records and the supervisor's assessment, which is why plant authorisation is separate.

Whether hours were properly worked

It knows presence.

It does not know travel time, setup, contractual entitlements or what was agreed about partial days.

Where to look instead: the subcontract, which should define what a day is before anybody argues about one.

Whether the subcontractor is performing

Headcount and hours describe input.

A subcontractor with more people on site is frequently one that is behind rather than one that is working harder.

Where to look instead: progress against programme, which is a different measurement entirely.

What it does support

That a credential was presented at a gate at a time.

A list of who should be on site, for a roll call.

Competence status and expiry at the moment of access.

And a defensible record of presence for a period.

Four things, reliably, and defending that boundary is what keeps them credible when a fifth is claimed and fails.

Why the overclaim matters

A site that believes the register answers a question it does not will stop asking that question elsewhere.

Which is how a commercial team relies on gate data in a dispute and loses an argument it was right about, and how a safety case rests on a register nobody has tested against a head count.

Stating the limits in the same document as the capabilities is the defence, and it costs a paragraph.

Where the pressure to overclaim comes from

The system costs money and somebody approved it.

Which produces an incentive to find uses for it, and the uses found are usually the ones it supports least.

Watch for the phrase "we have the data" as a justification for a conclusion the data cannot carry.

The question to ask of any claim

What exactly would the record show, and what would a person dispute?

If the answer to the second is "that it was me", the claim needs biometrics or supervision.

If it is "that I was working", the claim needs a supervisor rather than a turnstile.

Two questions, and they sort most of what gets asked of this data.

The sentence worth writing into the assessment

What the register does, what it does not, and what covers the gap.

Three lines, and they prevent the conclusion that a hazard was controlled because a system was bought — which is the reading an investigator will otherwise apply.

And they protect the register's credibility for the things it does support, which is the practical reason to bound a claim rather than the rhetorical one.