Termination and wind-down: documents to prepare
Terminating an intellectual property licence and winding the arrangement down calls for four groups of documents: the termination notice itself, an audit of use to date, a schedule of assets to return or destroy, and a mutual release. Assemble all four before the notice goes out, not after the clock has already started running.
What changes once notice is served
Once notice is served, the right to use the licensed material narrows immediately or after a cure period, depending on the trigger relied on. Deliverables, source files, and confidential information become due for return on a fixed date set either by the agreement or by the notice itself. Any sub-licences granted under the terminated agreement need their own wind-down, on their own separate schedule.
Royalty or fee accounting does not stop automatically the day notice lands. Payments already earned before that date usually remain owed, and a final statement is normally required before the file can close. Confidentiality and indemnity clauses typically survive termination on their own terms, independent of the licence they came from.
Operationally, access to shared systems, repositories, and data feeds should be revoked on the same date the licence stops, not before and not after. A gap in either direction is one of the most common sources of later disputes about whether use continued past termination.
Documents to prepare, stage by stage
| Stage | Document | Usually prepared by | Typical timing |
|---|---|---|---|
| Before notice | Audit of use and inventory of licensed material | Licensee, checked by licensor | One to two weeks before notice |
| Notice | Termination notice stating the trigger and any cure period | The terminating party | Day zero |
| Cure period | Response or remedy plan, where a cure is available under the agreement | The receiving party | Within the period the agreement sets |
| Wind-down | Return or destruction certificate for materials and confidential information | Licensee | Within the agreed wind-down window |
| Wind-down | Notice to sub-licensees and, where data processing is involved, to Subprocessors, including local delivery partners overview and what to | Licensee, acting as sub-licensor | Alongside its own wind-down |
| Closing | Mutual release and final accounting of sums due either way | Both parties | After return or destruction is confirmed |
What to do
- Pull the complete licence file: the main agreement, amendments, and any side letters that touch termination or wind-down.
- Identify the trigger — expiry, breach, insolvency, or termination for convenience — since it decides whether a cure period applies at all.
- Draft the notice in the exact form the agreement requires: address, delivery method, and language, because a defective notice can reset the clock.
- Inventory everything covered by the licence, including code, know-how, brand assets, and data sets, and confirm which sub-licences currently exist.
- Build a wind-down calendar covering the cure period, return deadlines, and any transition support the licensor still owes.
- Close the file with a signed release and a final accounting, before archiving the correspondence and delivery receipts.
Where the licence covers commissioned work rather than a pre-existing right, check separately how ownership of the underlying output was structured. What changed in time limits ownership of results can shift which return obligations actually apply to that output.
Who decides
The terminating party decides, in the first instance, whether the trigger has occurred and whether notice is valid. That reading is not final. If the other side disputes it, the agreement's own dispute resolution clause decides where the disagreement is heard, and on what timetable. Where the agreement is silent on this point, the ordinary courts of the seat named in the agreement take the question instead.
Evidence gathered during the pre-notice audit tends to matter most once a dispute starts, including any record built while checking Proof of use. Keep that record separate from the notice file, and keep it complete even if the other side never challenges the trigger.
Forks
If the licence has already expired on its own terms, no termination notice is needed at all. Wind-down documents alone are enough, since there is no trigger left to prove.
If the other side stays silent through the entire cure period, treat the deadline as passed once it lapses. Move to wind-down steps as if the cure had failed, while keeping proof that the notice was delivered and received.
If sub-licences exist, wind them down on a schedule that finishes before or together with the head licence, never after. A sub-licensee cannot hold rights the head licensee no longer has.
If the licence was granted as a one-off, fully paid arrangement with no ongoing obligations, wind-down may consist of little more than a return certificate, since there is no royalty stream to close out.
What this page does not cover
This page does not value damages arising from breach, does not set insolvency-specific triggers, and does not fix the notice format required in every jurisdiction a group operates in. It also does not cover tax treatment of any final settlement payment, which depends on facts outside the licence file itself.
Where the licence sits alongside an assignment or a novation of the same rights, prepare that file separately. See Assignment and novation step by step for the documents that transfer, rather than terminate, a right.
Verified
Checked against the licence agreement itself, the notice already served, and the parties' internal registers of licensed assets. State on 12 March 2025.
FAQ
How long does termination and wind-down take in practice?
Simple licences with no sub-licences and a short cure period usually close within a few weeks once that period runs out. Licences covering software, shared data, or several sub-licensees typically take one to three months, mostly because of return and destruction logistics rather than the notice itself.
Which documents are needed to start?
An audit of use, the complete licence file, and a draft notice matching the contractual delivery method. Without these three in hand, the notice date is difficult to defend later if the trigger is ever disputed.
What happens if the other side does not respond?
Treat the contractual deadline as final once it passes, keep proof of delivery and receipt, and move to the wind-down steps unilaterally. Silence during the cure period does not extend it on its own, and does not require a second notice.
One adjacent situation comes up often once termination starts: a licensed right that was also pledged as security. See When a right is pledged on-chain in practice if that applies here.
Another comes up when a related patent family is still open for filing decisions. See The opt-out window is closing on a family patent if that is the case in this file.