ACARA v9 CONTENT DESCRIPTION “estimate the quantity of objects in collections and make estimates when solving problems to determine the reasonableness of calculations”
An estimate is a sensible approximation reached on purpose, not a wild guess. The difference is that an estimate uses something you know — a benchmark, a round number, a count of one group — to get close on purpose. Year 3 estimates in two settings the curriculum names: judging how many objects are in a collection without counting them all, and checking whether the answer to a calculation is reasonable. Both rest on the same instinct: trade a little exactness for a lot of speed, then decide whether being close is good enough for the question at hand. Often it is.
The benchmark of ten
You cannot count a scatter at a glance, but you can compare it to a known ten.
Use the group of 10 as a yardstick. About how many dots are scattered on the right?
Estimate a collection with a benchmark
Nobody can count a jar of jellybeans at a glance, but anyone can compare it to a known amount. Hold ten in mind, picture how many tens would fill the jar, and you have an estimate. The benchmark of ten is the simplest yardstick, and it works because the eye is far better at judging how many tens than at counting individual objects. This is a genuinely useful life skill — estimating a crowd, a pile, a handful — and it teaches that a good estimate always leans on a known quantity rather than a feeling.
Group to estimate
Estimate a big collection by counting one group and scaling up.
Counting every dot is slow. Count just one group, then judge how many groups there are.
Count one group, scale up
When a collection falls into roughly equal groups, the fastest estimate is to count one group carefully and judge how many groups there are. About twenty in a box and about four boxes means about eighty — an estimate built from a small exact count and the multiplication of the previous unit. This grouping strategy is how people estimate seats in a hall, books on a shelf, or cars in a car park, and it shows estimation and multiplication working together: the times facts are not only for exact answers, they power quick approximations too.
Round then add
Round each number to the nearest ten, then add for a fast estimate.
To estimate 38 + 51, round each to the nearest ten first.
Round, then calculate
The most powerful estimation tool is rounding to the nearest ten before calculating. To estimate 38 + 51, round to 40 and 50 and add to get 90 — quick, and within one of the true answer. Rounding replaces awkward numbers with friendly ones that are easy to work with in your head, and for most everyday purposes the rounded answer is close enough. This is the same place-value thinking from earlier units, used in reverse: where before we cared about every digit, now we deliberately blur the small ones to move fast.
Estimate a product
Round the awkward factor to a ten, then multiply for a quick estimate.
To estimate 4 × 19, round 19 to the nearest ten.
Estimating products
Multiplication estimates the same way: round the awkward factor to a ten, then multiply. For 4 × 19, round 19 to 20 and the estimate is 80, close to the true 76. Because one factor is now a round number, the multiplication is one a child can do instantly, and the answer is a reliable ballpark. Estimating a product before working it out exactly is what lets a child predict roughly how big the answer should be — which is exactly what makes the next idea, checking reasonableness, possible.
Reasonable answer?
An estimate is the quickest way to catch an answer that cannot be right.
Without working it out exactly: is 23 × 4 = 92 reasonable?
Estimate to check an answer
The descriptor's real prize is using estimation to judge whether a calculation is reasonable. If a child works out 23 × 4 and gets 412, a quick estimate — about 20 × 4 = 80, a bit more — shows at once that 412 is far too big; the answer should be near 90. Estimating first, or estimating to check, catches the slips that produce wildly wrong answers, and it is a habit good mathematicians never drop. An exact method gives an answer; an estimate tells you whether to trust it. The two together are far stronger than either alone.
Too high or too low?
Knowing which way you rounded tells you if your estimate is above or below the truth.
The estimate is 90. Will it be higher or lower than the true answer?
Knowing which way you rounded
A careful estimator also knows the direction of their error. If both numbers were rounded up, the estimate sits above the true answer; if both were rounded down, it sits below; and if one went each way, the errors tend to cancel and the estimate lands very close. Knowing whether an estimate is a little high or a little low makes it more useful still — you can say not just about ninety but a bit under ninety. With benchmarks, grouping, rounding, product estimates, reasonableness checks and the direction of rounding all in hand, estimation becomes a constant companion to exact calculation — and the modelling and money problems of the next unit lean on it at every step.
Quick self-check
1. What is the best estimate for 38 + 51?
2. 4 × 19 is about...
3. A jar holds about 10 lollies per scoop, and you take 5 scoops. About how many?