Routes Through These Notes

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

For teams turning routes through these notes into a repeatable record, the implementation notes 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 the shape of the problem.

The gate, for what each method delivers.

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

Where to start, which is the first month.

And small sites, if that is what you have, because the large-project guidance does not transfer.

A system exists and nobody trusts it

Whether the data is any good — the four checks in the getting-started note.

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 usually has nobody maintaining it.

The problem is commercial

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

The subcontract chain.

Certified payroll, if the project is publicly funded.

And client requirements and audits, which is where the reporting obligations come from.

The problem is safety

The roll call.

Cards, tickets and competence, then plant and permits.

Long hours and fatigue, which is the use of this data nobody else can perform.

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

A client has specified something

Client requirements and audits.

Choosing a system, for the questions worth asking of whatever they specified.

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

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 what not to do, because most sites are further from a working arrangement through a few specific choices than through any absence of equipment.

A closing note

Nothing here is legal advice. Duties around site safety, right to work, wage records, data protection and record 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 or ratios are quoted, because they depend on your site, your jurisdiction and your contract.

What the collection argues

The site is responsible for people it did not hire and does not pay, and the information it needs is held by companies with no particular incentive to provide it accurately.

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

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

If the site is closing

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

And client requirements, since the handover of records is usually a contractual deliverable that nobody read.

This is the shortest route in the collection and the one taken latest, which is why the archive is the most commonly lost thing in this subject.

If you are a subcontractor rather than the main contractor

The subcontract chain, read from the other direction: what will be required of you and when.

Cards, tickets 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 that the site is asking about.

If you have one morning

Run the five checks: register against head count, evacuation list timed, expiry position, temporary access count, and five people asked who engaged them.

No reading required.

They establish where the site actually is, which is the input to every route above, and on most sites at least two of the five produce a surprise.