BASALT · JOURNAL
Redacting due-diligence documents for a data room
Due diligence creates a volume problem and a judgment problem at once. Hundreds of documents must be made available quickly, yet the correct redaction depends on deal stage, requester, clean-team rules, employee privacy, customer commitments, and competitive sensitivity.
Build rules by document family
Group files into contracts, employee records, customer reports, financial statements, board materials, IP records, and litigation documents. Give each family a written rule set, reviewer, escalation path, and output naming convention.
Use a manifest with source hash, family, confidentiality tier, page count, reviewer, exceptions, output hash, and data-room destination. This controls scope better than relying on folders alone.
Minimize and process locally
Remove unnecessary pages and attachments before detailed review. Search common entities, codenames, domains, personal identifiers, account numbers, rates, and pricing. Then review tables, diagrams, and narratives for context.
Uploading an unredacted file to a web redaction service creates an additional disclosure before the data room is involved. Use an approved environment; local processing avoids that transfer.
Verify batches and access tiers
Apply destructive redaction and whole-document sanitization, then verify every output automatically and sample visually by risk. Check that filenames and folder names do not reveal removed information. Where the data room has staged permissions, generate separate artifacts for each tier rather than assuming viewer controls substitute for redaction.
Reverify after watermarking or combining, because those operations create new bytes. Preserve a release manifest so the team can answer exactly which version reached which audience.
Frequently asked questions
Can one redacted copy serve every bidder or deal stage?
Often not. Different recipients and stages may have different permissions, so create and track distinct release artifacts.
Are data-room permissions a substitute for redaction?
No. Access control limits who can open a file; it does not remove information from a file an authorized viewer downloads or sees.
How do I handle hundreds of PDFs consistently?
Use document-family rules, named presets, batch verification, manifests, and risk-based second review rather than ad hoc editing.
Doing it in Basalt
Basalt runs batch OCR, redaction, sanitization, Bates numbering, watermarking, and compression as named local presets with a preview of the safe step order. It verifies each output and records manifests without uploading source documents. 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.