Construction Compliance for Small and Mid-Size GCs

What does compliance actually mean for a 10-30 worker GC?

Strip away the consultant language and compliance is three questions asked by three people. An inspector asks: is every worker on this site trained and current for the work they are doing? A client’s procurement team asks: can you prove insurance, workers’ compensation clearance, and a safety program before we award this contract? Your own supervisor asks: who on tomorrow’s crew is cleared to work?

A GC that can answer all three from one system, in minutes, is compliant in every way that matters. A GC that answers them by digging through email attachments is gambling that nobody asks on a bad week.

Worker-level vs company-level compliance — what’s the difference?

Worker-level compliance is training: Working at Heights, First Aid/CPR, WHMIS, and trade-specific tickets, each with its own issuer, validity period, and renewal path. It travels with the person.

Company-level compliance is paperwork about the business: Certificate of Insurance (CGL), workers’ compensation clearance (WSIB in Ontario, WorkSafeBC, CNESST in Québec), COR® certification where clients require it, business registration, and bonding. It travels with the contract — and it is what gets requested most often, because every GC-to-sub relationship starts with it.

The two layers fail differently. Worker credentials fail by expiring quietly. Company documents fail by being requested urgently — a clearance certificate that takes three days to produce can cost a contract that closes in two.

How do you handle a compliance package request?

A compliance package is the bundle a GC or owner requests before work begins: typically the COI, workers’ comp clearance, safety program summary, and proof of training for the crew being deployed. The request usually arrives compressed — “by end of week” — because it sits on the critical path of someone else’s contract.

The GCs that handle these calmly keep the package pre-assembled: documents current, expiry-tracked, and exportable in one action. The ones that scramble treat each request as a new project. We wrote up a real example of how these requests unfold in the field — see the Field Notes link below.

What does an inspector or auditor actually ask for?

Training records for the workers present that day, proof the training is current, and — depending on the visit — the company’s safety program and incident records. Inspectors treat expired, unapproved, or unverifiable training as non-compliant; a certificate nobody can validate is functionally the same as no certificate.

During manual verification we regularly find documents that would fail this exact test: reference numbers that do not match the issuer’s records, or reissued cards whose validity actually ran from an earlier completion date. Verifying before the audit is cheap; discovering during one is not.