Expired COI Mid-Project: Who's Liable in Colorado?

A subcontractor's certificate of insurance shows a policy expiration of June 30. The worker goes down on July 8. You collected the COI in March and filed it. Nobody checked the date. Now you are fielding a call from your carrier asking why you allowed uninsured work to continue on your jobsite.

By Nick Streicher, Founder, StrikeDocs. Published 2026-07-13.

This situation plays out on Colorado commercial and residential projects constantly. The COI was valid when collected. The underlying policy was not valid when the incident occurred. The difference between those two facts is where liability lives.

This post walks through exactly what happens legally in Colorado when a subcontractor's policy lapses mid-project, which contract clauses control the outcome, what we've seen in real certificate data, and how to build a system that catches expirations before they become claims.

What "expired mid-project" actually means on an ACORD 25

The ACORD 25 certificate of insurance is a snapshot, not a guarantee. The standard disclaimer printed on every ACORD 25 says explicitly that the certificate "does not affirmatively or negatively amend, extend or alter the coverage afforded by the policies." The expiration dates listed in boxes 12 and 13 on the form reflect policy term as reported by the agent at the moment of issuance — nothing more.

If a policy lapses on June 30 and a loss occurs on July 1, the certificate dated in March is irrelevant to coverage. What matters is whether the policy was in force on the date of loss. The ACORD form does not update itself. It does not send you a notification. It sits in your inbox or your filing cabinet and says nothing about what happened after it was issued.

For a deeper breakdown of how to read the date fields on the form, see our guide on how to read an ACORD 25.

A mid-project expiration can happen three ways:

The policy simply runs out. Annual policies expire on their anniversary. A sub hired in February on a policy expiring March 31 is uninsured by April on a project running through December.
The policy is cancelled mid-term. Non-payment of premium, material misrepresentation, or a carrier pulling out of a line of business all trigger mid-term cancellation. Colorado follows the standard 10/30-day cancellation notice rules under C.R.S. § 10-4-109, but that notice goes to the named insured — not to you.
The sub obtains a new policy with a gap. The old policy expires July 1. The new policy is bound July 5. Work continued July 2–4. Any incident in those three days is uncovered.

Colorado's legal exposure when coverage lapses during active work

Colorado does not have a single statute that makes a general contractor automatically liable for a subcontractor's uninsured loss. Liability flows from three separate sources: contract, tort, and workers' compensation statute.

Contract liability. Your subcontract almost certainly contains an indemnification clause and an insurance requirement clause. If the sub failed to maintain the required insurance, they breached the contract. You can pursue breach of contract damages. The practical problem: a sub without active insurance frequently also lacks the financial resources to satisfy a judgment. The indemnity clause gives you a right; it does not give you money.

Tort liability. Colorado follows the premises-liability framework under C.R.S. § 13-21-115 and the general negligence standard. If you retained control over the work or the jobsite condition that caused the injury, you face direct negligence exposure regardless of whether your sub was insured. The Colorado Supreme Court's analysis in A.C. Excavating v. Yacht Club II Homeowners Ass'n (2004) and subsequent appellate decisions make clear that "retained control" is fact-specific and litigated constantly. Uninsured subs make plaintiffs more likely to name the GC as the deep pocket.

Workers' compensation. Under C.R.S. § 8-41-401, if a subcontractor fails to carry required workers' compensation insurance, the contractor up the chain can be treated as a "statutory employer" and held liable for WC benefits to the injured worker. This is not a contractual right — it is a statutory obligation. Colorado's Division of Workers' Compensation enforces this aggressively. You cannot contract around it.

The workers' compensation statutory employer exposure is the one that surprises GC office managers most often. You did not employ the injured worker. You had no payroll relationship with them. But if your sub let their WC policy lapse and their employee gets hurt on your site, Colorado law may treat you as the employer of record for WC purposes.

For a broader view of how COI requirements vary by state, see COI compliance requirements by state.

The contract clauses that determine who bears the loss

Three clauses in a well-drafted subcontract directly affect mid-project expiration liability. Most subcontracts used on Colorado commercial projects have at least two of them. Many residential subcontracts have none.

Insurance requirement clause. This clause specifies the types of coverage, minimum limits, and endorsement requirements the sub must maintain throughout the project — not just at contract signing. The phrase "throughout the duration of the work" is load-bearing. Without it, a court could find that the sub only had to carry insurance at inception. If you want to know whether your subcontract language actually requires continuous coverage, use our requirements generator to compare what you have against a standard commercial template.

Notice of cancellation clause. Your contract can require the sub to notify you immediately upon receiving any cancellation or non-renewal notice from their carrier. This creates a contractual obligation on top of (and earlier than) the statutory cancellation notice Colorado requires insurers to send the named insured. Many agents can also add an endorsement to the policy requiring notice to certificate holders — but that endorsement is not automatic, and the standard ACORD 25 language specifically disclaims any obligation to notify certificate holders.

Right to suspend work clause. If you discover a lapse, you need the contractual right to stop the sub's work without that suspension being treated as a breach on your part. Without this clause, stopping work may expose you to a wrongful termination or delay damages claim from the sub.

If your subcontract was drafted on a handshake or pulled from a template someone downloaded in 2014, verify all three clauses exist and say what you think they say before you accept the next COI from that sub.

What we learned running 59 real COIs through StrikeDocs

We processed 59 certificates of insurance through StrikeDocs to analyze how coverage is actually structured on documents submitted in the field. The findings are not hypothetical.

Only 21.3% of policies carried a Waiver of Subrogation endorsement. This means that in more than 78% of cases, the sub's carrier retained the right to subrogate against the GC after paying a claim — including for claims arising from lapses in coverage timing.
Only 33.9% of policies showed an Additional Insured endorsement. In the majority of submitted certificates, the upstream contractor was not listed as an additional insured on the underlying policy at all. A GC relying on AI status to trigger their own carrier's defense in a lapse scenario will find no such protection on two-thirds of the certificates they've collected.
The median GL each-occurrence limit across the corpus was $10,000, and 100% of GL policies were below $1,000,000. Every single GL policy in the set was below the $1M per-occurrence threshold that most Colorado commercial subcontracts require as a floor. A sub presenting a COI with a below-limit policy is operating out of compliance from day one — expiration is a secondary problem.

The third finding deserves to sit with you for a moment. If you have 20 active subs and 100% of the GL policies in a representative sample fall below the contractually required minimums, the COI you collected may be technically unexpired and still provide almost no real protection.

For a more complete breakdown of what each coverage line on a COI actually protects, see what does a COI cover.

How to catch an expiring COI before it becomes a claim

The process problem is not identifying expiration dates — they are printed on every ACORD 25. The process problem is that nobody looks at them again after the initial collection. A certificate collected in February for a project running through November will expire in the drawer unless someone has a system that surfaces it 30 days before the policy end date.

Here is what a functional tracking workflow looks like:

Log every policy expiration date at intake. Not the certificate date. The policy expiration date — the date in box 13 on the ACORD 25. These are different. The certificate was issued on a date. The policy expires on a different date. Track the policy expiration.
Set a 45-day advance alert. Forty-five days gives you time to request a renewal COI, receive it, review it for compliance, and push back if something changed. Thirty days is the minimum; 45 is better. StrikeDocs COI Tracker handles this automatically — you upload the certificate and the expiration gets queued for alert.
Require a renewal COI before the old one expires, not after. Your contract should specify that the sub must deliver a renewal certificate at least 15 days before the current policy expires. Waiting until after expiration to ask for the new certificate creates a gap.
Do not allow work to continue on an expired certificate. This sounds obvious. In practice, a sub is on-site, you cannot verify their renewal yet, and stopping their crew costs you schedule. The answer to that pressure is having the renewal COI in hand before the old one expires, which goes back to item 3.

The additional insured question also becomes acute at renewal. A sub may renew their policy with a different carrier and fail to reissue the endorsement naming you as additional insured. The new certificate looks valid. The endorsement is gone. See our post on what to do when your subcontractor's COI doesn't list you as additional insured for how to handle that conversation.

The renewal COI problem: why a fresh certificate isn't enough

When a sub renews their policy and sends a new ACORD 25, most GC office managers file it and move on. That is not enough.

A policy renewal is not a guarantee that all the terms from the prior policy carried over. Carriers change endorsements at renewal. Limits can change. Additional insured status — which must be affirmatively added by endorsement and is not automatic — may not have been re-requested or re-issued. The carrier may have changed entirely.

The endorsements that matter most in a Colorado construction context are:

CG 20 10 — Additional Insured, Owners, Lessees or Contractors, covering ongoing operations. Check our CG 20 10 endorsement decoder for what this endorsement actually says versus what agents claim it covers.
CG 20 37 — Additional Insured, covering completed operations. Ongoing operations coverage ends when work is done; completed operations coverage is what protects you after the sub leaves the site. These are two separate endorsements and both matter.
Waiver of Subrogation — Without this, the sub's carrier can sue you after paying a claim, even if you are contractually indemnified by the sub.
Primary and Noncontributory — Without this language, the sub's policy and your policy may share loss in proportion, rather than the sub's policy responding first.

For a detailed explanation of how primary and noncontributory works and why its absence creates real exposure, see what to do when a vendor's COI is missing the primary noncontributory endorsement.

When you receive a renewal certificate, the minimum check is: same or higher limits, same endorsements, same named insured, and an expiration date that runs past your project completion date. If any of those four elements changed, push back before the old policy expires.

The structured output from a StrikeDocs compliance check on a renewal COI looks like this:

ISSUE: CG 20 37 completed operations endorsement absent on renewed policy
FIELD: Description of Operations / Endorsements
SEVERITY: HIGH — completed operations exposure uninsured after sub demobilizes

ISSUE: Primary & Noncontributory language not confirmed by endorsement
FIELD: Additional Insured designation
SEVERITY: MEDIUM — certificate states "primary" but no endorsement number provided; carrier may dispute

ISSUE: GL each-occurrence limit $500,000 — below contract minimum of $1,000,000
FIELD: General Liability / Each Occurrence
SEVERITY: HIGH — sub is in breach of insurance requirement clause

This is the kind of output you need on every renewal certificate, not just the first one collected at contract signing.

Practical steps to close the gap today

If you are managing active subcontracts in Colorado right now, here is the short list:

Audit your current certificates for expiration dates. Pull every active sub's most recent COI and check the policy expiration dates — not the certificate date. Any policy expiring within 60 days needs a renewal request sent today. Use the free COI audit tool to run through your stack and flag which ones are expired or near-expiring.

Verify WC coverage specifically. Workers' compensation is where Colorado's statutory employer exposure bites. A sub with an expired WC policy is your single largest uninsured risk, and WC coverage lapses are common because WC premiums are audited and adjusted mid-term, creating non-payment cancellations. Check the WC expiration date separately from the GL.

Add the right language to your next subcontract. If your current subcontract template does not explicitly require continuous coverage throughout the work, notification of cancellation, and your right to stop work for an insurance lapse, fix it before the next subcontract is signed. The insurance requirements generator will produce language you can paste into a template.

Do not accept a certificate from a sub who says the renewal is "in process." The policy either exists or it does not. "In process" means there is a gap. Stop work, document in writing that you requested the certificate and it was not provided, and do not restart until the renewal COI is in hand. This documentation matters if a loss occurs during that window.

Check endorsements on renewal, not just limits. A GC that confirms limits but misses the dropped AI endorsement on a renewal is in the same position as a GC who never verified the certificate at all.

Colorado's construction market is active and subcontractor capacity is tight. The pressure to keep crews on-site when paperwork is incomplete is real. The workers' compensation statutory employer statute does not care about that pressure. The liability that attaches when a sub's WC policy lapses mid-project and a worker is injured is not negotiated — it is imposed by statute. The only defense is having the policy in force.