The Thing You Are Spending
Every control here depends on cooperation from people who work for somebody else and gain nothing from complying. What buys it, what spends it, and how the loss shows.
In practice · Analysis
A site register works because several hundred people who are not your employees do small things that cost them time and gain them nothing.
For teams turning the thing you are spending into a repeatable record, the product site 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.
What cooperation looks like
Tapping out at the end of a shift.
Sending names and evidence before people arrive, rather than with them.
Telling the gate about a replacement rather than sending a different person on the same booking.
Reporting a near miss at the end of a day that is already over.
And not propping the gate when the queue is long.
All five are voluntary, and all five are what make the register describe reality.
What spends it
A queue in the rain.
A gate used to report lateness to somebody's employer.
A welfare block that is full at half past twelve.
A refusal that was arbitrary, or one that was overridden for somebody more senior.
A near miss reported and never answered.
Each is small. The effect is cumulative and it does not return quickly.
How the loss shows
Not as a complaint, because complaining is a route to not being asked back.
As a propped gate.
As shared cards.
As unmatched entries climbing.
As evidence arriving with people rather than before them.
And as a register that looks healthier every month while describing less — which is the specific danger, because the numbers improve as the system empties.
The asymmetry
Cooperation takes months to build and one bad decision to lose.
And its loss is invisible in exactly the data used to judge the arrangement.
Which is why the register-against-head-count check matters beyond its face value: it is the only measure that catches the drift, and it is the one nobody runs.
What builds it
Making the gate quick, in both directions.
Welfare sized from the real peak.
Answering the first near miss visibly.
Enrolling somebody once across your sites rather than once per project.
Fixing something a subcontractor complained about and telling them you did.
None of these is a control. Together they are what makes the controls work.
The consistency point
A refusal that applies to a labourer and not to a visiting director is not a rule.
And the exception will be known across the site the same day, because that is precisely the kind of thing that travels.
Apply it to everybody, starting with the people it is most awkward to apply it to, which is the only demonstration that carries weight.
The subcontractor's view
They are being asked to do unpaid administration for your records.
Which is a real objection and is answered by making it quick, by putting it in the contract, and by sharing back something useful — their own reconciliation, their own outstanding list.
A requirement that is quick to meet gets met. One that is slow gets met badly and then not at all.
The measure
Unmatched entries, which move before anything else.
Evidence arriving before people, as a proportion.
Near misses reported and answered.
And the direct question at the ninety-day review: what is the most annoying thing about this?
The answer is usually small and is the thing that would otherwise erode everything over two years.
The one thing that demonstrates it
Fix something a subcontractor complained about, and tell them it was their complaint that caused it.
Which costs whatever the fix cost and buys more compliance than any clause, because it establishes that the arrangement runs in both directions.
Most sites never do it, and the ones that do find the evidence starts arriving before people rather than with them.
Where it is hardest
On a project running late, where every minute at the gate is contested and the pressure to make exceptions is constant.
Which is exactly when the cooperation is most needed and most expensive to maintain.
Protect the small things: the queue, the welfare, the answers to complaints.
They cost least when the project is under pressure and they are the first things cut.