When Word reports a coauthoring conflict, preserve each person’s outstanding edits before closing files or restoring an earlier version. Turning AutoSave off for the team is not the default fix: it can delay collaboration updates and make merges harder.
The error-specific controls below apply to supported desktop versions of Word for Microsoft 365. Word for the web, mobile apps and different builds may show different options.
Preserve the work that has not reached the shared document
Ask affected contributors to keep their documents open long enough to save a separate copy of important unsaved changes. Use Save a Copy or the recovery option Word offers. Verify the copy opens before choosing any discard action. Do not assume pressing Ctrl+S succeeded while an upload error remains.
Record the authoritative shared URL and keep local recovery copies clearly named by contributor. A recent-file entry or an email attachment may lead to a different copy of the document.
Follow the actual Word error
- Upload Failed with Save as/Discard: preserve the edits separately, reopen the live document, then reconcile missing work.
- Upload Failed with Resolve Conflict: use Resolve, review the conflicting changes and accept or reject them deliberately.
- Recovered Conflicts: review the recovered tracked changes instead of assuming they were already accepted.
- Upload Pending: check connectivity and leave Word open to retry saving; preserve important work if the wait continues.
See Microsoft’s coauthoring error guidance. A blanket instruction to close Word and wait thirty seconds can discard the opportunity to preserve local changes.
Compare separate copies without replacing the original
In desktop Word, use Review > Compare > Combine when you need to reconcile document revisions. Select the appropriate original and revised copies, expand the options and show changes in a New document. Review the differences and save the result under a new name. Microsoft’s Combine instructions explain the controls.
Keep the source copies until contributors approve the result. Check important tables, comments and formatting as well as text. Do not assume every generated change should be accepted or that a single merge has captured all contributors’ work.
Resume normal coauthoring
Have everyone open the agreed shared document, confirm appropriate edit access and verify that changes reach the cloud. Keep AutoSave enabled for normal supported coauthoring. Microsoft explains the collaboration drawbacks of turning it off.
If the error recurs, give IT the exact message, file location, Word version and affected users. Do not make tenant-wide AutoSave changes or restore an old document over outstanding contributions as a shortcut. Close the incident when the team has verified the accepted shared content and successful saving.