Word made every edit visible, attributable and reversible

The writer's problem

An editor marking up a manuscript on paper could show exactly what changed with a pen stroke, but a word processor's saved file offered no such trail unless the software built one in. The practical problem was making an edit both visible and attributable, so a writer could see what changed, who changed it, and decide whether to keep it, without the editor's copy overwriting the writer's own draft in the process.

What the documents show

Microsoft's current support documentation for Track Changes in Word, retrieved 16 September 2026, states that the feature marks deletions with strikethrough and additions with underlining, that different authors' changes 'are indicated with different colors,' and that a reviewer's name is attached to and displayed with each change. It describes several markup views, including one that shows only a margin line and one that shows full colored markup by reviewer, and states that changes are accepted or rejected individually or all at once, through the Review tab or a right-click menu.

The developer reference for the underlying TrackRevisions property confirms that recording changes and displaying them are separate settings: a document can track revisions internally while a separate setting controls whether that markup is currently visible on screen. That separation matters for a disclosure mechanism: a change can be recorded and attributed even when it is not, at a given moment, being shown.

The editorial choice

Borrowing track changes as a model for disclosing AI-assisted edits is an editorial choice that works because the mechanism already does the two things a disclosure needs: it attributes each change to whoever, or whatever, made it, and it keeps the original text recoverable underneath the edit. Extending that model to an AI-assisted pass means deciding, editorially, how a tool's name gets attached to a change the way a reviewer's name already is, since the documentation describes attribution by named reviewer, not by category of editor.

What stays with the author

Deciding which tracked changes to accept, and disclosing whose or what's changes they were, remains the author's or editor's own responsibility. The documentation records changes faithfully but does not resolve how a non-human contributor should be named in that same reviewer field.

• Is every substantive change attributable to a named person or tool, not just visible as markup?
• Could a reader reconstruct what the draft looked like before this specific change?
• If an AI tool made a suggestion, does the record say so as plainly as it names a human reviewer?

A feature built to let one human editor show another what changed, without hiding the original, turns out to be the same mechanism a writer now needs to show a reader what a tool changed, provided someone decides how to name the tool in the reviewer field.