What Happens When a Subcontractor's Insurance Lapses Mid-Project?

When a subcontractor's insurance lapses mid-project, the general contractor absorbs the risk. An incident during the coverage gap can fall back on your policy, void indemnity protection, and trigger claims your carrier may deny.

The certificate of insurance you collected at kickoff proves coverage existed on one day. It says nothing about whether that coverage is still active six weeks later when a sub's employee falls off a scaffold. That gap between "verified once" and "in force today" is where general contractors get hurt.

The Exposure Chain: What a Lapse Actually Puts at Risk

A subcontractor's coverage rarely fails in isolation. When it lapses, several protections you were counting on quietly disappear at the same time.

• Direct liability. If a sub causes property damage or injury while uninsured, the injured party looks up the chain — often straight to the general contractor with the deepest pockets and the highest policy limits.
• Indemnity agreements. Your subcontract likely requires the sub to defend and indemnify you. A sub with no coverage and no assets cannot honor that promise, leaving the indemnity clause worth little more than the paper it is printed on.
• Additional insured status. Being named as an additional insured on a sub's policy only helps while that policy is active. Once it lapses, so does your standing to tender a claim to their carrier.
• Your own loss history. Claims that should have hit the sub's policy instead land on yours. That drives up your experience modifier and future premiums for years.
• Contract and lender compliance. Many project owners and lenders require every tier to carry continuous coverage. An uninsured sub can put you in breach of your prime contract.

This is general information, not legal or insurance advice. The specific outcome depends on your subcontract language, your state, and your carrier's terms.

Why Coverage Lapses Without Anyone Noticing

Coverage does not usually vanish with a dramatic cancellation notice. It erodes quietly, which is exactly why lapses slip past busy project teams.

Common causes include:

• Non-payment. A sub misses a premium installment and the carrier cancels, often with little warning that reaches you.
• Ordinary expiration. Most policies run 12 months. A project that stretches past the certificate's expiration date outlives the coverage it documented.
• Policy changes. The sub switches carriers, drops a coverage line, or lowers limits below what your contract requires — and never sends an updated certificate.
• Reduced aggregate limits. Earlier claims on the same policy can exhaust the aggregate, so the "coverage" on the certificate no longer has room left for your loss.

The certificate of insurance itself compounds the problem. A COI is a snapshot, not a live feed. It reflects the policy on its issue date and carries no obligation for the carrier to tell you when things change. The standard "endeavor to notify" language on many certificates does not guarantee you will hear about a cancellation at all.

The Incident Timing Problem

The danger of a lapse is not the paperwork gap — it is the accident that happens inside it. Liability attaches based on when the loss occurs, not when you last checked a certificate.

Picture a framing sub whose policy expired on the fifteenth. On the twentieth, a stack of material tips and injures a passerby. It does not matter that you had a valid COI in your file from the project's first week. On the day of the incident, that sub was uninsured, and the claim flows toward whoever still has coverage.

Because most claims surface days or weeks after the event, you often learn about the lapse and the loss at the same moment — far too late to fix either. Continuous verification is what closes this window, and it is the single practice that separates contractors who get surprised from those who do not.

How to Catch a Subcontractor Insurance Lapse Before It Costs You

Catching a lapse early is a process, not a one-time document review. These steps keep coverage verified for the full life of the project.

1. Collect a current COI before any sub sets foot on site. No certificate, no work — treat it as a gate, not a formality.
2. Read the certificate against the contract. Confirm coverage lines, limits, additional insured status, and waiver of subrogation actually match what your subcontract requires.
3. Record every expiration date. Log the earliest expiration across all policies on each certificate, because coverage is only as continuous as its first gap.
4. Set reminders ahead of expiration. Chase renewals 30 days out, not on the day the policy dies. Build in time for the sub to produce updated paperwork.
5. Re-verify after renewal. A promise to renew is not proof. Require the actual updated certificate before removing the flag.
6. Halt work on lapsed coverage. Pause a sub's activity the moment coverage cannot be confirmed, and document that you did so.
7. Keep an audit trail. Retain every certificate version so you can show continuous coverage if an owner, lender, or claim ever demands it.

For a general contractor juggling dozens of subs across several jobs, doing this by hand in a spreadsheet does not scale. Reminders get missed, and a single overlooked renewal reopens the exposure chain.

What to Do the Moment You Discover a Lapse

Finding a lapse is not the emergency — how fast you respond is what limits the damage.

• Stop the affected sub's work until coverage is confirmed reinstated or replaced.
• Request a new certificate immediately showing active coverage and the required endorsements.
• Document the timeline of when you found the lapse and what you did, in case a claim references that period.
• Notify your own broker if the gap overlapped active site work, so you are not blindsided later.
• Review the subcontract for your rights to withhold payment or backcharge for compliance failures.

Modern COI tracking software turns this reactive scramble into routine maintenance by flagging expirations before they become gaps. TradeGuard tracks expiration dates across every subcontractor and sends reminders ahead of each renewal, so a lapse surfaces as an alert instead of a lawsuit.

Frequently Asked Questions

Is the general contractor liable if a subcontractor's insurance lapses?

Potentially, yes. If a sub causes a loss while uninsured, injured parties and their attorneys typically pursue the general contractor's policy, and a lapsed sub usually cannot honor its indemnity obligations. The exact outcome depends on your contract and jurisdiction.

Does a certificate of insurance guarantee coverage stays active?

No. A COI documents coverage only as of its issue date and does not obligate the carrier to notify you of a later cancellation or non-renewal. Continuous verification is the only way to confirm coverage is still in force.

How often should general contractors verify subcontractor insurance?

Verify at onboarding, again before each policy's expiration date, and after any renewal. On long projects, coverage should be confirmed as active for the entire time the sub is on site, not just at kickoff.

What is the difference between an expired and a cancelled policy?

An expired policy reached the end of its term without renewal, while a cancelled policy was terminated early — often for non-payment. Both leave the subcontractor uninsured, and both shift risk up the chain to the general contractor.

Can I keep a subcontractor working while their coverage is being renewed?

It is safer not to. Any incident during an unconfirmed gap can fall back on you, so most contractors pause work until an updated certificate proves coverage is active again.

Keeping every subcontractor's coverage verified through the entire project is exactly the gap TradeGuard is built to close. See how continuous tracking works with a free 14-day trial.