Legal Services Offshore blog
Prepare a subpoena response index that separates served from produced documents
An index that keeps the subpoena served, the documents collected, and the production set distinct so a later reviewer can trace every response item.

Key takeaways
A subpoena response has at least two document sets: what was served and what was produced. The index should keep them separate and show how each produced item relates to a request. Combining them into one list makes the response impossible to reconstruct. Use the approved template so the fields stay consistent across the team.
Give every request and every response item a stable identifier. Use the request number from the subpoena and a production identifier that does not change. Record the source path for each item so the file can be found again. Ask the named owner when the instruction is unclear instead of guessing.
Record objections, redactions, and withholding decisions beside the item they affect. Support staff can note the decision and the source, but the lawyer decides whether to object or withhold. The index should not imply a legal conclusion that was never approved. The person who performs the check should be able to explain the result.
Reconcile the index with the actual production before it is sent. A count that does not match the production set is a warning, not a rounding difference. Record the reconciliation and the person who completed it. A short written check is easier to repeat than an informal habit.
Separate served documents from produced documents
Start with the subpoena as served, including the caption, the issuing court, the date, and the requests. Record the service method and the date the firm received it. That record is the anchor for everything that follows. A small sample review can show whether the step is working.
Create a second set for the documents collected in response. Record the custodian, the source system, the date collected, and the request number each document may answer. Do not assume that a collected document will be produced. If the answer depends on a legal rule, route the question to the lawyer.
Create a third view for the production set that was actually delivered. Each item should point back to the collected document and the request it answers. A reader should be able to move from the production back to the source without guessing. Record the exception even when the outcome is resolved the same day.
Keep duplicates visible until the lawyer decides how to treat them. A duplicate may be a true copy, a different version, or a document from another custodian. The index should show the difference rather than silently collapsing the entries. Record the channel used so a later reader can find the same source again.
Give every response item a stable identifier
Use a production identifier that will not change when a folder is renamed or a document is renumbered. Record the original file name and path beside it. If the identifier is derived from a Bates number, record the full range. Use one identifier across the index, the source, and the delivery record.
Tie each production item to one or more subpoena requests. A document can answer more than one request, and the index should show every link. That mapping is what lets a reviewer explain why the document was included. The same check should work for a routine item and an unusual one.
Record the date range, the author or custodian, and the document type when those facts are known. These fields help a reviewer compare the production with the request. Keep unknown fields marked as unknown rather than filling them by inference. Keep the language neutral and avoid conclusions the record does not support.
Keep a change log for identifiers that must be corrected. Record the old value, the new value, the reason, and the approver. A silent renumbering can break the link between the index and the produced files. Note the open question and the person who will answer it.
Record objections, redactions, and withholding reasons
Record each objection against the request it responds to. Use the lawyer's wording or a faithful short label, and note the date the position was approved. Do not create a new objection category in the support lane. The review should be dated so a later reader knows which version was current.
For a redaction, record the document identifier, the page, the basis supplied by the lawyer, and the reviewer. Keep the unredacted source in the approved restricted location. The index should not include the redacted content itself. Store the evidence where the team already looks for the matter record.
For a withheld document, record the request number, the document identifier, and the reason supplied by the lawyer. Note whether a privilege log entry exists. A withholding note without a source is hard to defend later. Review the entry before the file moves to the next stage.
Keep the objection and production records in the same matter file. If the position changes, add a new entry rather than deleting the old one. The history should show what was produced at each stage. A second reader can catch a gap that the first reader no longer sees.
Reconcile the index with the production set
Count the items in the production and compare the count with the index. Check the identifier ranges, the page counts, and the number of files delivered. Record any difference and resolve it before the production is released. If the process changes, record the change and the date it took effect.
Spot-check several items from the index against the actual files. Confirm the identifier, the request link, and the redaction status. Record the sample and the result so the check is repeatable. The date of the check belongs beside the fact it supports.
Check that the delivery method matches the firm's instruction. A production sent through an unapproved channel creates a separate problem. Record the channel, the recipient, and the date. The record should show what was reviewed and what remained open.
Ask a second person to review the reconciliation when the production is large or the deadline is tight. Record the reviewer and the date. The second check is a control, not a comment on the first reviewer. Record the handoff so the next person does not restart the review.
Keep the service record next to the index
Store the subpoena, the service confirmation, the index, and the production receipt together. A later reader should not have to search several systems to reconstruct the response. Use the same matter identifier across the records. That record also helps when the same issue appears in a later matter.
Record any extension, modification, or withdrawal of the subpoena. A changed request can affect the index and the production scope. Note the date and the source of the change. The note should stand on its own without a call to the person who wrote it.
If the response is delivered in stages, keep a separate index for each stage and a master view that links them. Record the date of each delivery and the items included. A rolling production is easier to audit when the stages are visible. Name the person who completed the check and the date it was finished.
Close the index with a final reconciliation note and the name of the person who approved the response. Keep the note with the file. The record should show what was served, what was produced, and what remained open. The note should be short enough to complete on a busy day.
A supervised support lane can maintain the response index and reconciliation while the lawyer decides objections, redactions, and production. case file management support.
Sources
- American Bar Association, Model Rules of Professional Conduct
Used for supervision, confidentiality, competence, and communication boundaries in legal support work.
- U.S. Courts, Federal Rules of Civil Procedure
Used for the litigation, service, and production workflow context that these controls support.
- GAO, Standards for Internal Control in the Federal Government
Used as a general reference for documented ownership, review evidence, and exception handling.
- NIST Cybersecurity Framework 2.0
Used for access control, monitoring, and recovery language around shared legal records.