OneDrive for Business Word AutoSave troubleshooting for policy documents: creates conflicts

When multiple users edit a policy document in Word and OneDrive AutoSave is active, Word can create duplicate conflict files instead of merging changes cleanly. This typically happens because policy documents are often large, contain tracked changes or comments, and are edited by several people at the same time. AutoSave saves every keystroke to OneDrive, which increases the chance of version conflicts when two users edit overlapping sections. This article explains why AutoSave triggers conflicts on policy documents, provides step-by-step fixes to reduce or eliminate those conflicts, and describes related failure patterns such as blocked checkouts or lost comments.

Why AutoSave Creates Conflicts on Policy Documents

AutoSave in Word for Microsoft 365 saves changes to OneDrive every few seconds. This is useful for individual work but problematic for shared policy documents. When two users open the same document and edit different paragraphs, AutoSave uploads two separate versions within seconds of each other. OneDrive detects a conflict because both versions branched from the same base file. It then creates a second file named Document Name (conflicted copy <date>).docx.

Policy documents are especially prone to this because they often have tracked changes, comments, and complex formatting. Tracked changes themselves are stored as metadata that can conflict when two users accept or reject different revisions simultaneously. Additionally, policy documents are frequently opened by multiple reviewers who do not coordinate their editing windows. The result is a conflicted copy that the document owner must manually merge, wasting time and risking lost edits.

The Role of File Locking and Co-Authoring

Word uses co-authoring to allow multiple people to edit the same document at the same time. When co-authoring works correctly, each user sees others’ changes after a few seconds. However, co-authoring relies on OneDrive being able to merge changes from different sections. If two users edit the same paragraph or make conflicting tracked changes, the merge fails and a conflict file is created. Policy documents often have strict formatting rules or sections that must be reviewed as a whole, making section-level conflicts more likely.

Steps to Prevent AutoSave Conflicts on Policy Documents

The methods below reduce or eliminate conflict files. Choose the method that fits your team’s workflow. For most policy document scenarios, Method 1 (turning off AutoSave for that document) is the fastest fix.

Method 1: Turn Off AutoSave for the Specific Document

1. Open the policy document in Word
   Make sure you have the latest version saved and no other users are editing it at this moment.
2. Go to File > Options > Save
   In the Save dialog, locate the section labeled Save documents.
3. Uncheck AutoSave files stored in the cloud by default
   This disables AutoSave for all cloud documents globally. If you only want to disable it for this document, use the next step instead.
4. Alternatively, use the AutoSave toggle in the title bar
   Near the top-left corner of the Word window, click the AutoSave toggle switch to set it to Off. This disables AutoSave for only the current document. The toggle is available only after you save the document to OneDrive or SharePoint.
5. Save manually with Ctrl+S
   After turning off AutoSave, press Ctrl+S to save changes only when you want a new version. This eliminates the rapid-fire saves that cause conflicts.

Method 2: Use Check Out / Check In on SharePoint

1. Open the SharePoint document library in a browser
   Navigate to the library where the policy document is stored.
2. Go to Library Settings > Versioning settings
   Scroll down to the Require Check Out section.
3. Select Yes for Require documents to be checked out before they can be edited?
   Click OK to save. Now only one user can edit the document at a time. Others can open a read-only copy.
4. Instruct users to check out the document before editing
   In Word, click File > Info > Check Out. After editing, click Check In to save the new version. This completely avoids conflicts because no two users can write simultaneously.

Method 3: Limit Co-Authoring to Non-Overlapping Sections

1. Divide the policy document into sections by heading
   Use Word’s built-in heading styles (Heading 1, Heading 2) to create clear section breaks.
2. Assign each reviewer a specific section
   Communicate via email or Teams which section each person should edit. Avoid editing the same paragraph at the same time.
3. Enable Track Changes for all reviewers
   Go to Review > Track Changes and set it to For Everyone. This makes it easier to see who changed what and reduces the chance of conflicting tracked-changes metadata.

If AutoSave Conflicts Still Occur After the Main Fix

Even after turning off AutoSave or enabling check-out, you may still see conflict files. Below are the most common residual issues and their solutions.

OneDrive creates conflicted copies even with AutoSave off

This can happen if another user still has AutoSave enabled on their copy of the document. AutoSave is a per-user setting in Word. Verify that all editors have turned off AutoSave for that specific document using the toggle in the title bar. You can also set a group policy in Microsoft 365 admin center to disable AutoSave for all users in your tenant: go to Microsoft 365 admin center > Settings > Org settings > Word AutoSave and set it to Off.

Tracked changes cause merge failures

When two users accept or reject different tracked changes in the same paragraph, Word cannot merge them. The result is a conflicted copy. To avoid this, ask reviewers to accept or reject all tracked changes before saving, or use the Review > Compare feature after each reviewer finishes to manually merge changes.

OneDrive sync is paused or stalled

If OneDrive sync is paused, Word may still save locally and then upload all changes at once when sync resumes. This can create a conflict if another user saved in the meantime. Check OneDrive status by clicking the OneDrive cloud icon in the system tray. Make sure sync is active and not paused. If it is paused, click the pause icon and select Resume syncing.

AutoSave vs Manual Save for Policy Documents: Key Differences

Item	AutoSave On	AutoSave Off (Manual Save)
Save frequency	Every few seconds while typing	Only when user presses Ctrl+S or clicks Save
Conflict risk	High with multiple concurrent editors	Low, because saves are less frequent and coordinated
Version history	Creates many automatic versions in OneDrive	Creates versions only on manual saves
Co-authoring merge success	Works best when editors stay in separate paragraphs	Works best when editors coordinate who saves when
Recovery after crash	AutoSaved content is recoverable up to last keystroke	Only content saved before the crash is recoverable

After applying one of the methods above, your team should see fewer or no conflict files on policy documents. If conflicts persist, use the OneDrive web interface > Version history to restore a previous version before the conflict occurred. For ongoing collaboration, consider using SharePoint check-out for any document that goes through formal review cycles. A practical tip: keep AutoSave on for drafts but turn it off for final policy documents that require sequential sign-off.