Certificate of Insurance vs. Proof of Insurance: What's the Difference

"Proof of insurance" is not a document. It's a category — anything that shows an active policy exists. A certificate of insurance is one specific document inside that category: a standardized, one-page form issued by a licensed insurance producer, summarizing coverage types, limits, and dates for a named third party.

The distinction matters more than it sounds like it should, because the two phrases produce different results when you say them out loud. Email a vendor "please send proof of insurance" and you may get back a photo of their insurance ID card, a forwarded renewal notice, or a screenshot from their insurer's mobile app. All three are, technically, proof that a policy exists. None of them tell you the limits, whether you're named as an additional insured, or whether the policy covers the work they're about to do on your property.

Ask instead for a "certificate of insurance" — the ACORD 25 form specifically — and you get a document built for exactly this purpose: verifiable, standardized, and issued independently by the vendor's broker rather than handed to you by the vendor. This guide covers what separates the two, where two related documents (the insurance binder and the evidence-of-property-insurance form) fit in, and which one to actually ask for.

A certificate of insurance is a representation, at a single point in time, of the insurance a business has purchased — issued by that business's insurer or broker to a third party who needs to confirm coverage exists. The International Risk Management Institute's definition is precise on this point: a COI "has no bearing on the insurance coverages being represented"; it is evidence of the policy, not the policy itself, and it does not amend or extend coverage in any way.

In US commercial contexts, the certificate almost always means the ACORD 25 — "Certificate of Liability Insurance" — a form maintained by ACORD (the insurance industry's standards body) and used by virtually every carrier and broker in the country. Because the form is standardized, every field sits in the same place on every certificate: insurer, named insured, coverage grid, limits, policy dates, and the certificate holder box. That predictability is what makes a COI checkable — you know exactly where to look for the number you need. See the ACORD 25 glossary entry for a field-by-field breakdown.

Two things distinguish a COI from every other document that could loosely be called "proof of insurance": it is issued directly by a licensed producer rather than handed over by the insured party, and it names a specific certificate holder — you — rather than being a generic statement of coverage.

Ask a vendor for "proof of insurance" without specifying the document, and any of the following technically qualifies. None of them do what a certificate does.

A binder is a different document again, and it's worth naming because it shows up in the same conversations. Where a certificate of insurance verifies a policy that is already in force, a binder verifies coverage that is about to take effect — typically issued to bridge the gap between a policy being agreed and the formal paperwork being finalized, and it usually expires on its own within 30 to 90 days.

A binder is the right document at a real estate closing or when a new policy is bound mid-negotiation. It is the wrong document for ongoing vendor compliance, because it is temporary by design and isn't meant to be the permanent record a business keeps on file. If a vendor sends a binder in response to a certificate request, treat it as a placeholder — request the actual certificate once the policy is fully in force.

One more distinction trips people up, because it isn't about how solid the document is — it's about which risk it covers. The ACORD 25 shows liability coverage: whether a business can pay for injury or damage it causes to someone else. It's the form you request from a contractor, cleaner, or landscaper working on your property, and it's what every other guide on this site is built around.

The ACORD 27 and ACORD 28 forms show something different: evidence of property insurance, meaning whether the business's own property is covered if it's damaged or destroyed — the ACORD 27 for residential or small commercial property, the ACORD 28 (the more detailed of the two) for commercial buildings and equipment. Lenders and mortgage holders ask for these because they have a financial interest in the property itself, not in who it might injure.

The two aren't interchangeable, and requesting the wrong one gets you a document that answers a question you didn't ask. If you're leasing equipment or space and need confirmation the lessor's property is insured, that's an ACORD 27/28 conversation. If you're hiring anyone to do work that could hurt someone or damage something, that's the ACORD 25 — the certificate of insurance covered throughout the rest of this site.

This is the part every other article on this topic skips, and it's the one piece of practical advice that actually changes the outcome: the vague phrase "proof of insurance" invites a vague answer, and the specific phrase "certificate of insurance" invites a specific one.

Say "send proof of insurance" and a vendor who wants to move fast will send whatever is easiest to find — often a screenshot or a declarations page — because nothing in the request told them otherwise. Say "please have your broker send a certificate of insurance, ACORD 25, naming [your legal entity] as certificate holder" and there is only one document that satisfies it. The second version costs you nothing extra to type and removes an entire category of unusable responses.

This is the same principle covered in more depth, with copy-paste email templates, in how to request a certificate of insurance from a vendor — the wording of the ask determines whether you get a compliant document on the first try or a week of back-and-forth.

Once you have an actual ACORD 25 in hand, having the right document is only step one — it still has to be checked. Every certificate should be run through the same review before you consider a vendor compliant:

The patterns that turn a simple document request into a compliance gap discovered too late.

One request is easy to phrase correctly. The difficulty is doing it every time, for every vendor, across renewals that land on different dates all year — which is exactly where a casual "send proof of insurance" email creeps back in, because it's faster to type than the specific version.

This is a wording problem the first time and a tracking problem every time after. CoverSynx standardizes the request — vendors get a link that asks specifically for a certificate of insurance and checks what comes back against your requirements, flagging a declarations page or an expired certificate before you'd otherwise notice. It assists verification; it doesn't certify coverage or replace confirming anything unusual directly with the vendor's broker. For the fuller collection and renewal workflow, see how to track certificates of insurance, and for what forged or doctored certificates look like specifically, how to spot a fake certificate of insurance covers verification in depth.