Do Word documents still contain comments and tracked changes after they look final?
A Word document can look clean on the page while still carrying comments, tracked changes, hidden text, reviewer names, author fields, custom properties, and other document package parts. This matters before AI upload because the file is more than the visible page.
If the AI task does not need review history, do not send review history. Create a clean copy first.
What comments and tracked changes reveal
Review artifacts can expose:
- Reviewer names and initials.
- Internal legal or HR comments.
- Deleted text that was removed from the visible final version.
- Negotiation notes and unresolved questions.
- Salary, pricing, medical, customer, or employee details.
- Sensitive timing, authorship, and revision patterns.
The visible document may be polished. The package can still reveal how it got there.
| Hidden element | What it can reveal | How to clear it before AI |
|---|---|---|
| Comments | Reviewer names, internal legal or HR notes, unresolved questions | Delete all comments in the editor on a working copy |
| Tracked changes | Deleted text, edits, and who changed what | Accept or reject all changes so no markup remains |
| Hidden text | Content formatted as hidden but still stored in the file | Reveal hidden text in the editor, then remove what should not ship |
| Author and last-modified-by fields | Names of the people who wrote and edited the document | Strip with Metadata Remover |
| Custom document properties | Project codenames, client tags, matter numbers, and internal IDs | Inspect with Metadata Inspector and remove what is not needed |
Inspect the document before upload
Use Metadata Inspector to check DOCX metadata and content-part signals. Look for comments, tracked-change markers, hidden text, custom properties, author fields, and relationship targets. The guide on cleaning DOCX metadata before sharing with AI covers the full review.
If the AI only needs one section, avoid uploading the DOCX at all. Paste a sanitized excerpt into AI Prompt Privacy Checker, automatically detect common sensitive data, review or restore replacements, and manually label anything missed before sharing.
Create a clean copy
For a document that really must be uploaded, work on a copy:
- Accept or reject tracked changes in the editor.
- Remove comments that should not be shared.
- Inspect document properties and hidden fields.
- Strip metadata with Metadata Remover.
- Reopen the cleaned file and verify the visible text.
Do not overwrite the original if review history is part of the record.
Use PDF only after checking the source
Exporting to PDF can reduce some editable document history, but it can also create a new file with its own metadata. If you convert a DOCX to PDF before AI upload, inspect the PDF too.
The safest workflow is deliberate: clean the source copy, export only if needed, inspect the export, and upload only the version that no longer carries the review history.