The most useful starting point is a short brief that explains what the file represents and what you want to do with it. You do not need to solve the data problems first. Identify the source, describe the result you need, and note the decisions that only your team can make.
1. Describe the result in one sentence
Start with the task the cleaned file should support. “Make this spreadsheet better” leaves the reviewer guessing. A more useful brief is: “Prepare a supplier list we can check, using our approved IDs. Flag uncertain matches and keep the original records.”
State who will use the result, the output format they need, and whether this is a one-time handoff or a recurring process. Cleaning a single file and building a report you can refresh involve different work.
2. List the files before attaching them
Record the filename, file type, export date, relevant sheet names, approximate row count, and source system. Explain whether one file is the source, an approved reference, or an earlier attempt. Identify the current version without replacing or overwriting the original.
Note hidden or filtered records, formulas, linked files, or other dependencies you know about. Say whether all rows should be included. If several versions disagree, name the person who can determine which source to use; do not silently pick the newest-looking copy.
3. Explain what a row and each important field mean
Specify whether a row is an order, order line, delivery, invoice line, or something else. Similar-looking rows may represent different events. Give definitions for the identifiers, dates, quantities, amounts, and status fields that matter to the result.
- Identifiers: Are leading zeros, punctuation, or letter case meaningful?
- Dates: What format is used, and what event does the date represent?
- Amounts: Which currency is used, and what does the amount include?
- Quantities: What is the unit, and are pack sizes or returns involved?
- Blanks: Does an empty cell mean unknown, not applicable, or a missing entry?
If you do not know an answer, mark it as an open question. An open question is more useful than a guessed definition.
4. Separate known rules from decisions still needed
Share approved reference lists and examples of a correct record. State which fields can be reformatted and which changes need approval. Explain any existing duplicate rule, including what makes two records the same business event.
Keep a short decision list: question, evidence needed, decision owner, and effect on the output. For example, “Can these two vendor names share one ID? Purchasing owner to confirm against the approved master.” Do not turn a name similarity into a confirmed match.
5. Start with a safe, representative sample
To discuss the project, describe the file and provide a redacted or public-source example if useful. Include a normal row and a few problem rows: a suspected duplicate, an ambiguous date, a missing value, or an amount mismatch. A perfect sample can hide the work the project actually needs.
Remove unnecessary personal details and full payment information. Do not include passwords, keys, or access tokens. Check screenshots, comments, extra sheets, and filenames as well as visible cells. Agree on the transfer method, tools you allow us to use, access, and retention expectations before sending working data.
A brief you can fill in
- The result we need: [describe the decision or task the prepared file should support]
- Source files and size: [filenames, dates, sheets, and actual row counts]
- Rules already approved: [reference lists, identifiers, and permitted changes]
- Questions still open: [issue, evidence needed, and decision owner]
- Requested outputs: [prepared file, source copy, change log, and review list]
- Completion checks: [row accounting, comparable totals, and representative record checks]
Leave an answer open when you do not know it. Whether the project fits a fixed package depends on its actual inputs and complexity as well as row count.
6. Agree on how to check the finished work
- The original file and cleaned version are clearly labeled.
- Every source row can be accounted for, including excluded or held rows.
- Comparable counts and amounts can be reconciled using the agreed basis.
- Rules, assumptions, and exceptions are documented.
- The reviewer knows which decisions are still open.
- The file format, included revision, and limits of the work are written down.
Include a deadline to consider and any dependency on a colleague’s decision. Keep new source files or new output requirements separate from corrections within the agreed scope.
Use the brief, then review the method
Download the editable project brief and cleanup preparation checklist. They use placeholder fields and can be completed locally.
The reconciliation guide covers the cleanup method itself. If you need help with the work, review the spreadsheet cleanup packages and limits, then send a file description to discuss the scope.
Use these checks with your own records, systems, and approved policies. Linked portfolio examples identify their public sources and limits.
Clear scope. Careful checks.