Confirming what the default rule gives the employer: what the decision maker looks at
When code, designs or data are created by an employee, the default rule usually gives the employer ownership without a separate assignment. Confirming that this default applies is a fact-finding exercise, not a negotiation. A decision maker checks the employment relationship, the scope of duties and the timing of creation before treating the output as company property, and the check stands or falls on those three points alone.
What decides the default
The default allocation of rights in work made during employment follows the applicable intellectual property and labour framework of the jurisdiction where the work is performed. A decision maker does not start from the content of the code or the design. It starts from the employment contract, the job description and the instructions given at the time the work was produced.
Three questions carry the case. Was the person an employee, not a contractor, at the moment of creation? Was the work part of the tasks assigned, or a side project outside the role? Did the employer give any instruction, tooling or brief that shaped the result? A positive answer to the first two questions, and the default rule usually stands without further argument.
Evidence of timing matters as much as evidence of role. A commit log, a design file's metadata or a project tracker entry showing when the work was produced often settles a question that memory alone cannot answer months later.
What changes in practice
Confirming the default removes the need for a separate assignment clause for that specific output. It shortens the chain of title an investor or acquirer will check later. It also narrows the risk of a former employee claiming co-authorship after the relationship ends.
The timing of the check matters more than its complexity. A confirmation done while the employment record is fresh and colleagues are still reachable takes little effort. The same check attempted years later, after staff turnover, becomes a search for missing paperwork rather than a review of existing evidence.
If you are also reviewing a technology contract that stays silent on AI-generated output, the timing question carries a comparable weight to the one described here — see The contract is silent on AI output technology contract.
What to do
- HR or the line manager pulls the employment contract and the job description in force at the time the work was created.
- The legal team lists the specific outputs to be confirmed as employer property — a code repository, a design file, a dataset.
- The line manager confirms in writing that the work fell within the assigned tasks, not a side project pursued independently.
- Legal checks whether any instruction, brief or tooling from the employer shaped the output, and notes the source of that instruction.
- Legal drafts a short internal memorandum recording the confirmation, the evidence relied on and the date of the check.
- The memorandum is filed with the personnel record and referenced in any later due diligence file or transaction data room.
None of these steps requires the employee's signature. The confirmation is an internal record, not an agreement that needs counter-signing.
Who decides and how long
Internally, the confirmation is a legal and HR sign-off, not a court decision. It only reaches a tribunal or a court if a former employee later disputes the classification of a specific output.
| Stage | Who acts | Typical timing |
|---|---|---|
| Gather employment records | HR | 1–3 working days |
| Classify the output against the role | Line manager and legal | 2–5 working days |
| Draft and file the confirmation memorandum | Legal | 1–2 working days |
| Dispute, if raised | Labour tribunal or competent court | Depends on the forum's own calendar |
Most files close at the third row. The fourth row applies only where a former employee formally objects, which is uncommon once the memorandum is filed promptly.
Forks
If the employee worked partly on a personal device outside working hours, the confirmation needs a clearer link to the assigned tasks before it can stand alone.
If a contractor was involved alongside the employee, the default rule for employees does not extend to that contractor's share, and a separate contractual step is needed to cover it.
If the output involves a token distributed to users rather than software or a design file, the ownership question is replaced by a different timing question entirely — see The deadline that matters in this situation.
Where this stops
This page confirms that the default rule applies to a specific output. It does not draft an assignment clause, and it does not value the intellectual property once ownership is settled. Valuation and asset mapping belong to a separate exercise, closer to the work behind Asset in Lithuania: sources, route and limits.
It also does not chase a counterparty who disputes the classification or who owes money connected to the same project. That sits closer to the file described in Debtor in Czechia explained.
Related reading
Where the parties want a different split from the default, the contractual route is covered separately — see Drafting the contractual override ownership of results what the.
Verified
This overview reflects the internal procedure as applied at the time of the last review shown on the site. The steps described are procedural and do not depend on citing a specific statutory provision; where a dispute reaches a tribunal or a court, the applicable framework for that forum is confirmed at that stage by the counsel handling the matter.
If your file involves several outputs, several jurisdictions, or a former employee who already objects, a short call with our team narrows the next step within minutes during business hours. A price for the work follows within one business day.
FAQ
How long does confirming what the default rule gives the employer take in practice?
Where the employment records are complete, the internal confirmation takes about a week from the first request to the filed memorandum. Missing records, or a former employee who cannot be reached for a clarifying question, extend this materially.
Which documents are needed to start?
The employment contract in force at the time of creation, the job description, any written instructions or briefs connected to the specific output, and a list identifying exactly which code, design or dataset is being confirmed.
What happens if the other side does not respond?
Silence from a former employee does not block the internal confirmation. The employer proceeds on the record it holds. If the former employee later disputes the classification, the matter moves to a tribunal or a court, and the internal memorandum becomes part of the evidence considered there.