Suspected Word / SharePoint coauthoring corruption in complex document with footnotes, captions, cross-references, numbering, and lists

Ruben Nicolin 20 Reputation points
2026-04-02T09:49:22.7233333+00:00

Over approximately the last 1–2 months, we have encountered recurring problems in a collaboratively edited Word document stored on SharePoint. Text entered by collaborators sometimes disappears and is replaced by the character .

We are working in Microsoft 365 / Office 365 under an enterprise subscription. The affected document is stored on SharePoint. We are collaborating on the same Word document, often at the same time.

Context:

  • 1 user works in the desktop version of Word
  • 2 users work in Word for the web
  • All users edit the same SharePoint-hosted document
  • The document has complex structures - footnotes, numbered items, cross-references, slight tweaks to used styles, tracked changes by multiple authors, many comments.
  • Simultaneous coauthoring is common

It is the users working with Word for the web that have reported the  problem.

Typical pattern:

  • one or more sentences disappear
  • the missing content is replaced by the character 
  • the surrounding paragraph remains, but part of the sentence is gone

Example of corruption:

Correct text: The committee will review the draft budget on Thursday.^12 In preparation, the finance team has noted that several cost estimates for software licences require clarification and confirmation from the vendor.^13 As a next step, the revised figures will be circulated to all members.

Note: ^12 would be a footnote in Word.

Corrupted version: The committee will review the draft budget on Thursday.^12 In preparation, the finance team has noted that several cost estimates for software licences^13  As a next step, the revised figures will be circulated to all members.

Current preventative measures we're trying out:

For now, I have requested that all users only use the desktop version of Word, immediately start a new file version if corrupted text gets discovered, do not work on the same sections at the same time, and move the sections to be revised to a temporary document before merging it back to the master file. The last suggestion is excessive, but we've been losing a lot of time over these corrupted text issues and it seemed the easiest to avoid that changes, e.g., to numbered items in one part of the document conflict with changes elsewhere.

I'm happy about additional comments. Otherwise, I'm mainly posting this to document the bug.

Microsoft 365 and Office | Word | For business | Windows
0 comments
Answer accepted by question author
Alina Le 5,585 Reputation points Independent Advisor
2026-04-02T10:57:22.6066667+00:00

Hello @Ruben Nicolin

After reviewing your concern, this behavior is typically a result of a "Sync Reconciliation" process between different versions of Word. Your document is highly sophisticated, containing advanced elements such as footnotes, cross-references, and active Track Changes.

While Word for the Web is excellent for quick edits, the Word Desktop App is specifically designed to handle the deep technical layers of these complex structures. When multiple users edit the same paragraph across different platforms simultaneously, the system may occasionally place a temporary placeholder symbol (the character you see) to protect the document's integrity and prevent any data overlap.

To ensure the highest level of stability for your high-complexity documents, we recommend the following steps:

  • Use the Desktop Application: For documents with extensive footnotes and tracking, having all collaborators work in the Word Desktop App provides the most robust environment for merging changes.
  • Section-Based Collaboration: To allow for smooth real-time syncing, we suggest that team members work on different sections or paragraphs at any given time.
  • Manage Reviewing Modes: If possible, finalize or accept major tracked changes before starting a new intensive co-authoring session.

To help tailor future updates to your specific workflow needs, we encourage you to share your experience directly with the product developers. You can submit your feedback  Microsoft 365 Feedback Hub. Your insights are valuable and are considered directly by the production teams to refine the experience for all users.

User's image

If you've already submitted feedback, please share the link here, so not only me, but others can also vote it up to gain more attention.

User's image

If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Charles Kenyon 171.3K Reputation points Volunteer Moderator
    2026-04-02T15:27:34.12+00:00

    The main preventative measure is to have all people use the desktop application.

    The web app is not suitable for editing complex documents by a single person, much less co-authoring. https://addbalance.com/word/download.htm#MicrosoftWordPrograms

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-04-02T09:49:52.67+00:00

    The behavior described matches known coauthoring corruption issues in complex Word documents stored in SharePoint/OneDrive, especially when mixing Word for the web and the desktop client on feature‑rich documents (footnotes, cross‑references, complex numbering, tracked changes, comments).

    From the available information, the most reliable mitigations are:

    1. Prefer the desktop Word client for complex documents
      • Coauthoring in the Word desktop application is supported from Word 2010 onward, but Word for the web does not support all advanced features (for example, some numbering, fields, and controls). Unsupported features can cause corruption or loss of content when edited in the browser.
      • For complex documents with footnotes, cross‑references, and heavy use of tracked changes, editing only in the desktop client reduces the risk of corruption.
    2. Avoid unsupported or problematic features in coauthored documents
      • Features that can break or block coauthoring include:
        • OLE objects and ActiveX controls in the document body.
        • Master documents with subdocuments or HTML framesets.
        • Certain group policy settings that disable or interfere with coauthoring.
      • Removing such elements from the shared document can improve stability.
    3. Ensure the file format and storage are fully supported
      • Only .docx files stored on OneDrive or SharePoint support modern coauthoring. If the file was ever in .doc format and converted, ensure all collaborators are using the .docx version only.
      • Very large documents are more prone to issues; reducing embedded content (especially large images) can help.
    4. Use conflict‑handling workflows when coauthoring
      • When Word cannot merge edits from multiple authors, it raises coauthoring errors such as:
        • “Upload Failed: Save as / Discard”
        • “Upload Failed: Resolve Conflict”
        • “Recovered Conflicts”
      • For each of these, the recommended pattern is:
        • Save a copy if there are edits that must not be lost.
        • Reopen the live document from SharePoint.
        • Re‑apply any missing changes manually.
        • For “Resolve Conflict” or “Recovered Conflicts”, use the conflict/Review Changes view and accept/reject each conflicting change until the document is clean.
      • This reduces the chance that partially merged or conflicted content remains in the file as stray characters or missing text.
    5. Keep coauthoring conditions clean
      • Do not mark the document as final or apply password protection/IRM that is not configured for coauthoring; these can interfere with saving and merging changes.
      • Ensure “Store random numbers to improve Combine accuracy” is enabled in Word Options → Trust Center → Trust Center Settings → Privacy Options for documents that are frequently merged or coauthored.
      • Avoid requiring check‑out in the SharePoint library for documents that need real‑time coauthoring.
    6. When corruption is detected
      • Immediately save a new version of the document in SharePoint (or use version history to capture the current state).
      • If the file shows coauthoring errors, follow the documented “Upload Failed” / “Recovered Conflicts” flows to reconcile changes.
      • If the problem persists across sessions and users, consider:
        • Creating a fresh .docx from a clean copy of the content (without problematic elements like ActiveX/OLE or master/subdocuments).
        • Restricting editing to the desktop client for that document.

    The current mitigations already in use—desktop‑only editing, avoiding simultaneous edits in the same section, and using temporary documents for heavy restructuring—are aligned with the documented guidance for minimizing coauthoring corruption in complex Word files.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.