Skip to content

$ open ~/guides/court-audio-preservation-chain.guide

Court-Audio Preservation Chain

A five-stage visual workflow for documenting intake, preserving the complete source, working from a verified copy, checking results, and recording handoff and retention.

Workflow Court reporting Updated By

Print / save PDF Read the field note
The source package and handling record stay linked; the working copy stays separate.

Court-Audio Preservation Chain

Workflow · Andrew Mayes

  1. Document intake

    Record the source, receiver, date and time with time zone, transfer method, original paths and sizes, and any exception.

  2. Preserve source

    Protect the complete package in approved, access-controlled storage and record the first trustworthy SHA-256 baseline without overstating what it proves.

  3. Work from copy

    Verify a separate working copy before review or conversion, then log tools, settings, inputs, outputs, and errors.

  4. Verify

    Check the expected sessions, duration, boundaries, channels, playback, and known problem areas; keep mismatches visible.

  5. Handoff and retain

    Record each sender, recipient, time, method, included files, and manifest, then follow the controlling hold, retention, and disposal authority.

The preserved package and handling record stay together.A matching hash supports byte integrity, not origin, completeness, identity, authentication, or admissibility.Technical practice does not replace the controlling rule, order, contract, policy, or qualified professional judgment.

The working rule: Preserve the complete source. Do every review, conversion, cleanup, and export from a documented copy.

andrewmayes.com/guides/court-audio-preservation-chain/ Updated

Use this as an operational handoff

The chain connects the complete source package with its human handling record. Assign an owner, keep filenames and folder relationships, and follow the controlling rules, holds, and retention requirements. This is technical preservation guidance, not legal advice, a forensic-acquisition protocol, or a promise of authentication or admissibility.

Synthetic handoff example; no real matter or files. Packet DEMO-01 lists 001.trm, 002.trm, and session.xml. Operator A preserves the packet and records paths, byte sizes, receipt time with time zone, and SHA-256 values in intake.csv. A sends B a working copy and manifest through the approved transfer, logging both people, time, and method. B finds 002.trm missing: record the exception, pause review, and request the missing copy. Matching 001.trm cannot establish packet completeness.

One rule protects the source

Preserve the complete source. Do every review, conversion, cleanup, and export from a documented copy. Keep the preserved package access-controlled and separate from working files and deliverables.

  • Keep both records connected. The preserved package and handling record stay together.
  • Describe hashes accurately. A matching hash supports byte integrity, not origin, completeness, identity, authentication, or admissibility.
  • Follow the controlling authority. Technical practice does not replace the controlling rule, order, contract, policy, or qualified professional judgment.

Scope and primary references

The workflow follows the preservation and accountability principles in NIST IR 8387, Digital Evidence Preservation: Considerations for Evidence Handlers (opens in a new tab), while the current Federal Rules of Evidence (opens in a new tab) illustrate why technical integrity is only part of authentication and original-or-duplicate questions. SWGDE, Best Practices for Computer Forensic Acquisition, 17-F-002-2.1 (opens in a new tab) provides acquisition guidance for work that requires trained digital-evidence examiners. For additional context, the related field note explains the operating boundaries, exception handling, and printable checklist.

Related tool: DepoAudio

Free the record from proprietary court-audio formats.

Free, with no account or subscription, for Windows 10/11 x64 · macOS 13.3+ universal. The release page lists install requirements; verify each FTR/TRM result against the original recording.

Read the DepoAudio case study Get DepoAudio v1.0.2 (opens in a new tab) Release page: installers and requirements

Questions about your workflow? Start a conversation