Is a Certificate of Insurance Legally Binding?

Last updated August 2026.

A certificate of insurance is not legally binding on the insurer. The ACORD 25 states in its own header that it is issued as a matter of information only, confers no rights upon the certificate holder, and does not constitute a contract between the insurer, the producer and the holder. It is evidence that policies existed on the day it was typed. What legally binds an insurer to protect you is the policy and its endorsements.

This distinction decides whether a vendor insurance program actually works. Companies collect certificates by the thousand, file them, and treat a complete folder as proof of protection. The form itself says otherwise, in capital letters, in the first three lines. Understanding exactly what a certificate does and does not do is the difference between a program that transfers risk and one that only documents an intention to.

Is a certificate of insurance a legal document?

Yes, in the sense that it is a genuine industry-standard document issued and signed by a licensed insurance producer, and misrepresenting coverage on one carries professional and legal consequences for the person who issued it. No, in the sense most people mean when they ask. It does not create coverage, grant you rights against the insurer, or oblige anyone to maintain the policies it describes. A document can be real and consequential for its author while giving its recipient nothing.

The clearest way to think about it: some documents evidence a status, and some documents create a right. A certificate evidences. An endorsement creates. Confusing the two is the single most common failure in vendor insurance compliance, and it usually surfaces at the worst possible time, when a claim arrives and the additional insured status everybody assumed existed turns out to have been a ticked box.

Does a certificate of insurance give the certificate holder any rights?

No. The ACORD 25 form opens with three sentences that withdraw exactly that. It states that the certificate is issued as a matter of information only and confers no rights upon the certificate holder. It states that the certificate does not affirmatively or negatively amend, extend or alter the coverage afforded by the policies below. And it states that the certificate does not constitute a contract between the issuing insurers, the authorized representative or producer, and the certificate holder.

Each sentence closes a different door. The first denies you standing. The second stops the certificate from changing the policy, which cuts both ways: a certificate cannot add coverage the policy lacks, and it cannot take away coverage the policy grants. The third stops you arguing that the broker who typed it owes you a contractual duty. Courts across the United States have relied on this language when a certificate holder tried to claim coverage the underlying policy never provided.

What does "issued as a matter of information only" mean?

It means the certificate is a status report rather than a promise. The producer is telling you what the policies looked like at the moment of issuance, as a courtesy, without accepting responsibility for keeping that picture accurate or for the coverage actually responding. Nothing about the phrase is boilerplate that courts ignore. It is the operative disclaimer that defines the document, and it is why a certificate dated last March tells you nothing about whether the policy is in force today.

Is a certificate of insurance a contract?

No, and the form says so directly. A contract requires parties who intend to be bound and consideration passing between them. The certificate holder gives nothing and the insurer promises nothing. The real contracts in this arrangement are two: the insurance policy between the carrier and your vendor, and the commercial agreement between you and your vendor that requires the vendor to carry insurance. You have rights under the second one, against your vendor. The certificate simply reports on whether your vendor appears to be complying with it.

That is genuinely useful. If a vendor cannot produce a certificate, you can hold work, withhold payment or terminate under your own agreement. The certificate is evidence in a dispute with your vendor. It is just not a claim against the vendor insurer.

Can you sue an insurance company based on a certificate of insurance?

Generally no, and the disclaimer is the reason. The usual outcome is that the certificate cannot expand policy coverage, so a holder who was never made an additional insured by endorsement does not become one because a box was ticked. There are narrow exceptions in some states where a certificate holder detrimentally relied on a specific affirmative misstatement, and those cases typically proceed against the producer for negligent misrepresentation rather than against the carrier for coverage. Relying on that is a poor plan. It replaces an insurance claim with litigation you have to win first.

Which insurance documents actually bind someone

The endorsement is the document that matters

The ACORD 25 makes this explicit in the paragraph directly under the disclaimer. It warns that if the certificate holder is an additional insured, the policies must have additional insured provisions or be endorsed, that if subrogation is waived certain policies may require an endorsement, and that a statement on the certificate does not confer rights to the certificate holder in lieu of such endorsements.

Read that as instructions. The form is telling you which two things it cannot prove and what to ask for instead. The ADDL INSD and SUBR WVD columns are the only endorsement indicators on the whole certificate, and both are producer assertions. If your contract requires additional insured status, you need the additional insured endorsement page, usually CG 20 10 for ongoing operations or CG 20 37 for completed operations. If it requires a waiver, you need the waiver of subrogation endorsement, usually CG 24 04. Ask by form number and the request gets answered. Ask for confirmation that coverage is in place and you get another certificate.

Is an insurance binder legally binding?

Yes, and this is the useful contrast. A binder, typically an ACORD 75, is temporary evidence of coverage issued while the policy is being produced, and it obligates the insurer for the period it covers. A binder creates coverage. A certificate reports on it. When a vendor cannot produce a policy or endorsement quickly because a policy was just written, a binder is meaningfully better than a certificate, though it expires quickly and needs following up.

What happens if a certificate of insurance is wrong or fraudulent?

A materially false certificate exposes the producer who issued it to errors and omissions claims and to regulatory action from the state insurance department. Several states specifically prohibit issuing a certificate that misrepresents coverage terms. Forged certificates, usually produced by the vendor rather than any agency, are more common than most people expect and are also the easiest problem to solve: call the producer named on the form using contact details you look up yourself rather than the ones printed on the certificate, and ask them to confirm they issued it. Then request the endorsement pages, since a forger rarely fabricates matching endorsements.

What this means for how you run vendor insurance compliance

If certificates confer no rights, the job is not collecting certificates. The job is confirming that the documents which do confer rights exist, and that the policies behind them are still running. In practice that means four habits.

Record what each contract type actually requires, once, so the review has something to compare against. Request endorsement pages for every additional insured, waiver of subrogation and primary and noncontributory requirement, rather than accepting the checkbox. Track policy expiration dates per coverage line instead of one date per vendor, because auto and general liability rarely renew together. And re-verify at renewal, because endorsements get dropped quietly and the next certificate looks identical to the last one.

Insurance is rarely the only contractual duty a vendor owes you. Teams that also track indemnity, licensing, reporting and data-protection commitments tend to keep them in one place rather than across inboxes, which is what a general obligation and controls register is for. Insurance compliance is one lane inside that, and the reason it needs its own tooling is precisely the problem this article started with: the document everyone collects is the one document that proves the least.

The short version

A certificate of insurance is evidence, not a grant. It binds nobody to insure you. It can be accurate and still leave you with no coverage, because the rights you want live on endorsement pages the certificate merely refers to. Treat the ACORD 25 as a map of what to go and verify, and the compliance program starts doing the thing it was supposed to do.