Track Changes in Excel

What this does

Excel's classic Track Changes is not the Word feature people expect, and Microsoft has retired it from the ribbon. It only ever worked by turning the file into a Shared Workbook, which disabled tables, conditional formatting, charts and much else, and it stored the history inside the file. What replaced it is Version History: a workbook stored on OneDrive or SharePoint keeps timestamped versions you can open, compare and restore, with the author recorded for each. If you still need the legacy behaviour it exists, but it must be added back manually via File ▸ Options ▸ Quick Access Toolbar ▸ All Commands ▸ Track Changes (Legacy). Where you need a real audit trail of who changed which cell, neither feature is the right answer — a change-log sheet, or a database, is. Before you run it on a workbook other people depend on, try it on a copy or a few rows first. Undo only reaches back through the current session, so a quick trial run is the cheapest way to see exactly what will change before the file is saved and shared. Treat “track changes in excel” as a small repeatable workflow rather than a one-off click you hope to remember next time. Use a small test block before the live file, so any surprise in the affected cells shows up while it is still harmless. When this is a ribbon command, the selection matters more than the button: confirm the range, apply the command, then spot-check the output before saving. That turns a workflow that saves repeating the same clicks every week into a method you can reuse, explain, and defend when the workbook leaves your screen.

A worked example

A budget on SharePoint edited by four people. File ▸ Info ▸ Version History shows an entry per save session with the editor's name. Opening the version from Tuesday afternoon shows the numbers before the forecast revision, and Restore puts them back as the current version — leaving the intervening versions intact. The question is nearly always "what did this look like before, and who changed it" — and on a cloud-stored workbook Version History answers that without the costs the legacy feature imposes. When the result is not what you expected, undo straight away rather than repairing it by hand — undo restores the sheet exactly, while manual fixes tend to leave small inconsistencies behind that surface later.

In Google Sheets

This is a command rather than a formula, so there is no syntax to carry over. Google Sheets arranges its commands in menus across the top instead of a ribbon, names some of them differently and does not have every Excel command — look for the equivalent in the Sheets menus or its help before assuming the steps match. Nothing on this page is behind a login or a download: the exact answer is at the top, and the detail below it is there for when you need it. That is the whole promise here — the answer first, and just enough context to make it stick. Treat “track changes in excel” as a routine rather than a one-off. Once you know which setting or command controls it, the same few steps handle every workbook where it comes up in Excel, and you can explain them to a colleague in a sentence.

Common mistakes

• Expecting Word-style coloured markup in the cells — Excel never showed changes that way.
• Turning on legacy Track Changes and losing tables, slicers and conditional formatting to Shared Workbook mode.
• Relying on Version History for a local file, where nothing is being versioned at all.
• Treating the history as an audit log: it records saves, not individual cell edits, and it is not tamper-proof.
• Assuming AutoSave and Version History are the same thing — AutoSave writes, Version History is what lets you go back.

Frequently asked questions