OneDrive for Business Word AutoSave troubleshooting for review workflows: creates conflicts

When multiple reviewers open the same Word document stored in OneDrive for Business, AutoSave can create file conflicts that disrupt the review workflow. The root cause is that AutoSave writes changes every few seconds, and when two or more people edit simultaneously, OneDrive treats each save as a separate version that can clash with concurrent edits. This article explains why these conflicts happen, how to configure Word and OneDrive to reduce them, and what to do when a conflict file appears.

Why AutoSave Creates Conflicts in Review Workflows

AutoSave is a feature in Word for Microsoft 365 that automatically saves changes to the cloud every few seconds. When a document is stored in OneDrive for Business, AutoSave writes directly to the server without requiring the user to press Ctrl+S. In a typical review workflow, a document owner sends a file to multiple reviewers who each open and edit their own copy. However, if two or more reviewers open the same file from the same location and begin editing, OneDrive sees two separate write streams. The first save succeeds, but the second save triggers a conflict because the server version changed after the second reviewer opened the file.

OneDrive handles this by creating a conflict copy. The original file is updated with the first reviewer’s changes, and a new file named “filename (version conflict)” appears in the same folder. This conflict file contains the second reviewer’s changes. The document owner then must manually merge the two versions. This process wastes time and can cause data loss if the conflict file is overlooked.

The problem is worse when reviewers use Word desktop apps with AutoSave enabled. The desktop app saves every few seconds, while Word for the web saves continuously. Even a short overlap of one or two minutes can produce multiple conflict files. Review workflows that rely on tracked changes are especially vulnerable because AutoSave can interleave edits from different reviewers, making it difficult to see who changed what.

Steps to Prevent AutoSave Conflicts During a Review

1. Turn off AutoSave for the document before sending it for review
   Open the Word document. Go to File > Options > Save. Under the Save Documents section, uncheck the box for “Enable AutoSave for this document.” Click OK. This stops Word from saving automatically while the document is being reviewed. The reviewer must manually save with Ctrl+S or by clicking the Save icon.
2. Send a copy to each reviewer instead of sharing the same file
   Use OneDrive to share a copy of the document with each reviewer. Right-click the file in File Explorer or OneDrive online, select Share, and choose “Send a copy.” Each reviewer gets their own editable version. After all reviews are returned, the document owner merges the changes into the original.
3. Enable Require Check Out in the SharePoint document library
   If the file is stored in a SharePoint document library that syncs with OneDrive, go to the library settings. Select Library settings > Versioning settings. Under Require Check Out, choose Yes. This forces each reviewer to check out the file before editing. Only one person can have the file checked out at a time, which prevents simultaneous edits and conflicts.
4. Use Word for the web for real-time co-authoring
   If the workflow requires multiple reviewers to edit at the same time, use Word for the web instead of the desktop app. Word for the web uses merge-on-save technology that combines edits from multiple authors without creating conflict files. All reviewers must open the document through a browser and have a Microsoft 365 license.
5. Set the document to open in Reviewing mode
   Before sharing, go to Review > Track Changes and turn on Track Changes. Then go to Review > Restrict Editing. Under Editing restrictions, select “Tracked changes.” This forces all edits to be recorded as tracked changes. Even if a conflict occurs, the tracked changes make it easier to merge the two versions.

If a Conflict File Appears Despite Preventive Steps

OneDrive created a file named “filename (version conflict)”

Open the conflict file in Word. Compare its contents with the original file. Use Review > Compare to see the differences. Word will show what was added, deleted, or changed in the conflict version. Accept or reject each change to merge the content into the original file. After merging, delete the conflict file from OneDrive to avoid confusion.

Two conflict files exist with different timestamps

If multiple reviewers edited the file at overlapping times, OneDrive may create more than one conflict file. Open each conflict file and compare it to the original. Use the Compare tool in Word to merge each conflict version one at a time. Start with the earliest conflict file and work forward to ensure no changes are lost.

Tracked changes are missing from the conflict file

If Track Changes was not enabled before the conflict occurred, the conflict file will not show tracked changes. In this case, open both the original and the conflict file side by side. Manually copy the changes from the conflict file into the original document. To prevent this in the future, enable Track Changes before sharing the document for review.

AutoSave vs Manual Save for Review Workflows: Key Differences

Item	AutoSave On	AutoSave Off
Save frequency	Every few seconds automatically	Only when user presses Ctrl+S or clicks Save
Conflict risk with multiple editors	High – writes overlap easily	Low – saves are controlled by the user
Best use case	Single author or co-authoring in Word for the web	Formal review with multiple reviewers
Data recovery after crash	No manual save needed – changes are on the server	User must save frequently or risk losing work
Works with Track Changes	Yes, but conflicts can still occur	Yes, and fewer conflicts mean cleaner revision history

You now know how to prevent and resolve AutoSave conflicts in Word documents during review workflows. Turn off AutoSave per document before sending it for review, or send individual copies to each reviewer. If a conflict file appears, use Word’s Compare tool to merge changes without losing data. For advanced control, enable Require Check Out in SharePoint to block simultaneous edits entirely.