Responding to a subpoena: document production, done right

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.

Read the demand before you collect

Diligence starts with the four corners of the subpoena: who it's directed to, the exact categories demanded, the date range, the response deadline, and the place and form of production. Note your window to object — an overbroad or unduly burdensome request, or one that reaches privileged or plainly irrelevant material, may warrant a timely objection or a motion to quash rather than a scramble to comply. Calendar the deadline the moment the subpoena arrives, not the week it's due.

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.

A production manifest

A manifest pairs each produced file with a fingerprint the other side can independently verify:

Anyone can recompute a file's SHA-256 and compare it to the manifest; a single changed byte produces a completely different value. That turns "trust us" into arithmetic. Why a hash proves integrity is covered in chain of custody for digital evidence.

Privilege and a log of what you held back

Screening for privilege is as important as collecting. Attorney–client communications and work product are typically withheld — but withholding silently invites a dispute. The norm is a privilege log that identifies each withheld item (date, author, recipients, type) and the basis for withholding it, without revealing the protected content. Produce what's responsive, log what's withheld, and you've answered the demand without waiving anything.

Bates-label and organize the set

A production the other side can navigate is one that ends arguments instead of starting them. Number the pages in a simple Bates sequence (PROD-0001, PROD-0002…), keep documents in a sensible order, and pair the set with the manifest above so each reference resolves to a file and its hash. Where the demand listed discrete requests, note which documents answer which — it forecloses a later claim that you quietly skipped a category.

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.