What Your Certificate of Insurance Isn't Telling You
Overview
A trade contractor's guide to the gap between "proof of coverage" and actual coverage.
Ask a general contractor, a property manager, or a project owner what a Certificate of Insurance (COI) proves, and you'll get the same answer almost every time: it proves the subcontractor is covered.
That answer isn't quite right, and in some cases it's dangerously wrong.
A COI is not a policy. It isn't even a summary of the policy in any legally binding sense. It's a form, usually an ACORD 25, generated by an agency or carrier at a subcontractor's request, listing the types of coverage in force, the limits purchased, and the effective dates. It exists to communicate, not to guarantee. Near the bottom of nearly every COI, in small print, there's a sentence that undercuts the whole reason people rely on it:
"This certificate is issued as a matter of information only and confers no rights upon the certificate holder. This certificate does not amend, extend, or alter the coverage afforded by the policies below."
So the certificate carries a built-in disclaimer that it can't be relied on for the one thing everyone relies on it for.
That gap, between what a COI seems to promise and what the underlying policy actually provides, is where contractors get hurt. Usually not right away. Usually after a claim has already happened.
Why It Matters More For Trade Contractors
You Own the Loss Even When You Didn’t Do the Work
If you're a trade contractor working under a GC, inside a lease, or as part of a larger project team, certificates run in both directions. You issue them to satisfy contractual insurance requirements, and you often collect them from your own subs to cover your own exposure. Either way, the COI ends up doing more work in your risk transfer strategy than a one-page summary form was ever built to do.
This is really the second half of the coverage gaps piece. That one looked at gaps hiding inside the policy itself, things like sublimits, exclusions, and classification mismatches. This one is about a different problem: even when the policy is fine, the certificate representing it can still fail to tell the whole story, or tell a story that used to be true and no longer is.
What A COI Actually Verifies, And What It Doesn't
A COI can tell you:
That a policy existed as of the date the certificate was issued
The general type of coverage: GL, workers' comp, auto, umbrella, and so on
The stated limits of liability
The named insured, and sometimes additional insured status
What it can't tell you:
Whether the policy is still in force. Certificates are a snapshot. A policy can be cancelled or lapse for non-payment the week after a certificate is issued, and nobody's required to tell the certificate holder unless a specific endorsement says otherwise, and even thentiming varies by carrier.
The actual scope of coverage. A healthy limit doesn't mean much if the policy excludes the exact exposure the contract is trying to transfer, whether that's subsidence, faulty workmanship, EIFS, specific trade operations, or work done by uninsured subs.
The classification the carrier actually used. A COI lists coverage lines, not underwriting codes. A contractor working outside their classified scope may have a policy that responds very differently to a claim than the certificate suggests.
Whether additional insured status is real, or how broad it is. Being listed as a certificate holder isn't the same as being added as an additional insured. And the endorsements themselves vary a lot, some are broad form, some are ongoing-operations-only, some drop off once the work is done. The certificate almost never says which one is attached.
Whether the coverage actually matches what the contract requires. Contracts spell out limits, endorsements like waiver of subrogation or primary and non-contributory language, and sometimes a required duration for completed operations coverage. None of that gets confirmed by a certificate. It just tells you what was purchased, not whether it satisfies what was promised.
Where The Real Risk Hides
Exclusions never show up on the certificate. The ACORD 25 has no field for endorsements or exclusions, so a policy that excludes your exact scope of work looks identical, on paper, to one that doesn't.
Classification drives claim response quietly. Carriers price and underwrite around the operations disclosed at binding. If actual work drifts from what was classified, which happens often when a contractor picks up scope adjacent to their core trade, the certificate keeps looking the same while the policy underneath may respond very differently.
"Additional insured" isn't one thing. There are more than a dozen commonly used AI endorsement forms, and they offer meaningfully different scope. Seeing the words "additional insured" in the description box tells you almost nothing about which version is attached.
Timing gaps are common and easy to miss. Projects run long, and certificates are often issued once, at the start, and never refreshed unless someone specifically asks. A twelve-month job with a certificate from month one is running on eleven months of assumption.
Primary and non-contributory language is either endorsed onto the policy or it isn't. Contracts often require a sub's coverage to respond first, ahead of the GC's own policy, with no cost-sharing. Whether that's actually on the policy, versus just written on the certificate, isn'tsomething you can tell without looking at the policy itself.
The Practical Consequence
None of this shows up until there's a claim. A COI problem is rarely a paperwork issue in the moment, it's a discovery made by whoever is holding the bag when a carrier denies coverage, disputes additional insured status, or points to an exclusion nobody knew was there. By then, the whole reason the certificate was collected in the first place has already failed, and it's failed at exactly the moment it was supposed to work.
The Only Way To Actually Know
There's no real shortcut here. A certificate can be requested and filed away in a few minutes. Confirming that the coverage behind it actually matches what a contract requires, the right endorsements, the right classification, the right limits, the right duration, takes an actual look at the policy: the declarations page, the endorsement schedule, the exclusions.
That's a level of scrutiny most contractors, GCs, and property managers never apply, mostly because it doesn't feel necessary until something's already gone wrong. But it's a straightforward step, and it's worth doing before a contract is signed or a sub is put to work, not after a loss.
That's what our Gap-Free Policy Audit is for. We pull the actual policy behind the certificate, declarations, endorsements, exclusions, and check it against what your contracts actually require, so you know before a claim forces the question.
If you want a second set of eyes on a policy behind a certificate, yours, a sub's, or one tied to a contract you're about to sign, that's a conversation worth having now, while there's still time to fix what's found.
