What the Hardware Cannot Do

Access hardware on a construction site works in conditions it was mostly not designed for, and its limits are predictable.

For teams turning what the hardware cannot do into a repeatable record, contractor management workflows provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside ISO standards catalogue so the software choice remains grounded in site practice and applicable guidance.

Readers in the weather

Cards get wet, dirty and bent. Readers get rained on and knocked by scaffolding.

Cold reduces battery life in anything portable and stiffens fingers, which defeats fingerprint sensors.

Gloves defeat them entirely, and taking gloves off in January at seven in the morning is a queue.

Which means failed reads are a routine event rather than a fault, and the process has to absorb them without a phone call.

Turnstiles and throughput

A turnstile admits one person per authorisation, which is what stops tailgating.

And it is a serial device: everybody waits for the person in front.

Which makes lane count the binding constraint at shift start, and a site that saved money on lanes pays for it every morning in queue time it can calculate but never does.

Emergency egress is the other constraint: turnstiles must free-wheel or be bypassed on an alarm, which has to be tested rather than assumed from the specification.

Biometrics

Resolves card sharing and introduces failure modes of its own: wet hands, worn fingerprints from manual work, dirt, and a failure-to-enrol rate that is not zero.

Manual workers have measurably worse fingerprint readability than office populations, which is exactly the population being enrolled here.

Which means an alternative path is operationally necessary as well as legally advisable, and a site that has not built one will build it in the first week anyway.

Networks and power

Site networks are temporary, and so is site power.

A system that cannot admit anybody when the connection drops will be bypassed within the hour, and the bypass will become routine.

Local caching at the reader, with the register reconciling later, is the arrangement that survives — and the offline evacuation view is the same requirement seen from the other side.

What no system knows

Who presented the card, unless it is biometric.

Where somebody went after the gate.

Whether the person who entered is the person who was booked.

Whether somebody left through a gap in the hoarding, which on most sites exists.

Each of these is covered by supervision or by the permit system rather than by hardware, and pretending otherwise produces a register with unearned confidence.

The perimeter

The register assumes the boundary is the only way in.

On a live construction site the boundary is provisional: deliveries, plant movements, adjacent works, and the section of hoarding that came down on Tuesday.

Which is a security matter and a register matter at once, and a perimeter walk at the start of each phase is the check that connects them.

Designing around the limits

Assume failed reads and build the override with a record.

Assume network loss and cache locally.

Assume some people cannot use a biometric and provide an alternative without argument.

Assume the boundary is imperfect and walk it.

And assume the exit will under-record, and measure the gap rather than closing it artificially.

Five assumptions, all safe, and an arrangement built on them survives a real site.

What to ask a supplier

"What happens when the network drops, and what happens when the power goes off?"

"What is your failure-to-enrol rate on manual workers?"

"How do the turnstiles behave on a fire alarm, and can I see it?"

Three questions, and the quality of the answers sorts this market faster than any feature comparison.

The cost of ignoring the limits

A site that specified biometrics without an alternative path spends its first fortnight arguing.

One that specified too few lanes lives with a queue for two years.

One that did not test the fire-alarm behaviour discovers it during a drill, which is the good case, or during a fire, which is not.

All three are decided at specification and cannot be undone afterwards, which is why the three questions belong in the procurement rather than the commissioning.