A $38 million hospital addition in Atlanta is six weeks from substantial completion when a fire starts in the mechanical room. Damage totals $4.7 million. The HVAC subcontractor's COI is on file; it shows a $2 million per-occurrence general liability limit. What the GC didn't verify: the sub's policy contained a professional services exclusion that applied to the design-assist work the sub had performed on the mechanical system. The sub's carrier denies the claim. The builder's risk policy covers the physical damage, but the subrogation chain unravels in litigation for the next three years.
A certificate of insurance is evidence that coverage exists - not proof that the coverage is correct, adequate, or applicable to the work being performed. Understanding what a COI actually tells you, and what it doesn't, is foundational to construction insurance management.
What a Certificate of Insurance Is (and Isn't)
An ACORD 25 certificate of insurance is a one-page summary document issued by an insurance agent or broker. It represents the agent's understanding of the policies in force at the time of issuance. It is not a policy. It is not a guarantee of coverage. It does not bind the insurer to provide coverage as described.
This is not a technicality. Courts have repeatedly held that insurers are not bound by representations made on certificates of insurance if those representations differ from the actual policy terms. If the COI shows a $2 million per-occurrence limit but the policy contains a sublimit for a specific type of claim, the sublimit controls.
What the COI does provide: a starting point for verification. It tells you the insurer, the policy numbers, the effective dates, and the stated limits. It gives you enough information to ask the right follow-up questions.
ACORD 25 Fields for Construction
Understanding each field on the ACORD 25 helps you catch errors before they become coverage disputes.
| Field | What It Shows | What to Check |
|---|---|---|
| Producer | Insurance agent/broker name | Contact info for follow-up questions |
| Named Insured | Legal entity covered | Must match the subcontract signing entity exactly |
| Insurer columns (A-F) | Carrier names | Verify carriers are admitted in the project state and financially rated |
| Policy Type | Commercial GL, auto, WC, etc. | All required lines are present |
| Policy Number | Unique policy identifier | Use to request endorsements directly from carrier |
| Policy Effective/Expiration | Coverage dates | Both current and extending through project period |
| Limits | Per-occurrence, aggregate, etc. | Meet or exceed contract minimums |
| Description of Operations | Free-text field | Often contains AI/WOS language; not a substitute for endorsements |
| Certificate Holder | Entity receiving notice | Must be the correct legal GC entity |
| AI / WOS Checkboxes | Indicates endorsement requested | Does NOT confirm endorsement terms or scope |
The description of operations box is frequently misused. Agents will write "additional insured per written contract" or "waiver of subrogation applies" in this field. That language is informational - it describes what the agent believes to be true, not what the policy actually provides. If you're relying on the description box for AI or WOS confirmation, you're relying on the wrong source.
Project-Specific Requirements vs. Standard Requirements
Many GCs use a single standard insurance exhibit across all subcontracts, then wonder why their compliance rates are poor. Project-specific requirements often differ substantially from standard templates.
Lender requirements: Construction lenders frequently impose insurance requirements that exceed standard subcontract terms - higher limits, additional endorsements, or requirements that the lender itself be named as an additional insured. These requirements flow down from the owner and must be incorporated into subcontracts.
Owner requirements: Sophisticated owners, particularly public agencies and large developers, specify insurance requirements in the prime contract that GCs must flow down. If your subcontract doesn't match the prime contract requirements, you're carrying the gap.
Project type adjustments: A multifamily residential project requires attention to residential exclusions in GL policies. A project adjacent to an existing structure requires XCU (explosion, collapse, and underground hazard) coverage confirmation. A project with design-assist elements requires professional liability on top of standard GL. Standard templates don't capture these distinctions.
Subcontract value thresholds: Higher-value subcontracts should carry higher limits. A $5 million mechanical subcontract warrants different requirements than a $150,000 landscaping subcontract. Tiered requirements by subcontract value and risk level produce better outcomes than a single standard across all subs.
Builders Risk Coordination
General liability and workers' compensation get most of the attention in construction COI management, but builders risk coordination is equally important and frequently mishandled.
Who provides builders risk: On most commercial projects, the GC or owner provides builders risk coverage for the project structure. Subcontractors are typically named insureds or additional insureds under the builders risk policy - not the GL policy - for physical damage to their work.
What this means for COIs: Subcontractor GL policies are not the vehicle for physical damage coverage on the project itself. A sub's GL policy covers third-party claims. Physical damage to the project (fire, wind, vandalism) is a builders risk matter. Understanding this distinction prevents coverage gaps and disputes about which policy responds first.
Subcontractor materials: Coverage for materials stored off-site, in transit, or at the job site before installation can fall in gaps between the sub's inland marine coverage and the project builders risk policy. Verify that your builders risk policy covers materials from the point of ownership, and confirm that subs don't have conflicting coverage that could complicate claims.
Installation floaters: Mechanical, electrical, and specialty subs often carry installation floaters to cover their work product during installation. Confirm how these policies coordinate with the project builders risk policy to avoid coverage gaps or duplicate coverage disputes.
What to Check on Each COI
Beyond the standard limit and date checks, construction COIs warrant the following specific reviews:
Residential exclusions: GL policies for commercial contractors often contain exclusions for residential or mixed-use projects. If the project is residential (apartments, condominiums, single-family homes), verify that the sub's policy doesn't contain a residential exclusion.
Subsidence and earth movement: Excavation, foundation, and grading subs should not have subsidence or earth movement exclusions on their GL policies, or if they do, should carry separate coverage for these risks.
Mold and fungi: On projects with significant moisture exposure, verify that mold and fungi exclusions on sub policies don't create gaps, particularly for waterproofing and roofing subs.
Professional services: Any sub performing design-assist, engineering, or other professional services should carry professional liability in addition to GL. Standard GL policies exclude professional services claims.
Employment practices: Not a direct project risk, but if a sub's workers bring an EPLI claim during the project, it can complicate the project relationship. Some GCs require EPLI for larger subcontract values.
The Limits of COI Collection Without Verification
COI collection programs - systems designed to gather, store, and track certificate receipt - are widespread in construction. They solve the document management problem but not the compliance problem.
A collection system can tell you that a COI was received. It cannot tell you whether:
- The limits match the contract requirements
- The named insured matches the signing entity
- The AI endorsement is the correct form
- The WOS applies to all required lines
- The coverage contains exclusions that contradict the subcontract requirements
COIs are collected at a rate of roughly 70% first-submission non-compliance in the construction industry. Collection without verification means 30% of your subs have gaps that you've documented but haven't addressed.
Connecting COI Review to the Subcontract
The verification process only works when the COI is compared against the specific subcontract requirements - not against a general standard. This is where manual processes break down: reviewers often don't have the subcontract in front of them when reviewing the COI, or they're comparing against a remembered standard rather than the actual contract language.
Automated contract-to-COI comparison reads the subcontract, extracts the insurance requirements, and compares them directly to the COI data. Bramble handles this process across your entire sub portfolio - extracting requirements from subcontract language and flagging every discrepancy between what was required and what was submitted.
For GCs managing large project portfolios, this is the difference between documented compliance and documented exposure. Request a demo to see how Bramble handles construction certificate of insurance compliance.