How to Handle a Request to Add ‘Indemnified Parties’ to a COI – IA Magazine

You’re minding your own business, sipping coffee, when an email lands in your inbox like a toddler with a drum set: “Please add all Indemnified Parties to the COI.” If you felt your soul leave your body for a second, you’re not alone.

Here’s the good news: this request is common. Here’s the better news: you can handle it cleanly, professionally, and without turning a one-page certificate into a contract, a lawsuit, or an E&O claim waiting to hatch. This IA Magazine guide breaks down what the requester really wants, what a certificate of insurance (COI) can and can’t do, and the practical steps to respond like a pro.

Why People Ask for “Indemnified Parties” on a COI (and What They Usually Mean)

Most people requesting “indemnified parties” on a COI aren’t trying to be difficult. They’re trying to reduce risk and check a box in a contract compliance process. The phrase often shows up in vendor agreements, construction contracts, leases, and event permits, where one party agrees to indemnify (and sometimes defend) another.

The twist? Many requesters assume the COI is a magic wand that makes contract protections “official.” It’s not. A COI is closer to a snapshot: helpful, but not legally transformative. When someone says “add indemnified parties,” they often mean one (or more) of these:

• “Make us an additional insured.” (They want rights under your insured’s policy via endorsement.)
• “Prove we’re protected.” (They want documentation that the contract risk transfer is backed by insurance.)
• “Our portal demands it.” (A COI-tracking system has a field for “indemnified parties,” so someone must feed it.)

Quick Refresher: COI vs. Additional Insured vs. Indemnified Party

1) The COI: Proof-of-Insurance, Not a Coverage-Builder

The standard COI (often an ACORD 25) summarizes coverage: who’s insured, which policies exist, limits, and effective dates. It’s designed to communicate information quicklynot to grant coverage, rewrite policy terms, or create new legal obligations.

That’s why the form contains prominent disclaimers. In plain English: the certificate doesn’t change the policy, and it doesn’t automatically give the certificate holder rights. Think of it like a movie trailer: it tells you what’s coming, but it’s not the contract for the streaming service.

2) “Certificate Holder” Is Not “Covered”

A certificate holder is the party receiving the COI. They’re usually entitled to receive the document, and sometimes they may receive certain notices if the policy or process provides them (but don’t assume that means special rights). Crucially, being listed as a certificate holder does not automatically make them insured under the policy.

3) Additional Insured: Coverage Requires Endorsement

An additional insured is a party added to someone else’s policy by endorsement (or by policy provisions that function like one). Additional insured status can provide defense and indemnity for certain claimsbut usually only for liability arising out of the named insured’s work, operations, or premises, depending on the endorsement wording.

4) Indemnified Party: A Contract Creature

An indemnified party is protected by contract, not by being typed into a certificate. Indemnity is one party’s promise to pay (and sometimes defend) another under specified circumstances. It’s not insurance by itself, and it doesn’t automatically translate into additional insured status.

Bottom line: indemnity lives in the contract; additional insured status lives in the policy; and the COI is just the messenger running between the two.

The Core Problem with Listing “Indemnified Parties” on a COI

When a requester asks you to “add indemnified parties,” they’re asking the COI to do a job it wasn’t hired to do. Here’s what can go wrong if you try to comply by improvising on the certificate:

• It can misrepresent coverage. Listing names doesn’t create coverage, and it may imply coverage exists when it doesn’t.
• It can create E&O exposure. If a third party relies on a certificate statement that’s not backed by the policy/endorsement, the agent/broker can end up in the blast radius.
• It often conflicts with endorsement requirements. Many additional insured endorsements apply only when the named insured has a direct written contract with the party being added. If the contract lists a galaxy of “indemnified parties” (affiliates, lenders, architects, “anyone we’ve ever met”), that doesn’t mean the policy covers all of them automatically.

IA Magazine has highlighted this exact snag: the insured may not have a direct contract with every “indemnified party,” so broad lists don’t neatly translate into additional insured status. Some endorsements are better at handling broader “required by written contract” scenarios, but the endorsement language mattersevery time.

Step-by-Step: How to Respond (Without Starting a Fire)

Step 1: Ask the Most Powerful One-Word Question: “Why?”

Before you touch the COI, figure out what the requester is truly trying to accomplish. Ask:

• Are you requesting additional insured status, or just proof of coverage?
• Which policy lines are involved (GL, auto, umbrella, WC, professional, etc.)?
• Is this tied to a specific contract or a standard vendor requirement?
• Who are the “indemnified parties” exactlyand what’s their relationship to the insured?

Translation: you’re not being difficult; you’re doing triage. “Indemnified parties” is a contract phrase, not a certificate field, so you need to map the request to something insurance can actually deliver.

Step 2: Review the Contract Language (At Least the Insurance and Indemnity Sections)

You don’t need to play attorney, but you do need the relevant sections to confirm what is being required:

• Indemnity / hold harmless clause: Who must indemnify whom, for what, and how broadly?
• Insurance requirements: Which coverages, limits, endorsements, and wording are demanded?
• Who must be protected: Named parties, affiliates, “their officers/directors/employees,” etc.

This is where you’ll often find the mismatch: the contract demands a parade of protected parties, while the policy’s additional insured endorsement may only respond for parties with a direct contract (or only for certain operations).

Step 3: Translate “Indemnified Parties” into Insurance Tools That Actually Exist

Most “add indemnified parties” requests can be resolved by focusing on the right insurance mechanisms:

• Additional insured endorsement (GL and sometimes auto): adds the party to the policy for certain liability arising out of the insured’s work.
• Waiver of subrogation (where applicable): prevents the insurer from seeking recovery against the waived party, when properly endorsed.
• Primary & noncontributory wording (when available): clarifies the order of coverage between policies.
• Contractual liability coverage (GL “insured contract” concepts): may apply to certain indemnity obligations, depending on the policy and factsnever assume.
• Certificate holder listing: provides proof of coverage and identifies who requested the COI.

A key nuance: contractual indemnification and additional insured obligations are distinct and created by different contract provisions, even if they show up side-by-side. Treat them as two separate lanes with a shared exit ramp called “risk transfer.”

Step 4: Confirm What the Policy/Carrier Will Approve (Before Issuing Anything)

If the request is actually for additional insured status, the only safe order of operations is:

1. Request the endorsement (or confirm blanket AI wording applies).
2. Get carrier confirmation/issuance.
3. Then issue the COI reflecting what’s been endorsed.

Don’t “pre-announce” additional insured status on a COI and hope underwriting catches up later. That’s like sending wedding invitations before proposing. Romantic? No. Risky? Absolutely.

Step 5: Use the COI Description Box Carefully (And Honestly)

The description box is not a wish-granting genie. If you need to reference additional insured status, do it in a way that tracks realitye.g., “Certificate holder is included as additional insured as per endorsement on file,” only if that endorsement exists.

If the requester wants “indemnified parties” listed because the contract says so, your response should be gentle but firm: the COI doesn’t create indemnity, and the contractnot the certificatecontrols indemnification obligations.

Step 6: Offer a Clean, Professional Alternative

Instead of fighting their wording, give them an easy “yes” that’s actually correct:

• “We can list you as the certificate holder.”
• “If you need additional insured status, please provide the contract section; we’ll request the proper endorsement.”
• “The COI can reference the endorsement once issued; it cannot list ‘indemnified parties’ as a coverage grant.”

Practical Examples (Because Real Life Doesn’t Read Like a Policy Form)

Example 1: The Landlord Lease Request

Request: “Add Landlord and all Indemnified Parties to the COI.”

Best response: “We can provide a COI listing the landlord as certificate holder. If the lease requires the landlord to be additional insured, we can request the appropriate additional insured endorsement and reflect it on the certificate once issued.”

Example 2: The Big-Box Vendor Agreement

Request: “Add Big Box Store, its parent, subsidiaries, affiliates, officers, directors, employees, and ‘anyone who looks like they might sue’ as indemnified parties.”

Reality check: The contract may define those as indemnified parties, but the policy may only extend additional insured status to the contracting entity (and only for certain operations). If they want broader insured status, you’ll need the carrier to confirm what endorsement language can do thatand whether it’s available.

Example 3: Construction Project Layer Cake

Request: “Add the owner, GC, architect, lender, and the owner’s cousin’s LLC to the COI as indemnified parties.”

Common issue: The subcontractor may have a direct contract with the GC, but not with the owner, architect, or lender. Many AI endorsements hinge on that direct contract requirement. This is where you slow down, confirm the chain of contracts, and match endorsement wording to the actual relationships.

Red Flags That Should Make You Hit the Brakes

• “Modify the ACORD wording.” (Nope. Use approved forms and carrier guidance.)
• “Guarantee 30 days’ notice of cancellation.” (Policies and statutes control notice; COI promises can be dangerous.)
• “List additional insured even though endorsement is pending.” (That’s a classic E&O trap.)
• “Include every affiliate known to mankind.” (Overbroad lists often exceed what endorsements will grant.)
• “This is just a formality.” (Famous last words in risk management.)

A Simple “Risk Transfer” Checklist You Can Reuse

To keep requests from becoming an email marathon, use a repeatable checklist:

1. Identify the purpose: proof of insurance vs additional insured vs contract compliance.
2. Collect contract excerpts: insurance requirements + indemnity clause.
3. Confirm policy eligibility: does coverage/endorsement exist or need to be added?
4. Request endorsements first: additional insured, waiver of subrogation, primary/noncontributory, etc.
5. Issue COI second: reflect only what is actually in place.
6. Document everything: who asked, what you provided, and what you refused (politely) to promise.

Field Notes: of Real-World Experience (What Actually Works)

If you handle enough COI requests, you start to recognize patterns the way baristas recognize “I need caffeine” eyes. The “add indemnified parties” request usually comes from one of three places: (1) a contract template that’s been copied since 2009, (2) a COI tracking portal that needs a checkbox fed, or (3) a well-meaning procurement person trying to make “risk transfer” happen by sheer force of will.

In practice, the best results come from a two-lane explanation that doesn’t insult anyone’s intelligence: “Indemnity is handled in the contract lane; insurance is handled in the policy lane; the COI is just proof we’re in the right neighborhood.” When you frame it that way, you’re not saying “no.” You’re saying “yes, and here’s the correct yes.”

One common win: replacing the ask to “list indemnified parties” with a request to list the contracting entity as certificate holder and confirm additional insured status by endorsement. Many requesters accept that immediately because it gives them something verifiable: a named organization on the certificate and the promise of an endorsement they can request if needed. If they push back, the next step is usually to ask for the exact contract section that triggers the requirementsuddenly the conversation becomes about specifics instead of vibes.

Another recurring scenario is the “indemnified parties include everyone’s employees” language. That’s often fine in a contract, but it can be clunky in insurance reality. Additional insured endorsements frequently protect the organization, and the organization’s “who counts as an insured” may be handled by policy definitions rather than naming every human being with a badge. When someone insists on listing “officers, directors, employees,” a practical approach is to confirm whether the endorsement already treats those people as insureds in their capacity for the organization. If it does, you can explain that naming every category on the COI doesn’t expand coverageit just expands your typing.

The trickiest cases show up in construction, where a subcontractor’s contract might be with the GC, but the prime contract requires the owner and architect to be additional insureds. People will ask you to “just add them,” but the policy endorsement might require a direct contract with each party. This is where being calm and procedural saves the day: map the contractual chain, confirm what the endorsement allows, and if the contract needs broader insured status, raise it early so the insured can renegotiate requirements or purchase the proper endorsement (if available). The worst outcome is pretending the COI solved it, only to discover during a claim that the “indemnified party” list was aspirational fiction.

Finally, document your process like you’re writing a recipe someone else will follow: what was requested, what you delivered, and why. When you’re consistent, your clients learn the rhythm: contract first, endorsement second, COI last. The requests don’t disappear, but they get faster, cleaner, and far less dramaticwhich is the true definition of professional success in COI-land.

Conclusion

When someone asks to add “indemnified parties” to a COI, your job is to translate a contract concept into insurance reality. A COI can show evidence of coverage and reflect endorsementsbut it can’t manufacture rights, rewrite policy terms, or turn a broad indemnity definition into automatic additional insured status. The safest, smartest response is a structured one: clarify intent, review the relevant contract language, secure the proper endorsements, and issue the COI only after coverage is confirmed. You’ll protect your client, satisfy reasonable compliance needs, and keep your agency out of the “we thought the certificate did that” hall of fame.