Separate working files from retained evidence
Use different locations and permissions for editable working material, approved milestones and independent backups. Encrypting a folder does not control an upstream notebook platform, lab system or collaboration provider.
At a prototype milestone, the record owner exports an approved snapshot, verifies its manifest, places it in the protected archive, locks it, and stores a separately controlled recovery copy while daily work continues elsewhere.
Run the control in five steps
- 01Define working, milestone, retained and backup copy classes.
- 02Export the approved milestone without changing the source system.
- 03Verify filenames, counts and hashes against the register.
- 04Protect the retained set and close access when the step is complete.
- 05Store and test an independent backup under a different failure path.
Preserve the decision trail
Record milestone, source system, export time, manifest/hash, archive location, access group, backup location, recovery owner and test date.
Stop and investigate when
- The encrypted archive is also the only working copy.
- A synced folder is called an independent backup.
- Plaintext staging files remain after import.
State what encryption does not prove
Does not replace provider permissions, guaranteed backup, password recovery or enterprise identity management. It also does not determine inventorship, patentability, filing priority, evidentiary weight or disclosure authority. Obtain appropriate counsel.
Invention notebook security questions
Can the archive replace the lab system?
Not automatically. Source-system records and controls remain authoritative.
Is one encrypted copy enough?
No. Confidentiality and recoverability are separate requirements.
Sources for this decision
Links support specific boundaries and do not imply endorsement.