Published on August 22, 2026 · 8 min read
Most redaction failures aren't dramatic. Nobody needs to break the software. Usually it's just someone in a hurry who took a shortcut and assumed the document was clean.
Here are five mistakes that come up again and again.
This is the most common one. Someone opens the document, finds the sensitive passage, and draws a black rectangle over it. It looks fine at a glance. But the text is still in the file, just underneath the shape.
In Word and most other editors, a black shape sits on top of the text. Anyone who selects the area and copies can paste the hidden text somewhere else. In some cases, changing the font color or converting the file to another format reveals it too.
The fix: delete the text, don't cover it. If you want the reader to see that something was removed, replace it with [REDACTED] after deleting. Visually it's the same result — but there's nothing left to recover.
You go through the whole document, remove every name and ID number, save, and send. Everything you can see looks fine. The problem is in the parts you can't see.
Office files store the original author, the company name, the last person who saved the file, revision history, and often the first draft's path on disk. PDFs store author names, software version, creation and modification timestamps. Images carry GPS coordinates and device info.
A recipient who opens the file properties can see all of it. In some cases, the metadata contains information that isn't in the document at all — a department name, an internal project code, or the name of the person who drafted it.
Before sending any document, check the file properties. In Office, use "Check for Issues" → "Inspect Document" → remove what you don't want. For PDFs, Acrobat has "Remove Hidden Information". For images, strip EXIF before sharing.
After you finish redacting, open the file again. Not the source document — the exported one that you're about to send.
Read it as if you were the recipient. Look for anything that shouldn't be there. Open the file properties. Search for the sensitive terms you removed, in case one instance was missed. Check the comments panel in PDFs.
This step gets skipped a lot, usually because people are short on time. The cost shows up later, when a leak is discovered after the file has already left your control.
The filename goes out with the file. Contract_AcmeCorp_Dispute_Final.docx already tells the recipient who it's for and what it's about, before they open it.
Even if the body text is completely clean, the filename gives context. If the file is about a dispute, a settlement, or a specific client, the name is enough to cause a problem.
Rename to something neutral before sending. Contract.docx, Document.docx, Attachment_01.docx — anything that doesn't describe the content.
Phone numbers, IDs, and emails show up in more than one format in the same document. If you search for one format and stop, the other variations stay.
A phone number might appear as (555) 123-4567, 555-123-4567, or 5551234567. An email might be written in full, or just as the domain. IDs might have or not have dashes. This is exactly what pattern-based tools are for — a single rule can match all the variations.
If you're working by hand, at least search for the main variants: with and without spaces, with and without area codes, with and without separators. It's not a complete fix, but it catches more than a single search would.
Each of these, on its own, is easy to handle. The hard part is doing all five, every time, without slipping.
DocRedactNow automates most of them. It deletes the content instead of covering it. It strips metadata from Office files, PDFs, and images. It renames files on export if you configure that. It matches format variations through pattern rules. And it produces a log of what was changed, so you can review before sending.
14-day free trial, full features. Everything runs locally — no uploads, no network calls.
Try DocRedactNow free for 14 days.
⬇️ Download Free Trial