Keep each worked calculation connected to an editable record of its inputs, assumptions, steps, and displayed result. Link that record to the manuscript explanation and any related figure. When one value changes, recheck the dependent reasoning and wording rather than correcting only the final number.
Identify the calculation’s teaching role
A calculation may demonstrate a method, compare scenarios, or support a specific conclusion. Record that role before drafting the surrounding explanation. The same arithmetic can be presented differently depending on whether readers need to reproduce every step or simply understand what the result means.
For a book about planning a small exhibition, an example might estimate how many display positions fit within a chosen arrangement. Keep the arrangement assumptions explicit. A plausible total does not teach the intended method if the reader cannot tell which spacing or grouping choices produced it.
Preserve inputs separately from the displayed result
Store the starting values and their units in a structured record or a clearly organized working document. Identify which values are observations, which are illustrative assumptions, and which are derived from earlier steps. This distinction helps reviewers evaluate the example without reverse-engineering its final answer.
Give the example a stable identifier used by the manuscript and any supporting files. A filename such as calculation-final can become ambiguous as the book develops. The identifier should continue to refer to the same teaching example when a value or display convention changes.

Keep intermediate steps available for checking
Retain the operations used to reach the result, even when the published explanation omits routine detail. An editable calculation record allows a reviewer to reproduce the logic and locate an error. A screenshot of a finished number makes that investigation unnecessarily difficult.
Check that the published steps agree with the working record. If the text simplifies the method for the intended audience, make sure the simplification preserves the relevant logic. Do not allow a generated explanation to invent an intermediate step merely because it produces a smooth transition between the starting values and the answer.
Record rounding and presentation choices
Distinguish the underlying result from the value shown to readers when rounding or grouping is involved. State the convention that the example uses and apply it consistently. A later editor should be able to tell whether two slightly different displayed values represent an error or an intentional presentation choice.
Review the wording around approximations. If the explanation describes a result as exact while the example uses rounded inputs, the prose may overstate what was calculated. Keep the degree of precision appropriate to the teaching task rather than displaying extra digits simply because a tool can produce them.

Trace a changed input through the manuscript
When an input changes, identify every dependent element: intermediate values, final result, comparison statement, table, diagram, and later reference. Update them as one revision unit. A corrected table can still contradict a sentence that was written around the previous result.
Read the conclusion again after recalculation. The new result may alter the comparison the example was meant to illustrate. If so, decide whether to revise the lesson, choose a more appropriate illustrative case, or explain the changed outcome. Do not preserve the old conclusion by quietly adjusting unrelated assumptions.
Verify the exported example as a complete unit
Inspect the calculation in the final publication file with its explanation and visual material. Check symbols, line breaks, table alignment, and the association between each value and its label. A correct source record does not prove that the reader-facing example survived layout and export intact.
Retain the editable calculation and review notes with the project. Follow relevant KDP formatting guidance for the output, while treating mathematical and instructional correctness as separate editorial responsibilities. The resulting handoff should allow another reviewer to reproduce the example, understand its assumptions, and revise it without guessing how the numbers relate to the prose.
Frequently asked questions
Clear answers for this publishing decision.
Is the final answer enough to preserve?
No. Keep the inputs, assumptions, and intermediate reasoning needed to reproduce it. Those records make later corrections and independent review possible without reconstructing the method from a finished page.
What should happen when one input changes?
Recalculate the dependent steps and inspect every linked statement, table, and figure. Check whether the result still supports the lesson or comparison the example was designed to teach.
Can the manuscript show rounded values?
Yes, when the presentation is appropriate and clearly explained. Preserve the underlying calculation and the rounding convention so the displayed result remains understandable and internally consistent.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief