Construction defect claims, worker injury lawsuits, and property damage incidents happen on every GC's projects over time. When they do, coverage either responds or it doesn't. Whether it responds depends almost entirely on decisions that were made months or years earlier - during the COI review process that most GCs treat as an administrative formality.
Here are the seven mistakes that turn a covered claim into a GC-absorbs-the-loss scenario.
Mistake 1: Not Verifying Completed Operations Additional Insured Status
This is the single most consequential mistake in construction COI compliance - and one of the most commonly missed.
Most GCs verify that the sub has GL insurance and that the GC is listed as additional insured. What they don't verify: whether the additional insured status includes completed operations (CG 20 37), and whether it will remain in force for the duration of the applicable statute of repose after project completion.
Standard commercial GL policies include ongoing operations AI coverage during the project. Completed operations AI is a separate endorsement (CG 20 37) that continues coverage for claims arising from the sub's work after the project is complete. Without it, the GC loses additional insured protection for post-completion construction defect claims - which is precisely when the highest-value claims occur.
A roofing defect claim surfacing 3 years after project completion. A plumbing failure causing water damage discovered 2 years later. An electrical failure resulting in fire 18 months post-completion. These are completed operations claims. If CG 20 37 wasn't confirmed - and maintained - the GC is not an additional insured when the claim hits.
The fix: Require both CG 20 10 (ongoing) and CG 20 37 (completed operations) in the subcontract. Confirm both are in force before work starts. Track completed operations coverage separately, through every annual policy renewal, for the duration required by your subcontract.
Mistake 2: Accepting the COI Checkbox as Endorsement Confirmation
The ACORD 25 has a checkbox for "Additional Insured" and a description-of-operations field. Neither confirms that an endorsement was actually added to the policy.
A GC compliance team that checks the AI box on the COI and moves on may be working with a certificate where the endorsement was never formally added, or where the endorsement form used doesn't provide the coverage the subcontract requires. The insurer's position when a claim occurs: no endorsement was issued; the certificate is informational only and doesn't create coverage.
The fix: For every subcontractor, call the GL agent and confirm the AI endorsement form number (CG 20 10, CG 20 37, or equivalent), the effective date, and the named additional insured. Do not accept the certificate checkbox as confirmation.
Mistake 3: Applying One Limit Schedule to All Trades
A GC who requires $1M GL from every subcontractor - from the demolition contractor to the cleaning crew - is systematically under-requiring the high-risk trades and over-requiring the low-risk ones.
Demolition, steel erection, excavation, and roofing carry materially higher loss potential than interior finishes. A $1M per-occurrence limit for a demolition sub on a $15M commercial project is insufficient by most risk standards. When a demolition incident causes $2M in property damage and injuries, the gap between the $1M limit and the actual loss lands with the GC.
The fix: Implement trade-tiered requirements. High-risk trades (demo, structural, MEP, roofing) should carry $2M/$4M GL minimum and $5M umbrella. Standard trades: $1M/$2M with $2M umbrella. Calibrate to the trade's exposure, not a universal standard.
Mistake 4: Missing Waiver of Subrogation on Workers' Compensation
Most GC compliance teams check for WOS on the GL policy. Fewer check for WOS on the workers' compensation policy. When they miss it, the sub's WC insurer retains subrogation rights against the GC.
The scenario: a subcontractor's employee is injured on a GC-controlled site. The sub's WC insurer pays the claim - and then sues the GC for contribution, arguing that a site condition controlled by the GC contributed to the injury. If there's no WOS on the WC policy, the GC has no defense to the subrogation action.
The fix: Require and confirm WOS on all three primary lines: GL, WC, and auto. Call the WC insurer or agent separately to confirm the WOS endorsement is on the WC policy - it is a separate endorsement from the GL WOS.
Mistake 5: Ignoring the Primary/Non-Contributory Requirement
When both the GC's and sub's GL policies may respond to the same claim, insurers often dispute which policy is primary. Without a primary/noncontributory endorsement on the sub's policy, both carriers may argue the other is primary - delaying and complicating defense while the GC is exposed.
Standard AI endorsements do not automatically include primary/noncontributory language. It requires either a specific endorsement (CG 20 01 or equivalent) or AI endorsement language that explicitly provides P&NC status.
The fix: Require primary/noncontributory in the subcontract and confirm the endorsement exists on the policy. Ask the agent to confirm P&NC language and request the endorsement form if needed.
Mistake 6: Allowing Subs to Self-Submit COIs
COI fraud exists in construction - and it's not rare. Subcontractors have submitted certificates with altered limits, extended expiration dates, and in some cases entirely fabricated policies. The discovery typically happens at claim time, when the GC attempts to access coverage that was never in force.
GCs whose compliance process involves accepting COIs emailed directly from the subcontractor have no verification of authenticity. A GC that has never independently confirmed a certificate with the issuing agent cannot demonstrate that its compliance process was reasonable.
The fix: Require COIs to be submitted directly by the sub's insurance agent - not by the sub. Send the request directly to the agent with the certificate holder requirements and exhibit reference. When you receive a certificate directly from an agent's office, forgery risk drops to near zero.
Mistake 7: Not Tracking Policy Renewals Across the Project Duration
A multi-year project has multiple policy renewal cycles for every active subcontractor. A sub who was compliant at onboarding in Year 1 may have a non-compliant renewal in Year 2 - reduced limits, dropped endorsements, changed insurers - and nobody notices because the compliance review only happened at onboarding.
The lapsed coverage renewal scenario is common and costly. A sub's insurer non-renews coverage mid-project. The sub scrambles for new coverage and submits a renewed COI with a different insurer, lower limits, and missing endorsements. If nobody compares the renewal COI against the subcontract requirements, the GC now has a non-compliant sub working under an approved COI from a prior insurer.
The fix: Every renewal COI must be compared against the subcontract requirements - not just filed. Set 60-day advance renewal requests for every active sub. When renewed COIs arrive, run the same compliance comparison that was run at onboarding.
What These Mistakes Cost
Each of these mistakes, in isolation, is manageable. Together, across a portfolio of 300+ active subcontractor relationships, they represent systemic exposure. The $36,400/year manual compliance cost statistic represents the labor that builds these processes. The $500K+ average uninsured construction incident cost represents what happens when the processes fail.
The math is not close: investing in compliance processes and technology that prevent one material gap per year easily pays for the entire program.
Frequently Asked Questions
Are there any of these mistakes that are acceptable to make in certain situations? Some mistakes are less consequential for low-risk, low-value subcontracts. A painting sub on a $50K scope may not justify the same endorsement verification depth as a structural steel contractor on a $3M scope. Tiered compliance rigor - more intensive for high-risk, high-value subs - is rational. But applying tiered rigor requires first defining which tier each sub falls in, which itself requires a documented process.
How do I handle a sub who is mid-project when a compliance gap is discovered? Issue a formal deficiency notice with a specific remediation deadline. If the gap is material (missing AI endorsement, coverage below minimum), consider suspending work until remediated. The legal and commercial consequences of a mid-project work stoppage are typically less severe than the consequences of an uncovered claim.
What's the GC's liability if a sub's deficiency is known and work continues? Allowing work to proceed with a known coverage deficiency can be characterized as willful indifference to risk - which may eliminate defenses in a coverage dispute and could form the basis of a breach of contract claim by the owner.
Construction COI compliance mistakes are preventable. Every one of the seven above has a clear, documented fix. The question is whether the process and the tools are in place to implement it.
See how Bramble prevents all 7 mistakes for Construction or learn how contract vs. COI comparison works.
Stop making preventable mistakes. Book a demo at getbramble.com.