Legal Services Offshore blog
A redaction QA pass for produced documents
A second-pass redaction check that reviews native files, metadata, and sampled pages before a production leaves the firm.

Define the redaction categories before review
A redaction QA pass needs a written list of what may be redacted and why. The categories might include privileged information, personal identifiers, trade secrets, and information subject to a protective order. Each category should have a definition and an example. The preparer applies the category, but the attorney decides whether the legal basis applies. Without a shared list, two reviewers will redact different things and the production will look inconsistent.
Record the category, the specific basis, and the source of the requirement for every redaction. If a protective order governs the production, cite the paragraph. If the redaction is based on a client instruction, record who gave it and when. A redaction log that says confidential is not enough, because it does not tell a later reviewer why the information was withheld. The log is part of the production evidence and should be maintained from the first pass.
Check the native file, not only the image
Redactions applied to an image can leave the underlying text in the native file, the OCR layer, or the document properties. Review the native format wherever the production rules allow it. If the file must be converted, confirm that the conversion removed the hidden content rather than covering it. A black box drawn over a PDF is not a redaction if the text underneath can still be selected or extracted.
Use the tools the firm has approved to apply and verify redactions. Test a sample by attempting to select or search the redacted text in the produced copy. Check comments, tracked changes, speaker notes, and embedded objects. A spreadsheet may hide data in a hidden row, a column, or a named range. A presentation may keep deleted slides or notes. The QA pass should look at the file as a whole, not only at the page a reviewer happened to open.
Search for the identifiers that survive
Build a search list from the redaction categories and run it against the produced set. The list might include names, account numbers, email addresses, addresses, and matter numbers. Search the extracted text, the metadata, and the file names. A redaction that works on the visible page but leaves a name in the file path is still a disclosure. Record the searches run and the results.
Do not rely on a single search tool. Different tools extract text differently, and a scanned page may produce no text at all. Spot check the scanned pages visually. If the production includes audio or video, confirm the redaction method for those formats as well. The search list should be updated as the matter develops, because a term that was irrelevant in the first pass may become sensitive later.
Review metadata and embedded objects
Metadata can reveal authorship, revision history, file paths, and prior versions. Decide before production whether metadata will be included, and apply that decision consistently. If metadata is removed, verify the removal on a sample. If metadata is produced, confirm that it does not contain information outside the scope of the production. A document that looks clean on its face can carry a comment from outside counsel in its properties.
Embedded objects need the same attention. A spreadsheet may contain a linked workbook, a document may contain an embedded email, and a PDF may contain attachments. List the embedded objects and decide how each will be handled. Do not assume that flattening the pages removes the attachments. Record the decision and the reviewer. When a file cannot be cleaned reliably, route it to the attorney rather than producing it with a warning that may not be read.
Use a second reviewer on sampled pages
A second reviewer should check a sample of the produced set against the redaction log. The sample should include the longest document, the document with the most redactions, and a random selection of ordinary pages. The reviewer confirms that each redaction matches a logged category and that no unlogged redaction appears. The reviewer also checks that the produced text is readable and that the pages are in the correct order.
Record the sample, the reviewer, and the result. If the reviewer finds an error, correct it and check whether the same error appears elsewhere. A single missed redaction may indicate a tool problem, a training gap, or a category that is unclear. Investigate the cause before releasing the production. The second review is not a guarantee, but it is a visible control that can be tested and improved over time.
Record every redaction decision
The redaction log should identify the document, the page, the category, the basis, the reviewer, and the date. If a redaction is removed or changed, keep the earlier entry and add the change with its reason. The log should be exportable in a format the firm can produce if challenged. A log maintained only in a reviewer's notes is not a reliable record.
Where the production rules require a privilege log, coordinate the redaction log with the privilege descriptions so the two do not contradict each other. The attorney should review the log before production, especially for categories that involve judgment. The preparer can check completeness and consistency, but should not decide whether a privilege claim is substantively correct. A clear log makes the attorney's review faster and gives the firm a defensible account of what was withheld.
Release only after a documented check
Before the production leaves the firm, confirm that the file set matches the transmittal, the redaction log is complete, and the QA checks are recorded. Run a final count of documents and pages and compare it with the production index. Confirm that the delivery method is approved and that the recipient is correct. A production sent to the wrong party cannot be undone by a follow-up email.
Keep the QA record with the production file, including the searches run, the sample reviewed, and any open issue. If an issue is unresolved, do not release the affected documents without the attorney's decision. The offshore team can prepare and verify the production, but the firm owns the decision to produce. A documented check protects the client, the firm, and the preparer, and it makes the next production faster because the team can reuse a proven routine.