COI in Construction: What GCs Need to Know
Most industries track certificates of insurance as a paperwork checkbox. Construction is different. A COI on a job site represents layered liability transfer — from owner to GC to sub to sub-sub — and the endorsements that make that transfer legally effective are not on the certificate. They're on the policy. This guide explains what makes construction COI requirements different, what to look for field by field, and where GC project managers and admins most often get burned.
The most common mistake GCs make: accepting a COI that lists them as additional insured in the Description of Operations box — and not verifying that endorsement is actually on the policy. The certificate is issued by the agent. The endorsement is issued by the carrier. Only one of them grants you coverage rights if something goes wrong on the job site.
In this guide
What is a COI in construction?
A COI — certificate of insurance — is a one-page summary document, most often issued on the ACORD 25 form, that shows a contractor's or subcontractor's active insurance policies. It lists the insured's name, the insurance carrier, policy numbers, coverage types, per-occurrence and aggregate limits, and effective and expiration dates.
In a standard vendor relationship — an office supply company, a SaaS vendor, a cleaning service — a COI is primarily a verification document. You want to confirm the vendor is insured. The document itself is usually sufficient.
Construction is different. On a job site, the COI is your evidence that specific policy endorsements are in place — endorsements that determine who is covered, what is covered, and in what order policies respond when there is a loss. The certificate summarizes those endorsements, but the endorsements live on the underlying policy. What is written in the Description of Operations box on an ACORD 25 does not bind the carrier. What is on the policy does.
This distinction — between what the certificate says and what the policy actually provides — is where most construction COI problems begin.
What a COI is not: A certificate of insurance is not the policy. It is not legally binding on the insurer. It is evidence that a policy existed when the certificate was issued — not proof that coverage is currently active, not a guarantee that a claim will be covered, and not a substitute for the actual endorsement pages.
COI meaning in construction
In most industries, coi meaning is straightforward: a certificate of insurance is proof that a vendor carries coverage. In construction, the meaning goes further. A construction COI is evidence that specific policy endorsements are in place — endorsements that determine who is covered if something goes wrong on the job site, in what order policies respond, and whether completed operations claims are covered years after the project ends.
When a GC asks a sub for a construction COI, they are not just asking "do you have insurance?" They are asking: "Does your policy include additional insured status for my company via CG 2010 and CG 2037? Is your coverage primary and noncontributory? Does your aggregate reset per project?" These are the requirements that give the term coi in construction its distinct meaning.
A construction COI that does not reflect these endorsements may look valid on its face — correct limits, current dates, right policy types — but provide no practical protection if a claim arises from the sub's work.
Why construction COI requirements are more complex than other industries
Construction has a layered liability chain that no other industry replicates at scale.
The owner requires the GC to carry coverage. The GC requires every sub to carry coverage and name the GC — and often the owner — as additional insured. That sub may have sub-subs who must do the same. A typical commercial project might have three or four tiers of this requirement flowing down from a single prime contract.
The construction liability chain
Requires GC to carry coverage, names owner as additional insured on GC's policy
Requires every sub to carry coverage, names GC (and often owner) as additional insured on each sub's policy
Carries their own policy, names GC as additional insured — may also require their own sub-subs to do the same
Carries their own policy, names sub and GC as additional insured
This chain structure creates compliance complexity that does not exist in other industries:
- Each link in the chain must be verified independently. A GC who confirms their own coverage but does not verify their subs' COIs carries exposure if a sub's worker is injured on the job site.
- Flow-down requirements trickle from the prime contract. Coverage minimums the owner requires of the GC typically must be passed down contractually to every sub. If your prime contract requires $5M in umbrella coverage, your subs likely need to match that.
- Construction-specific endorsements are required, not optional. Completed operations coverage, per-project aggregates, and primary/noncontributory status are standard expectations on commercial projects — but they do not come standard on every policy. They must be specifically requested and endorsed.
- Policies renew annually, projects last longer. A sub who starts work in September may have their GL renew in March — mid-project. Without a process to track policy expirations against project timelines, a GC can go weeks with an uninsured sub on site without knowing it.
What to look for on a construction COI
These are the fields and endorsements that matter on a construction project — specifically the ones that are either absent from generic COI guidance or handled differently in construction.
Named insured matches your contract entity exactly
The legal business name in the Insured block must match the entity you contracted with — not a DBA, not a parent company, not a shortened name. A sub who operates as "Johnson Electric LLC" but whose policy is issued to "Johnson Electric" can create a coverage gap if a claim is contested. Require a corrected certificate before allowing work to start.
Additional insured via CG 2010/2037 endorsement — not a certificate notation
This is the most misunderstood field in construction COI review. A line in the Description of Operations box reading "[Your Company] is included as additional insured" is written by the insurance agent. It does not modify the policy. Additional insured status must be granted by endorsement on the actual policy.
For construction, require both:
• CG 2010 — covers claims arising from ongoing operations (work happening now)
• CG 2037 — covers claims arising from completed operations (defects discovered after the project ends)
Require the endorsement form numbers. If the agent cannot provide them, the endorsement is not on the policy.
Primary and noncontributory language
Without primary and noncontributory language, if a sub's worker is injured on your job site and a claim is filed, the sub's insurer and your insurer may both attempt to contribute — or both attempt to avoid being first. Primary and noncontributory means the sub's policy responds first, before your policy is triggered at all. This language must appear in the Description of Operations or on an attached endorsement, not just in your subcontract.
Waiver of subrogation endorsed on the policy
Subrogation is an insurer's right to pursue a third party that caused a loss. Without a waiver of subrogation, if the sub's insurer pays a claim that was partly your fault, they can turn around and sue you to recover what they paid. The waiver must be on the policy by endorsement — not just referenced in the Description of Operations box and not just required in your subcontract. Ask for the endorsement form number.
Per-project aggregate vs. blanket aggregate
A standard General Liability policy has a blanket annual aggregate — one pool of money covering all of a sub's projects for the year. If a sub has had claims on other jobs during the policy year, those claims erode the aggregate available for your project.
A per-project aggregate endorsement creates a separate aggregate dedicated to each job. For commercial work, require a per-project aggregate endorsement on any sub carrying significant liability exposure on your project.
Completed operations coverage with adequate tail
A sub's General Liability policy covers claims that happen during the policy period. Completed operations coverage extends that protection to claims that arise after the work is done — latent defects, structural failures, work that meets spec at completion but fails years later.
For occurrence-form policies, this is usually part of the standard GL form. For claims-made policies, the sub must maintain continuous coverage or purchase tail coverage after the policy lapses. In either case, verify that completed operations coverage extends at least as long as your state's statute of limitations for construction defect claims — typically three to ten years.
Umbrella/excess follow-form language
An umbrella or excess policy that does not explicitly follow form to the underlying GL — including additional insured status and primary/noncontributory language — provides less protection than it appears to. If you require $5M in total coverage and the sub's GL is $1M with a $4M umbrella, confirm the umbrella follows form. Otherwise, the additional insured status you negotiated may stop at the GL limit.
Policy period covers the entire project duration
Annual policies expire. Projects run longer than a year. Collect a renewed certificate before each policy lapses and note the renewal date for every coverage line — GL, WC, auto, and umbrella often renew at different times. A COI that is valid today may leave your project uninsured in four months without any notification unless you track it.
Common construction COI mistakes GCs make
These are the mistakes that actually happen in GC and PM offices — not theoretical errors, but the ones that surface when a claim is filed or an audit is conducted.
Accepting additional insured status via certificate notation only
An agent writes "[GC name] is named as additional insured" in the Description of Operations box. The GC files the COI and moves on. A claim is filed after a sub's worker is injured. The carrier denies the claim because no CG 2010 endorsement was ever added to the policy — only the certificate said so. This is the most common coverage gap in construction COI management.
Not requiring completed operations coverage
A sub finishes drywall on a commercial project and moves off-site. Eighteen months later, moisture intrusion caused by improper sealing surfaces. The sub's current GL policy is active, but the defect arose from completed operations — and their policy either does not include it or it was not required in the subcontract. Without a completed operations requirement written into the agreement, there may be no recovery.
Approving COIs without checking umbrella follow-form language
A sub carries $1M GL and a $4M umbrella. The prime contract requires $5M in total. The admin confirms total coverage appears to add up and approves the COI. A claim exceeds $1M. The excess carrier denies the additional insured claim because the umbrella does not explicitly follow form to the GL's additional insured endorsement. The GC's own policy has to respond.
Not tracking when annual policies expire mid-project
A sub's GL runs September to September. The project runs October to October. The COI collected at project start expires mid-project with no automatic renewal request. The sub renews but does not provide an updated certificate because no one asks. For six weeks, the sub is on site under a lapsed policy.
Collecting COIs at onboarding only — not at each project
A recurring sub carries a COI from last year's project. The GC's office has a file on them and assumes they're covered. The sub's policy was renewed with different limits to save on premium. The limits no longer meet the prime contract's flow-down requirements. No one noticed because no one requested a current COI for the new project.
How COI requirements vary by project type
COI minimums on a $50M commercial project are not the same as on a residential remodel, and public work carries its own requirements on top of the standard chain. Understanding how requirements scale down from the prime contract helps you set correct expectations with subs before onboarding.
Commercial — large GC contracts ($5M+)
- GL: $2M–$5M per occurrence, $4M–$10M aggregate
- Umbrella/excess: $5M–$25M, follow-form required
- Per-project aggregate required on most prime contracts
- Both CG 2010 and CG 2037 typically required
- Primary and noncontributory language standard
- Waiver of subrogation standard
- WC at statutory limits; GL and umbrella often flow down to sub-subs
Commercial — small to mid-size GC contracts (under $5M)
- GL: $1M–$2M per occurrence, $2M–$4M aggregate
- Umbrella: $2M–$5M depending on scope and contract
- Completed operations coverage required for most scopes
- Additional insured endorsement (CG 2010/2037) expected
- Blanket aggregate is common at this scale; per-project is better
- WC at statutory limits
Residential — single-family and small multifamily
- GL: $300K–$1M per occurrence is common, though inadequate for significant claims
- WC still required in most states even for small residential scopes
- Additional insured requirements vary widely by owner and GC
- Completed operations often not required — but should be for any structural work
- Texas WC opt-out is common in residential; GC exposure increases accordingly
Public and government-funded projects
- Often require the public entity as additional insured in addition to the GC
- Performance and payment bonds required in addition to COI
- Prevailing wage requirements may affect WC classification codes
- Notice of cancellation requirements often specified by contract (typically 30 days)
- Audit-readiness requirements may mandate retention schedules for all COIs
The practical rule: Review your prime contract's insurance exhibit before you set sub requirements. Whatever the owner requires of you flows down to your subs. If you pass lower requirements to your subs than your prime contract requires of you, you are accepting that gap on your own policy.
Managing COIs across multiple subs and projects
A single project with five subs is manageable with a spreadsheet and a folder. The tracking problem compounds when you have 30 subs with annual policies expiring at different points in the year, across five active projects, each with different coverage minimums flowing from different prime contracts.
Here is where spreadsheet-based COI tracking typically breaks down:
- Expiration tracking across policies. A sub's GL, WC, and umbrella may renew at different times. A spreadsheet with a single expiration date per sub misses two of the three renewal events.
- No automatic alerts. The expiration date passes. No one notices. The sub keeps working. The GC finds out when something goes wrong or when an owner's risk manager requests a current COI.
- Certificate collection is manual. Chasing a sub via email for a renewed certificate takes time the admin does not have. If the sub does not respond, the default is often to let it slide.
- Per-project requirements are hard to enforce. If Sub A is on Project 1 (requires $2M GL) and Project 2 (requires $5M GL), a flat coverage minimum spreadsheet cannot reflect that difference.
- Verification is separate. Even if the COI is current, a suspended contractor license or lapsed WC policy will not show up in COI tracking. License status requires a separate lookup process.
Managing COIs manually across projects?
TrackMyVendor is built for how GCs actually work — multiple subs, multiple projects, policies expiring at different times. Subs upload their own COIs via a one-time link. Expiration alerts go out automatically at 90, 60, 30, and 7 days before each policy lapses. The renewal link goes to your sub in the alert, so you do not have to chase them.
You can also set per-project coverage minimums on the Pro plan — so the same sub can meet $1M requirements on one project and $5M requirements on another, with the system flagging any gap automatically.
No credit card required. No implementation project. Works today.
Frequently Asked Questions
What is a COI in construction?
What is the difference between CG 2010 and CG 2037?
What is a per-project aggregate on a COI?
Can I accept a COI that lists me as additional insured in the Description of Operations box only?
How long should I keep construction COIs after a project closes?
Track COIs across every sub and every project — automatically
Expiration alerts, magic link collection, AI parsing, and license verification. First 25 subs free, no credit card required.
Start free today