Construction COI Compliance Checklist: What Every GC Must Verify

A framing subcontractor on a $22 million multifamily project in Denver submits their COI on Monday morning. The project admin checks the AI box - it's checked. Checks the limits - they meet the contract minimums. Files it. Three months later, a sub-sub's worker is seriously injured. During litigation, defense counsel discovers that the AI endorsement covers the named GC entity, but the project was contracted under a different LLC - a common structure for large developers. The additional insured coverage doesn't apply. Defense costs alone reach $800,000 before the case settles.

The checklist failed not because it was incomplete, but because the person using it didn't know that the AI checkbox on an ACORD 25 is not the same as a properly issued endorsement covering the right entity.

This guide gives you the complete verification checklist and explains the failure modes that most COI review processes miss.

The Core Problem: Collection vs. Verification

Most GC compliance processes are built around collection. The sub submits a COI, someone marks it received, and it goes into the file. That is not compliance management - it is document storage.

Verification means comparing every field on the COI against every requirement in the subcontract. It means checking endorsements, not just checkboxes. It means confirming that the named insured on the COI matches the legal entity that signed the subcontract. It means tracking renewal dates and re-verifying when policies renew.

The checklist below is organized by category. Work through every item on every COI, on every project, at every renewal.

Section 1: Named Insured Verification

• The named insured on the COI is the exact legal entity that executed the subcontract
• If the sub operates under multiple entities (e.g., "ABC Plumbing LLC" vs. "ABC Plumbing Inc."), confirm the signing entity is the insured entity
• If the sub is a sole proprietor, confirm the individual's name is correct
• The certificate holder matches the GC's correct legal entity name (not a DBA or outdated name)
• If the project requires the owner or lender to be a certificate holder, their name appears correctly

Entity name mismatches are responsible for a significant portion of coverage disputes. A sub operating as "Smith Electrical LLC" that has coverage under "Smith Electric Inc." may find their insurer denying coverage based on named insured discrepancies.

Section 2: Policy Dates

• All policies are currently in force (effective date before today, expiration date after today)
• Policy expiration dates extend through the anticipated project completion date
• If a policy expires during the project, a renewal COI process is in place and triggered before expiration
• For completed operations exposure, confirm the policy period or the extended reporting period (ERP) covers the required tail period

A COI with an expiration date two weeks from submission is a red flag. It either means the sub is scrambling, or it means their annual renewal is imminent and the coverage may change.

Section 3: Limits Verification by Trade

Match limits against your subcontract requirements. Do not rely on memory or standard minimums - check the actual contract.

Coverage Line	What to Verify
General Liability - Each Occurrence	Meets or exceeds contract minimum
General Liability - General Aggregate	Meets or exceeds (note: aggregate applies per policy, not per project, unless project aggregate endorsement is in place)
General Liability - Products/Completed Ops	Meets or exceeds contract minimum
Workers' Compensation	Statutory limits for the applicable state
Employers' Liability	Meets contract minimums (typically $500K/$500K/$500K or $1M/$1M/$1M)
Commercial Auto	CSL meets contract minimum; confirms hired/non-owned coverage if required
Umbrella/Excess	Meets contract minimum; confirm it follows form over GL, WC, and auto

Project-specific aggregate endorsement: Large projects often require a per-project aggregate on general liability. The standard policy aggregate is shared across all the sub's projects - if they have a large claim elsewhere, your project may be exposed to a depleted aggregate. Verify whether your contract requires a per-project aggregate and whether the COI reflects it.

Section 4: The Endorsement Problem

This is where most compliance processes break down. The ACORD 25 certificate has checkboxes next to additional insured and waiver of subrogation. Those checkboxes indicate that an endorsement has been requested - not that a compliant endorsement exists on the policy.

Additional Insured Verification:

• AI checkbox is checked on the GL line
• AI endorsement form number is listed (CG 20 10 for ongoing operations, CG 20 37 for completed operations)
• The AI endorsement names the correct GC entity - not just "as required by contract" (blanket AI language may not hold up for specific project claims)
• If your contract requires both ongoing and completed operations AI, both form numbers appear
• For high-value projects, request the actual endorsement page from the sub's insurer, not just the COI

Waiver of Subrogation Verification:

• WOS checkbox is checked on GL line
• WOS checkbox is checked on workers' compensation line
• WOS checkbox is checked on auto line (if required by contract)
• For workers' comp, confirm the WOS endorsement form (CG 24 04 or equivalent) is included

A COI that shows "blanket additional insured" in the description box is better than nothing, but it is not a substitute for verifying the endorsement form. Blanket AI endorsements come in many forms, and some exclude completed operations or contain project-type restrictions that may not be apparent from the COI.

Section 5: Coverage-Specific Checks

General Liability:

• No professional liability exclusion affecting the trade's core work
• No residential exclusion if the project is residential or mixed-use
• No subsidence exclusion for excavation or foundation work
• Confirm "explosion, collapse, and underground hazard" (XCU) coverage is not excluded if the work involves excavation or blasting

Workers' Compensation:

• State listed matches the project state
• If the sub employs workers in multiple states, confirm the policy covers all applicable states

Commercial Auto:

• Hired auto and non-owned auto coverage included if required
• Any vehicle exclusions reviewed against the sub's scope

Section 6: Common Subcontractor COI Mistakes

These are the deficiencies that appear most frequently in construction COI audits:

1. Wrong entity name: Sub submits COI under parent company; the subcontract is with the subsidiary
2. Expired policies: COI submitted days before a policy renewal, then renewal COI never submitted
3. Missing completed operations coverage: Ongoing ops AI is on the COI; completed ops is not
4. Aggregate limits already eroded: The policy aggregate shown is the original limit; actual remaining aggregate may be lower due to other claims
5. No per-project aggregate: Contract requires it; COI doesn't reflect it
6. Wrong certificate holder name: GC's entity name is incorrect, misspelled, or is an outdated legal name
7. WOS only on GL: Contract requires WOS on all three lines; COI only shows it on GL

Section 7: Verification Frequency

Initial COI verification is not a one-time event. Policies renew annually. Subcontractors switch carriers. Coverage terms change. A sub who was compliant at project start may be non-compliant six months in.

Build a renewal tracking process:

• Set calendar reminders 45 days before each sub's policy expiration
• Require renewal COIs 30 days before expiration
• Place non-compliant subs on work stoppage if renewal COI is not received and verified before their current policy expires
• Re-run the full verification checklist on every renewal COI - do not assume terms carried over

How Automation Solves the Scale Problem

A 50-subcontractor project means 50 initial verifications, potentially 50 renewal cycles, and hundreds of individual data points to track. Manual review at that scale produces errors - not because the reviewer is careless, but because humans are inconsistent when reviewing large volumes of similar documents.

Automated COI compliance tools read the subcontract requirements, parse the COI, and flag every discrepancy. Bramble compares contract language to certificate fields automatically, identifying missing endorsements, limit shortfalls, and entity mismatches without manual field-by-field review. When a renewal comes in, the comparison runs again.

The result is consistent, documented compliance decisions at a fraction of the manual labor cost - and an audit trail that demonstrates due diligence if a claim arises.

For general contractors managing multiple concurrent projects, automated verification is not a luxury. It is the only way to maintain genuine compliance across a full project portfolio. See how Bramble works for construction teams.