BASALT · JOURNAL
Using reason codes in PDF redactions
A redaction reason code answers a question the black bar cannot: why was this particular material withheld? Used consistently, codes make review faster and produce a defensible log. Used casually, they create contradictions between the page and the legal analysis.
Define the codebook before marking
Start with the authority that governs the production—protective order, public-records statute, discovery protocol, privacy rule, or internal policy. Create a short code, a full label, a description, and an owner who can answer interpretation questions.
Do not invent dozens of microscopic categories. Reviewers apply a small, distinct set more accurately than a long list with overlapping meanings. If two codes lead to the same treatment and reporting, consider one code with a note rather than two ambiguous choices.
Keep sensitive text out of the label
The visible overlay might say PII, PRIV, or Ex. 6; it should never repeat the content being removed. Comments and annotation popovers are especially dangerous because they can store the original text invisibly even when the page label is harmless.
For FOIA work, DOJ guidance on marking released records says releasable segregable material should be provided and generally that the amount, location, and exemption for a deletion should be indicated. Other regimes differ, so choose placement and wording from the controlling procedure.
Apply codes at the mark level
A page-level note is not enough when several reasons appear on one page. Store the reason with each redaction mark, then generate the log from those records instead of retyping it later. The log should normally include document ID, page, mark identifier, reason code, reviewer, and review status—never the secret text itself.
Validate consistency
Before release, filter the log by code and sample the corresponding marks. Check for uncoded redactions, codes not in the approved codebook, and the same type of material receiving conflicting treatment. Confirm that visible labels fit inside or beside the mark without covering releasable text.
Combine this with a redaction quality-control workflow and preserve the codebook version with the final log.
Frequently asked questions
Should every redaction have a visible reason?
Not always. Some procedures require visible grounds; others use an internal log only. Follow the controlling authority and keep the internal mark-level reason either way.
Can the redaction label include the removed words?
No. A label or comment becomes part of the released PDF and can recreate the disclosure. Use a neutral approved code.
What belongs in a redaction log?
Usually a document identifier, page and mark reference, reason code, reviewer, and status. Avoid recording the sensitive value unless a separate restricted system specifically requires it.
Doing it in Basalt
Basalt stores a reason with each mark, renders approved labels, and exports the review data to CSV or XLSX while preventing spreadsheet-formula injection. Its verifier checks the final PDF independently, and the entire workflow stays local. See basaltformac.com.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.