Negotiating limitation of liability: documents to prepare
Negotiating limitation of liability in a technology contract starts before the first call, not during it. Three documents carry the discussion: the current liability schedule with every cap and carve-out marked, an exposure estimate by failure scenario, and a summary of insurance cover. Without these, the negotiation drifts into numbers nobody can defend.
What changes once negotiation starts
A liability cap that looked acceptable in a template becomes a live commercial position once a counterparty pushes back. At that point the team needs a documented fallback, not an improvised number. Once the other side proposes a figure, the internal approval chain has to move fast enough to respond within the same negotiation window, or the deal timeline slips into the following contract cycle.
The point of no return is the moment a cap is confirmed in writing to the other side. Before that point, positions can shift internally without cost. After that point, walking back a number damages credibility for the rest of the negotiation.
Documents to prepare
| Document | Purpose | Owner |
|---|---|---|
| Current liability clause, annotated | Shows every existing cap, exclusion and carve-out in the draft | Legal team |
| Exposure estimate by scenario | Quantifies realistic loss for data loss, outage, IP claim, third-party claim | Finance lead |
| Insurance cover summary | Confirms whether proposed caps sit within current policy limits | Insurance broker or risk officer |
| Internal approval threshold note | States which caps can be agreed without further sign-off | Commercial owner |
| Fallback position with two or three cap structures | Gives the negotiator room to move without a new internal round | Legal team |
What to do
- Legal team pulls the current draft and marks every cap, exclusion and carve-out before any exchange with the other side.
- Finance lead prepares an exposure estimate for each realistic failure scenario, not a single headline number.
- Commercial owner confirms internally which caps are non-negotiable and which have room to move.
- Insurance broker or risk officer checks that any proposed cap structure stays within existing cover.
- Legal team drafts a fallback position with two or three acceptable structures, ready before the first call.
- Commercial owner schedules the negotiation session with a fixed agenda limited to liability terms, so the discussion does not merge with pricing or scope.
Documents produced at each step should be retained in a single file from the outset. See Retention: the report, the extracts and our copy in for how a working file is kept and for how long once the negotiation closes.
Who decides
Internal sign-off on a liability cap usually rests with a director or, above a set exposure threshold, with the board. On the counterparty side, procurement or in-house counsel typically holds authority to accept a proposed cap; anything below their internal risk threshold escalates further up before a reply comes back. A first exchange of positions usually takes five to ten working days. Full negotiation, from opening position to signed clause, runs two to six weeks depending on how many caps are contested and how many internal approvals each side needs.
Where this splits into scenarios
If the counterparty refuses any cap on liability for data loss or a security incident, escalate to an internal risk committee before continuing. This is no longer a routine negotiation point — it changes the deal economics and may need a different commercial structure.
If the contract involves processing personal data at scale, liability negotiation has to run alongside the data protection assessment, not after it closes. Caps agreed before that assessment finishes are often reopened once the real exposure is known.
If the other side offers an uncapped liability position in your favour, treat it as a signal to check, not a result to accept. Confirm enforceability and whether their insurance actually backs the exposure before relying on the offer.
Sources and limit
This page describes a negotiation procedure, not a legal opinion on a specific clause. It does not cover drafting the wording of a cap, does not cover cross-border enforcement of a liability limit once litigated, and does not replace review of the actual contract by counsel handling that file.
Two of the report products behind this workflow illustrate how far a preliminary check can go before a full review is needed: Counterparty in United Kingdom and its limits in practice shows what a counterparty check establishes and where it stops.
A parallel example from another jurisdiction is set out in Document in Austria and the deadline, useful when the negotiation involves a document produced abroad.
Verified
Reviewed for currency of the procedural description on the date this page was last published. The steps and timeframes above reflect internal negotiation practice on technology contracts and are not tied to a specific statutory deadline; where a statutory reference applies to a particular clause, it belongs to the specific contract review, not to this procedural overview.
Related publications
A comparable procedure for a different technology contract workstream is set out in Open source compliance review: documents to prepare.
FAQ
How long does negotiating a liability cap take in practice?
A first exchange of positions typically takes five to ten working days. Full negotiation through to a signed clause runs two to six weeks, depending on how many caps are contested and how many internal approvals each side needs to clear.
Which documents are needed before the first call?
An annotated current liability clause, an exposure estimate by scenario, and a summary of insurance cover. A fallback position with two or three acceptable cap structures should also be ready, so the negotiator is not improvising mid-call.
What happens if the other side does not respond to a proposed cap?
Set a fixed follow-up date when the position is sent, and escalate internally if that date passes without a reply. Silence on a liability cap should never be read as agreement; the fallback position stays open until the other side confirms a number in writing.
Once positions are confirmed on both sides, the next question is often what happens to on-chain payment obligations tied to the same deal — a separate procedure covered in When royalties encoded on-chain are ignored step by step.