How to Build a Certification Tracking Spreadsheet (and When It Stops Working)

What columns does a certification tracking spreadsheet need?

Seven, one row per certificate (not per worker): worker name, certificate type, issuing authority, certificate or card number, completion date, expiry date, and verification status. Add an eighth column for a link to the document scan if your sheet lives next to a shared drive.

Completion date and expiry date are separate columns on purpose. For Ontario Working at Heights, the 3-year validity runs from the date the course was completed — not the date printed on a reissued card — so a sheet that only records “expiry” inherits whatever mistake the card made. Record both and calculate.

Verification status is the column almost everyone skips, and it is the one that matters in an audit: “received” and “verified against the issuer” are different claims. A simple three-value convention works — unverified, verified, expired.

How do you make a spreadsheet warn you about expiries?

Two formulas get you most of the way. A days-remaining column — the expiry date minus TODAY() — and conditional formatting that turns the row yellow under 90 days and red under 30. Sort by days remaining every Monday and the sheet reads like a work queue.

What a spreadsheet cannot do is tell anyone anything. Nobody gets a push notification, an email, or a text — the warning only exists when someone opens the file and looks. Every lapsed certificate we see traced back to a spreadsheet failed exactly here: the formatting turned red on schedule, in a file nobody had open that week.

Who owns the spreadsheet — and what triggers an update?

One named owner, three update triggers: a new hire, a renewal, and a worker assigned to a new site. If updating is “everyone’s job”, the sheet forks — a site copy, an office copy, a foreman’s personal copy — and within a month nobody knows which one is real. We wrote up a real case of exactly this in Field Notes; the pattern is common enough that we can usually guess the ending.

Put the owner’s name in the sheet header and the update triggers in the first row. It feels bureaucratic; it is the difference between a record and a rumour.

When does the spreadsheet stop being enough?

Three triggers, any one of which is the signal: you run more than one active site, you deploy sub-trade workers whose certificates you have never personally collected, or an expired certificate has already cost you a morning at the gate.

Until then, a disciplined sheet with a named owner is genuinely fine — start there. When you cross a trigger, the move is not a bigger spreadsheet; it is a system where workers carry their own verified records and alerts fire without anyone opening a file. The next guide in this series compares the two options honestly, including cost.