What Happens When Vendor Insurance Lapses Mid-Contract

A vendor insurance lapse is not a hypothetical risk. It happens regularly and without warning to the hiring party. A vendor who was compliant at onboarding - whose COI was verified, filed, and approved - can become uninsured while actively performing work on your contracts. The COI in your files is still there. The coverage it described may not be.

Here's why lapses happen, what the exposure window means for you, and how to build a monitoring program that catches them.

How Insurance Lapses Happen

Non-payment: The most common cause. Commercial insurance premiums can be paid monthly, quarterly, or annually. A vendor who misses a payment receives a cancellation notice - typically 10-30 days - and if the premium isn't paid, the policy cancels. The vendor may continue working without telling you (or without even fully tracking their own coverage status).

Carrier non-renewal: Insurance carriers can choose not to renew a policy at expiration. If the vendor doesn't secure replacement coverage before the expiration date, they have a coverage gap. They may know about this. They may not have addressed it.

Coverage reduction mid-term: A vendor may not lose coverage entirely but may modify it - reducing limits, removing endorsements, or changing coverage types - mid-term. These mid-term changes can create compliance gaps even when the policy is technically active.

Policy endorsement removal: A vendor who added you as an additional insured at contract start may later have that endorsement removed - by their agent, by their carrier, or inadvertently. The ACORD 25 in your files still shows the AI box checked.

Business changes: A vendor who changes legal entities, merges with another company, or restructures their business may create a mismatch between their new business structure and the named insured on their existing policy.

The Exposure Window

During a lapse, the vendor is uninsured. Work continues. Your exposure continues. If an incident occurs during the lapse period:

• The vendor's prior insurer may deny the claim (coverage was not in force)
• The vendor's subsequent insurer may deny the claim (it happened before the new policy incepted)
• There may be no coverage at all

The hiring party - you - becomes the financially responsible party for a loss that your contract assumed would be covered by the vendor's insurance. The $500,000+ cost of an uninsured incident applies here with full force.

The lapse window is often short - days to weeks. But that window coincides with ongoing work and ongoing risk. A single incident during that window is enough.

Why Standard COI Tracking Misses Lapses

The standard COI compliance workflow verifies coverage at two points: onboarding and renewal. Mid-term lapses fall between these checks.

If a vendor's annual policy runs January to December and you verify in January, your next check may not happen until October or November to catch the renewal. A policy that cancels for non-payment in June creates a six-month window where you have no awareness of the gap.

Most manual programs have no mechanism for detecting mid-term lapses. They're invisible until a claim surfaces them.

How to Detect Lapses Before Incidents

Cancellation notice provisions: Standard commercial policies require the insurer to provide notice of cancellation to certificate holders - typically 30 days for most cancellations, 10 days for non-payment cancellations. This is your early warning system, but only if:

1. You're listed as a certificate holder
2. The notice reaches someone in your organization who acts on it
3. The process for receiving and responding to cancellation notices is defined

Continuous monitoring services: Some COI compliance platforms offer continuous monitoring - checking vendor policy status against carrier data on a regular basis, not just at renewal. This is more reliable than relying on cancellation notices, which can be slow or misdirected.

Mid-term COI requests for high-risk vendors: For vendors with the highest risk exposure - those performing ongoing work on your premises - consider requesting updated COIs mid-year, not just at renewal.

The Mid-Term Change Problem

Policy cancellation is visible - there's a cancellation date. Mid-term changes are harder to detect. A vendor who removes your AI endorsement mid-term won't trigger a cancellation notice. Their policy is still active. Their COI from January still shows the AI box checked. You have no way to know the endorsement was removed without requesting a new COI or requiring the carrier to notify you of coverage changes.

For your highest-risk vendor relationships, contractual language requiring notice of any material coverage change - not just cancellation - provides additional protection. Some sophisticated risk programs require direct notification from the carrier (not just the vendor) of any mid-term changes.

Building a Monitoring Program That Catches Lapses

A monitoring program for mid-term lapses has four elements:

1. Cancellation notice receipt: Ensure you're properly listed as certificate holder on every active vendor policy, so cancellation notices route to your team.

2. Defined response process: Someone needs to own the process of receiving, logging, and acting on cancellation notices. An unread email isn't a monitoring system.

3. Continuous or periodic mid-term checks: For high-risk vendors, don't wait for the annual renewal cycle. Request updated COIs quarterly or at project milestones.

4. Technology monitoring: Platforms that integrate with carrier data or use AI to monitor policy status can flag lapses in near-real-time rather than waiting for a notice to arrive.

The goal is to know about a lapse before an incident - not to discover it while investigating a claim.

Bramble monitors vendor compliance status continuously and alerts you to lapses, expirations, and coverage changes as they occur. See how it works.