IP indemnity negotiation: documents to prepare
Preparing for an IP indemnity negotiation means assembling five items before the first call: the underlying licence or supply agreement, a technical description of the software or dataset, prior IP clearance records, the counterparty's standard indemnity wording, and an internal note on your fallback position. Missing any one of these adds roughly a week to preparation and weakens the first draft you send.
Why the documents come first
An indemnity clause protects one party if a third party claims that the licensed technology infringes its rights. Negotiating this clause without the underlying documents means guessing at scope, at exclusions, and at the cap. Each guess turns into a redraft cycle later, and each cycle adds days to a process that otherwise closes within two to three weeks when the file is complete from the start.
The risk is not only delay. A negotiation opened without a clear ownership chain behind the technology can expose one side to a claim it did not expect. This mirrors a situation we cover elsewhere in a different context: When the buyer of a token is not the rights owner, the indemnity the buyer thought it held turns out to be worthless once tested. The same logic applies to software components and datasets inside a technology contract: an indemnity is only as strong as the ownership behind it.
Documents to prepare
| Document | Purpose in the negotiation | Who provides it |
|---|---|---|
| Underlying licence or supply agreement | Defines what is licensed and by whom | Contract manager |
| Technical description of the software or dataset | Sets the scope the indemnity must cover | Product or engineering lead |
| Prior IP clearance records | Shows whether third-party components were already checked | IP counsel or vendor |
| Counterparty's standard indemnity wording | Starting point for redlines | Counterparty's legal team |
| Internal fallback note | Sets the floor and ceiling the team will accept | Negotiating team lead |
Steps to prepare
- Assemble the five documents above before scheduling the first negotiation session. The contract manager owns this step and confirms completeness in writing to the rest of the team.
- Ask the counterparty in writing to confirm which components of the technology are licensed from a third party rather than owned outright. The negotiating team lead sends this request, not the business owner.
- Map every third-party component against the clearance records held on file. IP counsel completes this step; a general contract reviewer usually lacks the reference material to do it correctly.
- Draft a one-page fallback position stating the minimum cap and the exclusions the team will accept before it stops negotiating. Circulate this note internally before the first exchange of drafts, not after.
- Set a response deadline for each round of drafts, typically five business days, and record the deadline in a negotiation log rather than in email threads alone.
- Retain every version circulated, with dates and reviewer initials attached to each. Retention: the report, the extracts and our copy explains how file copies are kept once a matter closes and what a client can request later.
Who decides and how
Inside most organisations, the general counsel or head of legal signs off on the indemnity cap and the exclusions before a draft leaves the building. The negotiating team proposes a position; it does not set the ceiling alone. On the counterparty's side, an equivalent function usually applies, which is why the fallback note matters on your own side first: it tells your team where the conversation stops before pressure builds.
If the parties cannot agree on the cap, the contract's own dispute resolution clause sets the forum for what happens next. Most technology contracts route disagreement into a conversation between senior representatives first, with a fixed number of days before either side may escalate further. That number lives in the contract itself, not on this page, and it varies between agreements.
Common forks
If a third-party claim already exists when negotiation opens, treat the file differently from a routine renewal: notify insurers where cover exists, and shorten every internal deadline set out in the steps above.
If the contract is a framework agreement covering several schedules, prepare separate clearance records for each schedule rather than one combined file. A single indemnity clause rarely fits every schedule without carve-outs specific to each one.
If the counterparty refuses to share its own indemnity precedent, treat the refusal as a signal rather than a blocker. Proceed with your own draft, and record the refusal in the internal file for reference if the negotiation later stalls.
Limits of this page
This page does not draft indemnity wording, and it does not set the amount of a cap. Both depend on the specific technology, the specific counterparty, and the exposure sitting behind the claim, none of which a general procedure page can price in advance. Where the counterparty sits outside the EU, the exposure changes again: Counterparty in United States and its limits in practice sets out what a background check can and cannot confirm before a negotiation opens.
Nor does this page resolve a mismatch between the dates on a licence and the dates on a public register, which surfaces more often than either side expects mid-negotiation. Document report when dates do not match the register covers the first steps once such a mismatch appears in the file.
Related publications
Contract review against a security annex: costs drivers covers a related preparation stage, where the security annex rather than the indemnity clause drives the cost of review.
Verified
Reviewed against our internal negotiation files and current preparation templates. No external register or court record applies directly to this procedure, since the steps above describe internal practice rather than a statutory process. The sequence reflects how technology contract negotiations run in files handled for clients operating through Lithuania and Estonia.
FAQ
How long does IP indemnity negotiation take in practice?
Two to three weeks when all five documents are ready at the start. Add roughly a week for every document missing at the outset, and longer still if a third-party claim is already active before talks begin.
Which documents are needed to start?
The underlying licence or supply agreement, a technical description of the software or dataset, prior clearance records, the counterparty's standard wording, and an internal fallback note. All five together, not a partial set, keep the first draft accurate and reduce redraft cycles later.
What happens if the other side does not respond?
Escalate through the contract's own dispute resolution clause once the deadline recorded in your negotiation log passes without a reply. Record the missed deadline in the file before escalating; it becomes relevant evidence if the matter later moves toward a formal dispute.