Guide
Insurance Certificate Expiration Tracking: A Practical Guide
Tracking certificates of insurance (COIs) from vendors is a different problem from tracking your own insurance policies. You do not control the renewal — the vendor does. The COI in your files does not auto-update when their policy renews. And when an incident happens with a vendor whose insurance lapsed three months ago, the liability exposure falls on whoever was supposed to be monitoring it. This guide covers how to collect, verify, and track COIs across all your vendors and contractors — before coverage gaps become claims exposure.
COI vs insurance policy — not the same thing to track
| Aspect | Certificate of insurance (COI) | Insurance policy |
|---|---|---|
| What it is | A summary document (ACORD 25) issued by the vendor's insurance agent, listing active coverage types, limits, and expiration dates | The full insurance contract between the policyholder and the insurer |
| Who holds it | The party requiring proof of insurance — the project owner, landlord, or contracting company | The insured — the vendor, contractor, or service provider |
| What it proves | That coverage was active on the date the COI was issued — not necessarily that it is still active today | The terms, conditions, exclusions, and limits of the coverage in full |
| Expiration date meaning | The date shown on the COI is the policy expiration — not the COI document itself. COIs are point-in-time snapshots. | The date the coverage actually terminates — unless renewed or extended |
| What to track | The policy expiration date on the COI — and request a new COI when the policy renews | Tracked by the policyholder — not by the party requiring proof |
The ACORD 25 is the standard COI form used in North America. For reference on what fields appear and what they mean, see ACORD.org.
Who needs to track COI expirations — and what's at risk when they don't
General contractors
Volume: High — can reach 10–30+ subs per active projectCollects from: All subcontractors on every project
Coverage required: GL, WC, umbrella — per contract requirements
Liability exposure: GC is liable for subcontractor incidents if the sub's insurance lapsed and GC did not verify current COI
Property owners / landlords
Volume: Medium — one COI per tenant, one per major vendorCollects from: Tenants (commercial), vendors, maintenance contractors
Coverage required: GL minimum — often specified in the lease agreement
Liability exposure: Landlord named as additional insured on tenant's COI — lapsed COI removes additional insured protection
Operations / facilities teams
Volume: Low-medium — 5–20 active vendor COIs at any timeCollects from: Janitorial, HVAC, elevator, security, landscaping vendors
Coverage required: GL and WC — standard for any vendor with on-site access
Liability exposure: A vendor incident (slip and fall, equipment damage) is uninsured if the COI on file is expired
Event organizers / venues
Volume: Variable — concentrated around event datesCollects from: Vendors, caterers, entertainment, AV companies
Coverage required: GL — often event-specific with venue as additional insured
Liability exposure: Incident at event with uninsured vendor creates direct exposure for venue or organizer
Staffing agencies
Volume: Medium — one per client company with active placementsCollects from: Client companies (receiving workers) for worker placement agreements
Coverage required: WC and employer liability — varies by placement type
Liability exposure: Incorrect coverage classification creates liability gaps for on-site worker injuries
What expired COIs actually cost — three real exposure scenarios
Vendor slip-and-fall on your premises — vendor COI expired 45 days earlier
Your exposure: If vendor carried no active insurance, your GL covers the incident — at your deductible and against your claims history
Prevention: Active COI with verified current coverage eliminates this exposure by confirming the vendor's insurance is primary
Subcontractor property damage — GC did not verify updated sub COI after policy renewal
Your exposure: GC may be directly liable if sub's coverage lapsed and the GC failed to verify current COI at the time of work
Prevention: COI expiration tracking with 60-day update requests prevents coverage gaps from becoming GC liability
Vendor professional liability lapse — error discovered after project delivery
Your exposure: Claims against the vendor for professional errors require active E&O insurance — a lapsed policy means no coverage for the claim
Prevention: Track professional liability (E&O) separately from GL — different policies, different expiration dates
The seven-step COI collection and tracking workflow
Specify requirements before the relationship starts
Before contract signingInsurance requirements — coverage types, minimum limits, additional insured language — must be specified in the contract or agreement before signing. Requirements added after work begins are difficult to enforce and may not be accepted by the vendor's insurer.
Request the COI from the vendor's insurance agent — not the vendor
At contract executionVendors often forward the same COI they have on file — which may be expired or show lower limits than required. Requesting directly from the insurance agent (listed on the ACORD 25 as the agent of record) ensures you get the current, accurate document.
Verify coverage types, limits, and effective dates
Within 48 hours of receiptCheck that the coverage types match your requirements (GL, WC, umbrella, professional liability if required). Verify minimum limits are met — a $500K GL policy does not satisfy a $1M minimum. Confirm the policy effective date is current and the expiration date is in the future.
Confirm additional insured endorsement if required
At verification stepMany contracts require the receiving party to be listed as an additional insured on the vendor's policy — not just named on the COI. The COI alone is not proof of additional insured status. Verify with the vendor's insurer if this is a contract requirement.
Create one tracking record per vendor per coverage type
Immediately after verificationA vendor with GL, WC, and umbrella policies gets three tracking records — each with its own expiration date. Combining multiple coverages into one record means one expiration date hides the others.
Set reminders at 60 and 30 days before each policy expiration
At record creation60-day reminder: request the updated COI from the vendor's agent. 30-day reminder: if new COI not received, escalate. Do not wait for the 30-day reminder to start — insurers issue renewals on their own timeline.
Request updated COI before expiration — do not assume auto-renewal means auto-update
At 60-day reminderEven if a vendor's policy auto-renews, the COI on file in your records does not auto-update. The vendor's insurer issues a new policy; you still need to request a new COI showing the updated effective dates.
Five common COI tracking mistakes and how to fix them
Collecting COIs at onboarding but not tracking renewals
Consequence: COI expires silently — the vendor's coverage may lapse or change, but the record shows the old document as current
Fix: Track the expiration date from each COI and set a 60-day reminder to request an updated certificate before expiration
Accepting the COI as proof of additional insured status
Consequence: The COI names you as certificate holder — not additional insured. These are different. Certificate holder receives notice of cancellation; additional insured has actual coverage rights.
Fix: Require a separate additional insured endorsement from the insurer, not just additional insured language on the COI
Tracking one COI per vendor instead of one per coverage type
Consequence: A vendor's GL expires in March and their WC in August. One record shows 'insured through August' — the GL lapse in March is invisible
Fix: Create separate records per coverage type per vendor — GL, WC, umbrella each get their own expiration date and reminder
Requesting the COI from the vendor instead of their agent
Consequence: Vendor sends an expired COI or one showing lower limits than the contract requires — often unintentionally, sometimes not
Fix: Always request the COI from the vendor's insurance agent (named on the ACORD 25 form). The agent issues accurate, current documents.
Assuming auto-renewal means the COI on file is still current
Consequence: The vendor's policy renews automatically with new effective dates — but the COI in your files still shows the old dates
Fix: COI tracking triggers a request for an updated certificate at renewal — even when the policy itself is auto-renewed
1 record
Per coverage type per vendor — not one record per vendor. GL, WC, and umbrella each have separate policy terms and expiration dates. One record per vendor means two of three expiration dates are invisible.
60 days
Before policy expiration is when to request an updated COI from the vendor's agent — not 7 days before. Insurers issue renewals on their own timeline; early requests give time for follow-up if the COI is delayed.
No auto-update
COIs do not update automatically when a vendor's policy renews. The vendor's insurer issues a new policy; your files still show the old certificate. Active tracking — with renewal reminders — is the only way to keep COIs current.
Track every vendor COI — with reminders before each policy expires
FAQ
A certificate of insurance (COI) is a one-page summary document — most commonly ACORD form 25 — that lists a policyholder's active insurance coverages, limits, and policy expiration dates. It does not expire as a document — the expiration dates shown on the COI correspond to the underlying insurance policies. When a policy renews, a new COI must be requested from the vendor's insurance agent to reflect the updated coverage dates.
Certificate holder is a party listed on the COI who receives notice of policy cancellation — but has no coverage rights under the policy. Additional insured is a party with actual coverage rights under the vendor's policy — they can file claims directly against that policy for covered incidents. Contract requirements often specify additional insured status. A COI alone does not confer additional insured status; a policy endorsement does.
At the start of every new contract, when a vendor's policy renews (annually for most policies), and at the start of any new project where the vendor has on-site access. For high-risk vendors — those performing work on your property, handling your products, or providing professional services — verify current COI before each project or engagement, not just at annual renewal.
The party requiring proof of insurance — the project owner, landlord, or contracting company — is responsible for tracking COI expiration in their own records. The vendor is responsible for maintaining their insurance and providing updated certificates at renewal. Both have independent responsibilities. Assuming the vendor will remind you when their insurance renews creates gaps — proactive tracking from your side is the only reliable approach.
General liability (occurrence-based or claims-made), workers' compensation and employer's liability, commercial auto, umbrella or excess liability, and professional liability or E&O if applicable. Each coverage type may have a different policy term and expiration date. A contractor with GL expiring in June and WC expiring in September requires two separate tracking records — not one combined record.
Pause or do not begin the work requiring insurance coverage until a valid COI is received. Contact the vendor's insurance agent directly — the agent can usually issue an updated certificate same-day or next-day. If the vendor is uninsured or underinsured, this is a contract compliance issue that needs to be resolved before engagement continues. Document all requests and responses in writing.
Also tracking contractor licenses alongside COIs? See contractor license expiration tracking software.
Managing the full range of vendor documents — not just COIs? Vendor document expiration tracking.