Negotiating limitation of liability: costs drivers
Negotiating a limitation-of-liability clause in a technology contract rarely turns on drafting skill alone. Cost climbs with the number of parties, the number of governing jurisdictions, and whether a claim has already surfaced. The clause itself is short; the file behind it is not. This page sets out what drives cost and who decides at each stage.
What drives cost in this negotiation
The clause text is a handful of sentences. What sits behind it is a file: prior drafts, correspondence, and a chain of internal approvals. Cost is set by how much of that file has to be assembled and checked before a figure can be sent to the other side.
| Driver | Effect on cost |
|---|---|
| Number of counterparties on the other side | Each additional counterparty adds a separate approval chain and a separate fallback position. |
| Number of governing-law regimes in play | A mismatch between contracts on the same relationship forces a reconciliation step before any offer is made. |
| Whether a claim or incident has already occurred | A live claim removes flexibility and shortens the time available to negotiate. |
| Whether insurance or indemnity cover is linked to the cap | The cap has to be checked against the policy wording before it is proposed. |
| Whether the cap must be mirrored across a group of related contracts | One change triggers a review of every linked contract, not just the one being negotiated. |
| An external deadline, such as renewal or a go-live date | Urgency compresses the number of rounds available and raises the cost of each one. |
Who decides and how long it takes
Inside the client organisation, the point of no return sits with whoever holds authority to accept a cap below the value of the contract. That authority is usually a named signatory, not the negotiating team. On the other side, the same rule applies in reverse, and a mismatch in seniority between the two teams is a common source of delay.
Negotiation typically runs across two to four rounds of exchange, spread over two to six weeks. A file involving several related contracts, or a claim that has already been raised, extends both figures.
Steps to start
- The client instructs the file lead to map every contract that carries a limitation-of-liability clause tied to the same relationship.
- The associate requests copies of prior drafts and any correspondence about the clause.
- The file lead confirms which jurisdiction governs each contract and flags any mismatch.
- The negotiator prepares a fallback position before the first call with the counterparty.
- The partner signs off on the floor and ceiling before any figure is sent.
- The file lead logs each round of exchange and the date it closed.
Typical scenarios
If the contract references licensed content that a third party could remove, the cap has to address what happens once that reference disappears. When the referenced work is removed and the deadline sets out the mechanics of that risk.
If a data processing agreement sits alongside the main contract, check the cap in the main contract against the cap set out in the Data processing agreement overview step by step, so the two do not contradict each other.
If the other side stops responding mid-negotiation, the file does not stall by default. A follow-up date is set, and the point of no return moves once that date passes without a substantive reply.
Sources and limits
This page covers procedure and cost drivers. It does not establish facts about a specific counterparty, and it does not price a specific engagement.
Where the other side is unfamiliar, the cost driver often traces back to what can actually be established about it. Counterparty in Hong Kong and its limits in practice sets out the boundaries of that kind of check.
Where the negotiation is prompted by a filing deadline rather than a dispute, the relevant reference is Document report before filing with an office and the, which covers what a report can confirm before a submission is made.
Verified
This procedure was last reviewed in March 2025. It reflects internal file-handling practice for negotiating limitation-of-liability clauses in technology contracts and does not rely on a citation to a specific statute or regulation.
Related publications
For a comparable cost picture in a different drafting negotiation, see Open source compliance review: costs drivers.
Questions we are asked
How long does negotiating limitation of liability take in practice?
Typically two to six weeks across two to four rounds of exchange. A file with several linked contracts, or a claim already raised, extends both the number of rounds and the total time.
Which documents are needed to start?
The current draft, any prior correspondence on the clause, a list of every related contract that shares the same relationship, and confirmation of which law governs each of them.
What happens if the other side does not respond?
The file lead sets a follow-up date. If that date passes without a substantive reply, the matter is escalated to the partner, and the point of no return moves accordingly.