WSIB Clearance and COI Tracking: Why Spreadsheets Fail on ICI Jobs

It's pay run day. You're about to release $340,000 to six subcontractors. You open the compliance spreadsheet. Three WSIB clearance certificates are current. One expired last week. One shows “Dec” with no year. One sub isn't in the spreadsheet at all because they were added to the project after the tracker was set up.

You now have a choice. Hold the entire pay run while you chase down three subs for updated documents, or release payment and hope nothing goes wrong. Neither option is good. This is what happens when compliance tracking lives in a spreadsheet.

Why WSIB Clearance Matters

A WSIB clearance certificate confirms that a subcontractor is current on their Workplace Safety and Insurance Board premiums. It means the sub is in good standing and their workers are covered.

Here is where it gets serious. If a general contractor pays a subcontractor who does not have a valid WSIB clearance, and a worker on that sub's crew is injured, the GC can be held liable for the sub's WSIB obligations. That is not a theoretical risk. It happens.

WSIB does provide an online portal for verification, but the process is manual. You enter each sub's information one at a time, check the result, and record it somewhere. On a project with 20 active subs, that's 20 manual checks every time you run a payment cycle.

Why COI Tracking Is Just as Critical

Most ICI contracts require subcontractors to carry Commercial General Liability (CGL) insurance, typically in the range of $2M to $5M. The certificate of insurance (COI) proves the policy is active and lists the required coverage limits.

COIs have the same problem as WSIB certificates: they expire. A sub's COI from project start might be six months expired by the time you're processing their fifth progress billing. Insurance policies can also lapse mid-project if the sub misses a premium payment. The certificate you have on file means nothing if the underlying policy is no longer active.

What to Watch For

• Expiry dates. CGL policies typically renew annually. On a 14 month project, every sub's COI will expire at least once.
• Additional insured endorsements. Many GC contracts require the owner and GC to be listed as additional insureds on the sub's policy. The standard COI doesn't always confirm this. You need the endorsement.
• Coverage limits. A sub might have a $2M policy when your contract requires $5M. The certificate looks valid, but the coverage is insufficient.
• Policy lapses. A sub's insurer can cancel a policy mid-term. Unless you are listed for notice of cancellation, you won't know until it's too late.

Why Spreadsheets Fail at This

Spreadsheets are fine for a lot of things. Compliance tracking on active ICI projects is not one of them. Here is why.

No Automatic Expiry Alerts

You can put an expiry date in a cell. You can even use conditional formatting to turn it red when it passes. But nobody is watching that spreadsheet every day. By the time someone opens it for a pay run, the certificate has been expired for two weeks and the sub hasn't been notified.

No Link Between Compliance and Payment

The spreadsheet that tracks WSIB and COI status is completely disconnected from the system that processes payments. A controller can look at the spreadsheet, see a green cell, and approve the payment. But that green cell might be based on data entered three months ago that nobody has updated.

No Audit Trail

If a dispute arises, can you prove that you verified the sub's WSIB clearance on the specific date you released payment? A spreadsheet doesn't record who checked what, or when. You have a current snapshot, not a history.

No Single Source of Truth

On most projects, the compliance spreadsheet exists in at least three versions. The PM has one. The controller has another. The project coordinator emailed a copy to the owner last month that's now out of date. When the WSIB certificate comes in, it gets updated in one version and forgotten in the others.

No Proof of Verification at Time of Payment

This is the one that keeps controllers up at night. If something goes wrong, you need to demonstrate that your compliance process was followed at the time each payment was made. A spreadsheet with today's date on it proves nothing about what you knew six months ago when you released that draw.

What a Proper System Does

The fix is not a better spreadsheet. It is a system that ties compliance directly to payment gates.

Compliance Gates on Every Pay Run

Before a payment is released, the system checks the sub's WSIB clearance and COI status automatically. If the WSIB certificate is expired, the payment is blocked. The controller is notified. The sub is notified. Nobody has to remember to check. The system enforces it.

Automated Expiry Alerts

Thirty days before a WSIB certificate or COI expires, the sub gets a notification. Fourteen days out, the controller gets one too. By the time the document actually expires, everyone has had ample warning.

Timestamped Audit Trail

Every compliance check is logged with a timestamp, the user who reviewed it, and the document that was verified. If a question comes up 18 months later, you can pull the exact record showing that the sub's WSIB clearance was valid on the date you released payment number four.

Exception Handling with Accountability

Sometimes a payment needs to go out before a document is updated. A good system allows exceptions, but it records them. Who approved the exception, when, and why. That's the difference between a process and a shortcut.

Getting Started

If you are currently tracking WSIB and COI in spreadsheets, you are not alone. Most mid-size Ontario ICI firms do the same thing. The transition doesn't have to be painful. Start with your next project. Set up compliance gates on the pay run. Let the system handle the alerts and the audit trail.

The goal is simple: never be in a position where you are guessing whether a sub is compliant at the moment you release their cheque. Know for certain, and have the records to prove it.