The Lawyer Sent the Contract as DOCX. Opposing Counsel Could Read Every Deleted Clause.
In 2004, the SCO Group filed a breach-of-contract lawsuit. The Word document they submitted still contained tracked-changes metadata showing the original defendant in the lawsuit was Bank of America. Someone had done a find-and-replace on the company name without stripping the revision history. Opposing counsel could see the document's entire editing history. The mistake was not in what the document said on its face. The mistake was in what the DOCX file contained beneath the visible text.
Track Changes is a feature of Microsoft Word that records every edit made to a document while tracking is active. When tracking is turned off and all changes are accepted, the document appears clean to anyone reading it normally. But the revision data does not disappear. It remains in the file, accessible to anyone who opens the DOCX in a capable viewer or renames the file to .zip and reads the XML directly. Deleted text that was accepted away is still in the file, marked as accepted but present.
This is one of several categories of metadata that DOCX files carry that have no place in a document shared externally. Author name, organization name, edit time, comment threads, and revision history all travel with a DOCX file. None of this metadata appears when the document is converted to PDF. A PDF contains the visible document. It does not contain the document's history.
What DOCX Files Contain That Most People Do Not See
A DOCX file is a ZIP archive containing multiple XML files. The main document content is stored in word/document.xml. Anyone with a computer can rename a .docx file to .zip, open it, and read any of these XML files directly.
The document.xml file contains every tracked change that was ever made while track changes was active. This includes text that was deleted, text that was inserted, and the author attributed to each change. If a lawyer drafted a contract, made fifteen edits across two weeks of negotiation, and then accepted all changes before sending the document to the other party, all fifteen rounds of edits are visible in the XML to anyone who knows where to look. The visible document shows the final agreed text. The XML shows what was proposed, what was rejected, and who made each suggestion.
Comments are similarly persistent. A comment added to a document and then deleted from the interface may leave its XML element behind in the file. The document properties stored in Word files include the author's name, the organization name registered in the Office installation, and the cumulative total editing time for the document.
The Specific Risk in Legal and Commercial Contexts
The SCO versus DaimlerChrysler case is one of the more visible examples, but the pattern is common. Law firms, consulting firms, investment banks, and anyone who uses Word to draft documents that are then negotiated, revised, and sent to counterparties faces this risk every time they send a DOCX file.
Contract negotiation involves proposing positions, having them rejected or modified, and ultimately reaching agreed terms. The negotiating history, the positions taken and abandoned, and the internal thinking about acceptable ranges and fallback positions, is precisely the information that parties try not to share with each other during negotiation. A DOCX file that carries the full revision history of a negotiated contract can expose all of this.
In employment matters, severance agreements drafted in Word and sent as DOCX files have contained revision history showing original offers, internal notes about the employee's performance, and legal strategy comments. In mergers and acquisitions, term sheets sent as DOCX files have contained tracked changes showing the drafter's calculations and fallback positions.
The problem is that the accepted-changes version of a document looks clean. There is no visible indication to the sender that the XML still contains the full revision history. It looks like a finished document. It is a finished document with an attached negotiation diary.
What PDF Does Differently
A PDF generated from a DOCX file contains the rendered content of the document at the moment of conversion. It does not contain XML. It does not contain tracked changes. It does not contain revision history, author names from document properties, comments that were deleted in the Word interface, or any of the other embedded data that travels with a DOCX file.
Converting to PDF before sharing externally eliminates this entire category of risk. The recipient receives a document that shows exactly what you intended to share, with no access to the document's history, the author information in the file properties, or any comment or revision data.
This is the most important reason to convert DOCX to PDF before sharing legal documents, contracts, agreements, and any document that went through a drafting or negotiation process. It is not just about format consistency or preventing edits. It is about ensuring that the document you send contains only what you can see in the document.
Other Metadata Risks in DOCX Files
Beyond tracked changes, DOCX files carry several other categories of metadata that professional senders should be aware of.
The document properties include author name, organization, last modified date, and total editing time. The author field is set by the Word installation and may reflect the name of whoever installed Office on the machine, which may not be the person who sent the document. In legal contexts where authorship of a document is disputed, these properties have been used as evidence.
Custom XML data and content control tags can be embedded in Word documents by forms or document management systems. These tags may contain internal codes, database references, or workflow information that was never intended for external recipients.
Embedded objects, including Excel spreadsheets linked in a DOCX, can contain data that is not visible in the document but is accessible to anyone who inspects the embedded object. A financial model embedded in a contract as a linked table may expose calculation assumptions and underlying data ranges.
The Three-Second Fix
Converting a DOCX to PDF before sending it takes seconds and eliminates every one of these risks. The process strips all embedded metadata, tracked changes, comment history, and document properties from the output. The PDF contains the visible document and nothing else.
For organizations that regularly share Word documents externally, adding convert to PDF before sending to the checklist is a low-friction, high-impact change. The document still looks the same to the recipient. The difference is entirely in what is not visible: no negotiating history, no internal author information, no revision diary attached to every document that leaves the building.
Microsoft's Document Inspector tool can also find and remove metadata from within Word before sending the DOCX, but converting to PDF is simpler and more reliable: it produces a format that structurally cannot contain the metadata categories that DOCX carries.
Conclusion
A DOCX file is a ZIP archive of XML files. The visible document is only part of what is in the archive. Track changes, comments, author names, revision history, and editing metadata all travel with the file and are accessible to anyone who knows where to look. This is a known risk that has caused real damage in legal and commercial contexts.
ToolHQ's DOCX to PDF converter processes files securely on the server and deletes them immediately after conversion, producing a PDF that preserves the visual formatting of the Word document while containing none of the embedded metadata that makes DOCX files a liability when shared externally.
Frequently Asked Questions
Can people really see my tracked changes if I accept all before sending?
Yes. Accepting all changes marks them as accepted in the XML but does not delete the revision history from the file. Anyone who opens the DOCX in an XML viewer or renames it to .zip can read the full editing history.
Does converting to PDF remove all Word metadata?
Yes. PDF conversion renders only the visible document content. Tracked changes, revision history, author names, comments, and document properties from the DOCX are not included in the PDF output.
Is it sufficient to use Document Inspector in Word before sending?
Document Inspector can remove most metadata categories but requires you to run it explicitly and select the right categories. Converting to PDF is simpler and structurally eliminates all DOCX-specific metadata.