Review Excel Changes Before You Publish the Data

Before publishing an Excel table, use Copilot’s change-history skill to identify edits that need attention, then validate the release file yourself. The safe result is a sanitized publication copy verified against the reviewed source—not merely a workbook with a reassuring AI summary.

Mark each completed control; the result shows whether the workbook is ready to publish.

Suppose a shared workbook contains:

record_id	report_date	region	amount_usd
A-1042	2026-09-15	North	18450.00

The record’s status is Final. Before release, confirm that identifiers remain text, dates follow the intended convention, amounts are numeric, and no draft or private fields will reach the public file.

Ask Copilot for a Bounded Change Summary

Open the workbook in an Excel environment that supports the feature. Ask a specific question instead of only “What changed?” For example:

• Summarize changes to the Data sheet in the past seven days. Prioritize formulas, inserted or deleted ranges, and edits affecting many cells.
• Who changed Data!D2:D500, and what did they change?
• List changes made by Copilot in this workbook.
• What cell changes may have caused the formula in Summary!B12 to stop working?

Copilot can review changes across a workbook or narrow the request to a worksheet, range, cell, editor, or time period. It can report only edits available in the workbook’s underlying change history. Excel tracks supported changes for up to 365 days, but edits from unsupported versions or untracked features may be missing, according to Microsoft’s Copilot change-history documentation.

Microsoft says the generally available skill can summarize significant edits, highlight selected changes in the sheet, identify a person’s Copilot-assisted edits separately from manual edits, and investigate cell changes associated with a broken formula. It can also help reverse specified Copilot-assisted changes while preserving other edits, according to the Microsoft Excel Blog.

Treat the response as a review queue. It identifies where to look; it does not certify the dataset or prove that the history is complete.

Inspect Edits That Could Change the Published Table

Prioritize changes that can alter the meaning, shape, or coverage of the public data.

1. Inserted or deleted rows and columns: Confirm that every row still represents the same kind of record and that headers have not moved into the data.
2. Formula and reference changes: Recalculate the workbook, then compare row counts, totals, and a sample of formula results with a known-good version or source.
3. Bulk replacements: Check both the new value and the full affected range. A correction valid for one subset may be wrong when applied globally.
4. Identifier edits: Confirm that leading zeros and significant digits remain intact and that identifier columns are text. See why Excel shows long identifiers in scientific notation.
5. Date edits: Check the underlying values and exported representation, not only Excel’s display format. For a CSV release, follow the checks in Excel dates converted to numbers in CSV export.

If Copilot identifies an unwanted change, inspect the target cells before reversing it. After a repair, recalculate the workbook and rerun the affected totals, row counts, and spot checks.

Manually Check What Change History Omits

Microsoft says Show Changes tracks edits to cell values and formulas, including moving, sorting, inserting, and deleting cells or ranges. It does not currently show chart or shape edits, PivotTable operations, formatting changes, hidden cells or ranges, or filtering.

Edits made in an older or one-time-purchase Excel version cannot be tracked and can clear the Changes pane. Uploading, replacing, or saving a copy of the file can also clear that pane, according to Microsoft Support.

A pre-publication review therefore still needs manual checks for:

• hidden rows, columns, and worksheets;
• active filters that make an incomplete view appear complete;
• stale PivotTables or charts;
• number formats that conceal precision or units;
• comments, notes, formulas, or auxiliary sheets containing private information.

Do not upload sensitive information. Hiding a field, filtering it out, or excluding it from the visible table is not enough if the release workbook still contains it elsewhere.

Use Show Changes and Version History Separately

If a Copilot response looks incomplete, select Review > Show Changes and inspect the available underlying entries. The pane can help you review the location, editor, time, and previous and current cell values, although Microsoft notes that some previous values may be unavailable.

Use Version History when you need to inspect or recover an older workbook rather than reverse a narrow edit. Microsoft documents that Microsoft 365 version history works for files stored in OneDrive or SharePoint. You can open an earlier version separately and restore it if needed using Microsoft’s version-history instructions.

These controls answer different questions:

Control	Best Use	Main Limitation
Copilot change history	Summarize and investigate edits	Limited to available history
Show Changes	Inspect tracked cell entries	Omits several workbook features
Version History	Open or restore an older file	Requires OneDrive or SharePoint

None should be treated as a permanent, complete audit log. Preserve the reviewed working workbook and any separate release notes required by your process.

Create the Publication Copy After Reviewing History

Create the public copy only after completing the history review, because saving a copy may clear the Changes pane.

1. Preserve the reviewed source workbook, then create a clearly named release file such as regional_sales_2026-09-30.xlsx.
2. Remove every worksheet, column, note, comment, and object not intended for public release from that copy.
3. If the public format needs values rather than formulas, export the reviewed results while retaining formulas in the preserved source workbook.
4. Confirm unique, descriptive headers and include measurement units where needed.
5. Verify row count, column count, totals, nulls, dates, and identifiers against the reviewed source.
6. For CSV, inspect the raw export with a text-aware tool because Excel formatting does not travel with the file. Use Validate Spreadsheet Column Data Types Before Publishing as a final type check.
7. Upload only the sanitized release copy to TablePage or another public-data publisher.

Alongside the public table, record its source, coverage period, review date, and material transformations. Copilot change history can shorten the investigation, but the publication decision should rest on reproducible checks against the actual release file.