Publication
Motor Finance Redress: The Way Ahead
On August 1, 2025, the UK Supreme Court delivered its long-awaited judgment in Hopcraft v Close Brothers Limited and on 3 August the FCA announced it would consult on a redress scheme.
Global | Publication | September 2025
Liability is often a contentious topic (and typically the last provision to be agreed) in a technology or outsourcing contract negotiation. In a claim for losses suffered in connection with the contract, liability clauses can function as both a sword to the claimant and as a shield to the other party, if they are clearly drafted, by providing for:
Focusing on English-law governed technology and outsourcing contracts, here we:
The purpose of a liability clause is to allocate risk. While the negotiations often centre around legal principles and drafting, risk is ultimately a commercial issue, the appetite for which is driven by commercial imperatives.
Each party will be seeking to minimise its own financial exposure under the contract, while at the same time ensuring that it has adequate recourse to the other party for potential losses.
|
Not necessarily reciprocal A fair allocation of risk in a technology or outsourcing contract seldom results in reciprocal liability provisions for the simple reason that the parties’ individual risk profiles are typically fundamentally different. For example:
|
How a business approaches the allocation of risk in a liability clause depends on a number of factors, ranging from the industry in which the parties operate, the governing law and the parties’ bargaining position.
The approach is likely to vary jurisdictionally. For example, in technology and outsourcing contracts governed by US law (or drafted by US parties), liability provisions may be drafted not as a series of exclusions, but rather, in the form of an indemnity allocating risk.
From an English law perspective, a liability clause in a technology or outsourcing contract typically includes the following provisions (it is worth noting that liability provisions may be scattered throughout the contract and are not always contained in a single “Liability” or “Limitation of liability” clause):
We discuss each of these in turn.
|
“Nothing in this Agreement limits or excludes a Party’s liability for: … ”
|
This clause sets out the situations where the parties have agreed that neither party may rely on the financial caps and exclusions set out in the contract (including where the parties cannot limit or exclude liability as a matter of law):
|
Market trends As at the date of publication, we are seeing the following market trends in relation to liability in technology and outsourcing agreements:
|
|
“Neither Party shall have any liability to the other Party for: … ”
|
This clause lists the types of losses a party is unable to claim (that is, excluded losses).
When a party is calculating its losses that arise “under” (that is, from a breach of contract) or “in connection with” (that is, in tort) the contract, it will only be able to claim the types of losses that the contract permits. Technology and outsourcing contracts almost invariably exclude liability for indirect or consequential losses, but the parties often agree that certain other losses are excluded too, regardless of whether they are direct or indirect.
These may include (among others):
As at the date of publication, a market-standard position typically excludes liability for these types of losses. Some favour both parties and so are seen as less contentious. For example, excluding “loss of profit or revenue”:
The list of excluded losses should always be considered on a case-by-case basis so not to prevent a party from claiming the kinds and types of losses that are most likely to flow from the other party’s breach.
For example, a well-advised customer would not accept a “loss of data” exclusion in a scenario where data processing or storage is a central component of the service provider’s activities.
|
Market trends As at the date of publication, we are seeing customers more frequently and successfully resisting the standard “loss of use” exclusion in SaaS and cloud contracts. From the customer’s perspective, loss of use of a platform (either temporary or permanent) is one of the main consequences of a service failure on by the provider. Making the platform available is also the service provider’s core obligation, and such an exclusion implies that it may not be liable for failing to do so. Service providers may wish to draft more precisely to exclude the types of loss that may flow from the customer not being able to use the platform, to the extent not already captured in other exclusions, like “loss of revenue” (or not otherwise excluded by the application of force majeure or relief provisions). |
Assumed losses clauses
Technology or outsourcing contacts sometimes include a clause dealing with so-called “assumed losses”, which sets out specific types of losses that the parties have agreed are to be recoverable even though they might otherwise be excluded on the basis that they:
Such clauses are typically drafted unilaterally in favour of the customer. They have traditionally been more common in business process outsourcing contracts than in licences and other technology-driven contracts but are now more frequently included in contracts for business-critical platforms.
|
Market trends Service providers who might otherwise resist the inclusion of an assumed losses clause might be more open to including one if it is expressly stated that the service provider does not have uncapped liability for the assumed losses. An example of drafting to achieve this is: “The Parties agree that the following Losses shall be recoverable by [Customer] under or in connection with this Agreement notwithstanding the exclusions of liability in clause [x], but subject to the financial limits on [Supplier’s] liability in clause [y]: (a) [list of assumed losses]; and (b) ….. ”. Types of losses that are frequently negotiated for inclusion in an assumed losses clause include:
|
|
“[Party A’s] total liability to [Party B] for any losses incurred or suffered by [Party B] shall be limited to: … ”
|
This clause provides for the maximum amount for which a party is liable where claims arise under the contract. There is no magic formula for what a party’s liability cap should be - it is ultimately a commercial decision for each party based on an assessment of risk versus reward. That said, liability limits are often derived from market norms which differ depending on the nature of the technology or outsourcing in question.
Common approaches we see in technology and outsourcing contracts include:
While there are many other aspects of liability not dealt with here, the main principle to bear in mind is that liability caps should reflect the risk and reward under a contract.
A service provider will be reluctant to accept a liability cap that is out of proportion to the revenue it receives from the customer and the profit margin it can make from that revenue. On the other hand, the customer may argue that a cap exceeding such revenue is justified because of a particular risk presented by the services or technology.
In any event, the caps should be high enough to incentivise performance; if its caps are too low, the relevant party may consider that it is easier to walk away from the contract than to perform the contract.
|
Market trends As at the date of publication, we are commonly seeing the following:
|
There are, of course, a number of other principles and aspects to liability clauses that are not addressed here, including:
Overall, liability clauses need to be carefully considered so that risk is allocated to the party best able to ameliorate that risk.
|
Want more information? For more information in relation to:
|
Publication
On August 1, 2025, the UK Supreme Court delivered its long-awaited judgment in Hopcraft v Close Brothers Limited and on 3 August the FCA announced it would consult on a redress scheme.
Publication
The Regional Court of Munich (LG München I) has issued a landmark judgment in GEMA v OpenAI (Case No. 42 O 14139/24), holding that the use of copyrighted song lyrics for training generative AI models without a licence violates German copyright law.
Publication
Songa Product and Chemical Tankers III AS v Kairos Shipping II LLC [2025] EWCA Civ 1227 (07 October 2025) has clarified the extent of the obligation on the Charterer to redeliver a vessel following the termination of a Barecon 2001 charter and of the Owner’s right to require it to be redelivered to a port “convenient to them”.
Subscribe and stay up to date with the latest legal news, information and events . . .
© Norton Rose Fulbright LLP 2025