The framing sub on a mid-rise project north of Toronto had a clean binder. Certificate of Insurance — current. WCB clearance — dated this month. COR certified, business registration in order, bonding letter on file. The general contractor's office had reviewed all of it before the contract was signed.
Monday morning, 7:04 AM, four sub workers arrived at the gate. The supervisor had paperwork on the company that employed them. He had nothing on the four men themselves.
The sub's foreman vouched for his crew. They went up.
The contract is between two companies. The risk is between four workers and a roof.
Why the paperwork covers the wrong thing
The compliance package a GC collects from a sub before the contract starts — COI, WCB clearance, COR certificate, business registration, bonding — is contract-level documentation. It tells the GC the sub exists as a real business, is insured, has a safety program on paper, and can stand behind its obligations financially.
It tells the GC nothing about whether the four men swinging hammers today have a current Working at Heights ticket, an in-date WHMIS, or a First Aid card from an approved provider. That information lives in the sub's HR file. The GC has no contractual right to it, no realistic way to audit it, and usually no system that would let them see it even if they did.
So the GC ends up with strong documentation about the company and no documentation about the people. The two layers don't talk to each other.
"They're good" is not a control
In practice, the gap gets closed by a sentence. The sub's foreman says his crew is good, and the GC's supervisor accepts that and moves on. It's not that anyone's lying — the foreman believes his crew is good, because last he checked they were.
But the foreman doesn't carry the certs. They live in the sub's office. One worker is new this week and his ticket lapsed last month while he was between sites. One was pulled from another job at the last minute and never finished orientation here. The foreman doesn't know in real time. His vouch is a guess dressed up as a confirmation.
The GC's supervisor accepts the vouch because the alternative is calling the sub's office at 7 AM and asking for five certificates over the phone before the crew can start. Nobody does that. So the system runs on trust, and trust mostly works — until the morning it doesn't.
What the inspector sees
When a Ministry of Labour inspector arrives at 1:30 PM and asks to see Working at Heights certificates for the four workers on the roof, the chain that closes the gap on a normal morning becomes the chain that breaks under scrutiny.
The GC turns to the sub. The sub turns to the office. The office is closed, or the file is on someone's laptop, or the cert lapsed six months ago and nobody on site knew. The inspector isn't asking the sub. The inspector is asking the GC — because the GC is the one running this site, with this schedule, carrying this liability.
The paperwork that proves the sub is a real company doesn't help in that conversation. The paperwork that would help — current, verifiable, per-worker — is the paperwork the GC never had.
You can't subcontract liability. You can only subcontract the paperwork — and only one of those stays with the sub.
What changes when the wallet travels with the worker
The structural fix isn't more paperwork from the sub. It's the same paperwork, stored against the worker instead of the company, and visible to whoever is running the site they're standing on today.
When each worker carries a verified wallet, the GC sets the site's requirements once — Working at Heights, WHMIS, First Aid, site-specific orientation — and every worker who shows up, regardless of which sub employs them, shows green or red against those requirements before Monday morning. The foreman's vouch becomes a status. The sub's office stops being a single point of failure. The GC sees the same readiness data the sub does, from the same source, in the same view.
The contract still covers what contracts cover. The site finally covers what sites need to.