Negotiating Indemnification Clauses (2026)

An indemnification clause is a promise by one party to cover the other's losses from a defined event. It looks like boilerplate but it is one of the most powerful risk-shifting tools in a contract, because a well-drafted indemnity can give a dollar-for-dollar recovery without the usual hurdles of a breach-of-contract claim. This guide explains what you are actually agreeing to, which parts to negotiate, and a ladder of fallback positions. It is general information, not legal advice, and indemnity law differs by country, so take local advice on anything material. ## What an indemnity really does In an ordinary breach claim, you must prove the other side broke the contract, prove your loss, show the loss was not too remote, and try to reduce it. An indemnity can shortcut most of that. If the triggering event happens, the indemnifying party pays the defined losses, often including legal costs and often without you having to prove breach or foreseeability. That is why indemnities are worth negotiating carefully: they can expose you to liability far larger, and far easier to trigger, than a normal claim. The three questions that decide an indemnity's weight are: what triggers it, what losses it covers, and how it is controlled. ## The parts you negotiate The trigger. What event forces payment? Narrow triggers are safer for the party giving the indemnity: "third-party claims arising from our breach of this agreement" is far narrower than "any losses arising out of or in connection with this agreement." Watch the words "arising out of or in connection with," which cast a very wide net. Fault-based triggers (negligence, breach, wilful misconduct) are more balanced than no-fault ones. Third-party claims only, or direct losses too? The safest indemnities cover only third-party claims: a customer, regulator or other outsider sues, and the indemnifier pays. A broader indemnity also covers the other party's own direct losses, which turns the indemnity into a general compensation promise and is much more dangerous to give. What losses are covered. Reasonable: damages, settlements and legal costs from a covered claim. Dangerous: all losses "including indirect and consequential loss," which can swallow the liability cap. Tie the indemnity's wording to the rest of the contract's loss definitions. Control of the defence. If you are indemnifying, you usually want the right to control the defence and settlement of the claim, since you are paying. The other side wants a say, especially if a settlement would admit fault or affect its reputation. A common compromise: the indemnifier controls the defence, must not settle in a way that imposes non-financial obligations or admissions on the other party without consent, and the other party may join with its own counsel at its own cost. Conditions and cooperation. Prompt written notice of a claim, cooperation in the defence, and no admissions by the indemnified party without consent. These protect the indemnifier and are reasonable to include. ## Indemnities and the liability cap The most important technical point: does the indemnity sit inside or outside the limitation of liability cap? An IP infringement indemnity carved fully outside the cap can be a huge, uncapped exposure. An indemnity left inside the cap may be nearly worthless if the cap is only a few months' fees. Both sides should decide this deliberately, not by accident. A common landing: the IP indemnity is carved out of the cap (or given a higher super cap), while a general breach indemnity stays inside it. ## The common indemnities and who gives them - IP infringement. The supplier indemnifies the customer if the product infringes a third party's IP. Standard and usually expected.

• Data protection and security. Increasingly common; the party handling personal data indemnifies the other for breaches it causes.
• Confidentiality breach. Either side, for leaking the other's confidential information.
• Compliance with law. Each party indemnifies the other for its own legal or regulatory failures.
• Bodily injury and property damage. Common in services and physical-work contracts. ## A fallback ladder for the party giving the indemnity 1. Indemnity limited to third-party claims arising from your breach or negligence, covered losses limited to damages, settlements and reasonable legal costs, sitting inside the liability cap.

2. Accept the IP indemnity outside the cap, but with a right to control the defence, standard conditions, and the usual mitigations (you may modify or replace the infringing item, or refund the fees).
3. Offer a higher super cap for the indemnity rather than fully uncapped exposure.
4. Accept broader trigger wording only in exchange for a fault requirement and tight loss definitions excluding indirect loss.
5. Walk-away: refuse a no-fault indemnity for the other party's own direct and consequential losses with no cap, which is unlimited exposure in disguise. ## A fallback ladder for the party receiving the indemnity 1. Broad indemnity covering third-party claims and direct losses, legal costs included, carved out of the cap.
6. Third-party claims plus direct losses, with the IP and data indemnities carved out of the cap and others inside it.
7. Third-party claims only, but with the key indemnities (IP, data) given a meaningful super cap.
8. Accept the indemnity inside the cap, but push the cap high enough that the indemnity is still worth something. ## Common mistakes to avoid - Leaving the indemnity silent on whether it is inside or outside the liability cap.

• Accepting "arising out of or in connection with" without a fault requirement, which makes the indemnity fire on almost anything.
• Giving an indemnity for the other party's own losses, not just third-party claims, without realising it.
• Letting the indemnity cover indirect and consequential loss, undoing the exclusion elsewhere in the contract.
• Forgetting to secure control of the defence when you are the one paying.
• Not checking that any uncapped indemnity is backed by insurance you actually hold. ## Keeping indemnity exposure visible across your contracts A single indemnity can be read and reasoned about. The danger is the aggregate: which of your signed contracts contain uncapped indemnities, which ones you give versus receive, and whether your insurance covers what you promised. That is hard to see when contracts live in folders and inboxes. Keeping them in one connected workspace, where each agreement's indemnities and their relationship to the cap are surfaced clause by clause, lets you answer those questions without reading every file. Adira is built around that idea, on frontier AI, so the risks you took on sit together and visible rather than hidden in executed PDFs. If you cannot quickly list your uncapped indemnities, that is the gap worth closing. More at Adira. The negotiation guidance above works with any tool. ## Bottom line An indemnity is a shortcut to recovery, which is exactly why you must negotiate its trigger, its covered losses, its control of the defence, and above all its relationship to the liability cap. Keep the indemnity you give narrow, fault-based and tied to third-party claims where you can, carve out IP and data where it is fair to do so, and never give an uncapped indemnity your insurance would not cover. Confirm the detail with a qualified lawyer before signing anything material.