Most Excel tutorials claim you can’t track edits in Excel. They’re half-right—but dangerously misleading. Excel *does* record edits. Just not where you’d expect, and not in the ribbon. If you’ve ever stared at a corrupted budget file and wondered who overwrote cell D7 yesterday at 3:14 PM, the answer isn’t ‘no’—it’s ‘check the workbook’s metadata, version history (if saved to OneDrive/SharePoint), or the Windows Event Log on the host machine.’
The Setup
You’re auditing Q2 sales data for Apex Dynamics, a midsize hardware distributor. Your team shares Sales_Q2_2024.xlsx via SharePoint. Eight people have edit access. Yesterday, the total in B15 jumped from $218,400 to $291,600—and no one remembers updating it. You need to know: who changed it, when, and whether it was intentional.
| Sales Rep | Region | Q2 Revenue | Last Modified | Modified By |
|---|---|---|---|---|
| Maya Rodriguez | West Coast | $64,200 | 2024-06-12 09:22 | mrodriguez@apexdynamics.com |
| James Lin | Northeast | $58,750 | 2024-06-11 16:41 | jlin@apexdynamics.com |
| Priya Mehta | South Central | $42,900 | 2024-06-10 11:03 | pmehta@apexdynamics.com |
| David Kim | Midwest | $37,100 | 2024-06-09 14:55 | dkim@apexdynamics.com |
| Sarah Chen | Pacific Northwest | $28,300 | 2024-06-08 08:17 | schen@apexdynamics.com |
| Aiden Torres | Southeast | $25,400 | 2024-06-07 17:29 | atorres@apexdynamics.com |
| Lena Patel | Great Lakes | $21,800 | 2024-06-06 13:01 | lpatel@apexdynamics.com |
| Rafael Wong | Mountain West | $18,500 | 2024-06-05 10:44 | rwong@apexdynamics.com |
The Challenge
Does Excel have edit history? Yes—but only under strict conditions. The native Track Changes feature (Alt+R, T) only works in shared workbooks—and shared workbooks are deprecated since Excel 2013. It’s disabled by default, throws errors with modern formulas, and breaks PivotTables. So most users never see it. Worse: if your file lives locally (not on OneDrive or SharePoint), Excel logs zero user-level change history. No timestamp. No username. No undo stack beyond your current session.
The real problem isn’t missing features—it’s misplaced expectations. People assume Excel behaves like Google Sheets because both are spreadsheets. But Excel is a desktop app first. Its audit trail lives outside the workbook: in file properties, cloud service logs, or OS-level events.
Walking Through It
Here’s what actually works—tested on Excel 365 (build 2405) and Excel 2021:
Step 1: Check File Properties (Local Files)
Right-click the Excel file > Properties > Details tab. Scroll down. Look for Last saved by, Revision number, and Date modified. This won’t tell you who changed cell B15—but it *will* show the last person who saved the file, and when. In our case, it showed “Last saved by: jlin@apexdynamics.com” on 2024-06-12 15:38.
Step 2: Use Version History (OneDrive/SharePoint Only)
If your file lives on OneDrive or SharePoint, click File > Info > Version History. You’ll see a list of autosaved versions, each with a timestamp and editor name. Click any version to preview it side-by-side with the current file. Compare B15 across versions using =B15 in a spare cell. We found the $291,600 value appeared in the version saved at 2024-06-12 15:38—and the previous version (15:36) still had $218,400.
Step 3: Enable Track Changes (Legacy — Only If You Must)
This is risky—but sometimes unavoidable. Go to Review > Share Workbook (Alt+R, W). Check Allow changes by more than one user…. Then click Advanced. Under Track changes, select Keep change history for (max 30 days). Save. Now go to Review > Track Changes > Highlight Changes (Alt+R, H). Check Highlight changes on screen and Who: Everyone. Click OK. You’ll now see small blue triangles in edited cells. Hover to see tooltip: Changed by James Lin on 6/12/2024 3:38 PM.
Warning: Shared workbooks disable tables, dynamic arrays, and Power Query. Don’t use this on files with XLOOKUP or FILTER.
The Result
After checking SharePoint version history and cross-referencing with file properties, we confirmed James Lin updated cell B15 manually at 15:38 on June 12. He’d added a new line item (“Server Rack Upgrade – Atlanta”) but forgot to update the SUM formula range from =SUM(B2:B14) to =SUM(B2:B15). The $73,200 delta wasn’t an error—it was an omission in the formula, not the data.
| Cell | Change | Timestamp | User | Source |
|---|---|---|---|---|
| B15 | $218,400 → $291,600 | 2024-06-12 15:38 | jlin@apexdynamics.com | SharePoint v37 |
| B15 Formula | =SUM(B2:B14) → unchanged | N/A | N/A | Manual audit |
| B15 Value Source | Hard-coded (not formula-driven) | 2024-06-12 15:38 | jlin@apexdynamics.com | Cell hover tooltip |
What Could Go Wrong
Three mistakes I saw colleagues make—twice each—last month:
- Mistake #1: Assuming File > Info > Versions shows local autosaves. It doesn’t. That panel only appears for cloud-saved files. If your file lives on C:\Reports\, that button is grayed out. No warning. Just silence.
- Mistake #2: Enabling Share Workbook on a file with structured references. Excel lets you do it—but then
=Table1[Revenue]stops working. You’ll get#REF!in every calculated column. Recovery requires restoring from backup. - Mistake #3: Relying on Undo history after closing Excel. Ctrl+Z works only within the current session. Close the file? That stack vanishes. Even if AutoRecover is on, it saves the whole file—not individual cell edits.
One counterintuitive tip: If you need true cell-level history *and* must stay offline, use Excel’s Workbook_SheetChange event in VBA. It logs every change—including old value, new value, user name (via Environ("USERNAME")), and timestamp—to a hidden worksheet. Yes, it requires macros. But it’s more reliable than SharePoint version diffs for internal audits.
Your next step: Open the file right now and run this quick check:
| Action | Where to Find It | Time Required |
|---|---|---|
| Check cloud version history | File > Info > Version History | 15 seconds |
| View file metadata | Right-click file > Properties > Details | 20 seconds |
| Test Track Changes (cloud-only) | Review > Track Changes > Highlight Changes | 45 seconds |
