Every general contractor has a subcontractor insurance compliance program. Most of them have the same structural flaw: they verify COIs against a generic internal checklist, not against the actual subcontract.
That distinction matters enormously. The subcontract is where your specific risk transfer terms live. The generic checklist reflects what you think those terms say. Those two things are often different, and the gap between them is where your exposure lives.
Who Bears the Exposure When a Sub Is Non-Compliant
The GC Compliance Gap
When a subcontractor causes an incident on your site and their insurance doesn't respond the way it should, the claim doesn't disappear. It becomes your problem.
The owner looks to the GC. The GC's insurer looks at the subcontract to determine whether the GC properly transferred risk to the sub. If the sub's coverage didn't meet subcontract requirements, the GC is often left holding defense costs, settlement exposure, and coverage disputes that take years to resolve.
Uninsured incidents on construction projects cost an average of $500,000 in combined defense and settlement costs. That exposure exists even when you collected a COI. The question is whether the COI actually matched your subcontract.
The Document Comparison Problem
Generic Checklist vs Subcontract Verification
Most GC compliance programs work like this: a project coordinator or administrator receives a COI, opens a standard internal checklist, and verifies that the certificate hits the usual benchmarks. Limits above a threshold. Current dates. Some mention of additional insured.
What they're not doing is pulling the executed subcontract for that specific sub and reading the insurance exhibit clause by clause.
The practical result is that compliance decisions are being made against a generic standard rather than the actual contractual requirement. Here's why that creates gaps:
Limits vary by subcontract. Your electrical sub's scope warrants different limits than your landscaping sub's scope. If your checklist says "$2M per occurrence CGL" for everyone, you're over-verifying some subs and under-verifying others.
Endorsement requirements vary. Some subcontracts require primary and non-contributory additional insured language. Some require completed operations coverage for a specified tail period. Some require waiver of subrogation. These specifics live in the subcontract, not the generic checklist.
Entity names vary. On multi-project programs with different joint venture structures, the correct additional insured entity on one project may be different from another. A generic check misses this entirely.
What Proper Subcontract-Level Verification Looks Like
Verifying a subcontractor's COI against the actual subcontract means reading both documents simultaneously and confirming each requirement is satisfied.
| Subcontract Requirement | What to Check on the COI |
|---|---|
| CGL limit per occurrence | Policy limit listed under Commercial General Liability |
| CGL aggregate limit | Aggregate limit listed, plus whether shared or per-project |
| Umbrella / excess limit | Umbrella policy present, limits meet subcontract minimum |
| Workers' comp | Statutory limits listed or "statutory" notation present |
| Additional insured | Your legal entity name listed, not trade name or abbreviation |
| AI endorsement basis | Certificate remarks or endorsement confirms primary and non-contributory |
| Waiver of subrogation | Reflected in remarks or on separate endorsement |
| Completed operations tail | Coverage period matches subcontract requirement |
This is the check that most programs skip because it requires pulling and reading the subcontract for every COI received. At 10 active subs, that's manageable manually. At 50 or 100, it becomes the bottleneck that the program quietly abandons.
The Endorsement Trap
Additional insured requirements deserve special attention because they're the most commonly misunderstood element in GC subcontractor insurance compliance.
Being listed as an additional insured on a certificate and having enforceable additional insured status are not the same thing. The certificate is a summary document. The endorsement is what creates the actual coverage.
If your subcontract requires that you be named as additional insured on a primary and non-contributory basis, but the underlying policy has a blanket additional insured endorsement that is triggered only by written contract and excludes primary and non-contributory language, you may have far less protection than you think.
The way this failure surfaces is rarely during the project. It surfaces when you tender a claim to the sub's carrier and the carrier disputes the scope of your additional insured coverage. At that point, the argument is expensive and the outcome is uncertain.
The Compliance Program That Actually Works
A GC subcontractor insurance compliance program that protects you has three components working together.
First, the subcontract itself must contain specific, enforceable insurance requirements. Vague language like "adequate insurance" or "standard limits" gives you nothing to verify against.
Second, verification must happen at the subcontract level, not against a generic internal standard. The person reviewing the COI needs access to the executed subcontract for that specific sub.
Third, renewal COIs need to go through the same verification, not just a date check. Coverage that was compliant at contract execution may be restructured at renewal.
How Bramble Connects to This Problem
Bramble reads your executed subcontracts and extracts the specific insurance requirements for each sub. When a COI comes in, Bramble compares it against those subcontract requirements at the clause level, not against a generic internal checklist.
The result is that every COI is verified against the actual document that governs the risk transfer. Gaps that would have been invisible on a generic review surface immediately. Your team gets a clear view of what matches and what doesn't, organized by project and subcontractor.
When your compliance program is built on actual subcontract terms, you know your COI review means something.
See how Bramble works - book a demo
Frequently Asked Questions
What documents should a GC verify a subcontractor COI against? The executed subcontract for that specific subcontractor, not a generic internal checklist. Insurance requirements vary by scope, project type, and negotiated terms.
What happens if a subcontractor's COI doesn't match the subcontract? The GC retains the exposure the subcontract was intended to transfer. In the event of an incident, the GC's own insurer may dispute coverage based on improper risk transfer documentation.
How often should GCs reverify subcontractor COIs? At contract execution, when policies renew (typically annually), and any time there is a change in the sub's scope or project phase that materially affects risk.
What is the most commonly missed requirement in GC subcontractor compliance? The additional insured endorsement basis. Many programs verify that an additional insured is listed on the certificate but don't confirm that the underlying endorsement provides primary and non-contributory coverage as required by the subcontract.
What is 70% of COIs non-compliant at first receipt? Industry data shows that 70% of COIs submitted by contractors have at least one deficiency. The deficiencies range from minor date issues to significant gaps in coverage or missing endorsements.