Indemnification Clauses in Vendor Contracts: What They Actually Cover

An indemnification clause in a vendor contract is a promise, not a guarantee of outcome: one party agrees to cover the other party’s losses, defense costs, and settlements arising from a defined set of claims — not “whatever goes wrong,” but specific triggering events named in the clause itself. For a medical-supply or lab-equipment buyer, this is one of the most consequential paragraphs in a vendor contract and one of the least understood. This guide explains what an indemnification clause actually does in plain language, then walks through the practical question that matters more than the clause’s wording: does the vendor’s indemnification obligation actually reach as far as their insurance coverage, or could your institution be left holding the gap between what the vendor promised and what they can actually pay.

This is educational background, not legal advice. Indemnification language is negotiated clause-by-clause and interacts with state law, the rest of the contract, and the specific claim in question. Have institutional counsel review any actual contract before you sign it — the goal here is to help you ask better questions going into that review, not to replace it.

What an Indemnification Clause Actually Does

Strip away the legal phrasing and an indemnification clause does three things:

• Names who is protecting whom. A vendor-favorable clause has the buyer indemnify the vendor; a buyer-favorable clause has the vendor indemnify the buyer; a mutual clause has each side indemnify the other for claims arising from their own acts. Read the direction carefully — contracts are sometimes drafted (or later edited) so the indemnification runs the wrong way for the party relying on it.
• Defines the triggering claims. The clause lists specific categories — typically some combination of: claims arising from the vendor’s negligence, claims that the vendor’s product infringes a third party’s patent or other intellectual property, claims arising from a defect in the product itself, and claims arising from the vendor’s breach of the contract’s own representations (for example, a warranty that the product meets a stated regulatory specification). A clause covering only “breach of contract” claims is much narrower than one that also names product-defect and third-party IP claims — the list of triggers, not the word “indemnification” itself, is what determines what the clause is actually worth.
• Describes what gets covered once triggered — typically damages awarded or paid in settlement, plus the cost of defending the claim (attorneys’ fees), and sometimes court costs. Some clauses cap the total dollar amount the indemnifying party owes; others are uncapped for certain categories (IP infringement and gross negligence are common carve-outs from an otherwise-capped clause).

A Concrete Example

Say a hospital buys an infusion pump and a component fails, injuring a patient, and the patient sues both the hospital and the manufacturer. A standard vendor-favorable indemnification clause in the purchase contract would obligate the manufacturer to cover the hospital’s defense costs and any damages the hospital is found liable for, to the extent the injury was caused by a defect in the product rather than by how the hospital’s staff used it. That qualifying phrase matters enormously in practice: if the manufacturer can show the injury resulted from improper use, storage, or maintenance on the hospital’s end rather than a product defect, the indemnification obligation may not apply at all, and the hospital is defending the claim largely on its own.

The Real Question: Does the Promise Reach as Far as the Insurance?

An indemnification clause is only as good as the indemnifying party’s ability to actually pay when a claim lands. A vendor can sign a broad, buyer-favorable indemnification clause and still be functionally unable to honor it — through insolvency, or because the claim exceeds what their insurance will pay and they don’t have the balance sheet to cover the rest themselves. This is the gap a buyer needs to check for, and it has three common forms:

• The insurance policy excludes what the clause covers. The contract’s indemnification language and the vendor’s actual insurance policy are two separate documents, negotiated at different times by different people, and they don’t automatically match. A vendor’s commercial general liability (CGL) policy typically responds to bodily-injury and property-damage claims through its products-and-completed-operations coverage — but that line can carry its own sublimit, separate from (and lower than) the policy’s overall general-liability limit, and some CGL policies exclude specific product categories or contractual-liability assumptions entirely unless a contractual-liability endorsement is added. A clause that obligates the vendor to indemnify for a category of claim their policy doesn’t actually respond to is a promise backed by nothing but the vendor’s own assets.
• The policy limit is lower than realistic exposure. A vendor might carry $1 million in CGL coverage per occurrence while the contract’s indemnification obligation is effectively uncapped, or capped at a figure well above what the policy would pay out. If a claim exceeds the policy limit, the indemnification obligation doesn’t disappear — but the vendor’s ability to actually fund the excess does, and a claim large enough to exceed a modest CGL limit is exactly the scenario a buyer is trying to protect against by asking for indemnification in the first place.
• The policy could lapse or the certificate goes stale. Indemnification is a contractual promise; insurance is what actually funds it. A certificate of insurance is only proof of coverage as of its issue date, not a guarantee the policy stays active for the life of the contract — see Requesting a Certificate of Insurance from a Vendor: What to Check for the specific red flags (expired dates, coverage-line gaps, certificate-holder vs. additional-insured status) that determine whether a certificate actually backs up what the contract’s indemnification clause promises.

The practical fix is not to reject every indemnification clause that doesn’t perfectly match the policy — that match is rarely perfect. It’s to ask for the vendor’s certificate of insurance alongside the contract, confirm the coverage lines and limits are at least in the range of what the indemnification obligation could realistically require, and confirm your institution is named as an additional insured (not just a certificate holder) if the contract’s risk profile calls for it. An additional-insured endorsement gives your institution a direct right to make a claim against the vendor’s policy, which matters if the vendor becomes unable or unwilling to honor the indemnification clause directly.

Mutual vs. One-Sided Indemnification

Vendor-drafted contracts often start one-sided — the buyer indemnifies the vendor for claims arising from how the buyer uses the product, but the vendor doesn’t reciprocate for claims arising from a defect in what they sold. That asymmetry is negotiable more often than buyers assume, especially for a purchase of meaningful dollar value: it’s reasonable to ask that a vendor’s product-defect and IP-infringement exposure be indemnified by the vendor, mirroring the buyer’s own obligation for misuse claims. A genuinely mutual clause, where each party bears responsibility for claims caused by its own conduct, is generally the more balanced starting point for a negotiation, even if the final language ends up somewhere in between.

Where Indemnification Intersects Other Contract Terms

Indemnification rarely stands alone in a vendor contract — a few related terms affect how much it actually matters in practice:

• If you’re buying under a master service agreement that covers many individual purchase orders, confirm whether the indemnification language lives in the MSA (and therefore applies to every order under it) or gets restated per order, where it can drift or get dropped — see Master Service Agreement (MSA) vs. Individual Purchase Terms.
• A warranty promises the product will meet a stated specification and typically obligates the vendor to repair or replace it; indemnification is a different mechanism entirely — it addresses who pays when a third party (not the buyer) is harmed and sues. A contract can have a strong warranty and a weak indemnification clause, or vice versa; check both separately rather than assuming one implies the other. See Warranty vs. Service Agreement for Medical Equipment for how warranty coverage is scoped.
• If the contract auto-renews, confirm the indemnification language (and the insurance requirements backing it) carries forward on renewal rather than lapsing to whatever the vendor’s current standard terms happen to be — see Sunset Clause vs. Auto-Renewal in Vendor Contracts.
• Total cost of ownership calculations rarely price in indemnification risk directly, but a vendor whose indemnification obligation doesn’t hold up in practice is effectively shifting uninsured liability risk onto the buyer — a cost that belongs in the same risk conversation as the figures in Total Cost of Ownership (TCO) in Medical Equipment Purchasing, even though it rarely shows up as a line item.

Note that indemnification works differently outside a supply or service contract — a university licensing its own intellectual property to a commercial partner faces a distinct set of considerations, covered separately in Indemnification Clauses in University Patent License Agreements. That guide addresses why universities typically refuse to indemnify licensees for a technology’s use; it is not the same fact pattern as a hospital or lab buying equipment from a vendor, which is what this guide covers.

Questions to Bring Into Contract Review

• Which party indemnifies which, and for which specific categories of claim — not just the presence of the word “indemnification,” but the actual list of triggers?
• Is the indemnification obligation capped, and if so, at what figure relative to the contract’s value and the vendor’s certificate of insurance limits?
• Does the vendor’s certificate of insurance name your institution as an additional insured, or only as a certificate holder?
• Do the coverage lines on the certificate (general liability, products-and-completed-operations, professional liability if applicable) actually correspond to the claim categories the indemnification clause names?
• Does the indemnification and insurance-verification obligation survive contract renewal, and does it require the vendor to notify you if coverage changes or lapses?

None of these questions require a law degree to ask a vendor — they require reading the certificate of insurance and the indemnification clause side by side. Whether the answers are acceptable for a specific purchase, and how to negotiate the gaps, is exactly the judgment call institutional counsel is positioned to make on the actual contract in front of them.

Frequently Asked Questions

What is an indemnification clause, in simple terms?

It’s a contract clause where one party agrees to cover the other party’s losses, legal defense costs, and settlements arising from a specific, named list of claims — not every possible loss, only the categories the clause actually describes.

Is indemnification the same thing as insurance?

No. Indemnification is a contractual promise between the buyer and the vendor. Insurance is a separate policy the vendor (or buyer) carries with a third-party insurer that may or may not actually fund that promise when a claim arises. A vendor can owe indemnification under the contract and still lack the insurance or assets to pay it.

What’s the difference between mutual and one-sided indemnification?

One-sided indemnification has only one party (often the buyer, in a vendor-drafted contract) covering the other’s claims. Mutual indemnification has each party covering claims that arise from its own conduct — generally the more balanced structure, though the specific split is negotiable.

Does a certificate of insurance guarantee the vendor can meet its indemnification obligation?

No. A certificate is evidence that a policy existed as of its issue date, with stated coverage lines and limits — it doesn’t guarantee the policy stays active, that its limits are adequate for a large claim, or that its coverage lines actually match what the contract’s indemnification clause promises. Checking the certificate against the clause is a step, not a substitute for the underlying review.

Who should review an indemnification clause before we sign?

Institutional legal counsel, on the actual contract language, not a general guide like this one. This page is meant to help you understand what you’re looking at and ask sharper questions during that review — it is not a substitute for it.