Evidence of creation and dates: what the decision maker looks at
A dispute over who wrote a piece of code, drew a design or assembled a dataset turns on evidence, not on assertion. The decision maker — an internal reviewer, a mediator or a court — reconstructs a timeline from documents, logs and testimony. The side with the earlier, more consistent record usually prevails. Nothing created after the dispute starts can rewrite that timeline.
What changes once the question is raised
Once a claim is raised, both sides lose the option to build new evidence retroactively. The claimant must show when the work first existed in a fixed, identifiable form. The respondent must show an earlier or independent origin, or a valid transfer of rights from the original author. Anything dated after the dispute became known carries far less weight, however genuine it is. This is why the file has to be assembled from what already exists, not from what can still be produced.
The decision maker weighs consistency across sources. A version-control log that matches an email timestamp, which in turn matches a deposit certificate, is harder to challenge than any single document standing alone. A gap in the chain is read against the party who left it.
What to do
- Preserve the version-control history the moment a dispute becomes likely. Do not edit, rename or "clean up" commit metadata — the IT lead exports the raw log, untouched.
- Secure email and messaging records with full headers, not screenshots. Counsel or IT exports the original files, including timestamps and sender data.
- Locate any deposit, escrow or timestamping service used at the time of creation. The account holder retrieves the certificate directly from the provider.
- Identify anyone who observed the work in progress. Ask each witness for a short, dated, written statement before memory fades.
- Assemble a single chronological file — dates first, source second. Hand it to a legal adviser before any contact with the other side.
Who decides and how long it takes
| Stage | Decision maker | What happens |
|---|---|---|
| Internal review | Line manager or an internal IP panel | Both accounts are compared against the existing file; often resolved without escalation |
| External challenge | Mediator or arbitration panel | Each side presents its timeline and supporting evidence; a written finding follows |
| Adjudication | Competent court | Evidence is tested formally; findings are binding unless appealed |
Most disputes never reach the third stage. The earlier the record is put in order, the more likely the matter is closed at the first or second stage.
Two common scenarios
If the disputed work is software code sitting inside a wider technology arrangement, the same timing question arises elsewhere in that contract. Personal data flows to a new subprocessor technology contract walks through a parallel deadline in that setting.
If the work sits inside a token issuance and the issuer is related to the platform, the same authorship-and-date logic applies before launch, not after. The deadline that matters in this situation covers that timing question in full.
Sources and limits
This page describes the procedure. It does not size the work needed to check a counterparty's standing before a dispute escalates, and it is not a substitute for a review of your own file. Asset in Estonia: sources, route and limits sets out what such a report contains and where its sources stop. Debtor in Finland explained does the same for a debtor profile. Neither replaces advice on the specific timeline of your case.
This page does not cover authorship rules for employed staff versus contractors, or the split between economic and moral rights. Those questions belong to a separate page in this cluster.
Verified
Reviewed 4 November 2025. This page sets out the procedural pattern used on evidence-of-creation questions. It does not cite specific statutes: procedural pages in this cluster stay free of article numbers by design, so a reader is not pointed to a reference that cannot be checked from this page alone. Statutory citation, where it applies, sits on the overview page for this practice area and its underlying pages.
Related publications
Related reading: Transfer of results on termination: what the decision maker looks at the mirror question — the moment the work must be handed back once a contract ends.
FAQ
How long does evidence of creation and dates take in practice?
Internal review is often resolved within weeks if the file is in order. External challenge and adjudication take longer, and the length depends on how complete each side's record is when the dispute starts.
Which documents are needed to start?
A version-control log, dated drafts, correspondence with full headers, any deposit or timestamp certificate, and written witness statements. The file is stronger when these sources point to the same dates independently.
What happens if the other side does not respond?
Silence does not resolve the dispute. The decision maker still expects a documented timeline from the party raising the claim, and a lack of response from the other side is usually read as a weaker position at the next stage.