Why Track Changes Gets Turned Off (And What to Do About It)
You sent a contract draft with Track Changes turned on. The other side sends it back. You open the document. It looks clean. No red markup, no strikethrough, no margin comments. Just a smooth, polished document.
Maybe they accepted all changes to give you a clean read. Maybe they started fresh in a new template. Or maybe Track Changes was turned off at some point during their editing process, and the changes they made are simply invisible.
You have no way to tell which scenario it is by looking at the document. Word does not flag the difference. The document looks the same in all three cases: clean, final, ready for review.
This is not a theoretical risk. It happens in routine contract negotiations, and when it does, the changes made while tracking was off become invisible in the revision history. They are in the document. They affect the terms your client will be bound by. But they do not appear in any Track Changes markup, and unless you run an independent comparison, you will not know they exist.
This post covers why Track Changes gets turned off, how to detect it, what to do when you discover untracked changes, and why independent comparison should be your standard practice rather than a fallback.
Why Track Changes gets turned off
The natural assumption when you receive a contract without Track Changes markup is that something adversarial happened. Someone deliberately turned off tracking to hide edits. That does happen. But it is far less common than the mundane, accidental reasons that tracking gets disrupted in normal contract workflows.
Understanding the common causes matters because it changes how you think about the problem. This is not primarily a bad-faith issue. It is a workflow reliability issue. Track Changes is fragile. It depends on every person who touches the document keeping tracking enabled, and on every workflow step preserving the tracking state. In a multi-party, multi-round negotiation, the probability that tracking remains unbroken across every touchpoint is lower than most lawyers assume.
Someone accepts all changes to "start clean"
This is the single most common cause of lost tracking in contract negotiations. A reviewer on the other side opens your redlined draft. The document is dense with markup from prior rounds. They want to work from a clean view. So they click "Accept All Changes" to clear the slate, intending to turn Track Changes back on and make their edits fresh.
Except they forget to turn it back on. Or they turn it on partway through their review, after they have already made edits to three sections. Or they turn it on, but someone else on their team opens the document later and turns it off without realizing it was supposed to stay on.
The result: a document that looks like it was edited with tracking, but the tracking record is incomplete. The edits made before tracking was re-enabled are in the document but invisible in the markup. There is no indication that a gap exists.
The counterparty deliberately turns it off
This is the scenario that gets the most attention, even though it is the least common. A party to the negotiation intentionally disables Track Changes, makes substantive edits, and re-enables tracking (or sends the document back without tracking at all). The intent is for the other side to review the visible tracked changes while missing the untracked ones.
It is worth acknowledging that this happens. It is also worth acknowledging that it is difficult to distinguish from the accidental scenarios. When you discover untracked changes, you rarely know whether they were hidden intentionally or lost through workflow friction. The response should be the same regardless: document the discrepancy, raise it with the other side, and compare independently going forward.
Multiple editors with inconsistent settings
A partner reviews the substantive terms with Track Changes on. They save the document and pass it to an associate for the boilerplate sections. The associate opens it and, without checking whether Track Changes is enabled, starts editing. Maybe tracking is still on. Maybe the associate's Word settings default to tracking off. Maybe the associate opened a different copy of the file.
In firms with three or four people touching the same document in a single review cycle, the chain of Track Changes custody is long. Every handoff is a point where tracking can be lost. And nobody checks. They assume whoever had the document last left Track Changes in the right state. That assumption is wrong often enough to matter.
Document converted between formats
Format conversions are one of the most reliable ways to lose Track Changes history. When a Word document is converted to PDF and back to Word (common when a party only has the PDF version of a prior draft), the Track Changes history is lost entirely. The resulting Word document has no tracking metadata at all.
Google Docs to Word conversions have a similar problem. Google Docs has its own "Suggesting" mode, which is roughly analogous to Track Changes but implemented differently. When a Google Doc is exported to .docx format, the suggestion history may or may not survive the conversion, depending on the export method and the complexity of the document. Edits made in standard editing mode in Google Docs (not Suggesting mode) have no Track Changes equivalent at all in the exported Word file.
Even Word-to-Word conversions between different versions of the format can occasionally disrupt tracking metadata, particularly when the document uses complex features like nested tables, content controls, or structured document elements.
Template swap: content pasted into a new template
This is a variation of the format conversion problem, but it deserves its own section because it is so common in contract negotiations. Each side typically has their own firm template, and it is standard practice for the counterparty to take your contract draft and paste the content into their template before sending it back.
The template swap process almost always breaks Track Changes. Depending on how the content is transferred (copy-paste, Save As with template change, third-party conversion tool), the tracking history may be stripped entirely, partially preserved, or reconstructed in a way that does not accurately reflect the actual editing history. Style definitions from the new template get applied, which can change formatting, numbering, and even paragraph structure. These changes are real differences between your version and theirs, but they will not appear as tracked changes.
The counterparty may not even realize that their template swap introduced changes beyond formatting. If their template has default boilerplate for certain sections (a standard arbitration clause, a default governing law provision), the swap might overwrite the negotiated language with the template default. That is a substantive change introduced by a process that nobody thinks of as "editing."
Macro or automation that resets document settings
Some firms use document automation tools, macros, or templates that include scripts for document preparation. These tools can reset Track Changes settings as a side effect of other operations: applying firm styles, cleaning up metadata, preparing a document for external distribution, or running a document assembly workflow.
The person who triggered the macro may not know that it turned off Track Changes. The macro ran, the document was processed, and the settings were reset silently. If the user does not manually verify that Track Changes is still enabled after the macro runs, the next round of edits will be untracked.
This is particularly common with metadata-scrubbing tools. Many firms strip metadata from documents before sending them to opposing counsel (to remove internal comments, author information, and revision history). Some metadata scrubbers also reset the Track Changes state as part of the cleanup process, since Track Changes markup itself is metadata that reveals the editing history.
The risk: invisible changes in the contract
The practical consequence of Track Changes being turned off is straightforward: changes made while tracking was off exist in the document but are invisible in the revision history. They look like original text. They have no markup, no highlighting, no attribution. When you review the document using Track Changes, you see the changes that were tracked. You do not see the changes that were not.
This creates a specific kind of risk that is different from other contract review failures. When Track Changes shows you a change, you evaluate it. You might accept or reject it. You might negotiate further. But at least you know it exists. When a change is untracked, you do not evaluate it at all. You do not accept or reject it. You do not even know it is there. It passes through your review entirely unexamined.
The types of changes that are most dangerous when untracked are the ones that are hardest to spot by reading:
- Single-word substitutions that change the meaning of a clause. "Shall" becomes "may." "Including" becomes "excluding." "Reasonable" disappears from "reasonable best efforts." These changes are invisible in a 40-page contract unless you are reading word-by-word against the prior version.
- Deleted carve-outs or exceptions. A limitation of liability has an exception for "gross negligence and willful misconduct." The exception is removed. The paragraph reads smoothly without it. Unless you remember that the exception was there, you will not notice it is gone.
- Changed numbers. A cure period goes from 30 days to 10 days. A liability cap goes from $5 million to $500,000. A termination notice period changes from 90 days to 30 days. These are substantive commercial changes that are invisible when untracked because the surrounding text is identical.
- Added or removed definitions. A defined term is added that narrows the scope of an obligation. Or a definition is removed, leaving an undefined term that will be interpreted broadly in a dispute. Changes to the definitions section affect every clause that uses the defined term, but they are far from those clauses in the document.
- Reordered sections with cross-reference changes. Sections are renumbered, and cross-references are updated to point to different sections than in the prior version. The text of each section may be unchanged, but the relationships between sections have shifted.
None of these changes would raise a flag during a normal Track Changes review, because they are not in the Track Changes record. They would all be caught by an independent comparison, because an independent comparison does not rely on what was tracked. It compares what is actually in the two documents.
How to detect that tracking was off
The challenge with detecting a tracking gap is that Word does not tell you one occurred. There is no "Track Changes was disabled from 2:15 PM to 3:42 PM" log entry. There is no warning banner. The document looks the same whether tracking was on continuously or off for half the editing session.
That said, there are indirect signals that suggest tracking may have been interrupted. None of them are definitive on their own, but they should trigger a closer look.
The document looks "too clean"
You sent a heavily marked-up contract. The other side returns it with no tracked changes, or with only a handful of minor formatting adjustments. The substantive provisions you expected them to push back on are unchanged. The sections that were contentious in prior rounds show no edits.
This could mean they agreed with everything. It could also mean they accepted all changes, edited the document with tracking off, and returned a version that appears unedited but actually contains modifications. The cleanliness of the document, relative to what you expected, is the first clue.
This is a judgment call, not a rule. But if the Track Changes record does not match the scope of the negotiation (i.e., you expected pushback on multiple provisions and the document shows zero changes to those provisions), it is worth running a comparison to verify.
Metadata inconsistencies
Word stores metadata about the document: total editing time, number of revisions, last saved date, and so on. If the document shows significant editing time (hours of editing across multiple sessions) but very few tracked changes, the arithmetic does not add up. Someone spent time editing the document, and the tracked changes do not account for that time.
To check this in Word: go to File, then Properties (or Info, then Properties). Look at Total Editing Time and Revision Number. Compare these against the volume of tracked changes in the document. A document with 4 hours of editing time and 3 tracked changes suggests that most of the editing happened with tracking off.
This is not definitive. Editing time includes time the document was open but idle. Revision numbers increment for reasons other than tracked changes. But a large mismatch between metadata and tracked changes is a useful signal.
Running an independent comparison reveals untracked changes
This is the definitive test. Take the last version you sent and compare it against the version you received, using a comparison tool that compares document content independently of Track Changes history. If the comparison shows changes that are not in the Track Changes record, those changes were made while tracking was off.
The comparison does not tell you why tracking was off. It does not tell you whether the gap was intentional or accidental. It tells you that changes exist in the document that were not tracked, and it shows you exactly what those changes are. That is the information you need to make informed decisions about the contract.
This is also the only method that is reliable. The "too clean" heuristic and the metadata check are useful indicators, but they can both produce false positives (the document really is clean, the editing time was idle time) and false negatives (the untracked changes are few enough that the metadata does not look suspicious). The independent comparison catches everything, every time, regardless of the circumstances that led to the tracking gap.
What untracked changes look like in practice
To make this concrete, here are scenarios that play out regularly in contract negotiations. These are patterns, not hypotheticals.
The "clean draft" with silent edits
You are in round 3 of a license agreement negotiation. You send a redlined draft with your changes to the payment terms, the warranty provisions, and the termination clause. The other side responds with what they describe as a "clean draft reflecting all agreed changes." No Track Changes markup. The email says: "We've accepted your edits and cleaned up the formatting. Please review and confirm."
You review the clean draft. It reads well. The payment terms look right. The warranty section looks like what you proposed. But when you run a comparison against the version you sent, you discover that the termination for convenience clause now requires 90 days' notice instead of the 30 days you proposed. And the limitation of liability has a new carve-out for "direct damages arising from breach of the payment obligations" that was not in any prior draft.
Neither of these changes appears in Track Changes because there are no tracked changes in the document. The other side accepted everything, turned off tracking, made their edits, and sent it back as a "clean" version. Without the comparison, you would have reviewed a document that appeared to reflect your terms but actually contained two significant modifications.
The partial tracking gap
This one is harder to catch because the document does have Track Changes. An associate on the other side reviewed your draft, tracked their edits to four sections, then took a call. When they came back, they continued editing but did not notice that Track Changes had been turned off (perhaps by a system update, a co-editing session, or an accidental click). They made changes to two more sections without tracking.
The document you receive has visible tracked changes in four sections. It looks like a normal redline. You review the tracked changes, negotiate on those points, and send it back. The changes in the other two sections pass through unexamined. You never see them because they are not in the Track Changes record, and you have no reason to look for them because the document appears to have complete tracking.
This is the most dangerous scenario because it offers no obvious signal. The document has tracked changes. They look legitimate. The only way to catch the untracked edits is to compare the full document, not just review the tracked changes.
The template swap that introduces boilerplate
You negotiate a services agreement using your firm's template. After two rounds, the counterparty says they need to use their own template for internal compliance reasons. They paste the agreed content into their template and send it back. No Track Changes, because the document is "new" from their template's perspective.
When you compare the two versions, you find that most of the negotiated content carried over. But their template included a standard indemnification clause that replaced the one you negotiated. Their template's governing law provision specifies a different jurisdiction than the one you agreed on. And their template's dispute resolution section adds a mandatory mediation step that was not in any prior draft.
The counterparty may genuinely not know these changes were introduced. They pasted the body text into their template and assumed the template sections were empty or would be overwritten. They were not. The template's default language won, and nobody on their side compared the final version against the agreed redline.
What to do when you find untracked changes
Discovering that a contract contains changes that were not in the Track Changes record requires a specific response. This is not a moment for assumptions about intent. It is a moment for precision and documentation.
Step 1: Document the discrepancy
Before you contact the other side, create a clear record of what the comparison found. Save the comparison output. Note each specific change that appears in the comparison but was not in the Track Changes markup. For each change, note the section number, the text in your version, and the text in their version. You want a factual record, not a characterization.
This documentation serves two purposes. First, it gives you a precise list to discuss with the other side. Second, it creates a record in case the discrepancy becomes relevant later (in a dispute, a malpractice context, or an internal quality review).
Step 2: Raise it with opposing counsel
Contact the other side directly. Be factual. Do not accuse them of hiding changes. In most cases, the explanation is a workflow accident, and an accusatory tone will damage the relationship without adding useful information.
A good approach: "We ran a comparison of the version you sent against the version we sent in round 3 and found differences in Sections 5.2, 8.4, and 12.1 that do not appear in the Track Changes markup. The specific differences are [list them]. Can you let us know whether these changes were intended?"
This gives the other side a chance to explain (usually: "our paralegal accepted changes from the wrong version" or "we switched templates and didn't realize it changed those sections") and to correct the issue. If the changes were intentional, the conversation shifts to negotiation on those specific points. Either way, you are working from a shared understanding of what the document actually says.
Step 3: Compare every subsequent version independently
Once you have found untracked changes in one round of a negotiation, the prudent response is to compare independently for every remaining round. Do not rely on Track Changes alone for the rest of that deal.
This is not about distrust. It is about process reliability. If tracking was interrupted once, the conditions that caused the interruption (workflow habits, template conversion steps, multi-editor coordination) are likely still present. The probability of a second gap is higher than it was before the first one. Independent comparison for every subsequent round eliminates this risk entirely.
The additional time is minimal. Once you have the workflow established (save your sent version, compare it against the received version before reviewing Track Changes), it adds two to three minutes per round. The first time it catches another untracked change, those minutes are justified.
Step 4: Evaluate the pattern
A single instance of untracked changes is almost always a mistake. Multiple instances, or untracked changes that consistently favor one side, warrant a different level of attention.
If every untracked change in the document happens to benefit the counterparty (shorter cure periods, lower liability caps, broader indemnification obligations), the pattern may be coincidental, but it deserves a conversation with the lead lawyer on the deal. If untracked changes appear in consecutive rounds despite the other side being informed of the issue, that is a signal about either their workflow discipline or their negotiation approach. Both are relevant to how you manage the remainder of the deal.
Why independent comparison is the standard
The lesson from all of the scenarios above is that Track Changes is a convenience tool, not a verification tool. It shows you what the editing software recorded while tracking was enabled. It does not show you what actually changed between two versions of a contract. Those are different questions with different answers.
Independent comparison answers the right question: "What is different between the version I sent and the version I received?" It does not depend on whether Track Changes was on. It does not depend on whether the document was converted between formats. It does not depend on how many people edited the document or what tools they used. It compares the content of two files and reports every difference.
This is why independent comparison is the standard at large firms and the direction the entire profession is moving. It is not a replacement for Track Changes. Track Changes is still useful for understanding the other side's intent, for navigating their edits in context, and for the accept/reject workflow that structures negotiation rounds. But Track Changes is the starting point for review, not the complete picture. Independent comparison provides the verification.
The workflow is: review Track Changes to understand what the other side intended to change. Run an independent comparison to verify what actually changed. Cross-check the two. If they match, proceed with confidence. If they do not, investigate the discrepancies before responding.
Building the habit
The barrier to independent comparison is not cost or time. It is habit. Most lawyers have reviewed contracts using Track Changes for their entire careers. The workflow is ingrained: open the document, review the tracked changes, accept or reject, send it back. Adding a comparison step requires changing a workflow that feels complete as-is.
The most effective way to build the habit is to start with the highest-stakes comparisons and work down. Begin with execution copies: every time you receive a final clean copy for signature, compare it against the last agreed version before anyone signs. This is the comparison with the highest return on the time invested, and the strongest case for making it non-negotiable.
Once that is routine, extend it to the negotiation rounds where you expect significant changes: the first counterparty markup, any round where they reformatted or changed templates, any round where the Track Changes look suspiciously sparse. These are the rounds where tracking gaps are most likely to occur.
Eventually, it becomes part of the workflow for every round. Save the version you send. When you receive the response, compare before you review. It takes a few minutes. It catches everything Track Changes might miss. And it replaces the question "was Track Changes on the whole time?" with a question you can actually answer: "what is different between these two documents?"
Choosing a comparison tool
Any comparison tool that reads .docx files and compares content independently of Track Changes will work for this purpose.
Word's built-in Compare function (Review tab, Compare) works for simple cases. It generates a comparison document showing differences between two files. For short contracts with few changes, this is sufficient. For longer documents, Word Compare can produce noisy output that mixes formatting changes with substantive edits, making it harder to focus on what matters.
Clausul is designed specifically for this use case: upload two contract versions, get a comparison that classifies changes by type (substantive, formatting, numbering) so you can focus on what matters and verify quickly. If Track Changes was complete, the comparison confirms it. If changes were missed, the comparison catches them.
The tool matters less than the habit. The critical step is running the comparison, not which software you use. Pick the tool that fits your workflow and use it consistently.
The bottom line
Track Changes gets turned off. It happens accidentally, it happens during format conversions, it happens when multiple editors touch a document, and yes, it occasionally happens deliberately. The cause matters less than the consequence: changes made while tracking was off are invisible in the revision history, and you will not catch them by reviewing Track Changes alone.
The solution is not to demand that everyone keep Track Changes on (you can ask, but you cannot enforce it). The solution is to stop relying on Track Changes as your only source of truth about what changed. Run an independent comparison for every version you receive. Compare what you sent against what you got back. Treat the comparison result as the authoritative record of changes, and treat Track Changes as a useful supplement that shows intent.
This is not extra work. This is the work. The alternative is trusting a recording mechanism that can be interrupted, reset, or circumvented at any point in the editing process. That trust is misplaced, and the exposure when it fails is real.
Run a comparison. It takes minutes. If Track Changes was complete, you will confirm it and move on. If it was not, you will catch what was missed before it becomes your client's problem.
Frequently asked questions
Can someone turn off Track Changes without me knowing?
Yes. Track Changes is a local setting in Word. Anyone with editing access can turn it off, make changes, and turn it back on. Word does not log when tracking was enabled or disabled, and there is no indication in the document that a gap in tracking occurred. The only way to detect changes made while tracking was off is to compare the current version against a known previous version using an independent comparison tool. This is not a bug in Word. It is how the feature was designed: Track Changes records edits made while it is on, and nothing else.
How common is it for Track Changes to be turned off during contract negotiations?
More common than most lawyers realize, and usually accidental rather than deliberate. Track Changes gets turned off when someone clicks the button without noticing, when a document is converted between formats (PDF to Word, Google Docs to Word), when content is pasted into a new template, or when multiple editors work on the same document with inconsistent settings. Intentional manipulation happens but is rare compared to these routine workflow causes. The practical impact is the same regardless of intent: changes made while tracking was off are invisible in the revision history.
How can I tell if Track Changes was turned off at any point during editing?
There is no reliable way to determine this from the document alone. Word does not maintain a log of Track Changes enable/disable events. Some indirect clues can suggest a gap: a document with very few tracked changes despite significant content differences from the previous version, metadata showing more editing time or revisions than the tracked changes would suggest, or a comparison that reveals changes not present in the Track Changes record. But none of these are definitive from metadata alone. The only reliable method is to compare the received version against the last version you sent using an independent comparison tool.
What should I do if I discover changes that were not tracked?
First, document the discrepancy by saving the comparison output that shows the untracked changes. Second, raise it with opposing counsel directly and factually: "We ran a comparison and found changes in Sections 4.2 and 7.1 that do not appear in the Track Changes markup. Can you confirm these were intentional?" Most of the time, the explanation is a workflow accident. Third, compare every subsequent version they send independently, not just via Track Changes. Once you have found untracked changes in one round, independent comparison should become mandatory for every remaining round of that negotiation.
Is it standard practice to run an independent comparison alongside Track Changes?
At large firms, yes. Most Am Law 100 firms use dedicated comparison tools (typically Litera Compare or similar) as a verification step alongside Track Changes review. At smaller firms, the practice is less consistent, often because the tools have historically been expensive or difficult to set up. The trend is toward independent comparison as a standard step, driven by risk awareness and the availability of self-serve comparison tools that do not require enterprise procurement. If your firm currently relies solely on Track Changes, adding an independent comparison step is the single highest-impact improvement you can make to your contract review workflow.
Does accepting all changes and starting clean reset Track Changes history?
Yes. When you accept all changes in a document, the tracked markup is removed and the current state of the document becomes the baseline. If you then forget to turn Track Changes back on before making further edits, those edits will not be tracked. This is one of the most common ways tracking gaps are introduced: a reviewer accepts all changes to work from a clean view, makes substantive edits, and either forgets to re-enable tracking or assumes it is still on. The resulting document has no tracked changes at all, making it impossible to see what was modified without running an independent comparison.