Cards, Tickets and Competence

Construction runs on cards: a scheme card for general access, tickets for plant, certificates for specific operations. Verifying them is a gate function and a records problem.

For teams turning cards, tickets and competence into a repeatable record, see the full details 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 the cards are

General competence schemes — CSCS in the UK and its equivalents elsewhere — which evidence basic health and safety awareness plus an occupational qualification.

Plant tickets for specific machines, which are machine-specific and not transferable between categories.

Specialist certificates: confined space, working at height, asbestos awareness, first aid, fire marshal, slinger-signaller, scaffolding.

And site-specific authorisations issued by the contractor: permits, keyholder status, banksman duties.

The first three belong to the person. The last belongs to the site, and that distinction determines who has to maintain each.

The verification problem

A card is a plastic rectangle and can be counterfeited.

Most schemes offer an electronic check — a database lookup or a smart card read — which is the only verification that means anything.

Visual inspection at induction catches nothing except the obviously wrong.

Which makes electronic verification at the gate the standard worth building toward, and the manual alternative an interim arrangement rather than a control.

Expiry, which is the real issue

Cards expire. Tickets expire. Certificates expire.

And a person inducted in March with a card valid until June is still on site in August.

Which is the failure that defeats most sites: verification happens once, at induction, and nothing re-checks.

The fix is structural: hold the expiry date, check it at every access event, and refuse entry when it passes.

Any system that verifies at induction only is verifying that somebody was qualified once.

Who holds the evidence

The individual holds the card.

Their employer holds the training records.

The site needs to know the status and does not need the underlying certificates, which is worth stating because sites routinely collect more than they need and then hold personal data they cannot justify.

Status and expiry date. Not the certificate, not the qualification history, not the medical.

The subcontract obligation

The main contractor cannot train anybody else's operatives.

What it can do is require, in the subcontract, that every person presented is competent for their work, with evidence produced before first access.

And verify a sample rather than everything, which is proportionate and finds the systemic problems.

A subcontractor whose sample fails gets a full check. One whose sample passes repeatedly earns a lighter touch, which is an incentive that costs nothing.

The awkward case

Somebody arrives to do urgent work and their card cannot be verified.

The pressure to admit them is real and the decision should not be the gateman's.

Write the rule in advance: who may authorise a temporary access, on what evidence, for how long, and what supervision applies.

Because an unwritten rule is decided by whoever is under most pressure, and that is always in favour of admitting.

Measuring it

Access attempts refused on expiry, per month, which should be non-zero if the checking is real.

Cards expiring within thirty days, as a forward list, which is the report that prevents the refusals.

Sample verification results by subcontractor.

And the proportion of the workforce whose competence status is unknown, which on many sites is larger than anybody expects and is the honest starting figure.

Plant tickets specifically

Machine-specific and frequently assumed to be general.

A ticket for a telehandler is not a ticket for an excavator, and a ticket for one category of excavator is not a ticket for another.

Which means the gate check has to know what the person is going to operate, and that is information the register does not usually hold.

The practical arrangement: plant operation is authorised by the site separately from access, with a list held by whoever controls the plant.

Two registers, deliberately, because merging them produces a gate check that either blocks everybody or verifies nothing.

When a scheme changes

Card schemes revise their categories, withdraw old cards and introduce transition periods.

Which happens every few years and invalidates part of your held data overnight.

Watch for scheme announcements and re-run the verification against the new rules rather than assuming a held status is still meaningful.

A site running on a cached status from before a scheme change is verifying history.