Preserve the question as well as the record.
A folder says what you collected. A review boundary says what the collection can answer. Name the project, decision, time window, custodians and record classes before extracting a chronology. Write down excluded periods and systems. Otherwise a small collection can quietly acquire the appearance of a complete history.
For an owner, the first question may be whether a priced change matches authorized work. For counsel, it may be which version was available when advice was given. For a family office, it may be whether a portfolio report is supported by the underlying approvals. Each question needs a different collection boundary.
Give each source a passport.
| Field | What to record | What it prevents |
|---|---|---|
| Identity | Stable source ID, original filename, record type and attachment relationships. | Two similarly named revisions being treated as one. |
| Origin | Issuing person or system, supplier, acquisition method and collection date. | A forwarded copy being described as a direct export. |
| State | Record date, time zone, revision, issue status and stated purpose. | A draft becoming an issued instruction in the chronology. |
| Custody | Location of the unchanged copy, authorized handlers and transfers. | Unexplained edits or uncontrolled copies. |
| Integrity | File size and recorded checksum where appropriate, plus the method and time. | Silent byte changes being missed. |
| Limits | Missing pages, unreadable content, absent attachments and unresolved authenticity. | An incomplete record appearing conclusive. |
A checksum can help detect a byte change after collection. It does not establish that the author was honest, that the file is complete or that the record is admissible in a particular proceeding. NIST discusses provenance, custody and integrity checks in its preservation guidance. NIST: Digital Evidence Preservation.
Separate originals, working copies and extracts.
Retain the original as received. Work on a separately labelled copy. Treat OCR, translations, transcriptions, cropped photographs and redactions as derivatives linked to that original. Keep the transformation method, date, operator and any uncertainty with the derivative.
- A PDF print of an email is not the same object as the native message and its attachments.
- A screenshot can document what appeared on screen; it may omit metadata, surrounding context or later edits.
- An export time is not necessarily the event time. Keep displayed time, time zone and any conversion explicit.
- A duplicate may add custody information without adding an independent account of the event.
Do not rename away the original revision, edit the only copy or open unfamiliar active content merely to collect it. A qualified preservation specialist can help when the source is fragile, a device is changing or the collection may need forensic handling.
Make every material statement independently findable.
Use a precise locator: source ID, page or message, clause, table cell, drawing revision or log event. A link to a thousand-page folder is not a locator. Keep a statement ledger with four states: source states, independently checked, inferred and unresolved.
“SRC-14, page 6 records approval of CH-08 for a ceiling of $18,000” is a narrower statement than “the extra work was authorized.” The second statement also needs the authority, scope, conditions and relationship to the work actually done. Review those links in the approval-chain guide.
Correct the dependent work, not just one cell.
When a better scan changes an extracted amount from $18,000 to $13,000, preserve the original extraction as a working error. Correct the amount, note the reason and identify the chronology, variance table and conclusion that used it. Recalculate those dependent outputs and record who checked them.
A correction log should contain the old statement, new statement, triggering source, affected outputs and date. It is a practical way to make a review revisable without concealing how the explanation changed.
The useful handover pack is small and traceable.
- The decision question and exact reviewed boundary.
- A source index with authoritative-copy locations and access limits.
- A chronology with exact locators and unresolved time conflicts.
- A statement ledger separating source accounts from interpretation.
- A gap list ranked by which missing record could change the decision.
- An item-level money reconciliation when relevant, with assumptions and unallocated amounts.
- Deadline and notice questions for counsel, kept separate from any research timetable.
- A handling, correction and handover log, with the next decision owner named.
Give recipients only the records needed for their role. Keep privileged, personal or confidential material in a separately controlled location and agree handling with counsel where appropriate. A research engagement does not itself create legal privilege. This workflow is not a legal hold, a privilege opinion or a substitute for advice on preservation duties.