How to build a construction training matrix that actually works

A construction training matrix answers one question fast: who is qualified to do what, and until when? You'll also hear it called a skills matrix or competency matrix — same table, same job. The principal contractor asks for it at PQQ stage, the auditor asks for it every year, and you need it yourself every time you plan a crew. Here's how to build one that keeps answering that question — not just on the day you make it.

What goes in: roles × tickets

Start with the roles you actually deploy, then list what each role requires. For a typical contractor:

• Everyone on site — a valid CSCS card (most run five years) and site induction.
• Supervisors and managers — SSSTS or SMSTS, both valid five years, both with a refresher that must be done before expiry or it's the full course again.
• First aiders — first aid at work, typically a three-year certificate; check you have enough per site, not just per company.
• Plant operators — the specific ticket per machine: telehandler, excavator, MEWP. "Can drive a digger" is not a matrix entry; the card category is.
• Drivers — licence categories and, for professional drivers, Driver CPC.
• Sector-specific schemes — if you supply labour to rail, the matrix carries Sentinel competencies too; other sectors have their own equivalents.

Don't forget the entries that aren't people: vehicles have MOT due dates, and lifting equipment has LOLER thorough examination intervals (six or twelve months depending on the kit). They belong in the same overview, because they fail the same way — quietly, on a date.

The structure: one row per certificate

The instinct is a grid — names down the side, tickets across the top, colours in the cells. Resist it, at least for the underlying data. Build a flat list instead: one row per certificate, with columns for name (or asset), certificate type, card number, issue date and expiry date.

Why: the grid hides information. A coloured cell can't hold a card number, an issue date and an expiry date at once, and a grid can't be filtered ("show me everything expiring in the next 90 days") or imported into anything later. Build the list; generate the grid from it when someone wants the wall-chart view. Our free training matrix template comes pre-structured this way.

The single source of truth: the expiry-date column

One rule keeps the whole thing honest: the expiry-date column decides. Not the colour of the cell, not what the worker says, not the photocopy in the drawer. If a card is renewed, the row gets the new date — the moment the certificate comes in, not "when someone gets round to the spreadsheet". Every failure mode of a training matrix traces back to breaking this rule.

And a missing date is a status of its own. An empty cell doesn't mean "probably fine" — it means unverified, which for planning purposes is the same as expired. More on that in why absence has no status.

Traffic lights: 90 and 30 days

Colour the matrix from the expiry date, with two thresholds:

• Amber at 90 days. This is booking territory. Courses fill up, refreshers need scheduling around the programme, and an SMSTS refresher missed by a week means the full five-day course again.
• Red at 30 days. This is intervention territory: if it isn't booked now, plan for that person or vehicle to be unavailable.
• Expired is its own colour — and its own conversation.

The weekly ritual

A matrix is only as good as the last time someone looked at it. Put a 15-minute slot in the same person's calendar every week: filter on amber and red, chase what's unbooked, update what's come in. Name a deputy for holidays. If nobody owns this ritual, you don't have a matrix — you have a snapshot of the past.

Where the spreadsheet stops

Up to roughly 15 people, the ritual holds. Beyond that, the failure modes stack: versions multiply, the checking depends on one person's discipline, renewals land in inboxes instead of the file, and the week before an audit becomes a scramble. The honest comparison with Excel is that the spreadsheet is a fine data structure and a poor alarm system.

That's the point where the same list — because you built it one row per certificate — imports straight into software that does the weekly check nightly and emails people at 90, 60 and 30 days out. Certly is built for exactly that handover; there's a knowledge base covering the individual tickets, and a 14-day free trial if your matrix is ready to graduate.