The Consulting Proposal Metadata Problem: What You're Accidentally Revealing
Consultants routinely adapt proposals from previous engagements. The metadata left behind can reveal previous clients, pricing, and internal notes.
The template reuse problem
Management consultants, accountants, financial advisors, and professional services firms reuse proposal templates. This is standard practice and entirely sensible. You developed a strong proposal for one engagement, the next prospect has a similar need, and you adapt the existing document rather than starting from scratch.
The problem is that the adapted document carries metadata from the original. Unless you specifically address this, the proposal you send to Prospect B contains invisible evidence of Prospect A — their name, their pricing, their scope, and the internal discussions that shaped the original document.
This is not a theoretical risk. It happens routinely, and most firms never learn about it because the recipients who notice rarely say anything. They simply use the information.
What each metadata field reveals
Author and Last Modified By
The Author field in a Word document records the name of the person who first created the file. The Last Modified By field records who most recently edited it.
Risk scenario: A proposal sent to a prospective client shows the Author as "Sarah Chen" — who left the firm two years ago. The prospect searches LinkedIn, finds that Sarah now works at a competitor, and questions whether the firm has the current capacity to deliver the work.
Risk scenario: The Author field shows a name from the prospect's own competitor. This reveals that you prepared a similar proposal for that competitor, which may violate confidentiality expectations from the prior engagement.
Company field
Word stores the Company field from the system settings where the file was created.
Risk scenario: Your firm uses subcontractors to prepare deliverables. The Company field shows the subcontractor's name rather than your firm's name. The prospect now knows your staffing model.
Template path
Word documents store the path to the template (.dotx) used to create them. This path is part of the document's internal metadata.
Risk scenario: The template path reads C:\Users\jmiller\Documents\Proposals\AcmeCorp_Digital_Transformation_2024.dotx. Your prospect can now see that this proposal was adapted from work prepared for AcmeCorp.
Revision history
Word documents can retain revision history even after tracked changes are accepted. The internal XML structure stores revision session identifiers (rsid values) and may retain deleted text.
Risk scenario: Your proposal includes a pricing section. The revision history shows that the original pricing was 30% lower for the previous client's similar scope. Your prospect now has leverage in fee negotiation that you did not intend to provide.
Comments
Comments in Word documents persist in the file's XML even if they are resolved or deleted from the visible document. Resolved comments are particularly dangerous because the author may believe they have been removed.
Risk scenario: A partner's comment reads: "This client probably won't push back on pricing — they're desperate to move fast." The prospect reads this in the metadata and the relationship is damaged before it begins.
Custom properties
Word supports custom document properties — key-value pairs that firms sometimes use for document management system integration, matter numbering, or internal classification.
Risk scenario: Custom properties include MatterID: 2024-0847 and ClientCode: WIDGETCO. Your prospect can infer the previous client and the internal matter number from your DMS.
The pricing transparency problem
Pricing metadata deserves special attention. When you adapt a proposal from a previous engagement, the original pricing may persist in multiple places:
- Tracked changes that show deleted pricing figures
- Comments discussing pricing strategy
- Hidden text that was formatted as hidden rather than deleted
- Excel objects embedded in the proposal that contain full pricing models with the original client's figures
If your prospect discovers that you charged a previous client less for comparable work, the negotiation dynamic changes. If they discover you charged more, they may question your value proposition. Either way, the information was not meant to be shared.
A clean process for proposal preparation
Step 1: Start from a clean template
Rather than duplicating a previous proposal, maintain a set of clean templates with no client-specific metadata. These templates should have:
- Generic Author and Company fields
- No comments, tracked changes, or revision history
- No custom properties from previous engagements
- Template paths that do not reference client names
Step 2: Copy content, not files
When adapting from a previous proposal, copy the text content into the clean template rather than editing the previous file. This breaks the metadata chain from the original document.
Step 3: Scrub before internal review
Run metadata inspection before the document enters internal review. This catches inherited metadata early, before the review process adds its own layer of comments and tracked changes.
Step 4: Scrub after final approval
After the proposal is finalized and all tracked changes are accepted, run metadata inspection again. The review process adds new metadata — reviewer names, comments, edit timestamps — that also needs to be removed before external sharing.
Step 5: Verify the output
After removing metadata, re-scan the document to confirm that removal was successful. This verification step catches cases where metadata removal tools miss fields or where the removal process itself adds new metadata.
What about PDF conversion?
Converting a Word proposal to PDF before sending does not solve the metadata problem. The PDF inherits metadata from the Word source:
- Author, Company, and Title fields carry over
- The Creator field identifies the conversion software
- The Producer field identifies the PDF engine
- If the Word document contained comments or tracked changes at the time of conversion, some PDF converters embed that data in the PDF structure
PDF conversion changes the format but does not clean the metadata. You need to scan and clean the PDF after conversion, not assume that the format change handled it.
Firm-level recommendations
For professional services firms that send proposals regularly:
- Standardize the proposal creation workflow so that every proposal starts from a clean template, not a duplicated client file
- Configure Word profiles on shared systems with generic author and company information
- Add metadata scanning to your pre-send checklist — the same way you check for typos and formatting, check for metadata
- Educate proposal teams on what metadata is, where it hides, and why it matters. Most metadata leaks happen because the person preparing the document does not know the risk exists
Purgit scans proposals and professional documents for hidden metadata — author names, company fields, template paths, revision history, and embedded comments. It removes findings at the structural level and verifies removal before you send.
[Scan a File Free]