Reading settings
Can I build useful IP evidence now for work developed in the past?
Published 9 November 2026
Yes. Earlier deliveries, correspondence, development records and records held by other parties can support a history assembled today. Connect each claim to the material that supports it and distinguish original records from later recollections. Timestamping the assembled package creates a verifiable record from now onward; it does not backdate the work or resolve missing ownership agreements.
An incomplete history can still contain useful evidence
Consider a fictional startup preparing for investment. Its founders say they developed a prototype two years ago, before the company was incorporated. They have the current design, some old drawings and an email exchange with a manufacturer, but no timestamp certificate from that period.
Those records may still support an earlier history. Examine which parts of the account they substantiate: what was sent to the manufacturer, which features were present, who contributed and how the work reached the company. These are separate questions, and the evidence may answer some more clearly than others.
This is particularly relevant to unregistered software, designs and know-how. A patent application or registration already provides an official record for its own contents and procedural dates; reconstructing development history is not a substitute for reviewing that record.
Connect an earlier event to identifiable material
A useful historical record connects a date or event to particular content. In the prototype example, an original email with an attached drawing may support that the drawing was sent at that stage. A reply discussing a feature can add context. A copy retained by the manufacturer may provide corroboration beyond the founder’s own files.
The strength of that connection depends on the records’ authenticity, completeness and provenance. Preserve the original message and attachment where available, and record who supplied them. A screenshot showing an email date but omitting the attachment gives the reviewer less to examine.
Compare what different records actually support:
| Record recovered | What it may help establish | What still needs connecting |
|---|---|---|
| Manufacturer’s email and attached drawing | A particular design was exchanged at that stage | Which features carried through to the current design |
| Prototype invoice and delivery record | A prototype was ordered or delivered | The specification or version used to make it |
| Repository history and release archive | Development steps and the contents of a release | The reliability of the dates and identities recorded |
| Earlier timestamp certificate with matching files | The dated existence and integrity of those files | Their contributors, ownership and relationship to the present asset |
Several records can support one another, but check whether they come from independent sources. Three documents repeating the same unsupported date do not provide three independent confirmations. For software, see whether Git commits are enough to document development.
Separate the earlier version from what exists today
Suppose the manufacturer’s copy shows the prototype’s housing, but the current design includes a mechanism added later. The earlier exchange may support the housing’s history. It does not establish that the later mechanism already existed.
Preserve both versions and describe the differences. Where the link is uncertain, say so: “This drawing documents the housing used in the first prototype; we have not located a dated record of the mechanism before the later release.” That is more informative than assigning the earliest date found to the entire current product.
The same applies to know-how. An old test report may document a result without recording the process that produced it. Identify what the report contains and what still depends on an explanation from the people involved. For practical ways to define the material, see how to identify the exact asset under review.
Use recollections to explain the records, with their limits visible
Ask contributors to explain their own role, the sequence of work and the records they recognise. Date their account when it is prepared. Have them distinguish what they remember directly from what they infer from documents, and identify any uncertainty.
For example, a founder may recognise a drawing as the version used in an early demonstration but be unable to recall its exact date. Their account can connect the drawing to that event; a calendar entry, attendee’s correspondence or demonstration photographs may help establish when it happened.
A signature helps attribute an account to its author; the statements still need to be assessed against the available records. Preserve differing accounts and investigate material disagreements rather than editing them into an artificially consistent history.
Timestamp the evidence you can assemble now
Once the historical material and explanatory account are organised, preserve and timestamp that package. This establishes a dated record of the files available at the new certification point and allows someone to check later whether the presented files match it. It is useful even when the events described are much older: future reviewers can examine the same preserved material, and later additions can be distinguished from this starting point.
The earlier dates remain supported by the historical records and their context. If the package contains a drawing described as being from two years ago, today’s timestamp does not independently establish that earlier date. If you recover an earlier certificate, keep it with its matching files and verify it separately.
Preserve the certified package unchanged, using working copies for annotations. Add newly recovered evidence as a further dated version. Different timestamping methods, including blockchain anchoring, can support this process; see what a digital timestamp establishes and what to preserve alongside a certificate.
Establish the company’s rights separately
Evidence that a founder developed the prototype before incorporation does not, by itself, show that the company now owns the relevant rights. The history needs to connect to the agreements or legal rules through which the company acquired them. WIPO’s guidance for investors and buyers distinguishes identifying the IP used by a business from demonstrating ownership or permission to use it.
If a transfer is missing, address it with the relevant parties and adviser. A new assignment may cover earlier work, but it should record the actual signing date and satisfy the applicable requirements. See how companies document rights to employee and contractor work.
For confidential know-how, distinguish the development history from the history of confidentiality measures too. Introducing access controls today does not establish who could access the material in the past.
In this example, the completed review might support different conclusions with different levels of confidence: an early drawing is corroborated by the manufacturer’s records, the later mechanism is documented only from a subsequent release, and the transfer to the company was completed during preparation for investment. Keeping those distinctions visible makes the evidence useful to a reviewer without claiming a completeness the records cannot support.
Sources
- 1.World Intellectual Property Organization. Accelerate by Working with Investors and Buyers . Evidence of ownership, restrictions on use and transferability of key agreements.. Accessed 9 November 2026
