Transfer of results on termination: what the decision maker looks at
When a contract ends, code, designs and data do not move to the other side automatically. Someone has to check who owns what, whether a transfer clause exists, and whether the other side actually delivered what the contract describes. The decision maker — usually a manager, a court, or an arbitrator, depending on the stage — looks at three things: the paper trail, the state of delivery, and whether a deadline has already started running.
What changes once termination is triggered
Termination does not erase prior obligations. It starts a clock. From the date of notice, most contracts set a window for handing over source files, design assets or datasets, and for confirming that no copies remain with the departing party. Missing that window does not cancel the obligation. It usually shifts the dispute from a contractual request to a claim for non-performance, which takes longer and costs more to resolve.
The risk grows if results were never clearly separated from the wider project. A shared repository or a joint dataset makes the handover slower, because someone has to decide which parts belong to which side before anything can move.
What to do
- Identify the results in scope. The requesting party lists what should transfer: files, formats, versions, and any accompanying documentation.
- Check the transfer clause. The legal or contracts team confirms whether the agreement already assigns ownership on termination, or only grants a licence that ends with the contract.
- Send a formal handover request. The requesting party issues a written notice with a deadline for delivery, referencing the termination date.
- Collect proof of delivery. Both sides keep a record of what was sent, in what format, and when.
- Confirm deletion of retained copies. The delivering party confirms, in writing, that no working copies remain outside the agreed archive.
- Escalate only if the deadline passes. If nothing is delivered, the matter moves to a decision maker for a ruling on non-performance.
Who decides, and on what timeline
| Stage | Decision maker | Typical timeframe |
|---|---|---|
| Initial handover request | Contract manager on each side | Set by the notice, commonly 5–15 business days |
| Dispute over ownership of a specific file | Internal legal team, then mediator if unresolved | Weeks, depending on how many files are contested |
| Formal non-performance claim | Court or arbitral tribunal named in the contract | Months, driven by the forum's own docket |
The table shows escalation, not obligation. Most transfers close at the first stage. The second and third stages exist for cases where the other side disputes what belongs to whom, or simply does not answer.
Forks: how the path changes depending on your situation
If the contract already names a transfer clause and both sides agree on scope, the handover is administrative. Files move, deletion is confirmed, and the file closes without a decision maker ever being involved.
If the contract is silent on transfer and results sit inside shared infrastructure, the timing question becomes central. A comparable question arises when A hosting provider changes region technology contract the deadline starts running before either side notices — the clock does not wait for agreement on scope.
If the other side disputes ownership of specific files, the file moves to a decision maker, and the outcome depends on documentation created before the dispute, not after. The deadline that matters in this situation follows the same logic in a different setting: whoever holds the clearer paper trail at the point the clock starts controls the outcome.
What this page does not decide
This page describes the procedure and the sequence of checks. It does not establish who owns a specific set of results in your contract, and it does not calculate a deadline for your jurisdiction. Ownership depends on the wording of your agreement and on facts specific to your file. If you need a jurisdiction-specific factual layer to support that assessment, see Asset in Latvia: what can be established, and for a debtor-side check, see Debtor in Denmark explained. Neither report replaces legal advice on your contract; both give you the underlying factual record faster than requesting it manually.
Reviewed
This page was reviewed for accuracy of process description, not for statutory citation. As a procedural explainer, it names no article, regulation or national act, because the underlying registry entry for national implementation is not yet complete on our side. Where a specific reference is needed for your file, our team supplies it directly, checked against the current national text.
Related reading
A closely related question is what happens when a transfer already occurred informally and needs formal confirmation later. See Assignment ratification after the fact: what the decision maker for how a decision maker treats a transfer that was never properly documented at the time.
FAQ
How long does transfer of results on termination take in practice?
A clean handover with no dispute usually closes within the notice period, often two to three weeks. A contested handover that reaches a decision maker takes longer, and the timeline then depends on the forum, not on the transfer itself.
Which documents are needed to start?
The termination notice, the original contract or its relevant clauses, a list of the specific results in scope, and any prior correspondence about ownership or access. Without these, the decision maker has nothing to check the claim against.
What happens if the other side does not respond?
Silence after a formal handover request with a stated deadline typically converts the matter into a non-performance claim. At that point the requesting party moves from an administrative request to a formal escalation, with the decision maker named in the contract, or a court where none is named.