What Is an Indemnification Clause? Definition, Types and Examples

An indemnification clause is a contractual provision in which one party agrees to compensate the other for specific losses, damages, or legal fees arising from defined events, such as breach of contract, negligence, or third-party claims.

For legal teams managing hundreds or thousands of commercial agreements, indemnification clauses represent both critical protection and significant exposure. A single poorly drafted clause can shift millions in liability. Yet when written strategically, these provisions create clarity, allocate risk fairly, and prevent costly disputes before they arise.

This guide explains how indemnification clauses work, what makes them enforceable, and how legal teams can draft, negotiate, and manage them at enterprise scale.

An indemnification clause transfers financial responsibility for specific losses from one contracting party to another. Instead of leaving risk allocation ambiguous, these provisions explicitly define who pays when something goes wrong.

The clause establishes three core elements:

Consider a software vendor providing a SaaS platform to a corporate client. If the vendor’s code infringes a third party’s intellectual property, the client could face a lawsuit despite having done nothing wrong. An indemnification clause requiring the vendor to cover the client’s legal fees and damages solves this problem before it escalates.

Indemnification shifts risk to the party best positioned to control it. The software vendor can review its codebase, conduct IP clearance, and carry appropriate insurance. The client cannot. That asymmetry makes indemnification both logical and commercially fair.

Most indemnification clauses create two distinct legal obligations. Understanding the difference is essential for both drafting and enforcement.

This is the core financial commitment. The indemnifying party must reimburse the indemnified party for covered losses that have already been paid, and provide advance payment for unpaid liabilities such as pending claims or lawsuits.

Recoverable damages typically include:

• Judgments and settlements
• Legal fees and court costs
• Direct damages arising from the covered event
• Third-party claims and causes of action

The indemnified party must typically provide notice of the claim and cooperate in the defense. But once those conditions are met, the indemnifying party bears the financial burden.

The defense obligation is broader and more immediate. It kicks in the moment a claim is filed, regardless of whether that claim has merit.

This means the indemnifying party must:

• Pay for legal defense costs as they accrue
• Retain and direct defense counsel
• Assume control of the litigation strategy

The obligation to defend protects the indemnified party from burning cash on legal fees while waiting for a case to resolve. It also gives the indemnifying party control over settlement decisions, which can reduce total exposure.

Critically, the duty to defend is triggered by the allegations in the complaint, not the ultimate outcome. Even a baseless lawsuit activates the defense obligation if it falls within the scope of covered events.

You’ll often see contracts use all three terms together: “Party A shall indemnify, defend, and hold harmless Party B.” While this phrasing is common, the terms have distinct legal meanings, and in some states, those distinctions matter.

Indemnify creates the obligation to reimburse or compensate for losses after they occur.

Defend requires the indemnifying party to cover legal defense costs and control the defense, starting immediately when a claim is filed.

Hold harmless traditionally means the indemnifying party must advance payment for unpaid liabilities before the indemnified party incurs out-of-pocket costs. In some jurisdictions, it also releases the indemnified party from any related counterclaims by the indemnifying party.

In most U.S. states — including Colorado, Delaware, and Ohio — courts treat “indemnify” and “hold harmless” as synonyms. But California distinguishes between them, interpreting “hold harmless” as a separate right requiring advance payment even when the defined damages are limited to losses already paid.

For legal teams drafting contracts, the safest approach is to include all three terms if you want full protection. If you’re the indemnifying party, push to remove “hold harmless” or define it narrowly to avoid triggering advance payment obligations.

Not all indemnification clauses allocate risk the same way. The structure you choose determines who pays, when, and how much.

Type	Who It Protects	Risk Allocation	Common Use Cases	Enforceability
One-Sided (Unilateral)	Only one party (indemnified party)	Indemnifying party bears all risk for covered events	Vendor-customer agreements, product liability, service agreements	Generally enforceable if scope is reasonable and specific
Mutual	Both parties (each indemnifies the other)	Risk shared based on each party’s conduct	Commercial contracts between equal parties, professional services agreements	Highly enforceable; seen as balanced and fair
Broad Form	Indemnified party (even for their own negligence)	Indemnifying party liable even when indemnified party is at fault	Previously common in construction; now mostly banned	Often unenforceable due to anti-indemnity statutes and public policy
Intermediate Form	Both parties (proportional to fault)	Liability split based on comparative negligence	Construction contracts in states that ban broad form	Enforceable in most jurisdictions
Limited Form	Indemnified party (only for other party’s fault)	Indemnifying party only liable for losses they caused	Standard in negotiated commercial contracts	Highly enforceable; default in most states

In a one-sided clause, only one party agrees to indemnify the other. These are common when there’s an asymmetry in risk or negotiating power.

Example: A manufacturer indemnifies a distributor for product liability claims. The manufacturer controls product design and quality, so it makes sense for them to bear the risk of defects.

One-sided clauses favor the indemnified party but can face enforceability challenges if the language is too broad or if the indemnifying party had no role in causing the harm.

Both parties agree to indemnify each other for different types of harm. Mutual clauses are standard in commercial contracts between parties of roughly equal bargaining power.

Example: In a services agreement, the vendor indemnifies the client for IP infringement, while the client indemnifies the vendor for claims arising from misuse of the vendor’s services.

Mutual indemnification creates balanced risk allocation, but it also requires careful drafting to ensure each party’s covered events are appropriately scoped.

These terms describe how broadly the indemnifying party’s obligation extends, particularly when the indemnified party’s own negligence contributes to the harm.

Broad form indemnification requires the indemnifying party to cover losses even if caused entirely by the indemnified party’s negligence. Many states have banned broad form clauses as against public policy, particularly in construction contracts.

Intermediate form (also called “comparative” indemnification) allocates liability in proportion to each party’s fault. If both parties are negligent, each bears a share of the damages.

Limited form (also called “limited liability” indemnification) only requires indemnification for losses caused by the indemnifying party’s own negligence or wrongdoing. This is the narrowest — and most commonly enforceable — structure.

Most in-house legal teams default to limited form indemnification unless there’s a compelling business reason to push for broader coverage.

An enforceable indemnification clause must clearly define five elements:

Covered events: What specific actions or omissions trigger the obligation? Common examples include breach of contract, negligence, bodily injury, IP infringement, or regulatory non-compliance.

Recoverable damages: What types of losses are covered? The clause should specify whether it includes judgments, settlements, legal fees, direct damages, consequential damages, or all of the above.

Nexus language: How closely must the loss relate to the covered event? Phrases like “arising from,” “caused by,” “related to,” and “resulting from” create different scopes of liability. “Related to” is the broadest; “caused by” is the narrowest.

Liability caps: Is there a maximum dollar amount the indemnifying party must pay? Many contracts cap indemnification at the total contract value or a multiple thereof.

Time limits: How long does the indemnification obligation survive? Common durations range from three to five years after contract termination, though some survive indefinitely.

Additional provisions often include notice requirements, the right to control the defense, obligations to cooperate, and carve-outs for specific exclusions.

One-Sided Example:

“Vendor agrees to indemnify, defend, and hold harmless Client, its officers, directors, employees, and agents from and against any and all claims, liabilities, damages, losses, costs, and expenses (including reasonable attorneys’ fees) arising out of or resulting from (i) Vendor’s breach of this Agreement, (ii) Vendor’s negligence or willful misconduct, or (iii) any claim that the Services infringe or misappropriate any third-party intellectual property rights.”

Mutual Example:

“Each party (the “Indemnifying Party”) agrees to indemnify, defend, and hold harmless the other party (the “Indemnified Party”) and its affiliates, officers, directors, employees, and agents from and against any third-party claims, damages, losses, and expenses (including reasonable attorneys’ fees) arising from or caused by the Indemnifying Party’s breach of this Agreement, negligence, or willful misconduct, except to the extent such claims are caused by the Indemnified Party’s own negligence or breach.”

These are templates, not final language. Every indemnification clause should be customized based on the transaction’s risk profile, industry norms, and the parties’ relative bargaining power.

Even a well-drafted indemnification clause has boundaries. Courts and statutes impose limits to prevent overreach and ensure fairness.

Negligence and gross negligence: Many contracts exclude indemnification if the indemnified party’s own negligence caused or contributed to the loss. A typical carve-out reads: “The indemnifying party shall not be liable for any claim arising from the indemnified party’s negligence, gross negligence, or willful misconduct.”

Uncapped liability: Indemnification clauses often sit outside the contract’s general limitation of liability. But some jurisdictions require caps on indemnification to make the clause enforceable, particularly in adhesion contracts or contracts between parties with unequal bargaining power.

Public policy limits: Courts may refuse to enforce indemnification for certain harms — such as punitive damages, criminal penalties, or violations of public policy — even if the contract explicitly covers them.

Broad form unenforceability: Many states, including California, New York, and Texas, have enacted anti-indemnity statutes that void clauses requiring one party to indemnify another for the indemnified party’s own negligence. These statutes are especially common in construction, transportation, and high-risk industries.

Legal teams should research the governing law before finalizing indemnification language. What’s enforceable in Delaware may be void in Illinois.

Generally, yes – but enforceability depends on how the clause is written and the law governing the contract.

Courts enforce indemnification clauses when they are:

• Clear and specific: Vague or ambiguous clauses are construed against the indemnifying party.
• Reasonable in scope: Clauses that attempt to indemnify for all possible harms, including the indemnified party’s own fraud or criminal conduct, may be struck down.
• Consistent with public policy: Clauses that violate anti-indemnity statutes or attempt to shield a party from liability for gross negligence or intentional misconduct are often unenforceable.

State variations matter. California’s anti-indemnity statute voids clauses that require indemnification for the indemnified party’s active negligence. New York limits indemnification in construction contracts. Delaware generally enforces indemnification clauses as written, provided they are clear.

Adhesion contracts — those offered on a take-it-or-leave-it basis with no room for negotiation — face heightened scrutiny. Courts may refuse to enforce one-sided indemnification clauses in consumer contracts or contracts between parties with vastly unequal bargaining power.

For in-house legal teams, the takeaway is simple: draft clearly, avoid overreach, and know the law of the jurisdiction governing your contract.

Drafting an indemnification clause is both legal analysis and strategic negotiation. The goal is to allocate risk fairly while maintaining enforceability.

Nexus phrases connect the covered event to the recoverable damages. The phrase you choose determines how broad the indemnification obligation becomes.

“Related to” is the broadest. It can sweep in losses only tangentially connected to the covered event. The indemnified party prefers this language; the indemnifying party should resist it.

“Arising from” is moderately broad. It requires a clear connection between the event and the loss, but doesn’t require direct causation.

“Caused by” or “resulting from” are the narrowest. The indemnified party must show the covered event was a direct cause of the loss.

Most negotiated contracts land on “arising out of” or “arising from” as a middle-ground compromise.

Uncapped indemnification can expose the indemnifying party to unlimited liability. Smart contracts include caps tied to objective metrics — such as the total contract value, annual fees, or a fixed dollar amount.

Example cap: “Vendor’s total liability for indemnification under this Section shall not exceed the greater of (i) the total fees paid by Client in the twelve months preceding the claim, or (ii) $500,000.”

Time limits (also called survival periods) define how long the indemnification obligation lasts after the contract ends. Three to five years is standard for general commercial indemnification. IP indemnification and tax indemnification in M&A transactions often survive indefinitely.

If you’re reviewing a contract as the indemnifying party, push back on:

• “Any and all claims” — this is unlimited scope; narrow it to specific covered events
• No liability cap — always negotiate a cap unless you have exceptional insurance coverage
• Indemnification for the other party’s negligence — this may be unenforceable and is almost always unfair
• No exclusions for consequential or punitive damages — these should generally be excluded unless there’s a strong business reason

If you’re the indemnified party, focus on:

• Ensuring the covered events include the risks you actually face (e.g., IP infringement, data breaches, regulatory violations)
• Securing advance payment rights through “hold harmless” language
• Including attorney’s fees in recoverable damages

Preserving your right to control the defense if the indemnifying party refuses to defend.

Indemnification clauses vary significantly across industries. What’s standard in construction may be irrelevant in software licensing.

Tech contracts typically include two types of indemnification:

IP indemnification: The vendor indemnifies the customer for third-party claims that the software infringes patents, copyrights, or trademarks. This is non-negotiable in most enterprise SaaS agreements.

Data breach indemnification: The vendor may indemnify the customer for losses arising from the vendor’s security failures, though this is heavily negotiated and often capped.

Legal teams at software companies should carefully limit IP indemnification to infringement caused by the vendor’s core product — not customizations, third-party integrations, or the customer’s misuse.

M&A indemnification provisions are among the most heavily negotiated clauses in a purchase agreement. They allocate risk between buyer and seller for pre-closing liabilities.

Common M&A indemnification structures include:

• General indemnification: The seller indemnifies the buyer for breaches of representations and warranties.
• Specific indemnification: The seller indemnifies for known liabilities such as pending litigation or tax disputes.
• Baskets and deductibles: The buyer can only claim indemnification once losses exceed a threshold amount (the basket).
• Caps: Seller liability is typically capped at a percentage of the purchase price, except for fundamental representations (title, authority, capitalization) which may be uncapped.

Survival periods in M&A transactions range from 12 months (for general reps) to indefinite (for tax and IP indemnification).

A single indemnification clause is manageable. Five hundred are not — at least not without the right systems.

Legal departments at mid-sized and large enterprises face a common problem: indemnification obligations are scattered across thousands of contracts, stored in email, SharePoint, and legacy systems. When a claim arises, finding the relevant clause and understanding its scope becomes a scramble.

This is where contract lifecycle management becomes strategic, not administrative. A CLM platform gives legal teams the ability to:

Centralize all contracts in a single, searchable repository. Instead of hunting through folders, you can locate every contract containing indemnification language in seconds.

Standardize clause language through a pre-approved clause library. Legal ops can define standard, fallback, and prohibited indemnification terms, ensuring consistency across all agreements.

Track obligations and deadlines automatically. If an indemnification obligation survives for five years post-termination, the system alerts you before the deadline expires.

Analyze risk exposure across your entire contract portfolio. Which contracts have uncapped indemnification? Which have mutual vs. one-sided structures? A modern CLM platform can answer these questions without manual review.

DiliTrust’s Contract Lifecycle Management platform was built for exactly this challenge. Its AI-powered clause extraction automatically identifies and classifies indemnification provisions across all your agreements. Legal teams can search for specific language, compare clauses across counterparties, and flag high-risk terms for renegotiation. With a centralized clause library, you can draft from pre-approved, risk-validated indemnification language every time — reducing exposure before the contract is even signed. And when a claim does arise, a full audit trail and intelligent obligation tracking ensure you know exactly what you agreed to, when it expires, and who’s responsible.