The 9 things on a COI that actually matter (and the ones you can skip)
The ACORD 25 has a few dozen fields on it. Most offices try to read all of them, get bogged down somewhere around the policy number column, and end up either filing the certificate without really checking it or sending it back with a question that isn’t actually the problem.
I’ve read hundreds of these. There are nine things worth your attention. The rest is mostly there for the insurance industry, not for you.
The ACORD 25, at a Glance
A simplified illustration — the gold markers on the form match the numbered explanations.
A simplified diagram of the ACORD 25 Certificate of Liability Insurance form, divided into sections labeled Producer, Insured, Coverages, Cancellation, and Certificate Holder. Five numbered callouts explain each section: the disclaimer at the top stating the certificate is informational only, the Producer box identifying the issuing agency, the Insured box identifying the subcontractor, the ADDL INSD column showing whether additional insured status is indicated, and the Cancellation section stating notice will be delivered according to policy provisions.What you can skip
The producer’s full mailing address. The NAIC number. The revision date in the corner. The policy form numbers. The disclaimer paragraph at the top — yes, the one in all caps. You’ve read it a hundred times. It hasn’t changed since 2009 and it isn’t going to.
Skip them. Spend your attention on the nine that matter.
The nine that matter
1. The date the certificate was issued. If it’s from last year, what you’re holding is a record of what used to be true. Policies underneath have almost certainly renewed since then, and the certificate hasn’t gotten the memo.
2. The insured name. Has to match the legal name on the subcontract. Not the DBA, not “Bob’s crew” — the actual entity on the contract. Mismatches here are where coverage arguments start.
3. The producer. The agency that issued the certificate. Worth a quick glance against the sub’s last certificate. If the agency changed and nobody mentioned it, that’s a conversation worth having before filing.
4. The policy lines listed. General Liability, Auto, Umbrella, Workers’ Comp. If the sub has employees and there’s no Workers’ Comp line, that’s a question. If your contract calls for a coverage type and it isn’t listed, that’s also a question.
5. The expiration dates. All of them. One sub’s GL might run twelve months while their auto runs on a different cycle entirely, because insurance is like that. You want every date on your own clock, not theirs.
6. The limits. Compare to what the subcontract calls for. If the contract says $2M aggregate and the certificate shows $1M, you’ve found your reason to call.
7. The ADDL INSD column. A check means the policy should include additional insured status — but only if it’s actually been endorsed onto the underlying policy. A check on the certificate alone doesn’t create the right. If your contract calls for it and the box is unchecked, that’s an immediate flag.
8. The SUBR WVD column. Same logic. A check means the policy should include a waiver of subrogation. Same caveat — the certificate references it, the endorsement is what actually creates it.
9. The Description of Operations box. This is where the project gets named, where endorsement references get listed, and where cancellation notice language sometimes lives. A blank DOO box on a project that calls for the job to be referenced is a flag.
That’s it. Nine fields. Everything else on the form is either context, boilerplate, or there because the insurance industry needed somewhere to put it.
The one thing nobody tells you about the cancellation language
This is the part I'd most want a GC's office to understand, because it's quietly working against you.
Older ACORD 25s used to say the carrier would "endeavor to mail" notice of cancellation. Which sounds reassuring until you sit with the word "endeavor" for a minute. ACORD changed that language in September 2009. The current form just says notice will be delivered "in accordance with the policy provisions."
In plain English: if a sub’s policy gets cancelled in the middle of your project, most standard policies don’t require the carrier to notify you directly. Notice generally goes to the first named insured — that’s the sub — and the certificate holder finds out whenever the certificate holder finds out.
Which is usually too late.
A lot of GCs ask their subs to include cancellation notice language in the DOO box, typically 30 days for cancellation and 10 days for nonpayment. It's a reasonable ask. The thing worth knowing: text in the DOO box, by itself, doesn't change what the underlying policy requires the carrier to do. Same pattern as the ADDL INSD checkbox — the certificate can reference it, but the obligation only exists if it's been added to the policy through a Notice of Cancellation endorsement. And even then, most of those endorsements exclude cancellation for nonpayment, which is, in my experience, one of the most common reasons a policy actually lapses mid-project.
None of that is a reason to skip asking for the endorsement. It's a reason to know what it gives you and what it doesn't. Whether to require it on a given job, and what language fits your contracts, is a conversation for your attorney and the sub's agent.
The practical takeaway: a 30-day notice line in the DOO box looks reassuring on its own, but the form itself is quietly telling you the carrier won't be the one keeping your clock running on each sub's policy. That clock has to live somewhere on your side of the operation.
The disclaimer at the top says the quiet part out loud
Just below the header, in capital letters, every ACORD 25 says: "THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER."
That sentence is the whole point of the form, hiding in plain sight at the top. The certificate documents what existed when it was issued. It does not change what the policy covers, and it does not give the certificate holder rights the policy itself doesn't already grant.
The certificate points at the policy. The policy is the document that actually controls. If a particular contract has higher stakes, some GCs go beyond the certificate and request the policy declarations page or specific endorsements from the sub’s agent. Whether to do that on a given job is a call for you and your attorney.
What to actually record
Out of the few dozen fields on the form, here's what's worth capturing somewhere you can find again:
Who the insured is
What policies are listed
What the limits are
When each policy expires
Whether ADDL INSD and SUBR WVD are checked
How recent the certificate is
That list — and a system that flags what's missing or expiring before it becomes a problem — is exactly what CCS is built to do. Subs email their certificates in, the system organizes the documents, records the dates and limits, and flags the gaps. It doesn't make coverage decisions. Those still belong with you, your agent, and your attorney. CCS just makes sure the documentation side of the work doesn't get lost in somebody's inbox.
This post is general information about how COI documentation works. It is not insurance advice, legal advice, or a compliance determination. For questions about your specific coverage or contracts, talk to your licensed insurance agent or attorney.
