Guide to safer handling / 03

Building an encrypted working archive for independent journalist field notes

Separate editable working copies from encrypted retained copies.

FIELD NOTE
03/08
Diagram outlining three key actions for building an encrypted working archive for independent journalist field notes.

Three-stage practical decision map for this guide.

Separate draft reporting from encrypted evidence

Choose where editing happens, which copy becomes the controlled record and when that record is locked. A reporter returns from an interview with handwritten notes, an audio recording, and a separate contact sheet that identifies a confidential source. Design the workflow so that raw, edited and retained versions are not mistaken for one another.

Faceless archival workspace with encrypted media and separated record sets
Build a controlled archive that keeps raw, edited and retained versions distinct.

Separate active work from archive

Create distinct intake, working, reviewed and retained states for interview notes, source contact keys, draft transcripts, location notes and recording consent logs. Avoid editing the only recoverable original inside a time-sensitive handoff. Lock the maintained archive when it is no longer actively being edited.

Choose a protection mechanism

For controlled local storage, Folder Lock documents encrypted lockers. That is different from its non-encrypting folder-hiding feature. Record which one was selected and why. Test a harmless sample on the actual supported Windows version before moving the real independent journalist field notes records.

Documentary-style illustrative scene of journalist source protection workflow step 3; not a software screenshot
Working scenario: Encrypted working notes

Verify the authorized workflow

Have the reporting lead and an explicitly assigned editor confirm they can find an authorized item, add an approved new version and lock or close the collection without exposing a decrypted desktop copy. Backups must be secured independently of the local locker.

Applied example / editorial decision

Working-state example: source contact keys is edited in a limited-access workspace, checked for unintended copies, then entered into the approved encrypted archive as a named revision.

Practical implementation checklist

  1. Identify the accountable approver for independent journalist field notes and write down the exact event being protected.
  2. Choose a non-sensitive sample drawn from the same format as interview notes; never use a real identity, key or patient record in a public example.
  3. Compare the unprotected working copy, restricted recipient copy and intended retained copy. Confirm where extra versions are created.
  4. Record the approved destination, any failed test, and a date for reassessing the workflow when personnel or software changes.

Questions readers should resolve

Is hiding a folder equivalent to encrypting it?

No. Concealment and encryption are different protections; check which feature was actually used. For journalist notebooks, this means checking interview audio, handling source identity keys separately, and using a redacted source note as the review example. Maintain a small example that is easy for the owner to lock, reopen, close and recover without credentials from a real user.

Who should approve this independent journalist field notes workflow?

Assign a named owner. In this context, start with the reporting lead and an explicitly assigned editor and confirm the applicable organizational authority.

Research and documentation

These sources support the technical boundaries described here. They are not substitutes for testing the current software on the target device, checking legal requirements, or independently confirming product claims.

Original editorial scene of encrypted archive setup, part 1
Closer view: Encrypted working notes

Editorial note: No paid link placement is required for this guide. Product information, if mentioned, describes one possible tool and should not be read as an endorsement or an assertion of universal compatibility.