Legal Services Offshore blog

Set a document production log that can answer a later privilege question

A production log that ties each produced document to its source, its privilege decision, and the reviewer who approved the release.

Set a document production log that can answer a later privilege question editorial illustration
Defined workflowAttorney review gatesPractical escalation

Open the log at collection

A production log should start when the documents are collected, not when the production is ready to send. Record the collection source, the date, the custodian, and the search terms used. If the collection came from a vendor, record the vendor and the delivery date. A log opened at the end loses the decisions that shaped the set.

Assign a production identifier before the documents are reviewed. Use the identifier in the review platform, the privilege log, and the transmittal. Do not wait for the Bates numbers to start the record. The identifier should remain stable even if the document is later moved to a different production set.

Record the collection search terms and the person who approved them. A production log that cannot show how the set was built is difficult to defend later. If the terms changed, keep the earlier version and the reason. The collection history is part of the production record.

Assign each document a stable identifier

Use one identifier per document and keep it consistent across systems. If the review platform assigns a control number, record it beside the Bates number. If the document has multiple versions, give each version its own row and note the relationship. A log that merges versions cannot answer which one was produced.

Record the file name, the page count, and the source location for each document. These fields let a reviewer confirm that the produced image matches the reviewed file. If a document is a compilation, list the component parts or attach an index. A short description is not a substitute for a stable link to the source.

Record whether a document was collected from a live system or an archive. An archived file may have different metadata and a different version history. If the collection method changed during the matter, note the change and the date. The production log should let a reviewer compare like with like.

Record the privilege decision and reviewer

For each document withheld or redacted, record the privilege basis, the reviewer, and the date. Use the firm's categories consistently and do not invent a new label for each document. If the decision is a judgment call, note the facts the reviewer relied on. A bare privileged stamp cannot be reviewed later.

Keep the privilege log separate from the production log but link the two by identifier. The production log shows what was released, while the privilege log explains what was withheld. A reviewer should be able to move from one to the other without searching. If a document is partially redacted, record both the released and withheld portions.

Use a short description that helps a reader identify the document without reading it. The description should not reveal privileged content. A neutral phrase such as email chain about scheduling is enough. If the document is a draft, label it as a draft and record the version. The log is a finding aid, not a second copy of the file.

Track redactions against the source

A redaction should be tied to the exact page and the reason. Record the page, the redaction category, and the reviewer who approved it. If the redaction removes a name, a figure, or a sentence, note the type without reproducing the privileged content. The record should be specific enough to defend the redaction without becoming a second copy.

Check the redacted image against the source before production. A redaction box that covers the wrong line or leaves metadata visible is a common error. Record the check and the person who performed it. If the error is found after production, record the correction path and the recipient who was notified.

Check whether the redaction tool preserves the underlying text or metadata. A visually redacted page can still carry the original text in a layer. Record the tool and the export setting. If the team cannot verify the setting, use a flattened image and record the conversion. The production should not depend on a setting nobody checked.

Record the redaction tool and the export setting with the production. A visual redaction can leave text in a layer, and a flattened image can lose searchable text. The team should know which trade-off was chosen. If the setting changed during the matter, note the change and the date.

Keep the production transmittal with the log

The transmittal identifies what was sent, when, and to whom. Attach it to the production log and record the delivery method. If the production was sent in several parts, list each part and its identifier range. A transmittal without the log cannot show which documents were included in which delivery.

Record any replacement or supplemental production with the same care. Note the reason, the new identifier range, and the recipient. If a document was withdrawn, record the withdrawal and the instruction to the recipient. The production history should show the sequence rather than only the latest state.

If a recipient asks for a replacement copy, record the request and the new transmittal. Do not resend the original file without checking whether it contains the error. Note the recipient, the date, and the corrected range. The production history should show why a second copy exists.

Reconcile the log before closing

Before the matter closes, compare the production log with the review platform and the transmittal. Check for documents that were reviewed but never produced, produced but not logged, or logged with the wrong identifier. Resolve each difference and record the decision. A closing log that does not reconcile is an open question for the next reviewer.

Keep the reconciled log with the matter file and the privilege log. Record the reviewer and the date. If the matter may reopen, note where the source files are stored and who can access them. The log should answer what was produced, what was withheld, and who approved the release.

Keep a short list of documents that were reviewed but not produced and the reason. A document may be irrelevant, duplicative, or withheld. The list prevents a later reviewer from assuming the document was missed. Record the reason code and the reviewer.

A supervised review lane can maintain the production log and privilege fields while the lawyer makes every withholding and redaction decision. litigation document review support.

Sources

  1. U.S. Courts, Federal Rules of Civil Procedure

    Used for the litigation calendar and production workflow context that these controls support.

  2. American Bar Association, Model Rules of Professional Conduct

    Used for supervision, confidentiality, and communication boundaries in legal support work.

  3. GAO, Standards for Internal Control in the Federal Government

    Used as a general reference for documented ownership, review evidence, and exception handling.

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.