OneDrive for Business Word AutoSave creates conflicts for policy documents: Fix Guide

When you edit a corporate policy document in Word and AutoSave is enabled, OneDrive for Business may generate version conflicts that overwrite approved content or create duplicate files. This occurs because AutoSave saves changes every few seconds, and multiple editors or delayed sync operations can collide with the file lock. This article explains why AutoSave conflicts happen specifically with policy documents and provides a step-by-step fix to disable AutoSave for those files without affecting your other documents.

Why AutoSave Creates Conflicts for Policy Documents

AutoSave in Word for Microsoft 365 saves changes to OneDrive every few seconds as you type. This feature is designed for collaboration, but it causes problems when multiple people edit a policy document at the same time or when a document is opened from a synced folder on a secondary device. OneDrive treats each save as a new version, and if two saves occur within the same sync cycle, the server may create a conflict file named Policy Document (version conflicted copy).

Policy documents differ from regular working files. They require formal approval, contain locked language, and must not be altered after sign-off. A single AutoSave-triggered conflict can replace an approved paragraph with an unapproved edit, forcing a full review cycle. The root cause is that AutoSave ignores the manual save discipline that policy workflows depend on.

OneDrive sync also plays a role. If you open a policy document on two computers with the same OneDrive account, AutoSave on one machine may upload changes that conflict with the version on the other machine. This scenario is common for users who work on a desktop at the office and a laptop at home.

Steps to Disable AutoSave for Policy Documents

You have two options: disable AutoSave globally for all Word documents, or disable it only for specific policy files. The per-document method is recommended because it preserves AutoSave for drafts and collaborative files.

Option 1: Disable AutoSave Per Document

1. Open the policy document in Word
   Double-click the file from your OneDrive folder or open it directly from the Word app. Ensure the document is stored in OneDrive or SharePoint.
2. Locate the AutoSave toggle in the title bar
   At the top-left corner of the Word window, next to the document name, you see a switch labeled AutoSave. It shows On by default.
3. Click the toggle to turn AutoSave off
   Slide the switch to the Off position. The switch turns gray and the label changes to Off. This setting persists for this document only. Word remembers the setting for each file.
4. Save the document manually after edits
   Press Ctrl+S or click the Save icon in the Quick Access Toolbar. You control when changes are uploaded to OneDrive.

Option 2: Disable AutoSave Globally for All Word Documents

1. Open Word and go to File > Options
   In any Word document, click File in the ribbon, then Options at the bottom of the left pane.
2. Select the Save category
   In the Word Options dialog, click Save in the left navigation list.
3. Uncheck the AutoSave setting
   Under Save documents, uncheck the box labeled AutoSave OneDrive and SharePoint Online files by default on Word. Click OK to apply the change.
4. Restart Word for the change to take effect
   Close and reopen Word. AutoSave is now disabled for all documents. You can re-enable it per document using the toggle in the title bar.

If AutoSave Already Created a Conflict

If a conflict file was already created, you need to identify the correct version and remove the duplicate.

Recover the Correct Version from Version History

1. Open the policy document in Word
   Open the file that has the conflict. Do not open the conflict copy yet.
2. Go to File > Info > Version History
   Click File, then Info. In the right pane, click Version History. A panel opens on the right showing all saved versions with timestamps and editor names.
3. Open the version before the conflict occurred
   Scroll through the list and click the version that was saved before the conflict timestamp. Word opens that version in read-only mode.
4. Restore the correct version
   Above the document, click Restore. Word replaces the current version with the restored version. Confirm the action in the dialog box.

Delete the Conflict Copy

1. Open OneDrive in File Explorer
   Navigate to the folder where the policy document is stored. Look for a file with (version conflicted copy) in the name.
2. Move the conflict copy to the Recycle Bin
   Select the file and press Delete. Empty the Recycle Bin after confirming the correct version is restored.

Common Mistakes and Limitations

AutoSave toggle is grayed out

The AutoSave toggle in the title bar is unavailable when the document is not saved to OneDrive or SharePoint. Save the file to OneDrive first, then the toggle becomes active.

Disabling AutoSave globally affects all documents

If you uncheck the option in Word Options, AutoSave turns off for every document you open. You must manually re-enable it per document using the toggle. This is acceptable only if you rarely use AutoSave.

Policy documents on SharePoint still sync

Disabling AutoSave in Word does not stop OneDrive from syncing changes made by other users. If two people edit the same policy document on SharePoint, the second person to save still triggers a conflict. Use the Check Out feature in SharePoint to lock the document during editing.

AutoSave On vs AutoSave Off for Policy Documents

Item	AutoSave On	AutoSave Off
Save frequency	Every few seconds	Only when you press Ctrl+S or click Save
Conflict risk	High when multiple editors or devices are involved	Low because you control the upload timing
Version history granularity	Very fine, every keystroke creates a new version	Coarse, only manual saves create versions
Best use case	Drafts, collaborative editing with tracked changes	Final policy documents, contracts, approved content

You can now disable AutoSave for individual policy documents using the title bar toggle or globally through Word Options. Use Version History to recover the correct version if a conflict already occurred. For documents that require strict version control, combine AutoSave off with the SharePoint Check Out feature to prevent simultaneous edits entirely.