How to Read a Certificate of Insurance Field by Field

Certificate of insurance gets used loosely, as if the document itself were the coverage. Precisely, it is a one page summary of policies that were in force on the day it was issued, and nothing more. Learning how to read a certificate of insurance means learning which of its fields carry legal weight and which are only assertions. That distinction decides whether the risk you thought you transferred to a vendor actually sits on their policy, or quietly on yours.

The form, at least, is predictable. Most certificates in the United States arrive on the ACORD 25 certificate of liability insurance, which puts the same information in the same boxes every time. That consistency is what makes a disciplined read possible, and it is why certificate review can be systematized instead of improvised.

What Each Field on the Certificate Actually Tells You

Seven regions of the form carry almost all of the weight, and each one has a clear limit to what it can prove.

Two narrow columns sit between the coverage rows and the limits, and they deserve more attention than their width suggests: ADDL INSD and SUBR WVD. A check in either one is an assertion that an endorsement exists. It is not the endorsement.

The Distinctions Practitioners Get Wrong

Certificate holder is not additional insured. Being named in the certificate holder box means a document was addressed to you. It grants you no rights under the policy at all. Additional insured status is what gives you a defense and indemnity position, and it comes from an endorsement, not from that box. This is the most consequential misread on the form, and it is worth knowing what an additional insured actually is before treating any certificate as proof.

The checkbox is not the grant. ADDL INSD checked tells you the agency believes an additional insured endorsement is attached. The endorsement itself defines the scope: whether it covers ongoing operations only or completed operations too, whether it is limited to liability caused by the vendor, whether it survives the end of the contract. Request the endorsement when the stakes justify it. A summary is only as good as the party who wrote it, and here that party is the one being checked.

Aggregate limits are shared, not reserved. A general aggregate is the most the policy will pay across every claim in the policy period, for every certificate holder at once. A vendor working for 40 companies has one aggregate serving all of them. A per project aggregate endorsement changes that, and it belongs in the contract rather than in your hopes.

Primary and non contributory is not a field. Neither is waiver of subrogation, beyond that one column. Both are endorsement terms, and both often appear only as a sentence somebody typed into Description of Operations. Typed text in that box is a claim about an endorsement, not the endorsement. Adjacent distinctions such as blanket contractual liability and the four types of endorsement sit in the same territory.

Occurrence and claims made are not interchangeable. An occurrence policy responds to injury that happened during the policy period, whenever the claim eventually arrives. A claims made policy responds only if the claim is reported while the policy is active. For work with a long tail, that single difference is the entire risk transfer.

Why a Field by Field Read Changes the Workflow

Once you know how to read a certificate of insurance properly, the bottleneck moves. The problem stops being comprehension and becomes comparison, at volume, against a requirement that lives somewhere else.

That is the shift worth designing for. A reviewer who understands the form perfectly still has to hold the vendor requirement in mind, find the matching field, decide whether a shortfall is material, and record the answer somewhere it can be found again. Do that across several hundred vendors on rolling renewal dates and reading skill stops being the constraint. We wrote separately about why vendor certificate tracking never actually ends.

The fix is to make the requirement as structured as the form already is. Terra Compliance defines what each vendor type must carry as a set of rules rather than a paragraph in a contract: lines of insurance, document types, and special requirements that map onto the exact fields above, including additional insured name, AM Best rating, certificate holder, and Description of Operations. Incoming ACORD certificates are read automatically, the fields populate, and a person proofreads before anything counts. The platform then compares the document against the assigned rules and returns a status with the specific reason for any deficiency: insufficient limit, missing coverage, expired policy, missing document. Field by field, on every certificate, every time one arrives.

What to Watch For

• Entity name mismatch. The insured must be the entity on your contract, not a parent, an affiliate, or a similarly named DBA. This is the most common quiet failure.
• An expiration date already in the past. A certificate is a snapshot of its issue date. Nothing on the form obligates the insurer to tell you when a policy cancels, unless an endorsement says otherwise.
• Limits met through an umbrella. A required five million satisfied by one million primary plus four million excess is usually fine, but only if the umbrella actually sits over the right underlying line.
• A workers compensation section that looks empty. In the states where workers compensation is written only through a state fund, that section will not look the way it does elsewhere. It is not automatically a deficiency.
• Description of Operations doing contractual work. If the only evidence of a required endorsement is a sentence typed into that box, you have an assertion, not proof.

For risk managers, the practical takeaway is that certificate review is a rules problem wearing the costume of a reading problem. If response rate is your specific bottleneck rather than review quality, we covered improving COI response rates separately.

Ready to Make Compliance a Competitive Edge?

A certificate of insurance is a summary, written by the party you are verifying, accurate as of one day. Read field by field, it tells you a great deal. Trusted as a pass or fail stamp, it tells you almost nothing.