Limitation of liability clauses are among the most important — and most misunderstood — parts of any commercial contract. They're designed to cap the financial consequences if something goes wrong. But if you don't understand them, you could sign up to a contract where you're liable for millions while the other party is protected to the tune of a few thousand. Here's how to read them and what to watch for.
What is a limitation of liability clause?
A limitation of liability clause sets a ceiling on how much one party can claim from the other if there's a breach. Instead of claiming unlimited damages, you can only claim up to a certain amount. For example, a clause might say: "Neither party's liability under this agreement shall exceed the fees paid in the preceding twelve months." If you've paid £10,000 in fees, your maximum claim is £10,000, even if the breach caused £100,000 in damage.
These clauses exist because businesses need certainty. If you're a software provider and you're not sure whether a single bug could lead to a £1 million liability claim, you can't price your services or get insurance. Limitation clauses give you a cap on risk. They're standard in commercial contracts, and they're usually fair to both sides. But the details matter enormously.
How are liability limits usually expressed?
There are several common ways to express a liability limit. The first is a direct cap: "Neither party shall be liable for more than £100,000." This is simple and clear. The second is a proportion of fees: "Liability is capped at the fees paid in the preceding 12 months." This ties the cap to the value of the relationship. The third is a proportion of contract value: "Liability cannot exceed 50 per cent of the contract value." The fourth is a time-based cap: "Liability is limited to the fees attributable to the period in which the breach occurred."
The fourth method is important because it creates a very low cap. If you have a two-year contract worth £100,000 (so £50,000 per year), and something goes wrong in month 3, your liability is only the fees for that month, maybe £4,000. That's an enormous restriction, and if you're the one providing the service, you should be very careful with this approach.
Carve-outs and exceptions
Most limitation clauses have carve-outs — things that aren't subject to the limit. The most common carve-out is for "death or personal injury caused by negligence." You can't contract out of liability for killing someone. Another carve-out is for "fraud or willful misconduct." If you deliberately do something wrong, the cap doesn't apply. A third is "intellectual property indemnification." If you breach an IP indemnity and the other party gets sued, your liability might not be capped.
These carve-outs are usually fair. But watch for unusual ones. Some contracts say "liability is capped except for breach of confidentiality obligations," which creates an uncapped risk for breaching an NDA. Or "except for breach of payment obligations," which means the other party can claim unlimited damages if you're late on a payment. Read the carve-outs carefully. If there are too many, the cap becomes meaningless.
Consequential damages exclusions
Many limitation clauses also exclude "consequential damages" or "indirect damages." These are damages that flow from the breach but aren't the direct consequence. For example, if your software system is down, the direct damage is the value of the system. But consequential damages might include lost profits, lost business, or costs of finding an alternative solution.
A clause might say: "Neither party shall be liable for loss of profits, loss of business, loss of data, or any indirect or consequential damages." This is valuable protection because consequential damages are often much larger than direct damages. If you're providing a service, you want this clause. If you're receiving a service, you should push back. You want to be able to claim the actual financial impact of the breach, not just the direct cost.
The problem with asymmetrical limits
Many contracts have one-sided liability limits. A software provider might cap its liability at the fees paid (maybe £50,000) while the customer's liability for breach of payment or breach of confidentiality is unlimited. That's unfair. If you're both parties to the contract, liability limits should be symmetrical unless there's a very good reason.
Watch for this especially in supplier contracts. A vendor might cap its liability for non-delivery at a small percentage of contract value, while your liability for non-payment is the full invoice amount. Or a contractor might cap liability for poor work while your liability for not paying them is unlimited. Ask for symmetrical caps.
How low can the cap go?
There's no minimum legally required cap. Some contracts limit liability to £1, or to a nominal fee. That's obviously ridiculous and unenforceable, but you do see it. A reasonable cap is somewhere between 25 per cent and 100 per cent of the annual fees or contract value. If it's lower than that, you might be signing up to deliver services with almost no protection if something goes wrong.
When to push back on limitations
If you're the service provider, limitations are good. You want a low cap on your liability. If you're the service buyer, limitations are problematic. You want high exposure if the service is bad. But the contract is a negotiation, so you need to find the balance.
If you're receiving a critical service — cloud hosting, insurance, audit services — where a failure would be catastrophic, push for a higher cap or a carve-out for critical failures. If you're providing a low-value service, accept a lower cap. The cap should roughly correspond to the financial damage that could result from a breach.
When reviewing your contract, read the limitation clause carefully. Understand what's capped, what's excluded, whether it's symmetrical, and whether it makes sense given the value and nature of the contract. It's one of the most important clauses in any commercial agreement.