Subcontractor compliance
A spreadsheet can hold a thousand certificate dates and still miss every decision that matters. Here is where it breaks — and why it breaks at payment time and at audit.
Almost every general contractor starts tracking subcontractor insurance the same way: a spreadsheet, one row per subcontractor, a column for the expiration date. It works — right up to the moment the certificate actually matters, which is the moment a payment releases or a claim arrives. The failure is not carelessness. It is structural.
A spreadsheet cell holding a date does not watch the calendar. Certificates lapse while work continues, and nothing surfaces the gap until someone goes looking — usually when an auditor asks or a payment run needs a green light. By then, the subcontractor may have been working uninsured for weeks. The cell was accurate on the day it was typed; that was the last day it was accurate.
The cost of this structure is measurable. Insurance-industry analyses attribute roughly 65% of general contractor claims to subcontractor work, and the average subcontractor liability claim runs about $125K. The gaps are not rare outliers: a 2026 regulator-data analysis of California contractor licenses found roughly 1 in 17 non-exempt contractors currently lacks the workers’ compensation coverage the state requires. And the spreadsheet itself demands care — industry estimates put manual COI tracking at around 10 to 15 hours a week per coordinator, time spent maintaining cells that go stale anyway.
The deeper flaw: a COI column records what the subcontractor bought, not what the contract requires. Those are different facts. The subcontract specifies limits, additional insured status, endorsement forms, and durations. Comparing a certificate against those requirements is judgment work, and in a spreadsheet world it lives in one person's head. The sheet can tell you a certificate exists. Whether it satisfies the contract is a question the sheet cannot answer.
When a claim lands or an auditor arrives, the questions are not about dates. They are about decisions. Who reviewed this certificate. What they compared it against. What they concluded. Whether anyone noticed the missing endorsement. A spreadsheet holds none of that — a cell that says current, possibly with initials, is not a record of a decision. Every stakeholder reconstructs events from memory, and the reconstruction is exactly as defensible as memory is.
Not a better spreadsheet — a different model. Kernos treats each subcontractor's insurance as an object with requirements extracted from the contract, checks every certificate against those requirements with a rules engine, and turns every gap into a tracked exception with an owner. Verifications and approvals land in an append-only audit chain, so the question of who decided what, when, and on what evidence has a literal answer. And when a certificate is missing or non-compliant, the payment that depends on it stays blocked — the failure surfaces before money moves, not after.
Related reading: how to verify subcontractor insurance before releasing payment, and the subcontractor compliance checklist for payment runs. The platform overview lives here.