Skip to content
Everyone on Site

All notes  /  The register

The Roll Call

The reason the register exists, the one use where being wrong has consequences that are not commercial, and what it requires of everything upstream.

The register · Procedure

Every other use of a site register can tolerate an error rate. This one cannot, and it is the use that determines how the whole system should be designed.

For teams turning the roll call into a repeatable record, staff scheduling software provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside HSE construction guidance so the software choice remains grounded in site practice and applicable guidance.

What has to happen

An alarm sounds. People go to an assembly point. Somebody counts them against a list.

The list has to be current to within minutes, available at the assembly point, and readable in rain and darkness.

Which is three requirements, and most sites satisfy one.

Where the list comes from

The live register, at the moment of the alarm.

Which means the register has to be accessible when the site power is off, the network is down, or the office the server sits in is the thing on fire.

A cloud system with a mobile view is the usual answer and depends on mobile coverage at the assembly point — worth testing, because assembly points are frequently in car parks behind buildings.

A printed backup, refreshed automatically at intervals, is the arrangement that survives everything. It is unfashionable and it works.

The exit problem, again

A register that under-records departures produces a list of people who are not missing.

Which is the worst possible failure mode: marshals search for somebody who is at home, while the count appears not to reconcile and nobody can tell whether it is a data error or a person in a building.

Every minute spent on a phantom is a minute not spent on somebody real.

This is the practical argument for getting the exit right, and it is more persuasive to a site manager than anything about invoicing.

Marshals and the count

Named people, per assembly point, with the list and the authority to report.

Who need to know how the list is obtained if the usual method fails.

And who need to be on the rota: a marshal on holiday is a marshal who is not there.

Test that the deputy knows, which is the same lesson as every other part of this subject.

Subcontractor gangs and their own accounting

Many gangs count their own people, and do it well — a ganger knows exactly who came in the van.

Which is a resource rather than a complication.

Build it into the process: each gang leader reports their own count to the marshal, and the marshal reconciles against the register.

Two independent counts that agree is strong evidence. Two that disagree is the finding, and it is found in minutes rather than after the fact.

Visitors, deliveries and drivers

The people most likely to be missed and least likely to know where the assembly point is.

A visitor badge with the assembly point printed on it costs nothing.

And a delivery driver in a cab in a queue is on site, unaware, and not in anybody's count unless the vehicle gate process captures them.

Testing it

A drill, timed, with the register taken at the moment the alarm sounds.

Count: how long to obtain the list, how long to complete the count, how many discrepancies, and how many were data errors rather than people.

That last figure is the measure of the register, and it is the only honest audit of everything upstream of the alarm.

Quarterly, and after any change to the access system.

What the drill usually finds

The list was fifteen minutes out of date because it is generated on a schedule rather than on demand.

Nobody could open it at the assembly point.

Twenty names with no exit record.

A gang that had left at lunchtime and was still counted.

And a marshal who was not on site that day.

All five are fixable, all five are invisible without a drill, and the drill costs an hour.

What this requires of everything else

Induction has to place people on the register on their first day, before they reach the work area.

The gate has to record exits.

Subcontractors have to report their people.

And somebody has to own the register, because a list nobody maintains is accurate on the day it was built and degrades from there.