WorkSitePass
All guides

Construction Compliance

Managing Sub-Contractor Certifications Without the Blind Spot

Published 2026-07-15·Last reviewed 2026-07-15·Reviewed by the WorkSitePass Compliance Team·6 min

Managing sub-contractor certifications means treating a sub’s credentials as a standing requirement — visible to you, current, for the life of the contract — instead of a one-time package collected at signing. The GC rarely trains the sub’s workers, but on a multi-employer site the GC carries constructor-level responsibility when an untrained one gets hurt, which makes “their office handles it” the most expensive sentence in construction.

Why are sub-trade certifications the classic blind spot?

Because nobody owns them end to end. The sub’s employer owns the training; the GC owns the site; the worker owns the card. Each party reasonably assumes another is checking — and the result is that sub-trade credentials are the documents a GC is least likely to have ever seen, on the workers most likely to rotate without notice.

The exposure is not theoretical. On Ontario projects the constructor must ensure that every employer and worker on the project complies with the OHSA — “we assumed the sub handled training” has never been a defence. The same logic applies under OSHA’s multi-employer citation policy: controlling contractors can be cited for hazards created by subs.

What should a GC collect from every sub?

Two layers, same as your own compliance. Company documents: workers’ compensation clearance (WSIB, WorkSafeBC, or CNESST depending on province) and a Certificate of Insurance naming appropriate coverage — both current, not photocopies from last year’s bid. Worker credentials: the specific certifications your site requires for the trades the sub is deploying — heights, WHMIS, first aid coverage, equipment tickets.

Collect against the site’s requirements, not against a generic list. A drywall sub’s crew and a roofing sub’s crew have different mandatory tickets; asking every sub for everything produces piles of paper nobody reviews.

Why do one-time compliance packages fail?

A package collected at contract signing is a photograph of a moving target. Clearance certificates lapse in 90 days; insurance renews annually; worker certificates expire on their own schedules; and the crew that shows up in month four often isn’t the crew whose certificates are in the binder.

During manual verification we see the month-four problem constantly: the documents on file are genuine, current — and belong to workers who are no longer on the site. The package didn’t fail; the assumption that a snapshot stays true did.

What does a standing requirement look like in practice?

Three properties: the sub’s documents live somewhere the GC can see without asking; expiries alert both parties before they land; and new workers joining the sub’s crew are checked against the site’s requirements at assignment, not discovered at the gate.

Contract language helps — make current documentation a payment condition, not a courtesy — but the mechanism matters more than the clause. A shared system where the sub’s workers carry their own verified credentials removes the whole collect-chase-recollect cycle: the GC checks readiness instead of collecting paper.

Frequently Asked Questions