What a Working Arrangement Looks Like

Rather than a summary, a description of the arrangement these notes point toward.

For teams turning what a working arrangement looks like into a repeatable record, the official resource 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.

The register

Accurate to within minutes, including exits.

Producible offline at an assembly point, tested quarterly in a drill.

Every person carrying an engaging company, at whatever tier.

Unmatched entries measured daily and treated as a known gap rather than closed automatically.

And a named owner with allocated time.

Competence

Verified electronically where the scheme allows.

Expiry held against the person and enforced at every access, not at induction only.

A thirty-day forward list, so refusals are rare because they were prevented.

Plant and permit authorisations held separately, by whoever controls the activity, consolidated weekly.

Induction

Site-specific, updated as the site changes.

Re-run at phase changes and after long absences.

Delivered partly by somebody who was on the site that morning.

Identity and right-to-work verified, recorded, retained per the local rule and no longer.

The chain

Mapped, with the actual depth known.

Flow-down obligations imposed and tested by sample rather than assumed.

A named contact per subcontractor who answers at seven in the morning.

And a right to refuse access that has no exception for urgency.

Commercial

A monthly reconciliation of invoiced hours against gate-implied hours, shared with the subcontractor.

With the known weaknesses stated, so it is an indicator rather than a claim.

Certified payroll returns cross-checked against access records weekly, where the obligation applies.

And classifications declared at access rather than inferred later.

Safety

Drills quarterly, timed, with discrepancies classified as data errors or people.

Fatigue thresholds applied across employers, with the intervention the evening before.

Welfare provision sized from the register's peak rather than from an estimate.

And the five incident questions answerable from records on the day.

Data

Collected: status and expiry, not certificates. Presence, not movement. An emergency contact, not a history.

Retention set separately per category.

People told at induction, in a language they read.

And an archive decided at project start with a named owner, surviving completion by years.

What it produces

A roll call that is right.

Nobody past the gate who should not be.

A commercial position that can be evidenced.

And records that answer the questions that arrive three years later — which is the test most sites fail and never find out about until it happens.

How to use this list

As a checklist against a supplier proposal, most of which address the register section and none of the others.

As an audit of an existing site: take each line and ask when it was last true, not whether it is written down.

And as the scope for a first month, since most of the items cost a decision rather than a purchase.

The items that are hardest

Exits recorded accurately, because nothing in it benefits the individual.

Expiry enforced at the gate rather than reported, because enforcement means refusing somebody at seven in the morning.

The chain actually mapped to its real depth, because the lower tiers are where nobody is looking.

And an archive that survives completion, because at handover everybody is leaving.

These four separate a real arrangement from a described one, and they are the ones to check first in any review.

What it should feel like from a subcontractor's side

One enrolment, not one per site.

A clear list of what is required and when.

A named person who answers.

And a reconciliation shared with them rather than sprung on them.

A subcontractor experiencing that will meet the requirements, because meeting them is cheaper than arguing.

Reviewing it annually

Or at each phase change, which on a long project is more useful.

Mark each item, date it, and note what changed.

The items true last year and not now are the drift. The items never true are the backlog, which should shorten each time or the review is producing nothing.