Estimating by rounding

Activities to try

1. 1

   Sensible or silly? Judge before you compute

   Why it works: A rounded ballpark, formed before calculating, is enough to catch a wildly wrong answer — so estimation is a genuine check, not busywork or a guess made after the fact.

   1. Look at a calculation paired with a proposed answer, e.g. 412 + 389 = 121, and decide quickly whether it is 'sensible' or 'silly' BEFORE working out the exact answer
   2. Say aloud the rounded ballpark you used: '400-and-something plus about 390 is roughly 800, so 121 can't be right'
   3. Judge a batch of items, some with reasonable answers (e.g. 801) and some deliberately wrong, flagging the silly ones
   4. Record your estimate and the exact answer side by side in two columns, so you can compare the ballpark against the worked result
   5. Only after committing to your judgement, work out or reveal the exact answer and see whether your estimate caught the nonsense
2. 2

   Check by adding back: the inverse as an independent test

   Why it works: Checking with the inverse operation is an independent re-derivation of the answer, whereas repeating the same subtraction just reproduces the same potential error.

   1. Take a completed subtraction, e.g. 623 − 178 = 445, and check it by adding the answer back: 445 + 178
   2. Confirm that the sum returns to the starting number (623) — if it does, the subtraction is verified
   3. Contrast this with simply redoing 623 − 178 again, and explain why repeating the identical operation can easily repeat the original mistake, while adding back tests the answer a different way
   4. Use a bar model (the whole minus one part returns the other part) and a fact-family triangle linking the three numbers to see how addition and subtraction undo each other
3. 3

   How do you KNOW it's right? Reasoning discussion

   Why it works: An estimate bounds roughly how big an answer should be and flags gross errors, but it does not guarantee exactness; the inverse gives a separate confirmation. Knowing an answer is sensible is a matter of reasoning, not only recomputation.

   1. Respond to a prompt such as: 'A friend adds 412 + 389 and gets 121; another gets 801. Without working out the exact sum, how could you tell which answer must be wrong?'
   2. Explain how to check a subtraction like 623 − 178 WITHOUT just doing the same subtraction again
   3. Discuss: if your estimate and your exact answer disagree, which do you trust, and what do you do next?
   4. Consider whether an answer could be close to the estimate but still wrong — so what does an estimate tell you, and what does it not?