Support¿Hablas español? Access Portal
VETTICVETTIC
Resources

Insurance Forms

Understanding ACORD 25 Forensics: How to Audit a Certificate of Insurance for Construction Gaps

A forensic, field-tested checklist for General Contractors and Brokers: how to audit an ACORD 25 (COI) for hidden construction insurance gaps like missing Additional Insured wording, Primary & Non-Contributory, Waiver of Subrogation, and policy/effective date mismatches.

Why ACORD 25 “looks compliant” while your project stays exposed

An ACORD 25 (Certificate of Liability Insurance) is a summary of coverage “as of the date issued.” In construction, the gap happens when teams treat the certificate as proof of contractual risk transfer.

Key constraint: the ACORD form itself typically includes language that it does not amend, extend, or alter coverage. That’s why forensic COI audits focus on what’s missing as much as what’s shown.

What your COI audit must accomplish (the forensic standard)

Your objective is not “a COI on file.” Your objective is verifiable alignment between:

  • Contract requirements (insurance + endorsements + limits + project specifics)
  • Policy reality (forms/endorsements actually issued)
  • Dates + parties (who is covered, where, and when)
  • Evidence chain (audit-ready proof you verified it)

If you can’t defend it in a claim file, it’s not compliance.

Step-by-step: how to audit an ACORD 25 for construction gaps

1) Verify the certificate is project-relevant (not just “active somewhere”)

Audit checklist:

  • Named Insured matches the subcontractor entity on contract (watch for “DBA” vs legal entity).
  • Producer (broker/agent) is identifiable and contactable.
  • Certificate holder field is correct for your job (many are issued to the wrong GC/owner).
  • Project / location is present when your contract requires it (often in the Description/Remarks box).

Failure modes to flag:

  • Certificate holder is your corporate HQ, but the contract requires the project owner or project-specific holder.
  • The COI references the wrong project name or address (common in multi-job subs).

2) Confirm policy types match the job’s risk profile

On ACORD 25, confirm these are present when required:

  • Commercial General Liability (CGL): the baseline for most trades
  • Automobile Liability: especially when subs drive on/off site
  • Workers Compensation / Employers Liability: required for labor exposure
  • Umbrella / Excess: required for higher limits or high-hazard scopes

Construction-specific audit note:

  • “Umbrella exists” is not the same as “Umbrella follows form over CGL + Auto + EL.” If the umbrella doesn’t follow form, your limits stack can fail when you need it most.

3) Dates: the easiest gap to miss (and the easiest to prove you checked)

Audit checklist:

  • Policy effective date is on/before the subcontract start date.
  • Policy expiration date extends through the work window (and sometimes through warranty/operations where contract requires).
  • If the COI is reissued, document what changed (limits, carriers, endorsements, dates).

Evidence requirement:

  • Your compliance record should show “verified on” date and who verified it. In a dispute, “we had a COI” is weak; “we verified dates and endorsements on MM/DD/YYYY” is defensible.

4) Limits: verify the limits you need are the limits that matter

Common construction trap:

  • ACORD 25 may show limits, but sub-limits and aggregate erosion are not obvious.

Audit checklist:

  • Each Occurrence and General Aggregate meet contract.
  • Products/Completed Operations Aggregate is present and sufficient (critical for post-completion claims).
  • If your contract requires project-specific aggregates (rare but important), the ACORD alone is not enough—request evidence of the endorsement.

5) Additional Insured (AI): the words on the COI aren’t the endorsement

Most construction disputes revolve around whether the GC/Owner is actually Additional Insured under the policy and whether it’s ongoing + completed operations where required.

Audit checklist:

  • In the Description/Remarks box, look for AI language referencing the GC/Owner and the job.
  • Do not accept “AI: yes” without the endorsement form. Require the actual endorsement number (example patterns vary by carrier).
  • Confirm whether AI applies to:
    • Ongoing operations
    • Completed operations (often a separate endorsement requirement)

Operational policy:

  • Require a copy of the AI endorsement(s) when the contract requires AI. Treat the certificate as a pointer, not the proof.

6) Primary & Non-Contributory (PNC): the gap that turns into real money

PNC governs who pays first. If your subcontract requires PNC and you don’t verify it, you can end up funding defense costs or settlements you assumed would flow to the sub’s carrier.

Audit checklist:

  • The COI may state “Primary & Non-Contributory,” but you need:
    • Endorsement language or form reference confirming PNC for the additional insureds
    • Evidence it applies to your project (not a generic statement)

7) Waiver of Subrogation (WOS): the gap that creates post-claim litigation

WOS prevents the carrier from pursuing recovery against your party after paying a claim (when required by contract).

Audit checklist:

  • If WOS is required, verify:
    • WOS endorsement exists
    • It applies to the required lines (WC is common; CGL/Auto may also be required)
    • It applies to the additional insured / certificate holder as specified

8) “Description of Operations / Locations / Vehicles”: the most important box

Construction contracts live here because ACORD 25 fields can’t express:

  • Project name + address
  • Owner / GC / CM naming conventions
  • AI/PNC/WOS clauses
  • Completed operations requirements

Audit checklist:

  • The remarks must be specific (named parties + job) and non-contradictory.
  • If the remarks are vague (“as required by written contract”), treat it as a risk indicator and request endorsements.

9) Proof standard: what to request beyond the ACORD 25

Minimum “forensic” request set when the contract requires risk transfer:

  • Additional Insured endorsement(s) (ongoing + completed operations as required)
  • Primary & Non-Contributory endorsement (if required)
  • Waiver of Subrogation endorsement(s) (WC and/or GL/Auto as required)
  • Policy declarations (at least key pages confirming insured, term, and limits)

When you should escalate:

  • High-hazard scopes (roofing, structural steel, demolition)
  • Large contract values
  • Owner-mandated endorsements or OCIP/CCIP contexts

Audit outcomes: classify the COI into clear decision buckets

  • Green (Verified): COI aligns with contract and endorsements/proofs are verified where required.
  • Yellow (Conditional): COI is plausible but missing verification artifacts (endorsements/dec pages). Work starts only after cure.
  • Red (Gap): clear mismatch (missing policy type, dates, AI/PNC/WOS not verifiable, wrong insured entity).

Common construction “gap patterns” to train your team on

  • Wrong insured entity (holding company vs operating entity)
  • AI language without endorsement evidence
  • PNC claimed but not documented
  • WOS only on WC but contract requires GL/Auto too
  • Expired policies hidden by a reissued COI without updated term
  • Umbrella present but not follow-form

Practical compliance workflow (so you can prove you audited it)

  1. Intake the COI and parse the fields (insured, carriers, policy numbers, dates, limits).
  2. Compare against contract requirements (AI/PNC/WOS, limits, lines).
  3. If any endorsement is required, request it and store it.
  4. Record a verification event (who, when, what was verified).
  5. Re-verify on renewal and on scope/contract change.

Not legal advice

This resource is a technical risk-management guide for construction insurance compliance. For contract interpretation or coverage disputes, consult qualified counsel and the issuing broker/carrier.