Data Management
Set up spreadsheet handoffs that preserve meaning
Reduce import errors with stable columns, clear formats and a documented acceptance check.
IGS Editorial · 3 min read · Updated 17 November 2026

Spreadsheets are convenient exchange tools because people can inspect and edit them easily. That flexibility also creates handoff problems. A renamed column, automatic date conversion or hidden filter can change what the receiving team understands.
Treat a recurring spreadsheet exchange as an interface. Define its structure, owner and validation rules. The aim is not to remove every human action, but to make the transfer predictable enough that errors are found before they affect downstream work.
Establish a stable template
Use clear column names and document required fields. State whether extra columns are allowed and whether column order matters to the receiving system. Avoid merged cells and decorative headings inside the data range when the file will be imported.
Include a template version outside the record data or in a clearly defined metadata area. If the format changes, the receiving process should be able to recognise it rather than silently interpreting the new file as the old structure.
Protect data types
Identifiers may lose leading zeros if treated as numbers. Long numeric-looking values may display in scientific notation. Dates can change interpretation across regional settings. Define the intended types and test how the chosen export format preserves them.
For CSV files, confirm delimiter, encoding and quoting behaviour. A comma inside an address should not create an extra column. Test line breaks and special characters using realistic examples.
Distinguish values from formulas
Decide whether the recipient needs calculated results or the workbook's formulas. External links and unavailable source files can make formulas unreliable after transfer. A values-only export may suit an import while the working workbook remains separate.
Do not assume a displayed total establishes that every row is included. Filters, hidden rows and stale calculations can affect interpretation. Define the validation method independently of visual appearance.
Add an acceptance check
Compare expected row counts, unique keys and key totals where meaningful. Validate required fields and reference values before processing. Return a structured error list rather than making undocumented corrections in the received file.
For example, a supplier file with duplicate item codes should trigger an agreed review route. The receiver should not choose one row arbitrarily if different prices or descriptions are present.
Keep transfer history
Use an agreed naming and version rule, secure transfer location and acknowledgement process. Record which file was accepted and whether a replacement supersedes it. Avoid multiple attachments with names such as final-new-latest that leave ownership unclear.
Review recurring failures with the source team. The best improvement may be a validation rule at export rather than another manual check at receipt. A dependable spreadsheet handoff preserves meaning from the person preparing the file to the system and team using it.
Test the file on the receiving side
Prepare a small exchange file containing a leading-zero identifier, an address with a comma, a non-English character and an ambiguous-looking date. Open or import it using the actual receiving process. Compare the resulting values with the intended ones.
The test may reveal that the sender's workbook looks correct while the exported CSV changes meaning. Adjust the interface definition and export procedure, then repeat the receiving-side check. Do not rely solely on the file's appearance in the author's application.
Add a duplicate key and an incomplete required field to test rejection behaviour. Confirm that the receiver reports errors without silently dropping rows or choosing arbitrary values. Record the accepted file version and acknowledgement. A small, carefully designed test file can reveal more than a large ordinary batch because it deliberately exercises the conditions that commonly break handoffs. Keep it as a regression example when templates or importing tools change, using synthetic information that is safe to share.
