Negotiating limitation of liability: what the decision maker looks at
The decision maker checks five things: the cap value, the carve-outs sitting outside it, the insurance behind the number, whether the cap runs both ways, and whether it survives contract termination. Everything else in the negotiation follows from these five points. Skip one, and the clause reopens later, at a worse moment.
What changes once the cap is on the table
Once a limitation of liability clause enters the draft, the negotiation stops being about the service and starts being about exposure. Legal teams on both sides shift from describing deliverables to pricing risk. The clock on the deal often slows here, because the number has to clear an internal risk committee before anyone signs, and that committee rarely meets on the same schedule as the deal team.
A similar delay pattern shows up around fee changes in adjacent digital-asset structures, for instance in Fee schedules in tokenised rights and the deadline, where a published change forces the same kind of internal sign-off before terms settle. The pattern is the same regardless of subject matter: a number changes, and someone with budget authority has to look at it before the contract can move.
The practical effect for a negotiator is timing, not drafting skill. A well-drafted cap that reaches the wrong internal reviewer at the wrong point in the quarter can sit unsigned for weeks. Sequencing the internal review earlier in the process, rather than after the commercial terms are agreed, removes most of that delay.
What to do before the call
- Map the worst-case exposure in monetary terms, separately from the contract value, before any number reaches the table.
- Pull the certificate of insurance and check whether the limit requested by the other side is actually covered.
- Draft an internal position paper stating the floor and ceiling the negotiator is authorised to accept.
- Identify who inside your organisation signs off on the final number, and confirm they are available within the negotiation window.
- Send a term sheet, not a marked-up contract, when the gap between positions is still wide.
- Log every concession with a date, so the audit trail shows why the cap moved.
The evidence a negotiator gathers here — exposure figures, insurance certificates, sign-off records — follows the same logic used in unrelated assessments of legitimate interest, where the file has to show what was checked and when. A short overview of that evidence discipline sits in Legitimate interest assessment overview and the evidence, and the habit transfers directly to a liability negotiation file: write down what was checked, not only what was decided.
Skipping step one is the most common cause of a stalled negotiation. Without a worst-case figure, neither side can tell whether a proposed cap is generous or thin, and the conversation drifts into anecdote instead of numbers.
Who decides, and how long it takes
| Question | Decision maker | Typical timing |
|---|---|---|
| Is the proposed cap acceptable in principle? | Commercial lead or general counsel on each side | 1–2 working days after the term sheet is read |
| Does the cap need risk-committee approval? | Internal risk or credit committee, where exposure exceeds an internal threshold | 1–3 weeks, run in parallel with drafting |
| Is the final number signed off? | Authorised signatory named in the position paper | Same day as the last redline, once the number is fixed |
The pace above assumes both sides have already gathered their evidence. A negotiation that starts before the exposure figures exist tends to run twice as long, because the same questions come back after the number is already on the table, and by then each side has already anchored to a position it is reluctant to move from.
Common forks in the negotiation
If the counterparty is a cloud or SaaS vendor, the cap usually sits close to fees paid in the preceding twelve months, and the carve-outs concentrate on data loss and security incidents. If the counterparty is a custom development shop, the cap tends to track the total contract value instead, because there is no recurring fee base to anchor it to.
If regulated data is involved, expect a separate, higher cap for data-related claims, negotiated on its own track rather than folded into the general limit. Mixing the two tracks into a single number usually produces a figure too high for one side and too low for the other.
If the other side pushes back on mutuality — asking for a one-way cap that protects only their exposure — treat that as a signal to check their insurance position before conceding, not after. A one-way request without insurance behind it is a different negotiation than a one-way request backed by a policy.
What this page does not settle
This page describes the negotiation sequence, not the exposure figure specific to any one deal. Before a developer is appointed, the exposure itself needs checking against the counterparty's own standing, not just against the clause wording. A separate check covers that ground: Counterparty report before appointing a developer, run before the appointment rather than after the cap is fixed.
Where the contract sits inside a Lithuanian corporate structure, the question of who inside the company can actually authorise the final number is a separate, documented fact rather than an assumption. That fact is established in Document in Lithuania and who decides, and it should be checked before the negotiator's authority is put in writing.
Related reading
A parallel procedure applies when the contract includes open source components, where the decision maker's checklist differs from the one above: Open source compliance review: what the decision maker looks.
Verified
This procedure was last reviewed on 14 February 2025. It describes internal negotiation and sign-off practice rather than a statutory requirement, so no legal citation applies to the steps above. Where a legal act is directly relevant to a specific contract term — data protection clauses, cybersecurity obligations, software licensing terms among them — that reference belongs on the substantive page covering that term, not on this procedural overview.
Frequently asked questions
How long does negotiating limitation of liability take in practice?
Once both sides have their exposure figures and insurance certificates ready, the core negotiation runs one to three weeks. Add another one to two weeks if a risk committee has to approve the number separately from the deal team.
Which documents are needed to start?
Three documents cover the start: a worst-case exposure estimate, a current certificate of insurance, and an internal position paper naming the floor, ceiling and authorised signatory.
What happens if the other side does not respond?
Set a response deadline in the term sheet itself, typically five to ten working days. If it passes without a counter, escalate internally before sending a reminder — a silent counterparty sometimes signals a decision still pending on their side, not a rejection.