Copilot in Word Summary Ignores Track Changes: Fix

When you use Copilot in Word to generate a summary of a document that contains tracked changes, the summary often reflects the original text instead of the accepted or rejected state. This happens because Copilot reads the underlying document content, not the visible tracked-change overlay. The result is a summary that does not match what you see on screen. This article explains why Copilot ignores track changes and provides a step-by-step fix to make summaries reflect the current document state.

Why Copilot in Word Ignores Track Changes

Copilot in Word generates summaries by processing the document content stored in the .docx file. Track changes are stored as metadata — they are not part of the final visible text until you accept or reject them. When Copilot reads the document, it sees the base text with change annotations, but it does not automatically resolve those annotations. The summary is therefore built from the original text plus the insertions and deletions as separate pieces of information, not the final intended version.

How Track Changes Metadata Works

Every tracked insertion and deletion is recorded in the XML structure of the .docx file. Copilot’s language model processes this XML. It sees both the original paragraph and the proposed change simultaneously. Because the model is designed to summarize the most coherent version of the text, it often picks the original content — the base version — rather than the edited version. This behavior is not a bug; it is a limitation of how Copilot reads document structure.

Why Accepting Changes Before Summary Is Required

To make Copilot summarize the final edited text, you must remove the change metadata. The only way to do this is to accept or reject all tracked changes so the document contains only a single version of each paragraph. After that, the document no longer has change markup, and Copilot reads the text exactly as it appears on screen.

Steps to Make Copilot Summarize the Final Document After Track Changes

Follow these steps to ensure Copilot generates a summary based on the accepted version of your document.

1. Open the document in Word
   Launch Word and open the document that contains tracked changes. Make sure you are in Editing mode, not Reviewing mode, so you can make changes.
2. Go to the Review tab
   On the ribbon, click the Review tab. This tab contains all commands for tracking, accepting, and rejecting changes.
3. Accept all changes
   In the Changes group, click the arrow below Accept. From the dropdown, select Accept All Changes. This command accepts every tracked insertion and deletion in the document, removing the markup.
4. Turn off Track Changes
   In the Tracking group, click Track Changes to turn it off. This prevents new changes from being recorded while you work with Copilot.
5. Save the document
   Press Ctrl + S or click the Save icon. Saving writes the final text to the file and removes the change metadata from the XML structure.
6. Open the Copilot pane
   On the Home tab, click the Copilot button in the Editor group. The Copilot pane opens on the right side of the window.
7. Generate the summary
   In the Copilot pane, type a summary prompt such as “Summarize this document” or “Give me a brief overview of the main points.” Copilot now reads the final accepted text and produces a summary that matches the visible content.
8. Review the summary
   Check that the summary reflects the accepted version. If it still shows old content, repeat steps 2 through 5 to ensure all changes were accepted and the document was saved.

If Copilot Still Shows the Wrong Summary

If you have accepted all changes but Copilot still returns a summary based on the original text, try these additional steps.

Copilot Summary Shows Original Text After Accepting Changes

This usually happens when the document contains comments or hidden content that Copilot interprets as conflicting text. To fix this, delete all comments in the document. Go to the Review tab, click the arrow below Delete in the Comments group, and select Delete All Comments in Document. Then save and regenerate the summary.

Copilot Summary Includes Deleted Text That Was Rejected

If you rejected changes instead of accepting them, the rejected text may still exist as hidden revision marks. To remove it completely, accept all changes first, then reject any remaining changes. Alternatively, use the Reject All Changes command to remove all insertions and revert to the original. After that, save and regenerate the summary.

Copilot Summary Is Blank or Incomplete After Accepting Changes

A blank or incomplete summary can occur if the document is very long or contains complex formatting like tables and images. Copilot has a token limit for processing. To work around this, break the document into sections and ask Copilot to summarize each section individually. For example, type “Summarize section 2” or “Summarize the introduction.”

Copilot Summary with Track Changes: Before vs After Accepting

Item	Before Accepting Changes	After Accepting Changes
Document content Copilot reads	Base text + change metadata (insertions and deletions)	Single final version of the text
Summary accuracy	Often reflects original text, not the edited version	Matches the visible final document
Time required	None — Copilot runs immediately but produces wrong output	1–2 minutes to accept changes and save
Risk of losing edits	Low — changes remain tracked	None — changes are permanently applied

Copilot in Word cannot resolve track changes automatically. The only reliable method is to accept or reject all changes before generating a summary. After you do this, Copilot reads the final text and produces a summary that matches what you see on screen. If you work with documents that go through multiple review cycles, make accepting changes the last step before using Copilot. This ensures your summaries are always based on the approved version.