IP indemnity negotiation: stages and deadlines
IP indemnity negotiation in a technology contract runs through four stages: position exchange, drafting of carve-outs, escalation of unresolved points, and sign-off. Each stage carries a deadline set by the deal timeline, not by statute. A negotiation of this kind typically closes within two to six weeks, depending on how many points survive the first exchange, and on how fast each side can confirm the origin of the technology involved.
What sets the pace
The pace depends less on the length of the clause than on how quickly each side can trace the origin of the technology it is indemnifying. A vendor using open-source components, licensed datasets, or tokenised assets needs to confirm provenance before it can accept an indemnity without qualification. A comparable provenance question, resolved in an adjacent context, is described in Metadata standards in tokenised rights and the deadline.
Once provenance is confirmed, the clause itself moves fast. Most delay sits in the confirmation step, not in the drafting. A component that turns out to be unlicensed, or a dataset with an unclear chain of title, can stall an otherwise agreed clause for a week or longer. Teams that gather this information before the first markup, rather than in response to a query from the other side, consistently move through the remaining stages faster.
Stages and typical duration
| Stage | Typical duration | Who acts |
|---|---|---|
| Position exchange | 2–5 business days | Commercial lead on each side |
| Provenance confirmation | 3–10 business days | Technical team, supported by counsel |
| Carve-out drafting | 2–4 business days per round | Drafting counsel |
| Escalation, if needed | 1–2 weeks | Senior decision-maker on each side |
| Sign-off | Same day once terms are agreed | Signatory with authority to bind |
The table reflects a typical file, not a fixed schedule. A deal with a hard closing date compresses every row. A deal without one lets the provenance step run long, sometimes past the point where the rest of the contract is otherwise ready.
What to do
- Ask the drafting team to list every claim category the clause is meant to cover, and every category it excludes, before the first markup goes out.
- Request the counterparty's component inventory before drafting starts, not after a dispute over scope has already begun.
- Set a response deadline in the cover email, and repeat that deadline inside the markup itself, not only in correspondence.
- Route any request for a cap or an exclusion straight to the person who owns the commercial risk, not to the drafting team handling the wording.
- Record the date each side proposed a clause and the date it accepted one, as two separate entries in the file.
Who decides and when
The wording of the clause is agreed by drafting counsel on each side. The cap, the exclusions, and any carve-out for a known third-party claim are decided by whoever owns the commercial risk: the business sponsor on the customer side, and the head of legal or the chief technology officer on the vendor side. Escalation, when it happens, goes to that person directly, not to a more senior lawyer on the same file.
A markup that sits with a junior drafter for more than a few days has usually stalled at the wrong desk. Moving it to the risk owner, rather than redrafting it again, is the faster route in almost every case observed on live files.
Common forks
If the counterparty refuses any cap on the indemnity, the negotiation has moved from a drafting exercise to a risk allocation discussion, and it should be escalated early rather than redrafted repeatedly around the same disagreement.
If the technology includes an unlicensed or unclear third-party component, the indemnity cannot be finalised until that component is replaced, properly licensed, or explicitly carved out of the clause. Redrafting the wording around an unresolved component wastes a full round.
If the deal carries a fixed closing date, the parties usually agree a narrower indemnity now and a side letter to widen it later, rather than let one clause block the whole signature.
Where this stops
This page describes how the negotiation runs, not how a specific clause should read for a specific deal. It does not set a cap, a carve-out list, or a figure for any particular file, because those depend on the components, the counterparty, and the commercial terms of that deal alone.
A file with an existing counterparty history benefits from a check before the next renewal round rather than a fresh negotiation from scratch; see Counterparty report before renewing a contract for how that check is structured.
For a view of what a finished file looks like once the clause is agreed and the record is closed, see Sample document report, as delivered and its limits.
Related reading
A markup that reaches the security annex stage raises a related question about who reviews it and what a reviewer actually checks; see Contract review against a security annex: what the decision.
Verified
This description reflects negotiation practice observed on live technology contract files, not a published deadline, because no regulator sets one for a privately negotiated indemnity clause. Records generated during a file review, including drafts and correspondence, are handled under the terms set out in Privacy notice overview and the evidence.
FAQ
How long does IP indemnity negotiation take in practice?
Most files close within two to six weeks of the first markup going out. Provenance confirmation, not the drafting itself, is the step most likely to stretch that window.
Which documents are needed to start?
The current contract draft, a list of the third-party and open-source components used in the technology, and any prior indemnity clause from an earlier version of the same relationship, if one exists.
What happens if the other side does not respond?
A markup without a response by the stated deadline should be followed by one reminder. If that reminder also goes unanswered, escalate to the counterparty's business sponsor rather than repeating the request to the same drafting contact.