BASALT · JOURNAL
A repeatable batch redaction workflow on Mac
Batch redaction saves time only when the rule is repeatable. A good workflow combines a defined data inventory, consistent searches, human review for exceptions, and a verification pass over every output.
Define the rule before opening files
List the identifiers and categories to remove, including alternate formats and OCR variants. Decide which pages may be omitted, which values must remain, and when a reviewer should escalate a document. Use a stable output naming convention that never overwrites sources.
Automate candidates; review exceptions
Search every file for known patterns, then review matches in context. Scanned pages, handwritten notes, tables, barcodes, and images need visual inspection. Keep a record of files processed, exceptions, and verification status rather than relying on a folder full of similarly named exports.
Verify the batch
Check that every expected output exists, opens, has the correct page structure, and no longer exposes the target values. Sample the visual result and inspect attachments and metadata. A failed file should be quarantined for review instead of silently entering the delivery set.
Frequently asked questions
Is batch redaction fully automatic?
No. Automation can find candidates, but context and images still need human review.
How should failed files be handled?
Keep them out of the release set, record the reason, and send them through a manual workflow.
Should every output use the same redaction mark?
Consistent marks help review, but the important control is permanent removal and verification.
Doing it in Basalt
Basalt keeps batch PDF work local and combines candidate search with destructive redaction and verification for repeatable Mac workflows. Download Basalt.
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.