How to justify redactions: a reason on every cover
A blacked-out passage invites one question: why is it missing? If you can’t answer at once, the redaction looks arbitrary, even when it isn’t. Here’s how to justify redactions: give each cover its reason, put that reason where the reader sees it, and keep a record for the file. Information-access law requires public authorities to give the reasons for withholding information, and guidance asks for them passage by passage. For contracts and case files, it’s how you show that you removed only what you had to.
How to justify redactions: why every cover needs its reason
A cover without a reason says only that something is gone. The reader can’t tell a third party’s name from a bank detail, or a legal exemption from a slip. So they ask, they complain, or they assume the worst.
A reason answers the question before anyone asks it. It also keeps the redaction honest. If you can’t name the reason for a cover, the passage may not need covering at all.
What information-access law expects
In the UK, a public authority that withholds information under the Freedom of Information Act 2000 must give the requester a notice. The notice specifies the exemption and states, if that isn’t otherwise apparent, why it applies (FOIA s. 17(1)). The ICO goes a step further, as good practice rather than statute: “If possible, indicate which sections you removed using which exemption” (ICO, refusal notice). The National Archives’ redaction toolkit asks you to record the reason for each non-disclosure, with every exemption that applies.
In Germany, a written administrative decision must state the essential factual and legal reasons behind it (§ 39(1) VwVfG). Under the federal Freedom of Information Act, the grounds for withholding information are set out in §§ 3 to 6: special public interests, the authority’s decision-making process, personal data, and intellectual property and trade secrets (IFG).
The detail for each country: redaction reasons under the German IFG and FOI redaction exemption codes in the UK.
Your own reasons for contracts and case files
Outside information-access requests, no statute dictates the label. You choose wording the reader understands at a glance, such as “Third-party personal data”, “Bank details” or “Not part of this matter”.
Three habits make reasons useful:
- One wording per kind of data. The same reason for the same thing, throughout the document, so the reader can match covers to reasons.
- Short over clever. A reason fits on the cover and reads in a second.
- A reason you’d defend. If someone challenges it, you can explain it in a sentence.
Answering a data subject access request, where other people’s data is covered? See subject access request redaction.
How to put the reason on the cover
In Dress Docs, each cover can carry its reason, printed on the cover. Write your own, or use a standard exemption set for information-access requests (FOI and IFG). Either way, the reason is your decision; check it against the law and your own policy.
On export, the reason becomes part of the flattened page image. It travels with the copy, and it doesn’t make the cover any thinner: the content under it is gone from the file, as with any cover (why a black box isn’t enough). Dress Docs then shows that the file has no text layer and empty metadata. What else an export removes: the metadata you forget to remove.
Keep the record: the redaction log
Reasons on the page answer the reader. Your file needs its own record. The redaction log lists covers, reasons, pages and date, and holds no document content. You can file it without creating a second copy of what you removed. You save it to your own files.
What a good log holds, and what it must not: the redaction log.
Reasons and the log are in Pro
Reasons on covers, the redaction log and search and cover are in the Pro, Team and Organization plans. Free does the redaction itself: solid covers, flattened export, metadata removal and the export check, with no account.
See everything on the features page, compare plans on pricing, or start Pro.