Your subcontract requires the framing sub to carry $2,000,000 in general liability. A framing crew member falls from scaffolding on the fourth floor. He's a day laborer - not on payroll, not covered by workers' compensation. The sub's GL policy has a labor contractor exclusion. The claim goes to the owner. The owner's contract requires the GC to indemnify. The GC looks to the sub's insurance. The insurance doesn't respond. The GC is now the responsible party for a seven-figure claim against a subcontract that expressly required adequate coverage.
This scenario repeats across the construction industry because the compliance process that is supposed to prevent it - verifying subcontractor COIs against subcontract insurance exhibits - fails at the point of comparison. COIs get collected. They don't get compared against the specific requirements in the subcontract. A framing sub with a certificate showing $2,000,000 GL passes the collection check. The labor contractor exclusion doesn't appear on the certificate. Nobody reads the policy. Nobody reads the subcontract's insurance exhibit to know what exclusions are prohibited.
Bramble is document compliance intelligence for general contractors and construction risk managers. It reads your subcontract insurance exhibits - the AIA form requirements, the project-specific additions, the owner-mandated endorsements - and compares those requirements against subcontractor COIs before mobilization. The comparison happens at the exhibit level, not against a generic construction checklist.
Why Construction Subcontractor Insurance Compliance Is Different
Construction is not a single-risk environment. A commercial office building project has different risk profiles than a hospital renovation or an industrial facility expansion. The subcontract insurance requirements for each project type reflect those differences - and in most cases, they reflect specific requirements the owner has imposed on the GC through the prime contract.
The insurance compliance chain in construction runs from owner to GC to sub to sub-sub:
- Owner-GC prime contract specifies the GC's insurance requirements (often substantial - $5M-$25M+ umbrella, professional liability if design-build, pollution if site work)
- GC-sub subcontract specifies the subcontract insurance requirements (typically flowing down from prime contract requirements, with adjustments for scope)
- Sub-sub-sub subcontract requires the first-tier sub to flow down requirements to any second-tier subs they engage
At each level, the insurance requirements are specific to the contract at that level. A generic construction COI checklist doesn't capture this structure. Subcontract insurance exhibits do - and Bramble reads the exhibit, not the checklist.
How Bramble Works for Construction
What AIA Subcontract Insurance Exhibits Require
AIA A201 General Conditions and the associated subcontract forms include specific insurance provisions that most GCs use as a baseline. Project-specific modifications - required by owners, lenders, or risk managers - add requirements on top of the AIA baseline. Common subcontract insurance requirements include:
| Coverage Type | Typical Subcontract Requirement | Common Compliance Gap |
|---|---|---|
| Commercial General Liability | $1M-$2M per occurrence / $2M-$4M aggregate | Aggregate eroded by prior project claims |
| Auto Liability | $1M CSL | Split limits or hired/non-owned only |
| Workers' Compensation | Statutory + $1M Employer's Liability | Employer's Liability limit short |
| Umbrella/Excess | $5M-$25M following form | Does not follow form to underlying GL |
| Professional Liability | $1M-$5M for design-assist subs | Missing entirely for applicable scopes |
| Pollution Liability | $1M-$5M for site work, demo, mechanical | Sudden-and-accidental only vs. gradual |
| Contractor's Pollution | As specified for applicable trades | Absent for trades with exposure |
| Builder's Risk | Per project, if required of sub | Coverage structure doesn't match exhibit |
| Additional Insured | Owner + GC + lender as required | Lender or owner entity missing |
| Primary & Non-Contributory | Required on GL and umbrella | Language not endorsed onto umbrella |
| Waiver of Subrogation | Required on GL, auto, and WC | Absent on WC line |
| Per-Project Aggregate | Required on GL for larger projects | General aggregate only, not per-project |
The per-project aggregate requirement is a specific example of a requirement that generic COI review misses. A sub with a $2,000,000 GL aggregate who has worked three previous projects this year may have an eroded aggregate of $600,000 remaining. Unless the subcontract required a per-project aggregate endorsement, the GC has no visibility into this without certificate comparison against exhibit requirements.
Generic Checklist vs. Exhibit-Level Compliance
Generic COI Checklist
✕ Same requirements applied to all subs
✕ Misses per-project aggregate gaps
✕ Cannot track owner flow-down requirements
✕ Tier-2 sub compliance invisible
✕ Labor contractor exclusions undetected
Bramble Exhibit Comparison
✓ Each sub evaluated against their specific exhibit
✓ Per-project aggregate verified per project
✓ Owner requirements traced through flow-downs
✓ Tier-2 sub compliance tracked and verified
✓ Exclusion mismatches flagged automatically
Tier-2 Sub Compliance: The Invisible Liability Layer
GCs manage first-tier subcontractors. But first-tier subs subcontract. The electrician on your project may use a subcontracted fixture installer. The roofing contractor may use a subcontracted waterproofing crew. Those tier-2 subs are on your site. If they are injured, if they cause damage, the liability chain runs back to the GC.
Most GCs have language in their subcontracts requiring first-tier subs to flow down the same insurance requirements to their subcontractors. Whether that flow-down actually happens - whether the first-tier sub has obtained and verified adequate COIs from their subs - is a question that most GC compliance programs don't track.
Bramble supports tier-2 sub compliance tracking. When first-tier subs are required to certify that their subcontractors maintain adequate insurance, Bramble can collect and compare those tier-2 certificates against the flow-down requirements from the prime subcontract. GC risk managers get visibility into their full on-site workforce insurance posture - not just the first-tier subs they contracted with directly.
The Project-by-Project Compliance Challenge
Construction risk managers face a compliance challenge that differs from most industries: requirements change project by project. A GC managing five active projects may have five different sets of subcontract insurance requirements - because each prime contract has different owner requirements, each project has different risk characteristics, and each subcontract may have been negotiated differently.
A generic COI compliance checklist cannot handle this structure. Subcontractors who work on multiple projects may have the same insurance policy evaluated against different project-specific requirements. A sub who is compliant on Project A may not be compliant on Project B because Project B's owner required a higher umbrella limit or a specific professional liability endorsement.
Bramble manages project-level compliance. Subcontract exhibits are read and stored per project. When a sub is active on multiple projects, their COI is compared against each project's specific requirements separately. Compliance status is maintained at the project level, not just the subcontractor level.
The Cost of Getting This Wrong
The financial consequences of subcontractor insurance non-compliance in construction are severe:
Direct claim exposure: An uninsured or underinsured sub shifts loss directly to the GC under the subcontract's indemnification provisions. A $500,000 claim against a sub whose coverage doesn't respond becomes a $500,000 GC exposure.
Prime contract indemnification: GCs typically indemnify owners against subcontractor-related claims. A subcontractor coverage gap means the GC absorbs the owner's exposure in addition to its own.
OCIP/CCIP complications: On projects with owner-controlled or contractor-controlled insurance programs, subcontractor compliance with OCIP enrollment requirements - and with residual insurance requirements for non-enrolled exposures - is a specific compliance obligation that standard COI review doesn't address adequately.
Prequalification consequences: A GC whose subcontractor compliance program is found inadequate during an owner audit or incident investigation faces prequalification consequences on future projects. Documented, systematic compliance is a competitive differentiator.
The annual cost of manual compliance staffing - $36,400 per FTE - does not prevent the $500,000+ incident cost of a single uninsured subcontractor claim. Bramble's 90%+ compliance accuracy compared to the 60-70% achievable manually is the difference between a compliance program that works and one that creates a false sense of security.
Construction Compliance by the Numbers
Frequently Asked Questions: Construction COI Tracking
What is construction COI tracking software? Construction COI tracking software verifies that subcontractor certificates of insurance satisfy the requirements in the subcontract insurance exhibit for each project. Unlike basic certificate storage tools, construction compliance software reads the actual subcontract insurance exhibit - including project-specific requirements layered on top of standard AIA provisions - and compares every requirement against the subcontractor's COI. Bramble automates this comparison project by project, subcontractor by subcontractor.
What happens if a subcontractor is injured on site and their workers' compensation is inadequate? If a subcontractor lacks adequate workers' compensation coverage, the GC may face direct liability for the injury depending on jurisdiction and project structure. In many states, an uninsured subcontractor can trigger the GC's workers' compensation obligations as a statutory employer. The subcontract's insurance requirement for workers' compensation exists to prevent this - but only if compliance is actually verified before the sub begins work.
What is a per-project aggregate endorsement and why is it required? A standard commercial general liability policy has a general aggregate limit that applies across all claims in the policy year, regardless of project. If a subcontractor has worked on multiple projects, the general aggregate may be eroded by prior claims. A per-project aggregate endorsement creates a separate aggregate limit for each project, ensuring the full limit is available for claims arising from your project regardless of what happened on others. Many subcontract exhibits require this endorsement for exactly this reason.
Can Bramble handle subcontractor compliance across multiple simultaneous projects? Yes. Bramble manages compliance at the project-subcontractor level. A subcontractor working on three projects has their COI compared against each project's specific requirements separately. A sub who is compliant for one project's requirements may be flagged non-compliant for a different project with higher limit requirements - both flags appear in the appropriate project's compliance view.
How does Bramble handle OCIP/CCIP enrollment and residual insurance requirements? Owner-controlled and contractor-controlled insurance programs create specific compliance requirements - enrollment verification, identification of covered vs. excluded scopes, and verification that residual coverage for non-OCIP exposures meets exhibit requirements. Bramble reads the OCIP/CCIP insurance requirements document and tracks enrollment compliance alongside standard subcontract insurance compliance. The specific configuration is reviewed during implementation for project-specific programs.
The Only Compliance That Protects You Is Verification Against the Exhibit
Every subcontract you signed has an insurance exhibit. That exhibit specifies exactly what coverage your subs must carry. The compliance question - the only question that matters - is whether the COIs you have on file actually satisfy those exhibits.
A COI collection process is not compliance. A spreadsheet of certificate expiration dates is not compliance. Compliance is comparing every COI against the exhibit in the subcontract that governs that relationship, identifying every gap, and resolving it before the sub mobilizes.
Bramble reads your subcontract insurance exhibits, compares them against subcontractor COIs, and surfaces every gap before your sub sets foot on site. Every project. Every sub. Every requirement.
See how Bramble handles subcontractor insurance compliance across your active project portfolio. Book a demo at getbramble.com/demo.
Related reading: Contract vs. COI Compliance: Why the Source Document Matters | Vendor Insurance Compliance | COI Tracking Software