Ownership of results: code, designs and data: the decisions this practice answers
Ownership of results answers one question: who holds the rights to code, designs and data once a project ends. The answer decides whether a sale, a licence or a token offering can proceed, and whose signature is required to release the asset. It also decides whether a contractor, a former employee or a joint-venture partner can block a deal months after the work was finished. This hub sorts situations by the decision they answer, not by document type, because two files with the same clause can lead to opposite outcomes depending on the fact pattern behind them.
For the contract layer behind these situations, read Technology contracts and outsourcing overview.
For output tied to a tokenised asset, read the Token issuance and trading overview and its limits.
What falls under this practice
Ownership disputes surface in a small number of recurring forms. Each form points to a different question, and each question has a different starting document. A company that grew through outsourced development, internal teams and a later token issuance typically carries all four forms at once, often without realising it until a buyer's due diligence team asks for the paperwork.
| Situation | Core question | Typical trigger |
|---|---|---|
| Contractor-built code | Who owns the code once delivery is accepted | No written assignment clause |
| Employee-built code or designs | Whether employment alone transfers the rights | Cross-border team, mixed jurisdictions |
| Pooled or generated data | Who controls the dataset once it is compiled | Multiple contributors, no data-sharing agreement |
| Output tied to a token or ledger entry | Whether the token carries the underlying rights | Issuance without a rights-transfer clause |
Two established European frameworks sit behind several of these questions. Directive 2009/24/EC sets the baseline for computer program protection. Directive 96/9/EC does the same for databases. National implementing law then decides who holds the rights by default, which is why the same fact pattern can produce different answers in Lithuania and in Estonia, even for a team working on a single shared codebase.
What changes once ownership is unclear
An unclear chain of title blocks a sale, a licensing deal or a token offering until it is fixed. It also weakens a claim against a contractor who reuses the same code elsewhere, because the claimant first has to prove it owns what it is defending. The practical cost is time: due diligence stalls, and a buyer's counsel asks for the assignment paperwork that was never signed.
The same gap changes the negotiation, not only the timeline. A party that cannot show clean title accepts a lower price or a longer indemnity period, because the counterparty prices in the risk of a later claim from a contractor, a former partner or a co-developer.
In a funding round, the effect is sharper still. Investors' counsel treats an open ownership question as a condition to closing, and the round does not complete until it is resolved or carved out of the warranties.
Where clients usually start
Most requests begin at one of three points: a buyer's due diligence questionnaire, a contractor who has just made a claim, or an internal audit before a token issuance. Each entry point needs the same underlying record, built the same way.
- List every contributor to the code, design or dataset, including former contractors and short-term hires.
- Pull the underlying contracts and check for an assignment or licence clause.
- Mark every gap where no written transfer exists.
- Route each gap to the person who signed the original agreement, not to the developer who wrote the code.
- Keep the audit trail; it becomes the evidence base if a dispute follows.
Who resolves a dispute
Most ownership questions are settled by the parties themselves, once the contract is read correctly and the missing signature is identified. Where the parties disagree, the matter moves to the forum named in the contract, typically a national court or an agreed arbitration panel. This hub does not fix a single forum, because the answer depends on the contract in front of you and on where the parties are established.
Common branches
- If a contractor built the code without a written assignment, the linked situation guide covers first response, evidence and notice.
- If the output feeds into a token or a ledger record, check the issuance terms before assuming the token carries the underlying rights.
- If the dispute spans Lithuania and Estonia, treat it as two separate ownership questions, not one, because the default rule can differ between the two.
- If the code or dataset was built jointly with an external partner, check the collaboration agreement before assuming either side holds full title.
Sources and limits
This hub sets out the decisions, not the paperwork. It does not list deadlines, filing fees or the register where a claim gets recorded; those sit inside the specific situation pages linked here.
Before a dispute reaches a counterparty, a factual check often narrows the argument on both sides. An Asset report lithuania can confirm what a counterparty actually holds before a claim is drafted, which keeps the negotiation grounded in fact rather than assumption.
Where the dispute involves a debtor rather than a counterparty's assets, the equivalent check is a Debtor in Lithuania in practice report, useful when an unpaid contractor is the party asserting ownership.
Related situations
Start with When a contractor claims ownership of the code in the situation library if a contractor is the other side of the dispute.
Next step
Send the contract and a short note on what was built, by whom, and when. A partner reviews it and points to the situation page that matches your case, rather than to a generic checklist.
Verified
Primary sources for this hub: Directive 2009/24/EC; Directive 96/9/EC. National implementing law, filing deadlines and forum-specific detail are addressed on the linked situation and overview pages, not on this hub.
FAQ
What does this change in practice?
Once ownership is confirmed, a sale, a licence or a funding round can proceed without a title gap holding up due diligence. Until then, the buyer's counsel treats the code, design or dataset as unverified property, and prices the deal accordingly.
Which deadline applies?
No single deadline applies across every ownership question. The situation pages linked from this hub set out the deadline for each specific scenario, such as a contractor dispute or a joint-authorship claim.
What do you need from us to start?
The underlying contract, or, if none exists, a list of everyone who contributed code, designs or data, together with the dates each contribution was made and the entity each contributor worked for.
Vaidas Kudirka