Everything was green. Something was still missing.

The matrix was green from top to bottom. Every ticket in date, nothing expiring inside ninety days. The contracts manager walked into the principal contractor's audit feeling, reasonably, quite good.

And came out with a non-conformance.

Not because anything had expired. Because one of the scaffolders had no IPAF ticket. He'd started in the spring, handed over a perfectly valid CISRS card, and nobody had ever established that his role required anything else. The mobile tower he'd been using for months was, on paper, being used by an unqualified man.

The blind spot is built in

This isn't carelessness, and it's worth seeing exactly why — because it's a property of every system that watches expiry dates, from the scruffiest spreadsheet to the smartest software.

An expiry tracker works on the documents you've put into it. For each one it counts the days remaining and raises a flag when the number gets small. As a design, that's sound. But it can only ever make statements about documents that exist.

A certificate that was never supplied doesn't expire. It has no expiry date, so it gets no colour, so it appears in no list and triggers no reminder. It isn't red. It isn't amber. It's simply absent — and absence has no status.

Which is how a matrix can be honestly, accurately, completely green while a scaffolder is missing his IPAF ticket. The matrix isn't lying. It's answering a narrower question than the one you thought you asked.

Two different questions

Your question, looking at the matrix on a Monday morning, is: what do I need to renew soon? A planner's question, and a fair one.

The auditor at the gate — or the principal contractor, or the HSE inspector after an incident — asks a different one: does everyone on this site hold the tickets their work requires? That's not a question about dates at all. It's a question about completeness, and a wall of green dates doesn't answer it.

Most firms can answer the first question and only believe they can answer the second. The gap shows itself at the same three moments every time: a new starter, an agency lad brought in for a busy fortnight, and someone moving trades — the labourer who's now spotting for the crane, the groundworker who's suddenly in the MEWP. Exactly the moments when someone should run through a required-tickets list, and exactly the moments when that list exists only in the site manager's head, on a site the manager isn't on.

Write the requirement down once

The fix is not "pay more attention". Attention is the resource that was already missing. The fix is turning the requirement itself into data.

That means role requirements: a stated list, per role, of what's mandatory. A scaffolder needs CISRS, and IPAF if he'll touch a MEWP — each with its own validity clock. A telehandler driver needs his CPCS or NPORS category. A supervisor needs the SSSTS or SMSTS layer on top. You define each role once, attach every worker to a role, and from that moment the question flips:

• On a worker's page, every required ticket shows as present or missing — and missing is now a visible status, with a colour, sitting right next to the expiry warnings.
• Across the whole workforce, you get one list of every gap: who's missing what, before an auditor compiles that list for you.

A new starter stops being an empty row that looks fine because it contains nothing red. He becomes a checklist with open items — which is what he actually is.

This is less work, not more

The objection writes itself: more admin. But notice that the requirement already exists — in your safety management system, in the principal contractor's minimum standards, in the method statement, in somebody's head. You're not inventing rules; you're attaching existing rules to the people they govern, once, instead of re-remembering them at every gate.

If you're building this from scratch, how to build a construction training matrix walks through it, and our free training matrix template gives you the grid. But be honest about what a spreadsheet can and can't watch: it will hold the roles, and it will still say nothing when a row is quietly incomplete — least of all in the week before the audit, when you've no time to cross-check anything.

That's why role requirements are built into Certly: define the role, attach the crew, and "missing" finally gets what it never had — a status. Green starts meaning what you always assumed it meant: not just nothing expiring, but nothing absent.

See your first gap in ten minutes. Try Certly free for 14 days — no card required.