Where to Start Reading

Fifty notes is more than anyone needs at once. These are the routes that fit the common positions.

For teams turning where to start reading into a repeatable record, the documentation page 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.

Nothing exists yet

Who is actually on site, for why this is different from workforce tracking anywhere else.

The gate, and the roll call, which is what the register is for.

Mobilisation, if the project has not started, because everything here is cheap before the first subcontractor arrives.

Where to start, if it has.

A system exists and nobody trusts it

Recovering a site that has lost control of its register, which is the quarter-long sequence.

The gate, for the exit problem, which is usually the cause.

How this goes wrong, for the recognisable failures.

And who owns the register, because an untrusted register almost always has nobody maintaining it.

The problem is commercial

Hours, invoices and what connects them, which is honest about how weak gate evidence is in a dispute.

The subcontract chain, and what to put in the subcontract.

Certified payroll, on publicly funded work.

And payment down the chain, which explains a workforce problem that is not a workforce problem.

The problem is safety

The roll call.

Cards and competence, then plant and permits.

Long hours and fatigue, which is the use of this data no other party can perform.

After an incident, which is what the records will be asked for.

And where the duties sit, which is the framework underneath all of it.

A client has specified something

Client requirements and audits.

Choosing a system, and reading a supplier's claims.

And the data note, because a client-specified system is still your processing decision.

The project is ending

What survives the project, which is decided at completion by whoever is still there.

And phase changes, because demobilisation is the least planned phase and the one where the arrangement lapses while people are still on site.

If you read only three

Who is actually on site, because the multi-employer framing changes everything else.

The roll call, because it is the use that cannot tolerate error and therefore sets the design.

And the five things that cost nothing, because it is what to do on Monday.

A closing note

Nothing here is legal advice. Duties around site safety, right to work, wage records, data protection and retention differ substantially by jurisdiction, and the notes say so where it matters.

Product comparisons are separated into practical guides and evaluated against operational requirements.

And no costs, ratios or retention periods are quoted, because they depend on your site, your contract and your jurisdiction. Every number worth having here is one you produce yourself.

What the collection argues

A construction site is responsible for the safety and presence of people it did not hire and does not pay.

The information it needs originates several tiers below it, with companies that have no particular incentive to provide it accurately.

Which makes this a subject about contracts, interfaces and one named person rather than about turnstiles.

And the register exists for the roll call before it exists for anything else — a site that has never tested that has an expensive list.

If you are a subcontractor

The subcontract chain and what to put in the subcontract, read from the other side: what will be asked of you and when.

Cards and competence, because the evidence burden sits with you.

Agency and self-employed labour, if you supply people.

And the data note, because you hold the employment records the site is asking about.

If you are a client

Client requirements and audits, for what is reasonable to specify.

Where the duties sit.

And what this cannot fix, because the commonest client error is specifying a system to solve a programme problem the client created.