The hidden-data check to make before sharing an Excel workbook
Share
Published
Before sharing an Excel workbook, make a separate release copy, remove information the recipient does not need, inspect hidden content and reopen the final file. Hiding a worksheet or filtering a customer list does not remove the underlying records.
A spreadsheet can look ready to send while still carrying last month’s customer list, comments about a supplier or an internal pricing sheet. The visible tab tells you what the sender intended to share. It does not tell you everything the file contains.
For a small business, the useful question is specific: what does this recipient need to do with this file? A courier needs delivery details for assigned orders. A designer preparing an annual report may need totals. Neither task automatically requires the original customer database.
Start with a release copy
Keep the working workbook in its approved location. Create a separate copy for the recipient and give it a clear name, such as delivery-round-approved.xlsx. Avoid a filename that exposes a customer’s condition, complaint or account status.
Write down the intended contents before editing. That might be today’s order reference, delivery address and contact number. Compare every column against that purpose. If the recipient only needs regional sales totals, prepare the totals rather than sending transaction-level records and asking them to ignore the names.
This is also the point to choose a format. A controlled folder can let you withdraw future access. An attachment creates another copy. A PDF may suit a fixed report, but exporting to PDF still requires a check of the pages and metadata. Our PDF redaction guide explains why covering text visually is insufficient.
Check beyond the visible worksheet
Review hidden rows, columns and sheets. Remove filters in the release copy to see the records they conceal. Check comments, notes, names, document properties, embedded objects, external connections and any supporting data used by charts or pivot tables. Which features are present depends on the workbook.
Microsoft’s Document Inspector guidance recommends inspecting a copy because removal can be difficult to undo. In supported desktop Excel versions, the route is File, Info, Check for Issues, Inspect Document. Review the results before removing anything: deleting hidden inputs can change calculations. The inspector is a useful check, not a substitute for understanding the file.
| What you find | Release decision | Check afterwards |
|---|---|---|
| A hidden sheet of customer records | Exclude it if the recipient does not need those records | Confirm totals still make sense |
| Internal comments about a customer | Remove comments from the release copy | Reopen and inspect the comments pane |
| A chart linked to another workbook | Decide whether the connection or source data is required | Check the output without access to the original |
| Extra names in a filtered table | Create a file containing only the approved records | Clear filters and count rows again |
A worked delivery example
Consider this fictional workflow. A retailer’s working file contains 620 orders, customer emails, delivery notes and refund histories. A rider has been assigned 14 deliveries. The export should start from those 14 assignments, with an agreed set of necessary fields.
The release reviewer checks that there are 14 data rows, no hidden worksheet and no refund comments. They also inspect free-text delivery notes. A note copied from a customer conversation may contain information that has nothing to do with finding the address.
The rider receives access through the agreed channel. The dispatch owner records the file version and the recipient. If assignments change, the owner replaces the dispatch list through that same channel rather than sending competing versions into several group chats. See our courier data-handover checklist for that part of the workflow.
Reopen the exact file you will send
Close the release copy and reopen it from its final location. Check every sheet and exported page. Ask a second person to review particularly sensitive releases. They should use the approved field list, not merely confirm that the file opens.
For a shared link, check the recipient permissions as well as the contents. A clean workbook in a folder available to everyone still has an access problem. For an attachment, verify the full email address after selecting the recipient; display names can look similar.
Keep a short release record containing the owner, purpose, approved fields, row count, version, recipient and review date. This records the decision without making yet another copy of the customer data.
Common questions
Does hiding a column protect its contents?
No. Hidden contents remain in the workbook and may be revealed by someone who receives it. Remove unnecessary data from the release copy and verify the saved result.
Is CSV automatically safe?
A CSV does not preserve Excel’s multiple-sheet structure, but its visible fields can still disclose too much. Check the exported text, selected records and destination before sending it.
What if the wrong workbook has already been sent?
Report it promptly through the organisation’s incident route. Preserve the facts and use the wrong-recipient email response checklist rather than relying on a recall message.
Featured image: AI-generated conceptual illustration.
