Running the Gate

Everything in this collection arrives at one place: a person standing at a barrier at seven in the morning deciding whether somebody comes in.

For teams turning running the gate into a repeatable record, see how it works 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 peak

Most of a site's workforce arrives within twenty minutes.

Which means throughput is the design constraint, and a system that reads in two seconds per person needs more lanes than anybody budgeted.

Count it: people expected, divided by lanes, times the read time, plus the failures. The answer is the queue, and on many sites it is longer than the walk from the car park.

A queue in the rain produces workarounds — propped gates, shared cards, people following through — which defeat the system more thoroughly than any deliberate evasion.

Staffing it

Somebody present at the peak, always.

Not to check everybody, which the system does, but to handle the failures: the forgotten card, the visitor, the delivery, the person whose card has expired.

Each of those is a decision, and the decision should not be theirs.

The decisions the gateman should not make

Whether to admit somebody unverified because the job is urgent.

Whether an expired card is close enough.

Whether a visitor needs an escort.

Whether a delivery driver counts as being on site.

All four should have written rules with a named authoriser, because a person under pressure at a barrier with twenty people behind them will decide in favour of admitting, every time, and should not be blamed for it.

Failed reads

Dirty cards, wet readers, gloves, damaged fobs.

A routine occurrence rather than an exception, and the process has to handle it without a phone call.

A manual override that records the person, the time and who authorised it is the right answer, and the count of overrides is a maintenance signal.

Where overrides are common on one lane, that lane needs attention rather than the people using it.

Deliveries and vehicles

A separate flow with a separate problem: the driver is on site briefly, the passengers may not be recorded, and the vehicle blocks the lane while it is resolved.

A vehicle marshalling arrangement away from the pedestrian gate is the usual answer, with its own recording process.

And a rule about passengers, because a van with four people and one card is the commonest quiet failure of the register.

The end of the shift

The half of the day nobody designs for.

People leave in a rush, the barrier is an obstacle, and there is no benefit to them in recording it.

Equal lanes outbound, and the exit as convenient as the entrance.

Or accept an unmatched-entry rate and publish it — which is the honest alternative and is better than an automatic sign-out that records an assumption as a fact.

What to watch weekly

Peak queue time.

Failed reads by lane.

Manual overrides, by authoriser.

Unmatched entries.

And the ratio of pedestrian to vehicle entries, which if it shifts suggests people are finding a route that suits them better than the one you built.

First day arrivals

Somebody arriving for the first time does not have a card, does not know where the office is, and is late because they were looking for the entrance.

Which produces a queue of one person absorbing all the attention at the worst moment.

Separate the flow: a first-day point away from the lane, signed from the road, staffed at the peak.

And tell subcontractors to send new people half an hour early, which costs them nothing and removes the commonest cause of gate congestion.

Weather and darkness

Readers fail more in rain. Gloves defeat fingerprint sensors. Cards live in wet pockets.

Winter mornings are dark, and the queue is outdoors.

Which means the gate arrangement that worked in June is the one people work around in January, and a review before the clocks change is worth the hour it takes.