Confirming what the default rule gives the employer: documents to prepare
When software, designs or data are produced by staff, the default position usually leaves ownership with the employer without a separate assignment. Confirming that position on paper is a different task from creating it. This page sets out the file a company assembles to prove, to a buyer or an investor, that the default rule already did its job.
Why the confirmation matters once it is questioned
The default rule works automatically at the moment the work is created. Nobody signs anything for it to apply. The difficulty appears later, when a due diligence team, a licensing partner or a customer asks for proof. Without a file, the company is arguing from memory. With a file, the same conversation takes an afternoon rather than a week.
When ownership documentation is thin, a customer notices. A customer demands unlimited liability technology contract when the other side moved the negotiation from ownership terms to liability terms, which is a common reaction to an unclear paper trail. Preparing the file before that conversation starts removes the reason for it.
Documents to prepare
| Stage | Document | Typical timing |
|---|---|---|
| Confirm employment status | Signed employment contract and job description on file | Same day, from the HR archive |
| Confirm the work sat within scope of duties | Task assignments, project logs, version history, time records | 1–3 business days to compile |
| Rule out prior rights | Records of any freelance or consultancy work performed before the hire date | 1–2 business days |
| Summarise the position | Internal memorandum signed by HR and legal, stating which items fall under the default rule | 2–3 business days after the inputs above are collected |
| Store and index | File held in the internal IP register, cross-referenced to the relevant project | Ongoing from that point |
Steps to build the file
- HR pulls the employment contract and job description for each contributor named on the project.
- The project lead lists the tasks that produced the code, design or dataset in question.
- Legal checks whether any contributor did related work before employment started, and flags gaps separately.
- HR and legal sign a short memorandum stating that the listed items fall within scope of duties.
- The company files the memorandum and its supporting records in the internal IP register.
- The register entry is reviewed whenever the underlying project changes ownership, licensing terms or team composition.
Who reviews and signs off
No external authority approves this file by default. The confirmation is an internal act: HR checks the employment facts, legal checks scope of duties, and a signing manager takes responsibility for the memorandum. An outside body becomes involved only once the position is disputed, and then a court or an arbitral tribunal decides on the facts each side puts forward.
When the file needs an outside legal opinion before a transaction, a partner responds within minutes during business hours, and the fee for that review is confirmed within one business day.
Where the default rule stops holding
The default rule assumes an employee, working within scope, with no earlier contract that says otherwise. A few situations move outside that assumption.
If the contributor was a contractor rather than an employee, the default rule for employees never reached them, and ownership has to be settled by a separate agreement rather than by this file.
If the same output later feeds into a public disclosure, such as a token offering built on the underlying code, the ownership file becomes an input to a separate document, not a substitute for it. That separate procedure is covered here: How update of the offering document token issuance runs.
If the work was produced before the current employment started, or across two group entities in different countries, the memorandum should say so explicitly rather than assume continuity.
What this page does not cover
This page confirms an existing position inside one company. It does not run a jurisdiction-specific check on a target company's assets. For what a search can establish in one jurisdiction, see Asset in Ireland: what can be established.
It also does not track a counterparty's solvency once a deal is signed. For monitoring a counterparty once insolvency signals appear, see Debtor report when insolvency signals appear in practice.
Verified
Reviewed for procedural accuracy on the date this page was last published. The material describes an internal confirmation procedure and does not cite a statutory reference. Where a dispute requires a statutory basis, that basis is added case by case and sits outside the scope of this page.
Related reading
For the situations where the default rule does not apply at all, see Drafting the contractual override: documents to prepare.
FAQ
How long does confirming what the default rule gives the employer take in practice?
Collecting the underlying records usually takes three to five business days once HR and legal are both engaged. Larger teams or older projects extend that mainly at the scope-of-duties step.
Which documents are needed to start?
Start with the employment contract, the job description and a list of the tasks that produced the output. Everything else in the file builds on those three items.
What happens if the other side does not respond?
If a former contributor is asked to confirm dates or tasks and does not respond, the default rule still applies on the facts already on file. The gap is noted in the memorandum rather than left unrecorded, so a later reviewer sees why one input is missing.