Track Every Subcontractor's Certificate of Insurance Before a Lapsed Policy Becomes Your Claim

The Signal

A subcontractor's insurance certificate sits in a project folder from the day work started. Eighteen months later, that subcontractor is on-site when someone gets hurt, or a piece of equipment damages a client's property. The general contractor pulls the certificate to file a claim against the sub's policy — and finds out the policy lapsed eleven months ago. The sub kept working. Nobody checked. Now the claim lands on the GC's own liability policy instead, premiums go up at renewal, and the client relationship absorbs the damage regardless of whose insurance was supposed to cover it.

That is the actual failure mode. It is almost never that a subcontractor never had insurance — it is that the insurance existed on day one, got filed, and was never looked at again.

Why this matters now

Businesses that coordinate subcontractors, vendors, or gig-based crews collect a certificate of insurance (COI) at onboarding because a client or a general liability policy requires it. That collection step is usually solid — someone asks for the COI before issuing a badge, a PO, or site access. The gap opens after that: a COI is a snapshot of coverage on the date it was issued, with a policy period that typically runs 6 to 12 months, and most companies have no process that revisits it before the next renewal cycle, if ever.

As a subcontractor roster grows, so does the number of silently expiring documents sitting in a shared drive. A company running five subcontractors can eyeball this manually. A company running fifty cannot, and the fifty-sub company is usually the one that only finds out it has a problem after a claim is already open.

The mistake to avoid

The common mistake is treating the COI as a one-time intake requirement instead of a dated instrument with an expiration. Teams build a solid checklist for onboarding — collect COI, verify the coverage limits meet contract requirements, file it — and then nothing fires when that same document stops being current. The document still exists. It still looks official sitting in the folder. Nobody schedules a recheck because the original collection felt like the finish line.

The expiration math nobody runs

Run this on your own roster: pull every active subcontractor's COI and check the policy expiration date against today, not against when you collected it. Two numbers matter here — how many certificates expire in the next 60 days, and how many have already expired without a renewal on file. Most companies that haven't run this before find at least one lapsed certificate on an active vendor. The certificate itself usually names an effective date and expiration date, along with the policy types and limits — general liability, workers' comp, auto — and whether your company is listed as an additional insured, which determines whether their policy actually responds on your behalf in a claim (see the overview of how additional-insured status works: https://en.wikipedia.org/wiki/Additional_insured). A COI with the wrong limits or missing additional-insured language protects you less than you think even while it's current.

What stays protected

Tracking expirations is not a reason to create friction with subcontractors who carry adequate coverage, and it is not a excuse to drop a vendor mid-project over a paperwork delay you could have flagged weeks earlier. The person who owns this process should have one job: flag upcoming expirations early enough that renewal is a routine ask, not an emergency, and distinguish a genuinely lapsed policy from a renewal that's simply in transit. Don't let this process become a weapon to end a subcontractor relationship pretextually — the point is risk visibility, not vendor management leverage.

The first move

Pull your current subcontractor or vendor list and check how many of them have a COI on file with an expiration date more than 30 days in the past. If you don't know the answer in under ten minutes, the gap isn't your subcontractors' insurance — it's your own tracking.

The move this week

Build a simple expiration tracker — a dated field per subcontractor is enough to start — and set a 60-day-out alert for every COI on file. Require a current COI before any PO or site access is issued, and make a fresh certificate a condition of starting the next job, not just the first one.