Insightsby Bernstein

How should I document the development of an idea, design or invention?

Published 29 October 2026

The short answer

Build a dated record as the work develops. Preserve meaningful versions, record who contributed and explain what changed. Add independently verifiable timestamps at important milestones, and retain the exact files they certify. Together, these records should let someone unfamiliar with the project understand what existed, when it existed and how it evolved.

Start with the work itself

Preserve the materials that explain your development process: sketches, drafts, design files, source code, experimental results, photographs of prototypes and technical notes. Include unsuccessful approaches when they help explain how you reached a solution.

Keep original working files alongside useful exports. A finished PDF or photograph may show the result, while the underlying files and earlier versions explain how you got there.

Give each meaningful version some context

For each milestone, record the date, contributors, changes and supporting files. A short note is often enough: what problem were you addressing, what did you try, and what did you learn?

For example, a prototype revision could include the updated drawing, photographs, test results and a note explaining why the dimensions changed. Keep relevant correspondence and agreements alongside the project when they help establish contributions, instructions or ownership arrangements.

Make the chronology independently verifiable

A date written in a document records what you say happened. A trusted digital timestamp provides additional evidence that a particular version already existed at a given time. Timestamping meaningful milestones can therefore strengthen the chronology of your development record. See RFC 3161, introduction and section 2.

Choose milestones that matter to the project: a significant design change, an experimental result, a software release or the version about to be shared with a partner. If you document earlier work retrospectively, distinguish the date of the original activity from the date you created the record.

Preserve the evidence so it remains usable

Retain the exact certified files, their certificates and the information needed for verification. Work on copies when making further changes, and maintain backups. A certificate cannot reconstruct a missing original, and an altered file may no longer match its certificate. See Your certificate is immutable. Your files are not..

Keep confidential records under appropriate access controls. Use a clear folder structure, identify sensitive material and make responsibility for maintaining the records explicit. WIPO recommends document-management measures that make confidential information identifiable and traceable, while remaining simple enough for people to follow.

Sources

  1. 1.
    C. Adams, P. Cain, D. Pinkas and R. Zuccherato. Internet X.509 Public Key Infrastructure Time-Stamp Protocol . RFC 3161; introduction and section 2. August 2001
  2. 2.
    Bernstein. Your certificate is immutable. Your files are not. . Preserve the version you certified. 16 October 2026
  3. 3.
    World Intellectual Property Organization. WIPO Guide to Trade Secrets and Innovation . Part IV: Trade secret management; Document management measures. Accessed 29 October 2026
Suggest a correction

Tell us what is wrong and, if you can, where the correct information is published.

This site is protected by reCAPTCHA.

The correction form opens soon.