Indemnity agreement: what it is and what to include

What an indemnity agreement is

An indemnity agreement, sometimes called a hold harmless agreement, is a legally binding promise by one party (the indemnitor) to compensate another party (the indemnitee) for specified losses. Those losses commonly include damages, settlements, judgments, penalties, and the legal fees spent defending a claim. The promise can stand alone as its own contract, but more often it lives as an indemnification clause inside a larger agreement such as a services contract, purchase order, commercial lease, or software license.

The core purpose is risk allocation. Rather than leaving the question of who pays to the background rules of tort and contract law, the parties agree in advance which risks each side will carry. A vendor might agree to indemnify a customer against claims that the vendor’s product infringes a third party’s intellectual property, while the customer agrees to indemnify the vendor against claims arising from how the customer used or modified that product.

Indemnities also differ in how far they reach. A broad form may cover losses regardless of fault, including losses caused in part by the indemnitee’s own negligence. An intermediate form covers everything except losses caused solely by the indemnitee. A limited or comparative form covers only the portion of a loss attributable to the indemnitor. How far an indemnity can extend toward the indemnitee’s own negligence is tightly regulated: many states apply “express negligence” or “clear and unequivocal” rules, and anti-indemnity statutes restrict these clauses in industries such as construction and oil and gas.

Key terms and clauses to include

A workable indemnity agreement spells out not just the promise but the mechanics of how it operates. The following elements deserve explicit attention:

• Definition of covered losses. State exactly what the indemnitor will pay for: damages, settlements, judgments, fines, and reasonable attorneys’ fees and costs. Vague references to “any and all losses” invite disputes over scope.
• Triggering events and scope. Identify the specific claims or circumstances that activate the indemnity, such as third-party claims, breach of the agreement, negligence, or intellectual property infringement. Distinguish first-party claims (between the two parties) from third-party claims brought by outsiders.
• Duty to defend versus duty to indemnify. The duty to defend requires the indemnitor to fund and manage a legal defense as claims arise, while the duty to indemnify reimburses losses once liability is fixed. These are separate obligations, and the duty to defend is often broader and more expensive.
• Notice and cooperation. Require prompt written notice of any claim and set out how the parties will cooperate. Late or defective notice can forfeit or reduce coverage.
• Control of defense and settlement. Say who selects counsel, who controls strategy, and whether the indemnitee’s consent is needed before settling. Include a rule that neither side may settle in a way that admits the other’s fault or imposes non-monetary obligations without consent.
• Caps, baskets, and limitations. Consider a monetary cap, a deductible or “basket,” and a deadline for bringing claims. Align these with the deal’s overall limitation of liability so the two provisions do not contradict each other.
• Carve-outs and exclusions. Identify losses the indemnity will not cover, such as consequential damages, losses caused by the indemnitee’s fraud, or amounts already paid by insurance.
• Insurance coordination. Require the indemnitor to carry insurance that supports the obligation and to name the indemnitee as an additional insured where appropriate.
• Survival. State that the indemnity continues after the contract ends or is terminated, and for how long, so obligations do not evaporate at closing.
• Governing law and dispute resolution. Because enforceability turns on state law, name the governing state and the forum for resolving disputes.

When you need one

Indemnity agreements appear across almost every kind of commercial relationship, and one is worth requesting whenever a party could be exposed to liability created by someone else. Common situations include:

• Vendor and supplier contracts, where a buyer wants protection against defective goods, IP infringement, or data breaches.
• Professional and consulting services, where a client seeks cover for errors, omissions, or third-party claims tied to the work.
• Construction and contractor work, where owners, general contractors, and subcontractors allocate injury and property-damage risk, subject to state anti-indemnity limits.
• Commercial leases, where landlords and tenants divide responsibility for injuries or damage on the premises.
• Software, SaaS, and technology licenses, where infringement and data-security indemnities are standard.
• Events, sponsorships, and use of facilities, where an organizer or venue wants protection against participant claims.

If a counterparty’s mistake, product, or conduct could realistically pull you into a lawsuit or regulatory action, an indemnity provision is one of the most direct ways to place that cost where it belongs.

Common pitfalls

Even experienced teams get indemnity clauses wrong. Watch for these recurring problems:

• Overbroad or unenforceable language. An indemnity that tries to cover the indemnitee’s own gross negligence or willful misconduct may be void as against public policy in some states.
• Silent conflict with the liability cap. When the limitation of liability and the indemnity are drafted separately, they often collide; decide expressly whether indemnity obligations sit inside or outside the cap.
• Confusing defend and indemnify. Treating the two as one obligation can leave a party paying for a defense it never meant to fund, or with no defense at all.
• Missing notice and control provisions. Without clear notice timelines and settlement controls, the indemnitor can be bound by a settlement it had no chance to influence.
• No insurance backstop. An indemnity is only as good as the indemnitor’s ability to pay; without insurance requirements, a promise from an undercapitalized party may be worthless.
• Ignoring survival. If the clause does not survive termination, the protection may end exactly when a latent claim finally surfaces.
• One-sided review. Parties sometimes accept a broad indemnity in a hurry; every indemnity should be read from the perspective of the party giving it, not just the party receiving it.

An indemnity agreement is only valuable if it is drafted precisely, tracked carefully, and enforced on time. That is where disciplined contract management matters: knowing which agreements contain indemnities, what each one covers, when the obligations expire, and how they interact with your insurance and liability caps. A CLM platform like Pactolane keeps signed agreements in a searchable repository with an audit trail, sends renewal and deadline alerts so survival periods and notice windows are not missed, and uses standardized templates and approval workflows to keep indemnity language consistent. Its AI copilot, PactAI, can run exposure analysis and risk scoring across a contract and surface conflicting clauses for your team to review, on the principle that PactAI prepares the analysis and the human decides. Handled this way, an indemnity clause stops being buried fine print and becomes a managed, understood part of how your organization allocates and controls risk. This is general legal information, not legal advice; consult qualified counsel before finalizing any indemnity agreement.