Sharing Digital Evidence Across Agencies Without Breaking Chain of Custody

Most digital evidence does not stay inside one agency. A robbery series crosses three jurisdictions. A regional task force pulls detectives from five departments into one case. A homicide file has to reach the district attorney intact and on time. Every one of those handoffs is a moment where the chain of custody can break — and in practice, cross-agency sharing is where it breaks most often, because it usually happens over the tools nobody built for evidence: email attachments, shared Dropbox links, and USB drives passed across a conference-room table.

This article is about moving digital evidence between agencies without losing the two things that matter: a defensible chain of custody, and clean data boundaries between the agencies involved. It is written for detective bureaus, task-force leads, and records staff who already share evidence today and want to stop doing it in a way a defense attorney can pull apart.

Why the cross-agency handoff is the weak point

Inside a single agency, at least the evidence lives in one place with one set of rules. The moment it leaves, three things tend to go wrong at once. The file gets copied, so there are now two originals and no clear record of which is canonical. The hash is not re-verified on the receiving end, so nobody can prove the copy matches what was collected. And attribution goes dark — the receiving agency logs that a file arrived, but not who sent it, when, or whether it was altered in transit.

None of these are exotic failures. They are the default outcome of emailing a video to a partner agency. The sender's outbox is not an evidence log, the receiver's inbox is not an evidence log, and the copy that lands has no cryptographic tie back to the original. By the time the case reaches trial, the honest answer to "can you prove this is the same file the witness gave you" is often no.

What a defensible cross-agency handoff actually requires

A cross-agency transfer holds up when four conditions are met. Treat these as the acceptance criteria for any method you use, whether that is a purpose-built system or a manual process you are trying to tighten.

1. 01Integrity is provable on both ends. The file carries a SHA-256 hash computed at original collection, and the receiving agency can re-compute that hash and confirm a match. If the hashes differ, the transfer is rejected, not quietly accepted.
2. 02The transfer itself is logged with attribution. Who released the evidence, who received it, exactly when, and to which case — recorded as an event, not inferred from an email timestamp.
3. 03Access is scoped, not broadcast. The partner agency gets exactly the assets relevant to the shared case, through a link or grant that can expire and be revoked — not a copy of the whole case file that lives on their drive forever.
4. 04Agency boundaries stay intact. Sharing one case with one partner does not merge two agencies' data. Each agency's other cases, users, and storage remain isolated from the other.

Why the common workarounds fail each test

Email fails all four: no hash verification, no real transfer log, no scoping (the attachment is a permanent copy), and no boundary (it now lives in another agency's mail system indefinitely). A shared cloud folder is a little better on convenience and far worse on boundaries — access tends to be all-or-nothing and rarely gets revoked when the case closes or a detective transfers. A USB drive is the worst of both: an untracked copy with no attribution the moment it leaves your hand.

How isolation and scoped access solve it

The structural fix is to share access, not files, and to keep every agency on hard tenant boundaries so a shared case never bleeds into the rest of either agency's data. Intelintake is built this way: agencies are isolated tenants that never share data, indexes, or storage by default, and cross-case sharing is an explicit, scoped grant rather than a copy. Every submission is SHA-256 hashed at intake and re-verified on transfer and download, so a partner agency can confirm integrity against the original rather than trusting an attachment.

Access travels over secure, single-use or time-bound links scoped to the relevant material, and every view, download, and export is written to the case's audit log with the user, timestamp, and IP. That turns a cross-agency handoff from an untracked email into a recorded event that names both sides — which is exactly what a prosecutor needs when the transfer is challenged.

A workflow that survives discovery

Here is the sequence a task-force or mutual-aid handoff should follow, regardless of the specific tool. If your current process cannot do these steps by default, that is the gap to close.

1. 01Keep the original in one place. The collecting agency holds the canonical asset; it is never re-encoded or duplicated to share.
2. 02Confirm the hash before anything moves. The SHA-256 fingerprint recorded at collection is the identity of the file, not its name.
3. 03Grant scoped access to the partner. Issue a time-bound, revocable link to exactly the assets the shared case needs — not the whole case, not a permanent copy.
4. 04Re-verify on receipt. The receiving agency re-computes the hash and confirms the match before working the material.
5. 05Log the exchange on both ends. Release and receipt are recorded with full attribution against the case.
6. 06Revoke when the shared purpose ends. When the case closes or a person transfers, access is pulled — the partner does not keep a standing copy.

Questions to pressure-test your current process

Use these with your own team or with any vendor. Each one maps to a way cross-agency sharing goes wrong.

• When we share evidence with a partner agency, can they cryptographically verify it matches what we collected?
• Is the transfer itself logged with who released it, who received it, and when — or only that a file appeared somewhere?
• Can we scope access to specific assets and revoke it later, or does sharing always mean handing over a permanent copy?
• Does sharing one case with one agency keep the rest of both agencies' data fully isolated?
• When a detective transfers off a task force, does their access to shared evidence end automatically?

Cross-agency work is not the exception in modern investigations; it is most of the hard cases. The agencies that handle it cleanly are not the ones with the strictest email policy — they are the ones who stopped moving copies and started sharing scoped, verifiable access to a single canonical record. If you want to see how that looks on a shared case, the demo link on this site routes to our team and we will walk it through on live data.