Singapore School Mathematics Operating Manual · Chapter 53
Use totals, subtotals, conservation-style identities and independent reconciliation checks to verify that every mathematical part returns consistently to the whole.
This is a cross-topic operating-control chapter for the Singapore Mathematics spine. It complements existing BTT owners and is intended to connect Primary reasoning, PSLE, SEC G1/G2/G3, E-Math, A-Math and JC Mathematics without replacing their topic-specific teaching.
1. Reconciliation compares two routes to the same total
Make reconciliation compares two routes to the same total explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
2. Parts should add back to the whole
Make parts should add back to the whole explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
3. Percentages of exhaustive categories should reconcile to 100%
Make percentages of exhaustive categories should reconcile to 100% explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
4. Probability branches should reconcile to 1
Make probability branches should reconcile to 1 explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
5. Frequency tables should reconcile to sample size
Make frequency tables should reconcile to sample size explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
6. Angles reconcile to geometric totals
Make angles reconcile to geometric totals explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
7. Area decompositions should reconcile
Make area decompositions should reconcile explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
8. Algebraic expansion can reconcile factorisation
Make algebraic expansion can reconcile factorisation explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
9. Cash-style balance identities illustrate flow reconciliation
Make cash-style balance identities illustrate flow reconciliation explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
10. Stock and flow must not be confused
Make stock and flow must not be confused explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
11. Beginning plus change should reconcile to ending value
Make beginning plus change should reconcile to ending value explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
12. Unit conversions should reconcile both ways
Make unit conversions should reconcile both ways explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
13. Rounding can create small reconciliation gaps
Make rounding can create small reconciliation gaps explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
14. Large gaps signal missing or duplicated components
Make large gaps signal missing or duplicated components explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
15. Double counting breaks reconciliation
Make double counting breaks reconciliation explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
16. Missing cases break reconciliation
Make missing cases break reconciliation explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
17. Independent totals are stronger checks
Make independent totals are stronger checks explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
18. Reconciliation can locate errors by subsection
Make reconciliation can locate errors by subsection explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
19. Tolerance should be stated for approximate reconciliation
Make tolerance should be stated for approximate reconciliation explicit before calculation. Use a small worked example, preserve the active domain and units, and check the result against an independent representation, bound or baseline where possible. The purpose is to control reasoning across topics rather than introduce a competing topic owner.
20. A reconciliation audit
Ask what must remain consistent, what is allowed to change, which bound or comparison is global, and what evidence would make the conclusion auditable from the original problem.
21. Worked examples
Example 1. If category percentages are exhaustive, their total should be 100% apart from justified rounding. A larger discrepancy signals a missing, duplicated or misclassified part.
Example 2. If a minimisation candidate uses 8 containers and a capacity argument proves at least 8 are necessary, the lower bound and construction match; 8 is optimal.
Example 3. In a what-if table, change one named parameter from the baseline while keeping the remaining assumptions fixed before interpreting the difference.
Example 4. Translating coordinate axes changes point coordinates but does not change the physical distance between the same two geometric points.
22. Independent practice
1. Give one mathematical total that can be reconciled in two ways.
2. Explain how a lower bound plus a matching feasible construction can prove a minimum.
3. State the difference between a baseline and a scenario.
4. Name one quantity preserved when a coordinate system is translated.
5. Explain why all compared scenarios must use consistent definitions.
23. Worked answers
1. Examples include probability branches summing to 1, frequencies summing to sample size, or component areas summing to total area.
2. No feasible answer can be below the lower bound, and the construction attains it, so nothing better exists.
3. The baseline is the reference set of assumptions; a scenario changes specified assumptions or parameters relative to it.
4. Distance between fixed geometric points.
5. Otherwise differences can be caused by hidden definition changes rather than the named scenario change.
24. Continue through Batch 14
Return to the BTT Mathematics Hub for Batch 14.