OneDrive for Business Word AutoSave creates conflicts for review workflows: Fix Guide

When multiple reviewers edit a Word document stored in OneDrive for Business at the same time, AutoSave can create version conflicts that disrupt structured review workflows. AutoSave saves changes every few seconds, so two reviewers editing the same paragraph may overwrite each other’s work without warning. This article explains why AutoSave causes conflicts in review cycles and provides three practical methods to prevent or resolve those conflicts.

Why AutoSave Creates Conflicts in Review Workflows

AutoSave is designed for single-author or real-time co-authoring scenarios where multiple people edit the same document simultaneously. In a structured review workflow, however, reviewers are expected to submit their changes sequentially or within a defined review period. AutoSave saves each keystroke to the cloud immediately, so if two reviewers open the same document at the same time, Word merges both sets of changes automatically. This merge can overwrite intentional edits, produce unexpected formatting, or create duplicate paragraphs.

The root cause is that AutoSave bypasses the traditional save-and-submit model. In a non-AutoSave workflow, a reviewer opens a document, makes edits, saves a local copy, and then uploads the final version. With AutoSave enabled, every change is written to the server as it happens. If Reviewer A deletes a sentence while Reviewer B revises that same sentence, the final merged document may contain a broken sentence or a duplicate. Word does not warn users that a merge conflict occurred unless the conflict is severe enough to trigger the merge conflict dialog.

AutoSave and Track Changes Interaction

Track Changes is often used in review workflows to show what each reviewer changed. When AutoSave is enabled, Track Changes marks each edit as it is saved. This means the document owner sees a continuous stream of tracked changes, not a single batch of finalized edits. If two reviewers both have Track Changes on, the document becomes cluttered with overlapping insertions and deletions, making it difficult to accept or reject changes cleanly.

Three Methods to Fix AutoSave Conflicts for Review Workflows

Choose one method based on your team’s review process. Method 1 works best for formal sequential reviews. Method 2 is suitable for individual reviewers who want full control. Method 3 is ideal for collaborative editing where changes must be visible to all participants.

Method 1: Check Out the Document Before Editing

1. Open the document in Word for the web or desktop app
   Navigate to the OneDrive folder that contains the Word file. Double-click the file to open it in Word.
2. Check out the file
   In the desktop app, go to File > Info > Manage Document and click Check Out. In Word for the web, click the ellipsis menu (three dots) on the file in OneDrive and select Check Out. A green checkmark icon appears next to the file name, indicating it is locked to you.
3. Make your edits with AutoSave still enabled
   Because the file is checked out to you, no other user can edit it. AutoSave continues to save your changes, but no merge conflicts can occur because only one person has write access.
4. Check in the document when finished
   Go to File > Info > Manage Document and click Check In. Word saves your final version to OneDrive and releases the lock so the next reviewer can check out the file.

Method 2: Turn Off AutoSave for the Document

1. Open the Word document
   Double-click the file in OneDrive or open it from the Word desktop app.
2. Disable AutoSave
   In the title bar at the top of the Word window, locate the AutoSave toggle switch. Click it to turn AutoSave off. The switch changes from blue to gray, and the word “AutoSave” changes to “Manual.”
3. Make your edits without automatic saves
   Word now saves the document only when you press Ctrl+S or click the Save icon. This lets you complete all your changes before saving a single version to OneDrive.
4. Save the final version manually
   When you finish editing, press Ctrl+S to save your changes. Word uploads the entire file to OneDrive as a single save action, which prevents intermediate versions from conflicting with other reviewers.

Method 3: Use Track Changes and Comments with Co-Authoring

1. Enable Track Changes before editing
   Go to the Review tab and click Track Changes to turn it on. All your insertions, deletions, and formatting changes are marked with your name and a timestamp.
2. Keep AutoSave enabled
   AutoSave remains on so that all tracked changes are saved to the cloud in real time. Other reviewers see your edits as you type.
3. Add comments instead of inline changes for suggestions
   If you want to suggest a change without altering the text, select the text and click New Comment on the Review tab. Type your suggestion in the comment pane. Comments do not create merge conflicts.
4. Resolve merge conflicts if they occur
   If two reviewers edit the same paragraph, Word may prompt a Merge Conflict dialog. Click Compare to see both versions side by side, then choose which version to keep. Accept or reject each tracked change to finalize the document.

If AutoSave Still Causes Issues After the Main Fix

The document shows a merge conflict dialog even with Check Out enabled

This can happen if another user opens the document in read-only mode and then tries to edit it. Check Out only locks write access, not read access. If a second user opens the file and somehow obtains a write token (for example, by saving a local copy and re-uploading it), a conflict can occur. To prevent this, ensure all reviewers use the Check Out feature from the same OneDrive location. Do not download a copy and edit it separately.

AutoSave toggle is grayed out in the desktop app

AutoSave is grayed out when the document is not saved to OneDrive or SharePoint. Save the document to a OneDrive folder first. If the document is already in OneDrive but the toggle is still gray, the file may be in compatibility mode (old .doc format). Convert the file to the .docx format by clicking File > Info > Convert.

Track Changes shows duplicate edits after AutoSave merge

When AutoSave merges two reviewers’ tracked changes, the document owner may see the same edit appear twice. This is a known behavior in co-authoring scenarios. To clean up duplicates, go to Review > Show Markup and uncheck Insertions and Deletions temporarily. Then accept all changes in one pass. If duplicates remain, use the Compare feature under Review > Compare > Compare to merge two versions manually.

AutoSave On vs Check Out: Key Differences for Review Workflows

Item	AutoSave Enabled	Check Out Enabled
Description	Saves every change to OneDrive automatically every few seconds	Locks the file so only one user can edit at a time
Conflict risk	High when multiple reviewers edit simultaneously	None because only one user has write access
Best for	Real-time co-authoring with Track Changes and comments	Sequential review workflows where each reviewer submits a final version
Version history	Every save creates a version, which can clutter the version history	Only the check-in action creates a new version

You can now control AutoSave conflicts in Word documents stored in OneDrive for Business by using Check Out, disabling AutoSave, or combining Track Changes with comments. Start by evaluating your team’s review process: if reviewers edit sequentially, use Check Out. If reviewers need to see each other’s changes in real time, keep AutoSave on and use Track Changes with comments. For advanced control, set up a document library with versioning and approval workflows in SharePoint to automate the review cycle.