When you co-author a Word document stored on OneDrive or SharePoint, you may notice that Track Changes turns itself off for all users after a sync cycle. This is not a random glitch or a settings conflict. The behavior is by design in Word’s real-time co-authoring system. This article explains the technical reason behind this automatic change and what you can do to work with it.
Key Takeaways: Why Co-authoring Turns Off Track Changes
- Real-time co-authoring uses a merge model that conflicts with tracked changes: Word disables Track Changes globally to prevent merge conflicts and ensure all collaborators see the same current version.
- Track Changes is a single-author review tool, not a real-time collaboration feature: When multiple users edit simultaneously, Word switches to direct editing to maintain version consistency.
- Re-enabling Track Changes after sync may not stick: If the document remains in co-authoring mode, Word will disable Track Changes again on the next sync cycle.
Why Word Disables Track Changes During Co-authoring
Word’s real-time co-authoring feature, available in Microsoft 365, uses a merge-on-save model. When two or more people edit the same document simultaneously, Word saves each user’s changes to the server and merges them automatically. Track Changes is designed for sequential review: one author makes changes, and a reviewer accepts or rejects them. In a co-authoring session, multiple users make changes at the same time. If Track Changes were active, the merge engine would need to track who changed what in overlapping time windows, which creates conflicts that Word cannot resolve automatically.
To avoid these conflicts, Word disables Track Changes globally for the document as soon as the second user opens it for editing. This happens regardless of whether the document was saved with Track Changes on or off. The setting is not per-user. It is a document-wide flag that Word toggles at the server level. When the document syncs, all users see Track Changes turned off.
The technical root cause is the difference between the co-authoring merge engine and the Track Changes markup engine. The merge engine works on the final content of the document, not on revision marks. If Track Changes were active, the server would need to store separate revision lists for each user and then merge those lists. This is not supported in the current Word co-authoring protocol.
Additionally, Word’s co-authoring uses a feature called version persistence. Each save creates a new version on the server. These versions are whole-document snapshots, not incremental tracked changes. When you open an earlier version, you see the document as it was at that point, not a list of revisions. This design makes Track Changes redundant during co-authoring.
What Happens to Existing Tracked Changes When Co-authoring Starts
If you have a document with existing tracked changes and a second user opens it for co-authoring, Word does not delete the existing revision marks. The existing tracked changes remain in the document as markup. However, any new edits made by any user after co-authoring begins are not tracked. The existing revisions stay visible until someone accepts or rejects them. Once the document exits co-authoring mode, you can turn Track Changes back on, and new edits will be tracked again.
The key point is that Word does not remove the tracked changes that were already there. It only stops recording new ones. This is a common point of confusion. Users see that Track Changes is off and assume all their work was lost. The existing markup is still present, but the feature is disabled for future edits.
How to Manage Track Changes in a Co-authored Document
- Finish all tracked changes before inviting collaborators
If you need to use Track Changes for review, complete the review cycle before sharing the document for co-authoring. Accept or reject all revisions, then turn off Track Changes. After that, share the document. Co-authors will not see any tracked changes, and the document will stay in direct editing mode. - Use version history to review changes after co-authoring
After a co-authoring session, go to File > Info > Version History. Word stores each save as a separate version. You can open any version and compare it to the current document. This gives you a change log without using Track Changes. To compare two versions manually, open the older version, select all content, copy it, and paste it into a new document. Then use Review > Compare to compare the pasted version with the current document. - Re-enable Track Changes after co-authoring ends
When only one user has the document open, you can turn Track Changes back on. Go to Review > Track Changes and click the Track Changes button. The button will highlight, indicating that tracking is active. All new edits will be marked. If another user opens the document again, Word will disable Track Changes again on the next sync. - Use comments instead of tracked changes for suggestions
If you need to suggest edits without changing the text, use comments. Select the text, then go to Review > New Comment. Comments are preserved during co-authoring and do not cause conflicts. Each user can see and reply to comments in real time. - Save a local copy with tracked changes before sharing
If you must preserve tracked changes for legal or compliance reasons, save a local copy of the document with Track Changes on. Use File > Save As and choose a location on your local drive. Then share the online version for co-authoring. You can later merge the local tracked copy with the final co-authored version using Review > Compare.
If You Need Track Changes and Co-authoring Together
Word Does Not Support This Combination Natively
There is no setting or workaround that enables Track Changes during real-time co-authoring. The feature is intentionally disabled at the server level. Any attempt to force Track Changes on by editing the document’s XML or using VBA macros will fail. The server will override the setting on the next sync.
Using SharePoint Approval Workflows as an Alternative
If your organization uses SharePoint, you can set up an approval workflow that requires a document to go through a review stage before it can be edited by multiple people. In the review stage, only one person has edit access, and Track Changes works normally. After the review is complete, the document moves to the co-authoring stage where Track Changes is off. This is not a direct replacement, but it gives you a structured review process.
Using Word Online vs Desktop App
Word Online (the browser version) also disables Track Changes during co-authoring. The behavior is identical to the desktop app. There is no difference in how the two versions handle Track Changes during co-authoring.
Word Desktop vs Word Online: Track Changes Behavior During Co-authoring
| Item | Word Desktop | Word Online |
|---|---|---|
| Track Changes disabled during co-authoring | Yes, automatically on sync | Yes, automatically on sync |
| Existing tracked changes preserved | Yes, until accepted or rejected | Yes, until accepted or rejected |
| Re-enable Track Changes after co-authoring ends | Yes, manually via Review tab | No, Word Online does not support Track Changes at all |
| Version history available | Yes, File > Info > Version History | Yes, File > Info > Version History |
| Comments supported during co-authoring | Yes | Yes |
Word Desktop lets you re-enable Track Changes after the last co-author leaves. Word Online does not support Track Changes even in single-user mode. If you need Track Changes, use the desktop app.
Conclusion
Word disables Track Changes globally during co-authoring because the real-time merge engine cannot handle overlapping revision marks from multiple users. Existing tracked changes are not deleted, but no new changes are recorded until co-authoring ends. To work around this, finish your review cycle before sharing the document, use version history to compare changes, or switch to comments for suggestions. If you must use Track Changes, edit the document alone and turn off sharing. For a structured review process, consider a SharePoint approval workflow before enabling co-authoring.