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

1. What is a COI in construction?
2. COI meaning in construction
3. What is COI in construction — and why it's different from other industries
4. What to look for on a construction COI
5. CG 2010 vs CG 2037: The additional insured endorsements GCs must require
6. Common construction COI mistakes GCs make
7. How requirements vary by project type
8. Managing COIs across multiple subs and projects

How to Handle Insurance Requirements on a Construction Site

Handling insurance requirements on a construction site comes down to three things: collecting the right documents before work starts, verifying those documents actually grant you the coverage your contract requires, and tracking renewals so coverage doesn't lapse mid-project.

Before any sub steps on site, you need a COI that confirms: (1) the named insured matches the legal entity in your subcontract — not a DBA or trade name; (2) you are listed as additional insured in Box 17 of the ACORD 25 with explicit endorsement references (CG 20 10 for ongoing operations, CG 20 37 for completed operations); (3) coverage limits meet your contract minimums and your owner's project requirements; and (4) policy periods extend through project completion — and through the completed operations period for structural, roofing, or mechanical trades.

Construction site insurance requirements can feel like a paperwork exercise — but when something goes wrong, the difference between a properly structured COI and a generic certificate is the difference between your sub's insurer paying the claim and yours doing it. The sections below explain each requirement field by field.

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.

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.

What is COI in construction — and why it's different from 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.

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. Reviewing every one by hand on each certificate is the slow part; you can have software extract these fields and limits from the uploaded PDF instead.

CG 2010 vs CG 2037: The additional insured endorsements GCs must require

Of the eight fields in the checklist below, the additional insured endorsements are where most construction COI failures occur — and where most GC admins unknowingly accept inadequate coverage. CG 2010 (ISO form CG 20 10) covers additional insured status for ongoing operations — claims arising while the sub is actively on site. CG 2037 (ISO form CG 20 37) covers additional insured status for completed operations — claims that arise after the sub's work is done, such as a defect discovered a year after project closeout.

Requiring only CG 2010 leaves the GC exposed the moment the sub completes their scope. Requiring only a Description of Operations notation — without endorsement form numbers — provides no policy coverage at all. Both forms, by number, are the standard for any commercial construction subcontract. See field 02 in the checklist below, and the full CG 2010 vs CG 2037 endorsement guide for a complete breakdown.

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.

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.

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 — unless you check each sub's license against the state database automatically alongside their COIs.

Frequently Asked Questions

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.

Related Guides and Tools

Subcontractor Insurance Requirements by State