Preserve Computation in Editable Artifacts

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Deliver an editable order workbook with quantity A2=10 and price B2=15. Total must change with inputs. A literal 150 in C2 looks correct but stays stale when the user changes quantity to 12.

Mechanism

Identify input and computed cells while preserving existing file conventions. Write =A2*B2 in C2 and briefly label editable inputs and units. Do not save a cached-values-only load that discards formulas. Recalculate with the target engine, then inspect formula strings and results separately. Change quantity in a verification copy to test dependencies while preserving delivery inputs.

Bad example

Create an editable order with 10 in A2,15 in B2 and 150 in C2. Make it attractive and deliver.

Good example

Create the same editable order with A2=10, B2=15 and C2 formula =A2*B2. Label quantity and price as inputs. Recalculate with the target engine and verify 150. In a copy, change A2 to 12 and confirm 180 with the formula retained; restore original inputs in the final artifact.

Why the change matters

Editable artifacts carry relationships between inputs and results, not just current values. Formulas preserve those relationships; real recalculation and input perturbation expose apparently correct hardcoded outputs.

Observable expectation

Record both formula =A2*B2 and cached result 150. In the verification copy, A2=12 yields 180. Reopen the final file to confirm the formula remains and original quantity 10 was not changed by verification. An empty cache does not alone imply a formula error; check whether calculation ran.

Limits

Immutable snapshots may legitimately contain values; formulas suit updating models. Verify engine compatibility, calculation mode, external links and macros under the file contract. Error-free formulas do not establish correct business logic, and reading cached values alone does not prove editability.