BASALT · JOURNAL
How to redact a police report PDF for release
Police reports combine structured fields with free narrative, which makes them harder to redact than a form. The same person can appear as a name on page one, initials in a supplement, a voice in a transcript, a plate in a photograph, and an address in an officer's narrative.
The disclosure decision belongs to the applicable public-records law, court order, and agency policy. This article addresses document production, not which information may lawfully be withheld.
Turn the decision into a review list
For each approved withholding, record the value or region, the reason code, and whether the reason should appear on the released page. Separate deterministic identifiers—names, dates, report numbers, phone numbers—from contextual material that requires a reviewer to read the narrative.
Search every known value in its likely formats. Plate numbers may contain spaces or hyphens; dates can be numeric or written out; names may appear as surname-first, initials, or misspellings. Search supplemental reports as well as the incident report.
Review what text search cannot see
Scanned forms may have an OCR layer, but handwriting and faint carbon copies routinely escape recognition. Photographs can show faces, house numbers, screens, plates, tattoos, and documents lying in the scene. A black rectangle over a photo is not sufficient unless the underlying pixels are actually changed.
Barcodes and QR codes deserve their own pass. They can encode an identifier that is unreadable by eye and remain scannable under a translucent or poorly aligned mark. Redacting barcodes and QR codes covers that workflow.
Make the reason visible without leaking content
Public-records procedures often require the amount and location of a withholding and its legal basis to be apparent. For federal FOIA releases, DOJ guidance on segregating and marking records explains the duty to provide reasonably segregable material and generally mark the exemption at the deletion. State rules differ. Use the exact labels your policy specifies, and never place original text into a redaction note or annotation.
Verify the release copy
Reopen the finished file independently and search for the review list. Inspect metadata, comments, attachments, form fields, hidden layers, and prior revisions. Confirm that every visible reason corresponds to the review log and that no unapproved area was removed. A second reviewer should sample or fully review based on the release risk.
Frequently asked questions
Can software decide what to redact from a police report?
Software can find likely identifiers, but it cannot reliably decide legal exemptions or contextual harm. A trained reviewer must make and document the withholding decision.
Are photographs in a police report searchable?
Not reliably. OCR may find clear printed text, but faces, plates, tattoos, screens, and handwritten material require visual inspection and pixel-level redaction.
Should redaction reasons appear on the released page?
That depends on the governing law and agency procedure. Use approved reason codes and verify that the label itself contains no sensitive text.
Doing it in Basalt
Basalt combines whole-document search, on-device PII suggestions, image and OCR-layer redaction, visible reason labels, and a review log. Its verifier reopens the output and blocks the save if removal cannot be proven. The document engine has no network entitlement. Learn more at 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.