It started as a reasonable solution.
A mid-size subcontractor in Edmonton — residential and light industrial, 40 to 50 workers depending on the season — built a certificate tracking spreadsheet in 2019. One column for each certificate type. One row per worker. Colour-coded by expiry status.
By 2024, three different people had edit access. There were two versions saved to the shared drive with different filenames and different dates. Nobody was sure which one the GC had last seen.
The spreadsheet didn't fail all at once. It failed slowly, across dozens of small decisions that each seemed fine at the time.
The Friday email
It arrived at 4:47 PM on a Friday. The general contractor needed an updated compliance list — current certificates, current statuses — for a new site starting Monday.
The office admin opened the spreadsheet. Then opened the other one. Neither matched the actual certificates on file. Two workers had renewed their Working at Heights tickets and nobody had updated the file. One worker's First Aid had expired in September. It was November.
Nobody had caught it because nobody had looked at the spreadsheet since August. And in August, the expiry column showed October 2024 — which was still three months away, which seemed fine, which meant nobody flagged it.
Why spreadsheets fail at this
Spreadsheets are passive. They store what you put in them and show it back when you open them. They don't alert you at 90 days before expiry. They don't tell you when a certificate has been renewed and the file hasn't been updated. They don't know when two people have edited different versions and diverged.
They require a person to do all of that — to check regularly, update correctly, and catch the things that drift. On a busy site, with a small office team, that person has other things to do.
The spreadsheet isn't the problem. The problem is using a static file to manage a dynamic situation.
What the shift looks like
Companies that have moved away from the spreadsheet model typically describe the same thing: the system alerts them, instead of them having to remember to check.
When a certificate is 90 days from expiry, the admin gets notified. When it hits 30 days, the worker gets notified. When it expires, it shows up in the dashboard as non-compliant — not hidden in a row of a spreadsheet that might or might not be the current version.
The live readiness view replaces the "Friday scramble" because the information is always current. When a GC asks for a compliance list, it takes seconds — not a weekend.
The question isn't whether your system works. It's whether your system works when nobody's looking at it.
Expiry tracking at WorkSitePass runs in the background. Certificates are uploaded once, verified once, and then tracked automatically until renewal. The spreadsheet doesn't go away — but it stops being the system that sites depend on.