From spreadsheet to training matrix software in one afternoon

Every training matrix starts the same way: someone opens Excel, types the names down the side and the tickets across the top, and colours the cells. For ten people it works. The trouble is that nothing tells you when it stops working — the spreadsheet fails quietly.

How the spreadsheet fails

It doesn't crash. It just drifts:

• Nobody owns the checking. The matrix only warns you if someone opens it, scans the dates and does the mental arithmetic. On a busy week, nobody does.
• The copy problem. The version on the server, the version in the site manager's inbox, the version the client was sent at PQQ stage — three matrices, three truths.
• Dates go stale silently. A renewed card gets handed in, the wallet copy gets updated, the spreadsheet doesn't. Now the matrix says "expired" for someone who's fine — or worse, "fine" for someone who's expired.
• The person who built it leaves. The formulas, the colour rules, the tab nobody understands — gone with them.

None of this shows up until a gate check or an audit finds the gap. By then it's a very expensive spreadsheet.

The fix is not a better spreadsheet. It's moving the same data into something that checks the dates every day and emails the right people at 90, 60 and 30 days out. Here's how to do that in one afternoon.

Step 1: clean the dates (30 minutes)

Open your current matrix and fix the one thing that breaks every import: inconsistent dates. "May 2026", "05/2026", "ASAP", a cell coloured green with no date at all — turn each of them into a real date. If you genuinely don't know an expiry date, leave the cell empty rather than guessing; an honest gap is better than a confident wrong answer.

While you're in there, delete people who've left and tickets you no longer require. You're about to give this data a long life — don't carry the clutter across.

Step 2: one row per certificate (30 minutes)

A classic matrix is a grid: people down the side, tickets along the top. Software wants a list: one row per certificate, with columns for name, certificate type, number, issue date and expiry date. So "Dave Miller, CSCS, first aid, telehandler" becomes three rows, not one wide one.

This feels like a step backwards. It isn't — the grid view comes back on screen, but the list format is what makes importing, filtering and reminders possible. If you'd rather start from a clean structure, our free training matrix template is already laid out this way.

Step 3: import (10 minutes)

Upload the file. A good import shows you, line by line, what it created and what it skipped — and why. Fix the handful of rejects (usually a date typo) and run it again. If you're weighing up whether the move is worth it at all, the Excel comparison page sets the two side by side honestly.

Step 4: check the role requirements (20 minutes)

Now do the thing the spreadsheet never did well: define what each role requires. A site supervisor needs SSSTS; a driver needs a valid Driver CPC; everyone through the gate needs a current CSCS card. Once requirements are attached to roles, the gaps surface themselves — including the person who was hired last month and never made it onto the matrix at all. That's also the moment you discover why absence needs a status: a missing certificate should look as loud as an expired one.

Step 5: switch on the reminders (5 minutes)

This is the step that retires the spreadsheet for good. Set the reminder thresholds — 90, 60 and 30 days before expiry is the sensible default, because training courses need booking weeks ahead. Point the emails at the right people: the certificate holder, and whoever books the training. From this point the question is no longer "has anyone checked the matrix lately?" but "have you read your email?"

One afternoon, honestly

Clean, restructure, import, define, switch on: for a company of 30–50 people this is genuinely an afternoon, most of it in steps 1 and 2. Certly was built around exactly this import path — the pricing page shows what it costs after the trial, and you can start free for 14 days with the import included. Bring the spreadsheet; leave with a system that checks itself.