Certificate Holder vs Additional Insured
These two boxes sit inches apart on the same form and mean entirely different things. One says you were sent a copy. The other says you may be covered. Confusing them is the most common and most expensive misreading of a certificate of insurance.
The short version
Certificate holder is an address. It identifies who the certificate was issued to — the party who asked for proof. Being named there gives you no rights under the policy whatsoever. It is a mailing label with legal-looking formatting.
Additional insured is a coverage position. It means the policy has been extended to protect you, usually for liability arising out of the named insured's work for you. That extension is made by an endorsement to the policy, not by the certificate.
If your contract requires additional insured status and the certificate names you only as certificate holder, the requirement is not met — no matter how official the document looks.
Why the distinction exists at all
A certificate of insurance is a summary document. ACORD 25, the standard form, says so on its own face: it is issued as a matter of information only, confers no rights on the holder, and does not amend or alter the coverage afforded by the policies it describes.
That sentence is doing real work. The certificate is a report about a policy. The policy and its endorsements are the thing that actually pays. A certificate can describe an additional insured endorsement correctly, describe one that was canceled last week, or describe one that was never issued — and it looks identical in all three cases.
What "additional insured" actually buys you
When a subcontractor names you as an additional insured, their insurer may defend and indemnify you for claims arising out of that subcontractor's operations. In practice this matters most when someone is injured on a site and sues everyone in the contractual chain: without additional insured status you are defending on your own policy, with your own deductible and your own loss history.
The scope is narrower than people assume. It is usually limited to liability arising out of the named insured's work for you — not your own independent negligence, and often not work already completed unless completed operations are specifically included.
The three things to check, in order
1. Is additional insured status shown at all? On an ACORD 25 this is a checkbox column and, usually, a line in the Description of Operations. A blank column with no supporting description is a failed requirement, not an ambiguous one.
2. Does it name the right party? "Additional insured as required by written contract" is common and is weaker than naming you. Whether that satisfies your contract is a question for whoever wrote the contract — but it is a different answer from your legal entity being named, and the two should not be recorded the same way.
3. Is completed operations included? If your exposure continues after the subcontractor leaves the site — and on construction it almost always does — ongoing operations coverage alone leaves the tail uncovered.
The certificate is not the endorsement
This is the part that gets skipped, and it is the whole point of the distinction. The certificate says an endorsement exists. The endorsement is what extends the coverage. If the two disagree, the endorsement wins, because it is the operative document and the certificate is a description of it.
For a material relationship — a large subcontract, a long-running vendor, anything where a claim would be significant — ask for the endorsement itself, or written confirmation from the agent naming the form number, the additional insured, the operations covered, and whether completed operations are included. A certificate alone is reasonable evidence for a routine vendor and thin evidence for a material one.
The failure mode automation usually hides
A scanned or faxed certificate frequently has a checkbox that cannot be read, or a Description of Operations block that is illegible. There are then two different true statements available: the certificate does not show additional insured status, and we could not read whether it does.
Most extraction tools collapse those into one answer, because a null and an unreadable field look the same once a value has failed to come out. That collapse is the expensive one: "not shown" sends you back to the vendor, while "could not be read" should send you back to the document. Recorded as "not shown" it also silently becomes a finding about the subcontractor's insurance, which is a claim nobody actually verified.
Read more on that specific failure: When a Certificate Can't Be Read.
Checking this automatically
Additional insured status is a rule with a threshold, which means it can be checked mechanically once your requirement is written down. The COI / ACORD 25 Verification API takes a certificate and your requirements and returns an itemized verdict — including which rules it actually evaluated, so a clean result can be told apart from a check that never ran, and any value it could not read is reported as unreadable rather than filled in.
Or try it on a real certificate right now, free and without signing up: the COI checker runs the same code this API does, including the part that tells you which fields it could not read.
And if you would rather test this than take our word for it: the COI Extraction Honesty Test is an open, synthetic test set for exactly this failure — four documents, documented ground truth, free to run against any tool.
Related reading: What Makes a Certificate of Insurance Deficient and Automating ACORD 25 Verification for Vendor Onboarding.
This is not legal or insurance advice
Whether a particular certificate satisfies a particular contract is a question about that contract and that policy. This page explains what the form shows and what it does not. Aervik Labs is operated by EAC Ventures, LLC and does not give legal, insurance, or risk advice — consult your broker or counsel for your actual obligations.