Evidence of creation and dates: stages and deadlines
Evidence of creation and dates proves who produced a specific version of code, a design, or a dataset, and when it existed. The procedure runs through four stages: contemporaneous logging, independent timestamping, secure storage, and retrieval once a dispute starts. Skipping an early stage cannot be repaired later; retroactive timestamps carry little weight.
Practical consequence
A gap in the record does not disappear once negotiations start. Courts and arbitral panels weigh contemporaneous entries far more heavily than a reconstruction produced after a dispute is announced. A missing timestamp at the drafting stage cannot be manufactured later, however detailed the explanation. The practical effect is that the strength of your position is fixed months, sometimes years, before the dispute becomes visible.
This is why the procedure below has no natural late-stage fix. Each stage either happens on time or the record stays weaker than it needed to be.
Stages and deadlines
| Stage | What happens | Practical deadline |
|---|---|---|
| Contemporaneous logging | The author records the work item in a version-controlled system with a timestamp | Same day as creation |
| Independent timestamping | A neutral system or third party stamps the file hash | Before the file leaves the team |
| Secure storage | Logs and hashes are archived under a fixed retention policy | Set by internal policy, typically several years |
| Retrieval on dispute | The records owner pulls the relevant entries and hash values | Within the timeframe set by the forum handling the dispute |
What to do
- The records owner nominates a single person responsible for logging creation events as they happen.
- The engineering or design lead routes drafts through a version-control or document-management system that records author, time, and file hash automatically.
- The records owner deposits milestone versions with a neutral timestamping service or a notary at agreed points in the project.
- The legal or compliance team fixes a retention period for logs, metadata, and correspondence, and stores them apart from working files.
- The contracting manager briefs external contributors on the logging procedure before work starts, not after a dispute appears.
- The records owner checks the log for gaps at each milestone, while the gap is still fixable.
The same discipline extends to access control. A contributor who loses control of their credentials creates a gap in the record that looks identical to fabrication, a scenario addressed in An integration partner leaks credentials technology contract who decid.
Who decides
Internally, the records owner decides what counts as a contemporaneous entry and enforces the logging procedure day to day. No single external authority certifies dates in advance. If the matter reaches a dispute, the forum handling it — a court, an arbitral tribunal, or a mediator appointed under the contract — assesses the weight of the record, not the software used to build it. No fixed calendar deadline governs the logging stage itself. The only deadlines that apply are contractual delivery dates and the procedural deadlines set once a dispute is formally opened.
Branches
If your team already uses version control with signed commits, the backbone of a provenance record already exists. Add timestamping at agreed milestones and the file is complete.
If contributors work outside your core systems — freelancers, agencies, short-term contractors — add a check-in step before payment is released, so the record does not depend on their own tools.
If your provenance chain touches a tokenised record of ownership, distribution control becomes a separate question once a partner is involved, addressed in When a partner distributes the token: who decides and.
If a dispute has already started, retroactive timestamping does not help. Focus on collecting what already exists rather than generating new records under pressure.
Limits
This page describes the evidentiary record only. It does not set a statutory retention period, because retention rules vary by document type and are not listed here. It does not decide who owns the result once creation is proven — that question sits on a separate page.
It does not price a review of an existing record. Where the question is whether a specific asset's records still hold up, a related check is described in Asset report when maintenance is in doubt and its.
Where the dispute has already reached the enforcement stage, a further step is described in Debtor report before starting enforcement in detail.
Verified
Last reviewed: 4 March 2025. This page sets out a working procedure and does not rely on a specific statutory citation, in line with the scope of a procedural page. Where a dispute requires a jurisdiction-specific rule, that rule is checked separately once the dispute is opened.
Related reading
See also Transfer of results on termination ownership of results.
FAQ
How long does evidence of creation and dates take in practice?
Setting up the logging habit takes a day. Building a full provenance record for an existing project usually takes two to six weeks, depending on how many repositories and contributors are involved.
Which documents are needed to start?
You need the current file inventory, a list of contributors with their access levels, and whatever timestamps or version history already exist. Contracts with contributors help but are not required to start.
What happens if the other side does not respond?
The record continues to build regardless of the other side. Silence does not weaken your position; it simply means the dispute has not yet been formally opened.
If you are setting this procedure up for the first time, or checking whether an existing record would hold up, get in touch and describe where your project stands today.