What a redaction QA report is, and why to keep one
When somebody asks, six months later, whether a document was properly blacked out before it went, the usual answer is that somebody remembers doing it. A redaction QA report is the alternative: a short record, made at the time, of what was taken out, what was checked, and what each check found.
What it contains
- What was removed, and from which pages. How many areas were covered and where, so the scope of the work is on the record rather than in somebody's memory.
- Which checks ran, and what each returned. Any text left in the file, earlier versions, document properties, attachments, bookmarks, page thumbnails, form fields, embedded scripts, and whether every box was painted solidly where it was meant to be.
- The method used. Which approach produced the file, because that determines which failures were possible in the first place.
- When it was done.
What it does not contain is any of your document. No covered words, no page images, no surrounding text. A report that quoted what was removed would be a second copy of the thing you were protecting, which is why this one counts occurrences and names checks rather than reproducing content.
What it is for
Answering the question later. Redaction questions surface long after the file has gone, usually because something else went wrong and somebody is retracing steps. A record made at the time is worth more than a recollection formed under pressure.
Handover. Where more than one person touches a document, the next person can see what was already done rather than redoing it, or worse, assuming it was done.
Catching your own near misses. A report that says a check was skipped, or that a page had no text layer and could not be searched, is a prompt while you can still act on it.
Showing your working to a client. Attaching a one-page record to the delivery says more about care taken than an assurance does, and costs nothing to produce.
What it is not
It is not a certificate, and it does not make anyone compliant with anything. Compliance is a property of a whole process rather than of a document, and no file can confer it.
It records what a particular set of checks found in a particular file on a particular day. It cannot tell you that you covered the right words, and where a page has been rebuilt as an image it cannot see what that image shows. Those remain yours to judge, and a report that implied otherwise would be worse than none.
Where to get one
Redaction Studio writes one for every file it produces. After it builds the redacted PDF it reopens its own output, runs the checks against it, and reports what it found — and if any check fails, it gives you the explanation instead of the file, because a refusal you can act on is more use than a file you cannot trust.
For a document somebody else redacted, the free checker produces the same kind of record from the file alone. What each check looks for is set out in how do I know my redaction actually worked. You can keep that beside a document you received as easily as one you made.
Both run entirely in your browser. The report is generated on your machine from a file that never leaves it.
Keep the record with the job
Check a document and keep the report — free, no account, nothing uploaded.