Who Is Actually on Site

On most construction sites the principal contractor directly employs a small fraction of the people present. Everyone else belongs to somebody else, and the site still has to know who they are.

For teams turning who is actually on site into a repeatable record, www.monitask.com 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.

Why this is not ordinary workforce tracking

In an office or a warehouse, the employer knows its people because it hired them.

On a site, the main contractor has a contract with a subcontractor, who has a contract with another, who engages labour-only gangs, who bring operatives the main contractor has never met.

Three or four tiers deep is ordinary. On large projects it is deeper.

Which means the register of who is on site is assembled from people the organisation has no employment relationship with, and every downstream process depends on it being right.

What the register is actually for

Evacuation. The first and least negotiable. A fire alarm requires a roll call, and the roll call is only as good as the register.

Competence. Nobody should be past the gate without the card, the ticket or the training the work requires, and checking that at the gate is the only place it can be enforced.

Induction. A person who has not been inducted does not know the site's hazards, its traffic routes, its assembly points or its permit system.

Right to work and identity, which is a legal obligation in most jurisdictions and carries penalties that fall on the contractor rather than on the agency.

And, last, commercial verification: whether the hours being invoiced were worked.

That order matters. Most systems are sold on the last item and justified on the first.

What goes wrong

The register is a paper book at a gate that nobody reconciles.

People sign in and never sign out, so at four in the afternoon the book says two hundred and the site has forty.

Subcontractors bring an extra pair of hands for a day and nobody records them.

Cards are checked at induction and never again, so an expired ticket sits on site for months.

And the evacuation roll call is done from a list that was accurate at eight in the morning.

The multi-employer problem, stated plainly

The main contractor is responsible for site safety and for who is present.

The employment, the pay, the training records and the competence evidence sit with several other companies.

So the information the contractor needs is held by people who have no particular incentive to provide it accurately — and every hour spent chasing it is unbilled.

Which is why this subject is about contracts and interfaces as much as about turnstiles, and why a system installed without the contractual obligations to feed it produces a register that is confidently wrong.

What this collection covers

Access control and the register, which is the foundation.

Competence and cards, and how to check them without becoming a certification body.

Induction, and why it expires.

The subcontract chain: what to require, from whom, and how to verify it.

Hours, invoicing and the verification that connects them.

Certified payroll and prevailing wage obligations where they apply, which turn a records problem into a compliance one.

And the safety obligations that sit on top of all of it, because the register exists for the roll call before it exists for anything else.

What it does not cover

How to run a payroll, build a rota or manage absence, which are subjects in their own right and are not specific to construction.

This is about the site: who is on it, whether they should be, and whether anybody can prove either.

The three registers most sites have

The gate record, which knows who passed through and frequently not who left.

The subcontractor's own timesheet, which knows who was booked and paid.

And the supervisor's head count, which is the most accurate and exists only in somebody's memory.

These three disagree every day, and the size of the disagreement is the honest measure of how well the site is controlled.

Comparing them once, for one day, is the most informative hour available to anybody starting on this subject.

Where to start reading

If nothing exists: the register and the gate.

If a system exists and nobody trusts it: the reconciliation notes.

If the problem is commercial — invoiced hours that cannot be verified: the subcontract chain.

And if the site is in a jurisdiction with certified payroll or prevailing wage obligations, start there, because those requirements dictate the record format and retrofitting them is expensive.