# How to QA Redactions Before Court Production (2026) > A 5-step pre-production checklist before court filing: visual scan, copy-paste test, metadata check, version comparison, and second-reviewer sign-off. - **Author:** Neetusha - **Published:** 2026-03-24 - **Updated:** 2026-05-07 - **URL:** https://www.redactifyai.com/blog/qa-redactions-before-court-production/ --- A paralegal produces a document set to opposing counsel under [FRCP 5.2](https://www.law.cornell.edu/rules/frcp/rule_5.2). Two weeks later, opposing counsel flags that a name visible on page 34 should have been redacted. The paralegal checks. It was redacted in version 1. But somewhere between that first pass and the final version, during a second round to add privilege redactions, the name was accidentally unblocked. Nobody caught it because the final version was reviewed as a standalone document. Nobody compared it against the previous version. This kind of failure is common, preventable, and almost always caused by the same gap: no structured review step before production. For the redaction requirements your court specifically imposes, see [court filing redaction rules](/blog/court-filing-redaction-rules-requirements/). > **Quick answer:** [How to check if redaction was successful](/answers/how-to-verify-redaction-successful/). Same topic, condensed to ~400 words. ## Why redaction review gets skipped Time pressure is the obvious reason. When a production deadline is hours away, the instinct is to finish redacting and send. But there are two less obvious factors that matter more. First, teams trust the tool. If an AI detection engine flagged and redacted PII in the first pass, reviewers assume it stays redacted through subsequent passes. That assumption breaks when a second pass adjusts content around a redacted region, or when someone restores a section to fix a different issue and inadvertently removes a redaction that was already applied. Second, most redaction tools make comparison hard. If you cannot open two versions side by side and see exactly what changed, comparison does not happen. People skip steps that feel difficult under deadline pressure, and that is a workflow design problem, not a discipline problem. ## What a proper pre-production redaction review looks like Before any redacted document leaves the firm, run through this checklist: - **Visual scan of every page.** Not just the pages where the tool flagged detections. PII appears in headers, footers, exhibit labels, and handwritten notes that automated tools may handle differently across passes. - **Copy-paste test on redacted areas.** Select a redacted region, paste into a text editor. If text appears, the redaction is cosmetic. This catches the [visual-only masking failures](/blog/how-to-redact-documents-safely) that still plague PDF workflows. - **Metadata check.** Open document properties and verify that author names, tracked changes, comments, and revision history have been stripped. Metadata has exposed client identities in [high-profile court filings](/blog/law-firms-pii-pdf-mistakes). - **Version comparison against the prior pass.** Open the current version and the previous version side by side. Confirm that every redaction from the prior pass is still present in the final version, and that new redactions were added correctly. - **Second reviewer sign-off for high-stakes productions.** On matters where a missed redaction carries sanctions risk or malpractice exposure, a second set of eyes on the comparison step is worth the 10 minutes it adds. The competence duty under [ABA Model Rule 1.1](https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_1_1_competence/) extends to verifying technology output, not just the underlying legal work. ## Why single-document review misses version drift Most firms review the final redacted document in isolation. They scroll through, confirm that redacted areas look correct, and produce. That process catches obvious mistakes (a page with no redactions that should have them) but structurally cannot catch a more dangerous failure: version drift. Version drift happens when a document goes through multiple redaction passes. The first pass removes PII: names, Social Security numbers, dates of birth. The second pass adds privilege redactions: attorney-client communications, work product references. Between those passes, someone might adjust surrounding content, restore a paragraph that was removed, or apply a new detection pass that resets a region the first pass already handled. The result is a final document where most redactions are correct, but one or two from the first pass are missing. Reviewing the final version alone will not reveal this. The document looks complete. The only way to catch it is to compare the final version against the prior version and look for differences in the redacted regions. This is the category of error that leads to the opposing-counsel phone call nobody wants to receive. ## How side-by-side comparison fits into a review workflow The fix is straightforward. Before producing any document that went through more than one redaction pass, open both versions side by side. Scan for any difference between the redacted regions. Confirm the final version contains everything from prior passes plus the new redactions. On a typical 20-page document, this takes three to five minutes. On a longer filing, maybe ten. The [comparison feature in RedactifyAI](/features/) lets you select any two versions of the same document and view them next to each other, so the workflow is select, scan, confirm, produce. This single step catches the category of error that single-document review structurally cannot catch. It turns "I think this is ready" into "I verified this against the last version and confirmed nothing was lost." For firms using [Clio](/blog/redact-documents-in-clio-without-overwriting-originals), having both the original and each redacted version preserved in the same matter makes this comparison step even more practical. You are not hunting through folders or email threads for the prior version. It is already there. ## Building the review step into your workflow without adding friction This does not require a new policy document or a mandatory training session. It is one step, added to the existing production checklist: before sending, compare the final version against the prior version. For routine productions, one reviewer handles it. Open the comparison, scan for differences in redacted regions, confirm, close. Five minutes. For high-stakes matters (large discovery sets, regulatory filings, anything involving [HIPAA or GDPR compliance](/blog/redact-documents-gdpr-hipaa-compliance)), add a second reviewer on the comparison step. Ten minutes total between two people. This is not a full re-review of the document. It is a targeted diff check: did anything that was redacted in a prior pass become unredacted in the final version? That narrow focus is what keeps it fast enough to actually happen under deadline pressure. The cost is five to ten minutes per production. The alternative is the call from opposing counsel, the motion to compel, and the conversation with the client about what went wrong. Firms that have been through that conversation once tend to add the comparison step permanently. When you are [choosing a redaction tool](/blog/best-redaction-software-comparison), look for one that makes this step easy rather than one that forces you to open two separate files and manually toggle between them. The easier the comparison, the more likely it actually happens before every production. Before your next production, test your redaction process: [upload a PDF to our free redaction tool](/tools/redact-pdf-free/) and run the verification checks from this article. No account required. For full production workflows with version comparison, [sign up free](https://app.redactifyai.com/auth/signup) or [book a demo](/support). ## Frequently asked questions ### What should I check before producing redacted documents? Run a four-step verification on every document. Copy test: select redacted areas and paste. output should be empty. Search test: search for any name or number that should have been redacted. zero matches expected. Cross-viewer test: open the file in a different PDF reader. Extraction test: run pdftotext or equivalent. Failure of any step means the document is not safe to produce. ### How do I verify a redaction is complete? Beyond the four content tests, also verify metadata (File > Properties or pdfinfo), check headers and footers separately (PII often lives there), inspect any embedded files or attachments, and review the document in a browser-based PDF viewer (some viewers reveal layers that desktop apps hide). For sealed exhibits, also confirm the seal status before production. ### Should opposing counsel be notified of redactions? Usually yes. Standard practice is to provide a privilege log or redaction log identifying what was redacted and the basis (privilege, court order, FRCP 5.2 compliance). Failure to log redactions can be treated as a waiver in some jurisdictions. The log accompanies the production rather than the document itself. ### What happens if a redaction fails after production? Move quickly. Notify the receiving party and request return or destruction of the unredacted version. File a motion to claw back if litigation is active. Notify your malpractice carrier and bar counsel if the failure was material. Most jurisdictions have rules under FRE 502(b) or analogous rules permitting clawback if reasonable steps were taken to prevent disclosure.