BASALT · JOURNAL
How to redact an incident report PDF
Incident reports often combine a narrative with witness names, contact details, photographs, employee IDs, and location data. A safety review may need the sequence of events without exposing every person mentioned.
Define the audience and purpose
Decide whether the copy is for an insurer, regulator, employee, client, or internal review. Keep dates, times, locations, and factual findings needed for the purpose. Redact personal phone numbers, home addresses, medical details, and unrelated witnesses unless disclosure is required.
Review narrative and attachments
Search names and identifiers in the narrative, headers, footers, captions, and appendices. Inspect photographs for visible badges, license plates, and screens. Check comments, attachments, OCR text, and form fields; incident reports are often assembled from several sources.
Preserve the audit copy
Never edit the original investigation file. Export a separate release copy and record what was removed for internal review. Reopen the PDF, search for redacted terms, inspect page images, and remove metadata that could reveal the author or file path.
Frequently asked questions
Should witness names be redacted?
Redact them when the recipient does not need identities, especially if the report is being shared outside the investigation.
Do photographs need redaction?
Yes. Faces, badges, plates, screens, and handwritten notes can contain identifying information.
Is a redaction log useful?
Yes. A private log records the reason and scope of each redaction without placing the sensitive value in the released PDF.
Doing it in Basalt
Basalt redacts incident narratives and scanned attachments locally, strips hidden file content, and verifies the final PDF before export. 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.