The Limitation of Liability Clause Explained (2026)

What a limitation of liability clause is A limitation of liability clause is the part of a contract that decides how much one party can be made to pay if things go wrong, and for which kinds of loss. It usually does two jobs at once. First, it sets a cap, a ceiling on the total money a party can recover. Second, it excludes whole categories of loss, most often indirect or consequential loss such as lost profits, lost revenue and lost business opportunity. Direct damages are the losses that flow naturally and immediately from a breach, for example the cost of fixing or re-procuring what was promised. Consequential damages are the knock-on losses that follow, such as the profit you would have earned if the service had worked. Direct damages are usually recoverable unless the contract clearly says otherwise. Indirect and consequential losses are the ones most clauses try to exclude, so the exact definition of "consequential loss" matters a great deal. ## Why it matters The clause is where the commercial risk of the whole deal is actually allocated. A vendor charging a modest annual fee does not want unlimited exposure if a downstream failure costs the customer millions. A customer, on the other hand, wants enough recovery to be made whole. The cap and the exclusions are how the two sides land on a number they can both live with. It also drives insurance and pricing. A supplier will often price a deal, and buy cover, based on the cap it has agreed. If the cap is too low the customer carries the real risk. If it is too high or absent the supplier may refuse the deal or raise the price. ## A typical structure Caps are commonly expressed by reference to the fees paid under the contract. A widely used market position for software and services is a cap set at the fees paid in the twelve months before the claim, sometimes expressed as the greater of fees paid or a fixed floor. Other contracts use a fixed sum, or a multiple of annual fees for higher-risk work. A sample clause reads along these lines: > Subject to the carve-outs below, each party's total aggregate liability arising out of or in connection with this Agreement, whether in contract, tort (including negligence), or otherwise, shall not exceed the total fees paid or payable by the Customer in the twelve (12) months preceding the event giving rise to the claim. Neither party shall be liable for any indirect or consequential loss, or for any loss of profit, revenue, anticipated savings, goodwill or data, in each case whether direct or indirect. ## How to negotiate it Set the cap by reference, not a guess. Fees-based caps scale with the size of the deal and are easier to defend than an arbitrary number. Decide whether the window is total fees, annual fees, or fees in the period before the claim. Pin down the exclusions. "Consequential loss" has a narrow legal meaning in some jurisdictions and a broad commercial meaning in others. List the specific losses you intend to exclude (lost profits, lost revenue, loss of data) rather than relying on the label alone. Agree the carve-outs. Certain liabilities are usually left uncapped or outside the exclusions because the law will not allow them to be limited, or because the risk is too important. These commonly include death or personal injury caused by negligence, fraud and fraudulent misrepresentation, a party's indemnities, breach of confidentiality, and infringement of intellectual property. Data protection and security breaches are frequently given a separate, higher "super cap". Make the clause mutual where you can. A cap that only protects one side invites a fight. Mutual caps, with agreed carve-outs, are easier to close. Check enforceability under the governing law. Most systems will not let a party exclude liability for fraud, wilful misconduct, or death and personal injury. Some require the limitation to be reasonable. A clause that overreaches can be struck down in full, leaving you with no protection at all. ## Common mistakes Relying on the words "consequential loss" to exclude lost profits, when under the governing law lost profits can be a direct loss. Setting a single low cap that also swallows the indemnities and IP claims you meant to protect. Forgetting to exclude death, personal injury and fraud, which can void the whole clause. Leaving the cap silent on whether it is per claim or aggregate across the contract term. ## One workspace to draft, review and track your clauses Most teams do not lose on the wording of a single clause. They lose because the clause lives in a Word file, the risk sits in someone's head, and the key date hides in an inbox. The fix is to keep drafting, review, tracking and governance in one place instead of five disconnected tools. The single-workspace idea is simple. You draft from your own catalogue and house style, the system reads any document and flags positions as favourable, neutral or unfavourable to your company, every edit is tracked with a timeline, and obligations and dates become alerts you can assign. Because the contract is held as a structured clause tree rather than flat text, you can change a clause in plain English and see exactly what moved. Adira is one such workspace, built on Anthropic's Claude and tuned to how your company actually contracts. India is deepest today, with other jurisdictions and a company command centre on the roadmap.