Methodology — Evidence Preservation
Last updated: October 21, 2026
Evidence that cannot be shown to be unchanged is weaker evidence. This method keeps three things true for every file and page Citizen Analyst relies on: the original still exists, anyone can check that it has not been altered, and there is a record of who handled it. The Berkeley Protocol on Digital Open Source Investigations (OHCHR and UC Berkeley) gives guidance on gathering, analysing and preserving digital information, and preservation is one of those three. This page is the lightweight, newsroom version of that discipline.
1. Original vs. working copy
Keep read-only original in encrypted storage; work on copies for annotation.
Name the original with its acquisition date and source, and never open it in an editor that can save over it. Every highlight, crop or OCR pass happens on a copy.
2. Hashing
SHA-256 on acquired files where feasible; record tool version for transcoding.
SHA-256 is one of the hash algorithms specified in NIST’s Secure Hash Standard (FIPS 180-4). NIST describes the purpose plainly: a digest is used “to detect whether messages have been changed since the digests were generated.” Record the hash when you acquire a file. Anyone who later recomputes it and gets the same value knows the file is identical. Transcoding a video or converting a PDF produces a new file with a new hash, which is why the tool and its version go in the log.
3. Web captures
Prefer institutional archives (Wayback) plus independent second capture when stakes are high.
The Wayback Machine’s Save Page Now saves one page, with its images and CSS, at a permanent URL that readers can open. A second capture with a different tool, such as archive.today or a local capture tool that records URL, timestamp and hash automatically, protects against a gap in either. What each tool saves is compared in Web Archiving for Evidence.
4. Chain of custody (lightweight)
Who acquired, when, from where, what changed (if anything). Suitable for journalism; consult counsel for litigation.
A one-line entry per handling event is enough: date and time in UTC, person, action, and file hash before and after.
5. Redaction before share
Strip metadata and third-party PII before public release.
Redact on a copy, and record the hash of the redacted file separately from the original’s hash.
Related skills
media-verification-specialist, secure-source-communication
Sources
- NIST, FIPS 180-4 Secure Hash Standard (read 2026-10-21)
- OHCHR, Berkeley Protocol on Digital Open Source Investigations (read 2026-10-21)
- Internet Archive Help, Save pages in the Wayback Machine (read 2026-10-21)
- Hunchly, product page (read 2026-10-21)
Expanded with AI research and drafting assistance from the primary sources cited; editorial review pending.
