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.
A COI in construction is a certificate of insurance — a one-page ACORD 25 summary proving a contractor or subcontractor carries the insurance a project requires before work begins. What makes a construction COI different from a generic one is the endorsements GCs must require: additional-insured status for both ongoing and completed operations (CG 20 10 and CG 20 37), primary-and-noncontributory wording, and often a waiver of subrogation. It lists each policy's coverage types, limits, and expiration dates, which the GC verifies against the subcontract before the sub steps on site.
In this guide
- What is a COI in construction?
- COI meaning in construction
- What is COI in construction — and why it's different from other industries
- What to look for on a construction COI
- CG 2010 vs CG 2037: The additional insured endorsements GCs must require
- Common construction COI mistakes GCs make
- How requirements vary by project type
- 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. Whether you call it a COI for contractors or a COI for subcontractors, the construction requirements are the same; what changes is who collects it from whom. For the document basics, see what a certificate of insurance is; for the sub side, the COI for subcontractors guide covers the specific limits and endorsements.
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.
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.
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. 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.
Click each card to mark it verified as you review the submitted COI.
How TrackMyVendor automates this
- Every field above is read off the PDF. Insured name, carrier, policy numbers, each coverage row with its own per-occurrence and aggregate limits and its own effective and expiration dates, the certificate holder, and the description of operations.
- The ADDL INSD and SUBR WVD boxes are read per coverage row, and the endorsement pages themselves are parsed — form number as printed, edition date, blanket or scheduled, which policy it amends, and whether it covers ongoing or completed operations. Pro
- Nothing is retyped into a spreadsheet, so the eight checks above are a review of what was read rather than eight fields somebody keys in.
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 TrackMyVendor automates this
- The certificate's tick-box and the endorsement behind it are read separately. A ticked ADDL INSD row with no CG 20 10 or CG 20 37 attached shows as exactly that, rather than as coverage you do not have. Pro
- Each coverage row carries its own expiration date, so a workers' comp or auto policy ending months before the general liability row is visible instead of hiding behind one date per sub.
- The whole PDF is stored either way. Send the endorsement pages with the certificate now and the reading catches up when the plan does — nothing has to be uploaded twice.
Reading an endorsement is not a legal opinion on it. Whether CG 20 10 04 13 satisfies your prime contract is a question for your broker or counsel; we tell you which form is actually attached.
See what AI parsing reads from a certificateHow 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 — 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
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.
How TrackMyVendor automates this
- Coverage minimums are set per project, not per company. The same sub can clear $1M on one job and fall short of $5M on another, and the shortfall is flagged against the job that requires it. Pro
- Your own baseline requirements apply everywhere else, so a sub with no project attached is still measured against the limits you set once in Settings.
- A project roster reports as a unit — who is compliant, who is short and what is missing — as a PDF or spreadsheet for the owner or the risk manager who asked. Pro
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. At that scale, dedicated COI tracking software replaces the spreadsheet — collecting certificates, reading expiration dates, and alerting you before each policy lapses.
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.
How TrackMyVendor automates this
- Subs upload through a one-time link. No account for them to create, no portal login, no app — they open it on a phone and drop the certificate in.
- Each policy row is tracked on its own dates, so general liability, workers’ comp and umbrella renewing at three different points in the year are three deadlines rather than one.
- Per-deadline reminders at 90, 60, 30 and 7 days go to your team and to the sub, and the sub’s copy carries the upload link — so the renewal comes back without an admin chasing it. Starter and above
- A contractor licence is re-checked against the state board every day, which is the half of the problem a certificate cannot answer: a current COI and a suspended licence can sit on the same sub.
- Every plan gets the Monday summary — one digest of every sub with something expired or expiring, to your team and never to the sub.
Tracking certificates on this job?
Do it by hand properly, or stop doing it by hand.
Free template
The COI tracking spreadsheet
A pre-formatted .xlsx with columns for certificate details, licence numbers, expiration dates and W-9 status, plus an Instructions tab. Tell us where to send it — no account to create.
Stop maintaining it by hand
Let the subs fill it in
Your first 25 subs are free. They upload through a one-time link, AI reads every coverage row and its dates, and licences are re-checked against the state board daily — so the tracker is current between meetings, not just at them.
Start free — no credit card →Up and running in about 10 minutes.