Limitation of liability clauses, explained in plain English

Almost every commercial contract contains one clause that decides, in advance, the maximum amount of money that can change hands when the deal goes badly. It is usually a single paragraph, it is usually written in capital letters, and it is usually skimmed.

The limitation of liability clause is worth understanding properly, because it is the difference between a bad outcome costing you what you paid and a bad outcome costing you the company.

The three moving parts

A complete limitation of liability provision does three separate things. Confusing them is the most common reason founders misread their own exposure.

Read them in that order and the clause stops being a wall of capitals. The cap says how much. The exclusion says what kinds. The carve-outs say which claims ignore the first two.

The cap

The most common formulation in software and services contracts is:

Each party's total aggregate liability arising out of or related to this Agreement shall not exceed the fees paid or payable by Customer in the twelve (12) months preceding the event giving rise to the claim.

Three details in that sentence do a lot of work.

"Paid or payable" matters at the beginning of a contract. If you're two months into an annual deal and the cap is limited to fees paid, the ceiling may be two months of fees. "Paid or payable" measures against the committed annual value instead.

"Twelve months preceding the event" is a rolling window, not the contract value. On a three-year deal the cap is one year of fees, not three.

"Total aggregate" means all claims across the life of the agreement share one ceiling — not one cap per incident.

Is the cap proportionate to the risk?

The honest question is not "is 12 months of fees standard" — it is, and it usually is. The question is whether 12 months of fees is proportionate to what happens if this specific vendor fails.

A $2,000/year tool that formats invoices and a $2,000/year tool that holds your entire customer database carry the same cap and wildly different exposure. Where the fee-based cap is far below the realistic harm, that mismatch is the thing to negotiate — usually by moving the high-risk categories out of the general cap rather than by raising it across the board.

The exclusion of indirect and consequential damages

Separate from the cap, most contracts exclude whole categories of loss: indirect, incidental, special, consequential, exemplary and punitive damages, and — named separately because courts have not treated it consistently — lost profits.

The practical effect is larger than it sounds. In a lot of real disputes, the damage a business actually suffers is lost profit and lost business opportunity. A clause that excludes those categories can leave a claim theoretically alive and economically empty, even well under the cap.

Two things to check:

• Is it mutual? An exclusion that protects only one party is an obvious asymmetry and an easy ask to fix.
• Does it swallow the indemnities? If a party owes an indemnity for third-party claims, and consequential damages are excluded without a carve-out, the indemnity can be argued away. Well-drafted contracts state that the exclusion does not limit indemnification obligations.

The carve-outs: where the negotiation actually happens

Carve-outs name the liabilities that sit outside the cap, the exclusion, or both. The list is the single most negotiated part of a commercial agreement, and the usual candidates are:

• Breach of confidentiality — often carved out, or given a higher cap.
• Indemnification obligations — especially IP infringement indemnity.
• Gross negligence and willful misconduct — very commonly carved out; in some jurisdictions these cannot be limited by contract in any case.
• Breach of data protection obligations — increasingly carved out or supercapped as privacy exposure has grown.
• Death or personal injury caused by negligence — unenforceable to exclude in many jurisdictions, so contracts usually say so explicitly.
• The customer's obligation to pay fees — vendors carve this out so the cap can't be used as a ceiling on unpaid invoices.

The asymmetry to look for: a clause that carves out the customer's payment obligation and the customer's indemnities, but nothing of the vendor's. That's a mutual-looking cap that binds one side.

Supercaps

Where a flat carve-out is too much and the general cap is too little, the usual compromise is a supercap — a second, higher ceiling for named categories.

...provided that each party's aggregate liability for breach of Section 8 (Confidentiality) and Section 10 (Data Protection) shall not exceed three (3) times the fees paid or payable in the twelve (12) months preceding the claim.

Supercaps are a genuinely useful negotiation tool because they give the counterparty a bounded number rather than open-ended exposure, which is usually what they're actually defending.

How to read the clause in ninety seconds

1. Find the cap. Write down the formula and calculate the actual dollar figure for your deal. A cap you haven't converted to a number is a cap you haven't evaluated.
2. Check "paid or payable" and the length of the look-back window.
3. Find the exclusion and check whether it's mutual.
4. List the carve-outs and mark which side each one benefits.
5. Compare the number to the harm. If this vendor fails in the worst realistic way, what does that cost you? If the answer is much larger than the cap, you've found the thing to negotiate.

Step 5 is the one people skip, and it's the whole point. The cap is not inherently unfair at 12 months of fees — it's unfair when the fees are small and the data is not.

What a fair clause tends to look like

Across the vendor agreements we see, a version both sides usually accept looks roughly like:

• A mutual cap at 12 months of fees paid or payable.
• A mutual exclusion of indirect and consequential damages and lost profits, expressly not limiting indemnification obligations.
• Uncapped: gross negligence, willful misconduct, death or personal injury, and the customer's payment obligations.
• Supercapped at some multiple of annual fees: confidentiality breach, data protection breach, and IP infringement indemnity.

That shape is defensible from either side of the table, which is what makes it easy to propose.

Related reading

The indemnity carve-out only makes sense alongside the indemnity itself — indemnification clauses, explained covers who pays and who controls the defense. For where this clause sits in a full review, see how to review a contract without a lawyer, and for the other clauses we flag most often in vendor paper, five clauses we always flag in vendor MSAs.

A disclaimer

This explains how limitation of liability clauses are typically structured and negotiated. It is not legal advice and does not create a lawyer–client relationship. Enforceability varies significantly by jurisdiction — some limitations are void as a matter of law, some require specific formatting or conspicuousness, and consumer contracts follow different rules entirely. Take the numbers that matter to a lawyer.