You are working on a document with Tracked Changes enabled, and you ask Copilot to summarize the edits or list the revisions. Instead of a useful answer, Copilot returns a generic response or says it cannot access the tracked changes. This happens because Copilot in Word reads the final merged state of the document, not the revision metadata stored by Tracked Changes. This article explains the technical reason behind this limitation and shows you the workarounds available to get the information you need.
Key Takeaways: Copilot and Tracked Changes in Word
- Copilot reads the current accepted text only: It cannot see insertions, deletions, or comments from Tracked Changes.
- Reviewing Pane > Show All Revisions: Use this built-in Word feature to see a full list of changes before using Copilot.
- Accept All Changes first: If you need Copilot to summarize the final content after edits, accept all changes before asking Copilot.
Why Copilot Cannot Read Tracked Changes Metadata
Copilot in Word uses the Microsoft Graph API to access the document content. The Graph API returns the document as it appears when Tracked Changes is set to Final: No Markup or Final view. The revision data such as who made a change, what the original text was, and when the change was made is stored in a separate layer of the document file format. This layer is not exposed through the current Copilot integration.
How Tracked Changes Stores Data
When you enable Tracked Changes, Word stores each edit as a revision object in the document XML. Each revision includes the old text, new text, author name, timestamp, and a unique revision ID. Copilot does not query this revision log. Instead, it reads the final visible text stream. If you have set the document view to All Markup, Copilot still sees the final text with markup indicators, but it does not interpret the revision metadata.
What Copilot Can and Cannot Do with Tracked Changes
Copilot can answer questions about the visible text on the page. For example, if a sentence appears in red strikethrough, Copilot sees the strikethrough formatting but does not know that the text was deleted two hours ago by a specific reviewer. Copilot also cannot list all changes, count revisions, or show the author of each change. These actions require direct access to the revision log, which Copilot does not have.
Steps to Work Around the Tracked Changes Limitation
- Accept all changes before using Copilot
Open the document. On the Review tab, click the arrow below Accept and choose Accept All Changes. This merges all revisions into the final text. Now Copilot can read the complete content and answer questions about the document. - Use the Reviewing Pane to get a change list
On the Review tab, click Reviewing Pane and select Reviewing Pane Vertical. The pane shows every insertion and deletion in sequence with author names and timestamps. Copy this list to a separate document. Then ask Copilot to summarize that list. - Ask Copilot about the document after accepting changes
After accepting all changes, type a prompt like: “Summarize the key edits made in this document.” Copilot will now process the final merged text and give you a summary of the content. - Use a macro to extract revision data
If you need a structured list of changes, run a VBA macro that exports revision details to a new document. Press Alt+F11 to open the VBA editor, insert a module, and paste a macro from Microsoft support. Run the macro to generate a plain-text list of all revisions. Then use Copilot on that list. - Compare documents instead of using Tracked Changes
If you control the workflow, save the original document and the edited document as separate files. Then ask Copilot: “What are the differences between Document A and Document B?” Copilot can compare two documents by reading their final text streams.
If Copilot Still Returns No Data After Accepting Changes
Copilot says “I can’t find changes in this document”
This message appears when Copilot detects that the document has Tracked Changes enabled but the current view is set to Final: No Markup. Switch the view to All Markup on the Review tab, then accept all changes. After accepting, save the document and close it. Reopen the document and ask Copilot again.
Copilot returns a summary that ignores accepted changes
If you accepted changes but Copilot still references old text, the document may have unsaved revisions in the undo stack. Save the document after accepting changes. Close and reopen the file. This forces Word to flush the revision log. Then ask Copilot again.
Copilot cannot see comments even after accepting changes
Comments are separate from Tracked Changes. Copilot cannot read comments in the current version. To work around this, copy all comments to a new document. On the Review tab, click Show Comments, select all comment text, copy it, and paste it into a blank document. Then ask Copilot to summarize that document.
Copilot in Word vs the Reviewing Pane: Key Differences
| Item | Copilot in Word | Reviewing Pane (Word) |
|---|---|---|
| Access to revision metadata | No | Yes |
| Shows author name per change | No | Yes |
| Shows timestamp per change | No | Yes |
| Can summarize changes in natural language | Yes, after accepting changes | No |
| Works on cloud-only documents | Yes | Yes |
You can now use the Reviewing Pane to see the full revision history and then accept all changes to let Copilot summarize the final document. For future workflows, consider using document comparison instead of Tracked Changes when you need Copilot to analyze edits. A concrete advanced tip: create a Word Quick Part that runs a macro to export revisions to a new document, so you can combine Copilot with revision data in one step.