How to Track Worker Certifications

Why does certification tracking fail on real job sites?

Most contractors do not lack training records — they lack current ones. Certifications live in a binder in the site trailer, a folder on someone’s laptop, and a spreadsheet that was accurate the week it was built. Every new hire, every renewal, and every sub-trade crew that rotates through makes the copy of record a little more wrong.

During manual verification at WorkSitePass we repeatedly see the same pattern: workers upload certificates that expired months ago, or photos cropped so tightly the expiry date is cut off. The problem is almost never missing training — it is that nobody had one place to check what was current before the worker arrived on site.

The failure mode matters because responsibility sits with the employer. In Ontario, for example, constructors and employers must ensure workers on a construction project have valid Working at Heights training before they work at height — an inspector will not accept “the card is in the truck”.

What should you record for every certificate?

Five fields cover nearly every audit and gate check: the certificate type, the issuing authority, the certificate or card number, the completion date, and the expiry date. The completion date is not bookkeeping trivia — 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.

For certificates that never print an expiry (WHMIS site-specific training, OSHA 10/30 cards in the U.S.), record the employer’s own refresh policy as the working expiry. Most GCs we work with settle on 1–3 years, which keeps every credential on the same review cycle instead of a special-case list.

How do you set up tracking that survives crew turnover?

The systems that survive are the ones where workers carry their own records and admins see the aggregate. When the certificate lives with the worker — in a wallet they keep across employers — a new hire arrives with their history instead of a pile of photocopies, and the admin’s job becomes reviewing, not re-collecting.

Expiry alerts need to fire well before the date: 90, 30, and 7 days out is the cadence we default to, because refresher courses book out weeks ahead in busy seasons. An alert on the day of expiry is a notification that you already have a problem.

Spreadsheet, shared drive, or software — which one?

A spreadsheet works at 5 workers and quietly stops working somewhere before 20 — column owners change, versions fork, and nobody gets an alert because spreadsheets do not send them. A shared drive keeps the documents but answers no questions: it cannot tell you who on tomorrow’s pour is expired.

Purpose-built tracking earns its cost when three things are true: you run more than one active site, you use sub-trades whose certs you have never seen, or an expired certificate has already cost you a morning. If none of those apply yet, a disciplined spreadsheet with a named owner is genuinely fine — start there and move when it breaks.

How does verification fit in?

Tracking tells you a certificate exists; verification tells you it is real and current. A surprising share of what we manually review fails not because of fraud but because of honest confusion — an expired card that “looks valid”, a refresher that was booked but never completed, a provincial certificate used out of scope.

Whatever system you use, add a verification step for the high-stakes certificates: check the issuer’s registry where one exists (Ontario’s MLITSD keeps Working at Heights records), and require the original document rather than a re-photographed photocopy.