Legal Services Offshore blog

Document production indexing for a rolling review

Keep a rolling production index that tracks batches, custodians, source paths, redactions, and reviewer decisions without turning the index into a legal conclusion.

Document production indexing for a rolling review editorial illustration
Defined workflowAttorney review gatesPractical escalation

Define the batch before the first file moves

A rolling production is a sequence of batches, not one large folder that grows without labels. Before work begins, define what constitutes a batch, who approves it, and how it will be identified in the record. The batch identifier should be stable and should never be reused for a later set of documents. Record the matter, the production request or order, the custodian or source, the collection date, the review status, and the destination.

If a batch is supplemented, create a new batch record rather than editing the old one. The index should show the relationship between the original and the supplement, including which documents were added or replaced. A batch without a scope statement is difficult to defend later. Write down what was included, what was excluded, and why. Exclusions may include duplicates, non-responsive items, privileged material, or documents outside the agreed date range. The index does not need to reproduce the legal reasoning, but it should point to the reviewer decision that supports the exclusion.

Give every document a stable identity

Use a document identifier that survives renaming, reformatting, and transfer between systems. The identifier should be separate from the file name, because file names change and may contain characters that break exports. Record the original path, the hash or system identifier when available, and the page count. For each document, capture the custodian, the date shown on the document, the document type, the source collection, and the review status.

If the document has attachments, record the parent-child relationship rather than treating each file as unrelated. A missing attachment is often more important than the parent document itself. When a document is re-produced or corrected, link the new version to the old one. Do not delete the earlier entry, because the history may be needed to explain a change in the production. A reviewer should be able to see what was produced, what was withheld, and what was replaced without reconstructing the sequence from email.

Track redactions as decisions with evidence

A redaction is a reviewed decision, not a formatting step. The index should record who approved the redaction, the basis category used, the date of approval, and the location of the supporting note. The offshore team can apply an approved redaction and check that the correct version was exported, but it should not decide privilege or confidentiality on its own. Before release, compare the redacted file with the approved instruction.

Check the page, the area, and the reason code, and confirm that the underlying text has not leaked through metadata or a hidden layer. If the file format makes that check impossible, escalate rather than assuming the export is safe. A redaction log should also record when a redaction is removed or changed. The reviewer needs to know whether the change came from a court order, a client instruction, or a correction of an earlier mistake. Each reason leads to a different follow-up, and the record should make the difference visible.

Keep the review queue separate from the production log

The review queue manages work in progress, while the production log records what was actually released. Combining them makes it hard to tell whether a document is waiting for review or already produced. Use separate status fields and reconcile them at the end of each batch. A document may be reviewed, approved, and still not produced because the export failed or the recipient did not receive it.

The production log should record the release event, the delivery method, the recipient, and the confirmation. A queue that says complete is not proof that the other side received anything. When a production is rejected or returned, preserve the original release record and add the rejection reason. The correction should reference the rejected batch, not overwrite it. This history is useful for both the client and the reviewer, and it prevents the same error from being repeated in the next batch.

Make the index usable during a deposition or hearing

The index will be read under time pressure, so it must answer basic questions quickly. Can the reader find a document by identifier, custodian, date, or subject? Can they see whether it was produced, withheld, or replaced? Can they locate the source file and the reviewer note without opening a dozen folders?

Use consistent column names and avoid free-text fields where a controlled list will do. A short legend should explain the status codes and the date format. If the index is exported to a spreadsheet, test the export before the hearing so that long identifiers and special characters do not break. A printed or offline copy may be needed when the team cannot access the document system. Keep a current export in the approved location and record when it was generated. An outdated index can be worse than no index because it creates false confidence about what was produced.

Sample the index against the actual files

A monthly quality check should compare a sample of index rows with the files they describe. Verify the identifier, the custodian, the date, the page count, the production status, and the redaction note. If the index says produced, open the produced file and confirm that it matches the entry. Record every mismatch with a reason code, such as missing file, wrong version, incorrect custodian, broken link, or status error.

Fix the index and, when necessary, the production process. A pattern of the same mismatch suggests a design problem in the collection or naming step, not a one-off typing error. The sample should include a recent batch, an older batch, and a corrected item. Older records are more likely to have broken links or inconsistent statuses, and corrected items show whether the repair process actually preserved history. Report the result to the reviewer with one recommended change and a date for the next check.

Close the production with a reproducible package

At the end of a production, assemble a package that includes the index, the batch approval, the transmittal record, the redaction log, and the exception list. The package should let another authorized reviewer understand what was sent and why without contacting the preparer. Store it in the approved matter location and link it from the production entry. The close note should state the batch identifier, the number of documents, the delivery date, the recipient, and any open items.

If a follow-up production is expected, say so and name the owner. Do not mark the matter complete merely because one batch was sent. Review the package before closing for consistency between the index, the transmittal, and the actual files. A final check by someone who did not prepare the batch is worth more than a second review by the same person. Record the reviewer, the date, and any correction made.

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.