# What must survive when a spreadsheet model becomes a shared product?

By Sean Everett · October 6, 2026

Preserve the model’s inputs, calculation behavior and operating meaning when moving beyond a workbook. Test representative cases, resolve differences deliberately and define who controls the shared version.

Topics: Product modernization · Calculation models · Data quality

## Describe the model behind the visible cells

Begin with the decision the workbook supports and the outputs people actually use. Identify input fields, units, assumptions, intermediate calculations and external dependencies. Include manual adjustments and steps performed outside the file. A screen showing the same totals can conceal a different model.

Microsoft’s Excel recalculation documentation describes dependency tracking, calculation order and automatic or manual recalculation. Inventory the behavior the current workbook relies on, including iterative calculations where present. A migration needs a deliberate replacement for that behavior rather than an assumption that formulas will execute equivalently.

Choose a reference version and a responsible model owner. Record which variations are intentional and which copies contain unreviewed changes. Establish whether the project is preserving an accepted method, correcting known errors or changing the method itself. Those changes need different acceptance evidence.

## Compare behavior under defined inputs

Create a set of representative input cases with reviewed expected outputs. Include ordinary work, boundary values, missing inputs and conditions that should produce an error. Compare important intermediate results as well as final displays so an accidental cancellation of differences does not look like equivalence.

Microsoft documents both floating-point limitations and Excel’s alternative date systems. Check numeric representation, rounding and date interpretation explicitly when moving calculations to another runtime. Define acceptable differences according to the model’s use, and investigate discrepancies before choosing a convenient tolerance.

The government AQuA Book distinguishes checking implementation against its design from validating whether the model meets users’ needs. Apply both checks: reproducing an old workbook’s answer can establish consistency while leaving the underlying method’s suitability unresolved. Review consequential assumptions with someone qualified to assess the model.

## Give the shared model a controlled operating life

Define who can change inputs, calculation rules and published assumptions. Separate a person’s exploratory scenario from the accepted shared version. Keep enough version information with an output to reconstruct which model and inputs produced it, within the applicable access and retention arrangements.

Agree how corrections reach dependent reports and integrations. Identify which distributed copies remain in use and how their users will recognize the supported replacement. Moving calculation into a shared service does not automatically remove old exports or change who may receive the results.

Make acceptance cover calculation checks, user interpretation and the complete handoff into ordinary work. Retain reviewed test cases for later changes and assign ownership for failures and model updates. Retire the old workflow only after its required uses have a supported path in the new product.

## Related reading

- [Microsoft: Excel recalculation and dependencies](https://learn.microsoft.com/en-us/office/client-developer/excel/excel-recalculation)
- [Microsoft: Floating-point arithmetic in Excel](https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/excel/floating-point-arithmetic-inaccurate-result)
- [Microsoft: Date systems in Excel](https://support.microsoft.com/en-us/excel/date-systems-in-excel)
- [UK Government: The AQuA Book on analytical quality](https://www.gov.uk/guidance/the-aqua-book)
- [UK Government: Model ownership and versioned records](https://www.gov.uk/government/publications/government-analysis-functional-standard--2/government-functional-standard-govs-010-analysis)
- [Planning a legacy-platform migration](https://evergences.com/insights/legacy-platform-modernization-roadmap/)

Source: https://evergences.com/insights/spreadsheet-model-migration/