The Additional Insured Trap: What Your COI Won't Tell You
Your COI says you're Additional Insured. The policy may say otherwise. Here are the common traps where AI status looks fine on paper but defeats in practice.
TL;DR: A COI that lists you as Additional Insured can still leave you fully exposed if the underlying policy lacks the actual endorsement (CG 20 10 / CG 20 37), uses a narrow 2013 edition, or carries blanket-AI language that requires a written contract executed before the loss. Always demand the actual endorsement pages and check the form edition before relying on AI status.
Every general contractor knows the drill: require subs to name you as Additional Insured, collect the certificate, move on, but there's a persistent gap between what a COI says about Additional Insured status and what the sub's policy actually provides. The "Additional Insured trap" is the space between these two things, and it's where GCs lose claims they thought they were covered on.
This post covers the specific traps that cause AI coverage to fail even when everything looks fine on paper.
Trap 1: The Endorsement Doesn't Exist
The first and most obvious trap: the COI claims you're Additional Insured, but no endorsement has actually been added to the policy. The producer may have written the AI language into the Description of Operations box to satisfy your request, but the underlying policy has no endorsement attached.
When a claim hits and the sub's insurer pulls the policy file, there's no CG 20 10 or CG 20 37 to find. The COI is just a statement made by the producer, not a modification to the policy. You have no coverage.
How to avoid it: always request the actual endorsement pages, not just the COI. Any legitimate producer can send them within a day.
Trap 2: The Wrong Form Edition
CG 20 10 has multiple edition dates. The 2013 edition is narrower than earlier versions. It only covers the Additional Insured for liability caused "in whole or in part" by the sub's acts or omissions, and only to the extent required by contract.
If your sub's policy uses an outdated or overly narrow edition, AI coverage that looks broad on the COI may actually be limited in ways that defeat coverage for common construction scenarios.
How to avoid it: check the edition date on the endorsement page. For moderate and high-risk work, require subs to carry endorsements that match or exceed the coverage provided by ISO form CG 20 10 10 01 or similar.
Trap 3: The Blanket Endorsement That Doesn't Apply
Blanket AI endorsements extend AI status to any party the named insured is required to add by written contract. They're efficient because you don't need to be individually scheduled on every sub's policy, but they only kick in if three things are true:
- The sub's policy has a blanket AI endorsement
- Your contract with the sub requires AI status
- Your contract is in writing and executed before the loss
If any of the three are missing, the blanket endorsement doesn't apply to you. A common failure mode: verbal sub agreements or letters of intent without a signed subcontract. The blanket AI might cover parties who executed contracts, but not you.
How to avoid it: always execute the subcontract before work begins. Require written contracts with explicit AI language even on small jobs where you'd normally use a PO.
Trap 4: Sole Employee and Similar Exclusions
Some CGL policies exclude coverage for claims by the insured's own employees against anyone. If a sub's employee is injured on your project and sues your GC, you'd normally expect the sub's CGL via AI endorsement to defend you. A sole employee exclusion can defeat that, leaving you to defend with your own insurance.
This exclusion is more common on policies written for smaller contractors or specialty trades with aggressive pricing. It's a landmine for GCs who don't review the actual policy.
How to avoid it: check the sub's exclusion pages for employee-related exclusions. "Cross-liability" endorsements can remedy the gap if present. See our deeper post on endorsement clauses that break COI compliance.
Trap 5: Residential Exclusion on a "Residential-Adjacent" Project
Many commercial CGL policies exclude work on residential buildings. The trap: some projects that look commercial have residential components (a mixed-use building with apartments above retail, a condo conversion, an apartment complex serving as corporate housing). If the sub's policy excludes residential work, the AI coverage is meaningless for the residential portions.
How to avoid it: confirm that the sub's policy covers the actual character of your project. For mixed-use and multi-family work, specifically verify that residential exclusions don't apply.
Trap 6: Primary and Non-Contributory Missing or Narrow
AI status makes you covered under the sub's policy. Primary and Non-Contributory makes that coverage pay first without contribution from your own policy. Without PNC, you may be Additional Insured in name but still share losses with the sub through contribution between insurers.
A COI can reference AI without PNC, and most GCs don't notice the omission until a claim forces the issue. At that point, both your insurer and the sub's insurer argue about who should pay, delaying resolution and costing both sides money.
How to avoid it: require PNC explicitly in the subcontract and verify the CG 20 01 endorsement or PNC language on the AI endorsement. Our post on primary and non-contributory coverage covers this in detail.
Trap 7: The Waiver of Subrogation Gap
Even if AI coverage works correctly, the sub's insurer may pay a claim and then pursue subrogation against the GC on a theory that the GC's actions contributed. Waiver of Subrogation (CG 24 04) prevents this.
The trap: your contract requires waiver of subrogation, the COI references it, but the actual endorsement either doesn't exist or is for a different party. You think you're protected; you're not.
How to avoid it: verify the CG 24 04 endorsement alongside the AI endorsements. Same rules apply as AI verification: request the actual pages, confirm the form number and your eligibility.
Trap 8: Claims-Made vs Occurrence
Most construction policies are occurrence-based, meaning they cover claims for incidents that occurred during the policy period regardless of when the claim is reported, but some are claims-made, meaning they only cover claims reported during the policy period with a restrictive retroactive date.
If a sub's policy is claims-made and their coverage lapses or changes, old work may become uncovered. Construction defect claims often surface years later, so a claims-made gap is devastating.
How to avoid it: require occurrence-based coverage in your subcontract. The ACORD 25 has a checkbox showing whether the policy is Occurrence or Claims-Made. Reject claims-made CGL on construction work.
The Common Pattern
All eight traps share a structure: the COI looks fine, the contract language is in place, but something about the actual policy defeats the coverage you think you have. The only way to avoid the traps is to verify the actual documents, not just the certificate.
For GCs without a full-time risk manager, this means:
- Routinely requesting endorsement pages, not just COIs
- Scanning for the red flags above
- Escalating anything unusual to your broker or attorney
- Documenting the verification in the sub's file so there's a record
PaperBoss handles the document collection and organization layer. Every sub's COI, endorsements, and supporting documents live in a searchable vault so you can actually review and retain them. The review itself is still human work, but organized documentation makes it possible.
Start a 14-day free trial, no credit card required.
Frequently Asked Questions
Can I catch all of these traps with software?
No. Some can be flagged automatically (missing PNC reference on the COI, claims-made coverage type), but the deeper traps (exclusions, form editions, blanket language requirements) require human review of actual policy documents.
What's my recourse if I discover AI coverage failed after a claim?
You may have a bad-faith claim against the producer or broker who misrepresented the coverage, but that's a separate lawsuit and recovery is uncertain. The better path is to catch the gap before accepting the certificate.
Do I need to verify AI status on every sub or just the big ones?
Every sub you require AI status from. The verification effort can scale with risk, but the fundamental verification (checking the COI + endorsement pages) applies to all.
How often do the traps actually happen?
More often than most GCs think. Coverage disputes in construction frequently come down to one of these gaps. A risk-mature GC treats every claim as an opportunity to confirm the verification process is working.
Can I require the sub's broker to certify there are no exclusions?
Some brokers will complete supplemental forms like ACORD 855 that ask about exclusions directly. These provide an additional layer of verification beyond the standard COI.
This article is for educational purposes only and does not constitute legal or insurance advice. Consult a licensed construction insurance broker or attorney for specific verification and coverage questions.
Ready to automate your compliance tracking?
PaperBoss collects COIs, W-9s, and compliance documents from your subs automatically. 14-day free trial, no credit card required.
Start Free TrialRelated articles
The 8 Endorsement Clauses That Break COI Compliance
A COI can look perfect and still leave you exposed. Here are the 8 endorsement clauses that most commonly defeat subcontractor insurance, and how to spot each one.
Additional Insured Endorsement Explained: What Every GC Needs to Know
What an Additional Insured endorsement actually does, why it matters for general contractors, the difference between CG 20 10 and CG 20 37, and how to verify you're protected.
On-Site vs Off-Site Coverage in Construction: What GCs Miss
Most COI disputes in construction come down to whether a loss happened on-site or off-site. Here's what the difference means, how each is covered, and the gaps that trip up GCs.