How Document Metadata Derailed a $2.3B Acquisition
Deal documents carry metadata that can reveal negotiation strategy, advisor identities, and timeline. Here's what M&A teams need to strip before sharing.
The deal room has a leak — and it's in the files themselves
In mergers and acquisitions, every document shared between parties is a strategic communication. Term sheets, letters of intent, NDAs, due diligence requests — each one is crafted to present a specific position. But the metadata embedded in those documents often tells a different story.
Document metadata in deal files can reveal who actually drafted a document, when negotiations began, what the original terms were before they were revised, and which advisors are involved. This information gives the receiving party an asymmetric advantage — one the sending party never intended to provide.
What metadata appears in deal documents
Author and template paths
Every Word document records the author who created it and, in many cases, the file path of the template used. A letter of intent saved from a template at C:\Users\jsmith\Documents\Deals\Acme Corp\LOI Template v3.docx reveals the law firm associate who drafted it, the target company name, and the fact that this is at least the third version of the template — meaning at least two prior deals used similar terms.
In one documented case involving a SPAC filing, the template path embedded in a Microsoft Word document revealed the name of a shell company that had not yet been publicly disclosed. The opposing party's counsel found it in under thirty seconds using standard document properties.
Revision history and tracked changes
Word documents retain tracked changes even after they are "accepted" in the visible document. The underlying XML structure can preserve deleted text, previous versions of key clauses, and the identity of each person who edited the document.
For deal documents, this is particularly dangerous. A term sheet where the purchase price was changed from $18 per share to $22 per share — with the original figure still sitting in the revision XML — tells the buyer that the seller started lower and may accept less.
Timestamps and editing duration
Documents record creation time, last modification time, and total editing time. A letter of intent that was created three weeks before it was sent reveals that the sending party has been considering the deal longer than they claimed. An NDA that shows four minutes of total editing time suggests it was generated from a template with minimal customization — signaling that this may be a standard form rather than a carefully negotiated agreement.
Advisor identification
The "Last Modified By" field and the "Company" field in document properties often reveal which law firm or advisory bank prepared the document. If a buyer sends an LOI and the metadata shows it was last modified by someone at Goldman Sachs, the seller now knows which bank is advising the buyer — information that may not have been disclosed and that affects negotiation dynamics.
Real consequences in deal environments
Shell company exposure
In a 2019 SPAC transaction, a draft registration statement circulated among advisors contained a template path referencing the name of the acquisition target — a company whose involvement had not been publicly announced. The document was shared with a broader group of advisors than intended, and the target's identity leaked before the formal announcement. The deal closed, but at revised terms after the target lost negotiating leverage.
Negotiation strategy revealed
A mid-market private equity acquisition in 2021 involved a purchase agreement where tracked changes had been accepted but not fully purged from the XML. The seller's counsel extracted the revision history and discovered that the buyer's initial internal draft had included an earnout provision that was removed before the document was shared. This gave the seller insight into the buyer's willingness to include performance-based components — information that influenced the final deal structure.
Timeline manipulation discovered
In a cross-border acquisition, the buyer claimed they had only recently become interested in the target. The metadata on their initial letter of intent showed a creation date six months prior to the first official contact. This discrepancy raised concerns about whether the buyer had been trading on material non-public information, triggering an internal compliance review that delayed the deal by three months.
What M&A teams should strip before sharing
Every document leaving the deal room needs cleaning
The following metadata fields should be removed from every document shared externally in a deal context:
- Author and Last Modified By — Remove individual names and replace or clear
- Company field — Remove advisory firm identification
- Template path — Remove all file system paths
- Tracked changes — Accept and then purge from XML, not just from the UI
- Comments — Remove all comments, including resolved ones
- Timestamps — Consider whether creation and modification dates should be normalized
- Custom properties — Remove any custom document properties that may contain deal codes or internal references
- Embedded objects — Check that embedded Excel charts or images do not carry their own metadata
NDAs and LOIs deserve special attention
NDAs are often the first document shared between parties, before any trust is established. They are frequently adapted from templates used in prior deals. The template metadata — file paths, previous author names, prior deal references — is particularly dangerous in NDAs because the recipient has no existing relationship and every reason to extract whatever intelligence they can.
Letters of intent carry similar risks. They are strategic documents where the metadata can directly contradict the stated negotiating position.
The systematic approach
Manual metadata removal does not scale in a deal environment where dozens of documents are exchanged weekly. Deal teams need a systematic approach: scan every document for metadata before it leaves the deal room, remove all identified fields, and verify that the output is clean by re-scanning.
The cost of metadata leakage in an M&A context is measured in millions — in revised deal terms, lost leverage, delayed closings, and compliance investigations. The cost of cleaning documents before sharing is measured in seconds.
Purgit scans documents at the structural level, identifying and removing metadata fields that manual inspection misses. Upload a document to see what hidden data it carries before you share it.
[Scan a File Free]