.webp)
If someone just forwarded you an ACORD 25 certificate and your first instinct was to stare at it and hope it would explain itself, you're in good company. This form shows up constantly in business relationships, and almost nobody gets a proper introduction to it. That ends here.
The ACORD 25 certificate is the standard one-page form used to prove that a business carries liability insurance. You may also hear it called a certificate of liability insurance or simply a COI. Whether you're reviewing it for a contractor, a vendor, or a new partner, this guide walks you through every section that matters, in the order you'll actually encounter it.
An ACORD 25 certificate is the insurance industry's universal document for sharing proof of insurance. ACORD, the Association for Cooperative Operations Research and Development, isn't an insurance company. It's the organization that created the standardized form formats the industry runs on. The "25" refers specifically to the certificate of liability insurance form, as opposed to other ACORD forms covering different document types, such as the ACORD 27, which serves a distinct purpose for evidence of property insurance.
Think of it as a snapshot of a business's current coverage: who's insured, what they're covered for, and for how long.
Yes, completely. The ACORD 25 is the form; COI is the shorthand. Both terms refer to the exact same document. You'll hear people use them interchangeably, and that's fine. The only time it matters is if someone asks you to pull up a specific ACORD form by number, but for day-to-day compliance conversations, COI and ACORD 25 mean the same thing.
Reading an ACORD 25 gets a lot easier once you know which sections to focus on. You don't need to parse every field, just the ones that tell you whether this vendor is actually covered for your work together.
Here's what to look for, in order:
This is the business or individual that holds the policy. It should match exactly who you're hiring or contracting with. If you're working with ABC Electrical and the named insured reads "XYZ Holdings LLC," that's worth a follow-up before you proceed.
The producer is the insurance agent or broker who issued the certificate. This isn't usually a compliance concern, but it's useful contact information if you need to verify anything directly.
This section is the heart of the form. The four core coverage types to look for are general liability insurance, workers’ compensation, auto liability, and umbrella liability (sometimes called umbrella/excess liability). Each line shows the policy number, effective dates, and insurance coverage limits, which means the maximum the insurer will pay per occurrence or in aggregate.
What do those limits mean in practice? If you require vendors to carry at least $1M in general liability insurance, you'd confirm that the "Each Occurrence" limit meets or exceeds that amount. Your contracts or internal compliance requirements should dictate the minimums you're looking for.
The policy expiration date is one of the first things to check. A certificate showing coverage that expired last quarter isn't proof of current insurance. It's proof of former insurance. If the dates are outdated, request a current certificate before the work begins.
The certificate holder is the company that requested proof of insurance. In most cases, that's you or your organization. Your name and address should appear in this field. This matters for record-keeping and for ensuring the right party is identified if a claim arises.
This section notes how much advance notice the insurer will provide if the policy is cancelled or not renewed. Thirty days is standard; some contracts require more. It's a small field, but it tells you whether you'd have time to react if your vendor's coverage lapses mid-project.
This is probably the most common point of confusion on the form. The named insured is the party whose business is actually covered by the policy. The certificate holder is simply the entity that asked for the certificate (you, in most cases).
Being listed as the certificate holder does not give you any coverage rights. If you need protection under the vendor's policy, you'd need to be added as an additional insured, which requires a separate endorsement on the policy. That addition won't appear automatically on the ACORD 25. You'll need to request it and verify it's actually in place.
Here's something the form won't tell you: whether everything listed is still accurate right now.
An ACORD 25 certificate reflects coverage at the moment it was issued. Policies can change after a certificate is generated. Endorsements can be modified, limits can shift, and coverage can lapse between your request and the start of work. The form itself doesn't update automatically, and there's no industry-wide alert that flags changes after the fact.
This isn't a red flag unique to any particular vendor. It's simply how the system works. A certificate is a starting point, not a guarantee. The real compliance question isn't just "does this vendor have coverage?" but "does their coverage stay current throughout our entire working relationship?"
That gap between a one-time certificate review and ongoing, accurate compliance is where most organizations run into trouble.
That's exactly the gap that illumend, powered by myCOI, was built to close.
Reviewing a single COI is manageable. Tracking dozens or hundreds of them across active projects, varying contract requirements, and constantly rotating vendors, is where the process breaks down fast. With help from illumend, teams can manage that complexity without needing an insurance background or a compliance department.
Lumie™, illumend's AI compliance guide, takes this a step further. Rather than just flagging that something looks off, Lumie explains what it means and walks you through what to do next, in real time and in plain terms. It's a bit like using TurboTax for your taxes: you don't finish the process knowing everything about tax law, but you feel confident it was handled correctly. That same guided clarity is what Lumie brings to insurance compliance.
With illumend, the vendor side is also frictionless. No logins are required for third-party partners, and real-time compliance decisions mean you're not waiting days to find out if a certificate meets your requirements.
Ready to stop chasing certificates and start managing compliance with confidence? Schedule a demo to see Lumie in action.
illumend catches the gap.
You save the project.
With Lumie™, compliance is covered. So is everyone on your project.
