Transfer of results on termination: stages and deadlines
When the contract that created the right to results ends, transfer does not stop automatically. It moves through a fixed sequence: notice, inventory, hand-over of files, and confirmation of receipt. Each stage has its own deadline. Missing the deadline for the hand-over stage is the point after which the original holder can no longer be compelled to cooperate.
What changes once the contract is over
Before termination, the party that created the results usually has a standing duty to keep files organised and to respond to requests. That duty does not survive the contract by default. Once the termination date passes, cooperation becomes voluntary unless the termination clause or a separate letter fixes a further window.
This shift matters for timing. A request sent one day before termination sits inside an enforceable duty. The same request sent one day after termination sits inside goodwill only. Practically, this means the notice stage should start before the contract ends, not after.
The risk is not that the right disappears. The risk is that the practical means of exercising it — source files, design assets, data sets, credentials — become harder to obtain with each week of delay, and the other side has fewer reasons to answer quickly.
Stages, in the order they normally happen
| Stage | What happens | Typical deadline | Who acts |
|---|---|---|---|
| Notice of termination and transfer | The party ending the contract states, in writing, that a transfer of results is due | Sent alongside or before the termination notice | The party terminating the contract |
| Inventory of results | Both sides list what exists: code, designs, data, documentation, credentials | Within days of the notice | The party that holds the results |
| Hand-over of files and access | Files, repositories, and access rights are transferred or re-issued | Set by the notice or by prior agreement | The party that holds the results |
| Confirmation of receipt | The receiving party confirms in writing what arrived and what did not | Shortly after hand-over | The receiving party |
| Escalation, if needed | A follow-up letter, then a formal demand, then a claim | Only if earlier stages stall | The receiving party |
What to do
- Send the transfer notice before or at the same time as the termination notice, not after.
- List every item expected: repositories, design files, data exports, keys, and passwords.
- Set a short, stated deadline for hand-over inside the notice itself.
- Confirm receipt in writing, item by item, rather than with a general acknowledgement.
- Keep every message dated — the dates carry the case if hand-over stalls.
- Escalate on the day the stated deadline passes, not weeks later.
Who decides
At the notice and inventory stages, nobody decides anything — the parties simply exchange documents. A decision-maker only appears once one side stops responding. At that point the matter moves to whoever the contract names for disputes: usually a court or an arbitral forum stated in the same contract. Absent a forum clause, the forum follows the seat of the party that must comply, and the applicable deadline for a formal claim follows that forum's own rules, not the contract's internal deadlines.
A related fork is what happens when the contract itself was already running past its expected life before termination, as in The contract term outlives the product technology contract who decides and when — the same escalation path applies, but the starting point for deadlines shifts.
Forks
If the other side hands over files within the stated deadline, the matter closes with the confirmation of receipt — no further step is needed.
If the other side responds but the hand-over is partial, the receiving party should send a second, itemised list naming only the missing pieces, with a new short deadline attached.
If the other side stops responding entirely, the matter moves to a formal demand letter, and from there to the escalation forum named in the contract or, if none is named, to the ordinary forum for the party in default.
How the file is structured
A transfer file is built stage by stage, not written after the fact. The notice sits at the top, followed by the inventory, then every hand-over message with its date, then the confirmation or its absence. A file assembled this way shows, at a glance, which stage stalled and on which date — which is what a forum or an opposing counsel will ask for first.
Where a transfer runs alongside a token issue that was interrupted mid-sale, the sequencing question is close but not identical — see When the issue is paused mid-sale: who decides and when a different set of stages applies.
Limits
This page does not set the price of preparing or reviewing such a file. It does not state a fixed number of days for any specific jurisdiction, because that figure depends on the forum named in the contract and on national procedural rules that sit outside this page. It also does not cover disputes over whether a result was created under the contract at all — that question belongs to a separate procedure.
Sources and limits
This procedure is checked against internal file templates and correspondence logs, not against statutory text, because a procedural page of this kind carries no article or act references by design. Where a transfer stalls because an assignment record is missing rather than because a party refuses to answer, the closer template is Asset report when an assignment is missing and its record trail. For a worked illustration of a completed file, see the Sample debtor report, as delivered in detail.
Verified: 12 March 2024.
FAQ
How long does transfer of results on termination take in practice?
There is no fixed figure. A clean transfer with full cooperation closes within days of the notice. A stalled one runs to weeks once escalation starts, and further once a forum becomes involved.
Which documents are needed to start?
The termination notice, an inventory of results, and a list of access points — repositories, exports, credentials. Without an inventory, hand-over cannot be checked against anything.
What happens if the other side does not respond?
A follow-up message with a new short deadline, then a formal demand letter, then a claim before the forum named in the contract or, absent that, the ordinary forum for the party in default.
Related publications
A closely related procedure covers a different starting point — where consent for a past act was never formal to begin with: Assignment ratification after the fact ownership of results.
For the wider set of questions on who holds rights in created work, start from Ownership of results.