Guide
Responding to a subpoena: document production, done right
A clean production answers exactly what was asked, on time, in a form the other side can verify — and keeps a record of what you sent.
Not legal advice. Subpoena scope, objections, privilege, and production format are governed by rules that vary by jurisdiction. Confirm strategy and obligations with counsel.
A subpoena duces tecum lands and the clock starts. A good response is methodical: know exactly what's demanded and by when, collect what's responsive, hold back what's privileged, and produce the rest in a form whose integrity you can prove later. The failure modes are missing the date, producing too much (or too little), and handing over files you can't later show were unaltered.
Work backward from the demand
- Parse the demand into discrete requests and the production date.
- Map each request to the documents that respond to it — and note where there are none.
- Screen for privilege and scope before anything leaves the building.
- Produce a complete, organized set — and keep your own record of precisely what you sent.
Why the production format matters
Months later, someone may claim a produced document was altered — or that a file they received isn't the one you sent. The defense is to produce with a manifest of hashes: a SHA-256 for each file. The recipient recomputes them and confirms a match; you keep the same index as proof of exactly what left your office and that it was intact.
"Here are the documents" invites a fight later. "Here are the documents, and here's the hash of each" ends it.
Keep the date and the production together
The production deadline and the documents that satisfy it belong in the same place — so the date is tracked, the responsive files are attached, and the package is one action, not a scramble. (Tracking the date itself is covered in tracking court dates, deadlines, and subpoenas.)
How Scribe handles this
In Scribe Verbatim, parsing a subpoena tracks the production and puts the date on the case calendar. You attach the responsive files and download them as a single zip with a SHA-256 index — a verifiable package the other side can check and you can stand behind. Every file's integrity is already established by the case's tamper-evident chain of custody, so a production is the natural last step, not a separate forensic project.
Frequently asked
What is a SHA-256 index in a production?
A manifest listing each produced file with its SHA-256 hash. The recipient recomputes the hashes to confirm the files arrived unaltered, and you keep the index as a record of exactly what you produced.
Can Scribe track the production deadline too?
Yes — parsing the subpoena tracks the production and adds the date to the case calendar with reminders. See tracking court dates and deadlines.