COI term
Named insured
The company the policy actually belongs to. If it is not the exact legal entity you signed the subcontract with, the certificate covers someone else.
Key takeaways
- The named insured is whose policy it is — who pays the premium, who is defended by right, and whose work the coverage follows. It appears in the INSURED box, upper left on the certificate.
- It is a different thing from an additional insured (added by endorsement, for liability arising out of the named insured's work) and from the certificate holder (who was mailed the paper, and nothing more).
- The common real-world failure is an entity mismatch: you signed with "Peak Roofing LLC" and the certificate says "Peak Roofing", "John Peak dba Peak Roofing", or a parent company. Those are not all the same legal person.
- The first named insured carries duties the others do not — premium, notice of claims, and receipt of the cancellation notice. On a policy listing several entities, it decides who actually hears that coverage is ending.
By the Sealinn team · 4 min read · Updated July 2026 · Written for general contractors
Three boxes, three different roles
A certificate names your company and the sub's company in different places, for different reasons, and reading the wrong box is how a GC concludes they are protected when they are not.
- Named insured — the INSURED box, upper left beneath the producer. This is the policyholder. The coverage exists to protect them, follows their work, and defends them by right rather than by endorsement.
- Additional insured — not a box at all. It is a status granted by an endorsement to the policy, which the certificate can only report on with a Y/N tick in the ADDL INSD column. It gives you some of the named insured's protection, for liability arising out of their work.
- Certificate holder — the box at the bottom left, usually holding your name and address. It means you were sent the document, and the form's own disclaimer is explicit that being sent it confers nothing.
So the named insured is the only one of the three that describes the policy rather than the paperwork — and it is the one worth checking first, because if it is wrong, nothing else on the page applies to your subcontractor. The difference between holder and additional insured is the same lesson from the other direction.
The mismatch that actually happens
Almost nobody sends a certificate for a completely unrelated company. What arrives is a certificate for something close — and close is the problem, because entities are exact. You executed a subcontract with Peak Roofing LLC. The certificate's INSURED box reads "Peak Roofing". Is that the LLC, a trade name, or John Peak trading as a sole proprietor?
It matters because the entity you would pursue has to be the entity the policy covers. An LLC is a separate legal person from the individual who owns it. If the LLC signed your contract and the policy names the individual, there is a real argument — one you would be having after a loss, with a carrier's counsel, not before one — about whether the party you contracted with had coverage at all. The same applies in reverse when a sub incorporates mid-year and nobody updates the policy.
Compare it against the signed contract, character by character
Not against the invoice, not against how they answer the phone, and not against what you have them saved as in your phone. The subcontract names an entity; the certificate names an entity; those two strings should match. Where they differ, the fix is not a reissued certificate with the name typed differently — it is an endorsement amending the named-insured schedule on the policy declarations, which is what actually puts the entity on the policy. Ask the agent for that, and ask for the amended declarations page as proof.
Affiliates, trade names and joint ventures
Three variations come up often enough to be worth naming. A parent and subsidiary: a policy naming the parent does not automatically cover an operating subsidiary, and the entity that signs your subcontract is usually the operating one. A trade name or dba: this is a name, not an entity, and the underlying legal person is what the policy has to identify. A joint venture: generally its own legal entity, and generally not covered by either partner's policy unless it is specifically named — which on a large job is exactly the arrangement that gets missed.
One more distinction that pays for itself. Where a policy lists several named insureds, the first named insured carries duties the rest do not: paying the premium, reporting claims, and — the one that reaches you — receiving the cancellation notice. If the sub you contracted with is second on the list, they are not the party the carrier writes to when the policy is being canceled, which quietly weakens whatever notice of cancellation your subcontract asked for.
Pinning the requirement to the legal entity
- Record the legal entity name once, from the signed subcontract or the W-9, and use it everywhere. Most mismatches are your own records disagreeing with themselves — collecting the W-9 at onboarding gives you the legal name and the entity type in the same document.
- Require the sub to be the named insured on every policy the contract lists, not merely "covered" by one.
- Ask about affiliates up front where the sub is part of a group, and name the entity that will actually perform the work.
- Re-check at renewal. Entity changes — incorporating, adding a partner, forming a JV for one job — happen between certificates, and the renewal certificate is where they surface.
Copy-paste to the sub’s agent
Subject: Named insured on the policy vs our subcontract — [Project]
Hi [Agent name], We're the general contractor on [Project]. Our subcontract is with [exact legal entity name from the contract], and the certificate we received shows the insured as [name as printed on the certificate]. Could you confirm whether [exact legal entity name] is a named insured on the policy? If it isn't, we'd need it added by endorsement to the named-insured schedule rather than a reissued certificate — a copy of the amended declarations page would settle it. Also, if the policy lists more than one named insured, could you tell me which is the first named insured? We want to know who receives the cancellation notice. Thanks, [Your name], [Your company]
Sealinn flags a name that does not match
When a certificate is read, Sealinn compares the named insured on the document against the subcontractor's name in your list and raises a warning when the two are not a close match — one of the few checks here that compares the certificate to something outside itself. Two caveats. It is a warning, not a blocking violation: it surfaces for the reviewer, it does not hold up an approval on its own. And the comparison is deliberately loose, so a suffix difference — "Peak Roofing" saved against a certificate reading "Peak Roofing LLC" — will trip it. That is a nuisance pointing the right way: store the legal entity name and it stops. The named insured is also one of the fields that must be read confidently before a certificate clears without a person, which is a separate mechanism.
Where this comes from
- ISO — Commercial General Liability Coverage Form (CG 00 01 occurrence / CG 00 02 claims-made)
- ACORD — Certificate of Liability Insurance (form 25)
The right coverage on the wrong entity is no coverage.
Sealinn compares the name on the certificate against the subcontractor in your list, so a near-miss gets a second look instead of a filing.
