Transfer of results on termination: documents to prepare
When a services or development contract ends, the party holding the results must hand over source files, a signed assignment confirmation, and a full inventory of deliverables before ownership formally passes. Preparing these documents before the notice period expires avoids disputes over what was created and who owns it. The handover usually takes two to six weeks.
What changes once termination is triggered
If the outgoing party delays the handover, the receiving party often loses working access to code, designs or datasets it needs for a live product. Continued use without a signed assignment pushes both sides into Negotiating limitation of liability after the fact, which is a harder conversation than settling the same terms before termination takes effect. The longer the gap between notice and handover, the more the file relies on memory rather than paper.
Silence from the other side does not stop the clock. Most contracts fix the termination date by notice, not by cooperation, so the receiving party should start preparing documents as soon as notice is served, not after the counterparty confirms it will cooperate.
Documents and stages
Four documents carry the transfer: an inventory of deliverables, a signed assignment confirmation, an export of source and design files with metadata, and a handover protocol that both sides sign. Each has one owner. Splitting ownership between departments is the most common cause of delay.
- Project lead compiles the inventory of deliverables against the contract's scope.
- Legal counsel drafts the assignment confirmation and circulates it for signature.
- Technical lead exports source repositories and design files with version metadata intact.
- Both parties sign the handover protocol, dated and referencing the inventory.
| Stage | Document | Prepared by | Typical timing |
|---|---|---|---|
| Inventory | Deliverables list | Project lead | Week 1 |
| Assignment | Assignment confirmation | Legal counsel | Week 1–2 |
| Export | Source and design files with metadata | Technical lead | Week 2–3 |
| Handover | Signed handover protocol | Both parties | Week 3–4 |
| Access transfer | Credentials transfer record | IT or hosting provider | Week 4 |
| Archiving | Signed document set | Compliance officer | Week 4–6 |
Where results include hosted keys, wallets or access credentials, the transfer follows the same logic as How custody arrangement review token issuance runs in practice: control passes only once both sides confirm receipt in writing, not the moment a password is emailed.
Who decides
The parties' appointed contract managers decide the handover schedule and confirm each stage in writing. Disagreement over what belongs in the inventory, or over whether an item counts as a deliverable, escalates to the forum named in the contract: internal escalation first, then arbitration or the courts if the parties cannot agree. There is no external registry that approves the transfer itself; it happens by agreement, documented on paper.
If you are in one of these situations
If the contract names an escrow agent, the agent releases materials only after both sides sign an acceptance notice, not on request from one side alone.
If the other side stops responding, send a formal notice with a fixed deadline and reference the default procedure agreed in the contract; most contracts allow the receiving party to complete the inventory unilaterally if the deadline passes.
If the deliverables include third-party licensed components, check licence compatibility before the handover protocol is signed, since a licence gap can block use of the transferred results even after ownership has passed.
What this page does not cover
This page covers the paperwork of transfer, not its value. Where the dispute is really about what the results are worth to a lender or a court, that question sits in Asset report austria, not in a handover protocol.
Where the other side is not just silent but insolvent, the risk shifts from documentation to recovery, and the relevant questions are answered in Debtor report before starting enforcement: what it costs to before any enforcement step is taken.
Sources and verification
This material describes a procedural sequence agreed between contracting parties, not a statutory obligation, so no article or regulation number is cited here. It was last checked for consistency with current administrative and court practice on 4 March 2025.
Related reading
A related handover scenario, where an assignment is confirmed only after the fact rather than at termination, is covered in Assignment ratification after the fact: documents to prepare.
FAQ
How long does transfer of results on termination take in practice?
Most transfers close in two to six weeks. Straightforward files with a single deliverable and a cooperative counterparty move faster; multiple jurisdictions or a non-responsive party add weeks.
Which documents are needed to start?
Start with the inventory of deliverables and the draft assignment confirmation. Everything else, including the export and the handover protocol, builds on those two documents.
What happens if the other side does not respond?
Send formal notice with a fixed deadline under the contract's default procedure. If the deadline passes without a response, the receiving party typically documents the inventory unilaterally and proceeds on that basis.