Excel Audit Trail: What It Tracks and How to View It

How-to basics · Updated November 20, 2026

Yes, Excel can show an audit trail, but it is not a complete, permanent record of every action in every workbook. In Microsoft 365, the most useful built-in options are Show Changes for recent cell edits and Version History for earlier saved versions; both work best when the file is stored in OneDrive or SharePoint.

What an Excel audit trail means

An audit trail is a record that helps answer who changed something, what changed, and when. Excel has several features that provide parts of that record, but they serve different purposes. Show Changes is designed to show cell-level edits in a supported shared workbook. Version History preserves earlier file versions so you can inspect or restore a saved state. Microsoft 365 administrators may also have organization-level activity logs for files.

These features are not interchangeable. A cell-change list is useful for checking an altered assumption in a budget, while a previous file version can help recover a workbook after a major mistake. Neither should be treated as proof that every action, including every view or every change made by every tool, has been captured. For regulated or high-stakes records, confirm the required controls with your organization’s IT, compliance, or records team.

How Show Changes works

In current Microsoft 365 Excel for Windows, open a workbook saved to OneDrive or SharePoint and choose Review > Show Changes. Excel opens a pane listing supported changes, with details such as the editor, time, cell location, previous value, and new value. Select an entry to navigate to the affected cell. The pane can be filtered to focus on a particular sheet, range, or person, where those filters are available in your build.

Show Changes is intended for collaboration and provides a recent history, not a permanent audit archive. Microsoft describes its history as covering up to 60 days. The amount of detail available can depend on the workbook, how it was edited, and the Excel version used. If a particular edit does not appear, do not assume the cell was never changed; check Version History and any organization-level logs as well.

For a practical review, use this sequence:

  1. Confirm that you opened the shared cloud workbook, rather than a downloaded copy with the same name.
  2. Choose Review > Show Changes and inspect the editor, time, cell, and old and new values for relevant entries.
  3. Use the pane’s filters, if present, to narrow the list to the sheet, cells, or person you need to review.
  4. For a change older than the available cell history, open Version History and compare an earlier saved version.

Excel for the web also offers Show Changes for supported workbooks, with a web-based interface. The current Microsoft 365 app for Mac may offer the feature too, but availability and interface details can vary by update. If you cannot find the command, check that Excel is up to date and that the file is stored in OneDrive or SharePoint; the browser version is another option for a cloud workbook.

Version History and recovering earlier work

Version History is a file-level record of saved versions, rather than a running list of every individual cell edit. It is available for workbooks stored in OneDrive or SharePoint, subject to the account and organization’s settings. In Excel for Windows, try File > Info > Version History. Depending on the interface, you can also select the workbook name in the title bar and open Version History. In Excel for the web, use the file name or the file’s menu to find its version history.

Open an older version to inspect its contents. If you need to recover it, consider saving a separate copy of the current workbook first, then use the restore option in the history interface. Restoring an old version can replace the current contents, so it is worth checking the date and comparing important sheets before proceeding. Version History is particularly useful when a formula was overwritten, a sheet was removed, or a group of edits needs to be rolled back.

It does not necessarily explain each difference by itself. For a careful comparison, open the older and current versions separately and check the relevant cells, formulas, and sheets. You can also ask a Microsoft 365 administrator whether the SharePoint or OneDrive environment retains additional activity information. Version retention and access may be affected by organization policy, so do not assume that a version will remain available forever.

What Excel does not record reliably

A workbook saved only on a local drive does not automatically gain a complete, permanent, cell-by-cell audit log simply because it is an Excel file. The Undo list is not an audit trail: it is intended to reverse recent actions in the current editing session, and it is not a durable record of who made an edit. Likewise, ordinary file properties such as the last-saved time are not a detailed change history.

Show Changes has scope limits. It is aimed at supported edits in a shared workbook; certain actions, editing methods, or older app versions may not produce the detail a reviewer expects. Changes made in a separate downloaded copy will not appear as edits to the cloud original unless that copy is later incorporated. A user who can edit a file may also be able to make changes outside the workflow you intended. Treat the feature as a helpful review aid, not as a tamper-proof ledger.

Also distinguish an edit history from a record of access. Knowing that a file was opened does not reveal exactly which cells a person read, and seeing a cell edit does not necessarily tell you every step the editor took. Excel’s normal interface is not designed to prove every action taken by every person.

Legacy Track Changes and shared workbooks

Older Excel versions included a feature called Track Changes, associated with the legacy Shared Workbook workflow. It could mark edits and let users review or accept changes, but it is not the same as modern coauthoring and has limitations. In current Microsoft 365 Excel, legacy commands may not appear on the ribbon by default. They are generally not the first choice for a new collaboration process when cloud coauthoring and Show Changes are available.

Some organizations still encounter legacy workbooks or procedures built around these commands. Before changing such a file, check how it is shared and whether other users depend on the old workflow. Mixing older features with modern collaboration can cause confusion about which changes are visible and where the authoritative copy lives. For a new process, use a cloud-stored workbook and test the required review steps with the people who will maintain it.

Organization-level audit logs

For workbooks managed by a business or school, Microsoft Purview audit logs may provide broader information about activity in Microsoft 365, depending on the organization’s configuration, licensing, permissions, and retention rules. An administrator can search for relevant events involving services such as SharePoint or OneDrive. These logs can help investigate file activity, but they are not necessarily a cell-by-cell history of the workbook’s contents.

Employees usually cannot assume they can access these logs themselves; access is controlled by the organization. Ask an administrator or compliance contact what events are logged, how long records are retained, and who can search them. If a business needs reliable evidence of approvals or edits, it should define the process and retention requirements rather than rely on a workbook feature alone.

Choosing the right option

Choose the feature that matches the question you need to answer:

  • Who changed this cell recently? Use Show Changes in a supported cloud workbook.
  • What did the workbook look like before a major edit? Use Version History and inspect an earlier saved version.
  • Who accessed or acted on a file across the organization? Ask an administrator about Microsoft 365 audit logs.
  • Do you need a formal approval record? Use an approved business workflow with documented permissions, review, and retention; do not assume ordinary Excel history meets the requirement.

For a small team, a sensible baseline is to keep the authoritative workbook in a managed OneDrive or SharePoint location, limit editing access to people who need it, and use Show Changes when reviewing recent edits. For critical work, keep a separate approved record of decisions and have the owner confirm that the organization’s backup and retention policies cover the file.

Common problems and practical checks

If Show Changes is missing or empty, first check the file location and account. A local copy, email attachment, or workbook opened from an unrelated folder may not be the shared cloud file. Confirm that you are signed in to the account with access, and check for Microsoft 365 updates. If the relevant edit is older than the recent history window, look in Version History instead.

If collaborators say they edited a cell but you cannot find an entry, verify that everyone edited the same workbook and not separate copies. Ask which Excel app and version they used, and whether the change was made through an unsupported workflow. Compare the current cell with a previous saved version, and contact the Microsoft 365 administrator if a formal investigation is needed. Do not overwrite or restore the workbook until you have preserved a copy of the current state.

A useful prevention step is to agree on one shared file location and a clear naming convention. Multiple files named “Final” or “Final revised” make it difficult to establish which changes belong to the official workbook. Use permissions to reduce accidental edits, and communicate when a version is being reviewed or approved. These process controls do not create a perfect audit trail, but they make the available history more useful.

Frequently Asked Questions

Can I see who edited an Excel cell?
Often, if the workbook is stored in OneDrive or SharePoint and the edit is available in Show Changes. Open Review > Show Changes and look for the editor and cell details. It is not guaranteed to show every edit in every circumstance.

How far back does Excel Show Changes go?
Microsoft describes Show Changes as providing up to 60 days of change history. For older work, check Version History or ask an administrator about organization-level logs and retention.

Does Excel track changes in a file on my computer?
A local workbook does not automatically have the same cloud-based Show Changes and Version History experience. Save the shared authoritative file to OneDrive or SharePoint if those collaboration features are needed.

Can I recover a deleted sheet or overwritten formula?
Possibly. Check Version History for a saved version from before the change, inspect it, and preserve the current file before restoring anything. Recovery depends on whether a suitable version was retained.

Is Excel’s audit trail tamper-proof?
No. Excel’s built-in history features are useful for collaboration and recovery, but they should not be treated as an immutable, complete compliance log. Ask your organization about controls designed for formal auditing.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.