Get a feel for how big a number is, round it to a clean value, and set up to estimate.
Numbers do real work all day long: a price tag, a house number, the number of steps to the door. Most of the time you do not need the exact figure — you need a quick, confident sense of how big it is. That is what this lesson builds: you will learn to glance at a pile and say "about thirty," to round a number to a clean ten or hundred, and to write "≈" when two numbers are about equal. Every rule rests on the number line you met in 1.4 and the place value from 1.3 — the same tools, now put to work for estimates. With a feel for size, you can check whether an answer is even reasonable before you ever compute it.
Look around and numbers are everywhere — but they are not all doing the same job. Some count how many: there are 8 chairs at the table. Some give a position: you live at the 3rd house on the street (an order, not an amount). And some are just a label: a phone number or a bus route number names a thing — it does not measure or rank anything, and adding two of them would be nonsense.
So the first habit of good number sense is to ask: what does this number stand for? A count answers "how many," a position answers "which one," and a label answers "which thing." We met counts and positions back in 1.1; here we just notice that the same string of digits can play very different roles.
Before you do anything with a number, decide its job: a count (how many), a position (which one), or a label (which thing). Only counts and positions behave like sizes you can compare.
Suppose a grid of dots flashes by. Counting each one is slow; instead you estimate — you glance, lean on what you know (a full row is ten), and say a quick, close-enough number. An estimate is not a wrong answer; it is an honest answer that trades a little precision for a lot of speed.
A good way to estimate is to find a chunk you can size up at a glance and then count chunks. If two full rows of ten are filled and a third is half-full, "about twenty-five" is a fine estimate — you did not touch a single dot one-by-one.
Drag to change how many dots there are. First guess "about how many," then check the exact total.
Three full rows of ten and four more is an exact 34; at a glance you might say "about 30." Close enough to be useful, and far faster than counting to 34.
To turn a messy number into a clean one, ask which clean number it is nearest to. Take 38. It lives between 30 and 40. The halfway point is 35. Since 38 sits to the right of 35 on the number line, it is closer to 40 — so 38 is "about 40." This is exactly the "farther right is bigger" idea from 1.4, now used to measure distance to each neighbor.
The number line never lies here because it is drawn to scale: equal steps cover equal distance, so the side a number leans toward is genuinely the nearer one. Watch the picture as you slide a value and you will see the mark cross the halfway mark exactly when the answer flips.
The dashed line is the halfway mark. Whichever side the dot is on is the nearer ten — that is where it rounds.
You do not always have a number line handy, so here is the rule that gives the same answer every time. To round to the nearest ten, look at the ones digit — the digit you are about to drop: if it is less than 5, round down (keep the ten you are in); if it is 5 or more, round up (go to the next ten). Then tidy the ones to a 0. The same rule rounds to the nearest hundred — there you look at the tens digit you are dropping.
Why does exactly 5 round up? Because we agree on one fixed rule so everyone gets the same result — this is called round half up. A 5 is exactly at the halfway mark, and our convention sends it up. The widget and every figure on this page follow round-half-up, so they always agree with the rule stated here.
Switch the target. Watch the dropped digit in the readout decide up or down.
Rounding is decided by the digit you drop, not by the others. 34 rounds down to 30 — even though 34 feels "close-ish" to 40, its ones digit 4 is less than 5, so down it goes. Do not let the rest of the number talk you out of the rule.
When a number is rounded or estimated, we mark it honestly with the ≈ sign — the wavy equals — which reads "about equal to." So 297 ≈ 300 says "297 is about 300," not "297 equals 300." Keeping the two signs apart matters: = means truly the same, while ≈ means close but not exact.
The reason to bother is convenience. Working with 300 in your head is easy; working with 297 is fussy. The "≈" lets you swap in a clean nearby number while staying honest that you traded a little exactness for ease.
297 rounds to the nearest hundred by its tens digit, 9 — that is 5 or more, so round up: 297 ≈ 300. We write ≈, never =, because 297 is not really 300.
Now the payoff. Before adding or subtracting two numbers, round each one to a clean ten first; then the easy version can be done in your head for a ballpark answer. For example, 29 and 41: round to 30 and 40, so the sum is about 70. (The exact answer is 70 here, but the point is you knew "about 70" instantly.) The full machinery of adding comes in a later stage; for now, the skill is sizing things up.
A ballpark answer is also a safety check: if you later compute and get 700, you will know something went wrong, because two numbers near 30 and 40 cannot add to 700. Number sense guards your arithmetic.
Each number is rounded to the nearest ten; the ballpark uses ≈, and the exact total is shown for comparison.
Round first, then estimate. Clean tens are easy to add in your head, and the ballpark tells you instantly whether a later exact answer is reasonable.
Three ideas do all the work in this lesson — the rounding rule, the meaning of ≈, and the round-first habit.
| Idea | The rule | Example |
|---|---|---|
| Round to nearest ten/hundred | Dropped digit < 5 → down; ≥ 5 → up (round half up) | 34 → 30 · 38 → 40 |
| The ≈ sign | ≈ means about equal; = means exactly equal | 297 ≈ 300 |
| Round first, then estimate | Clean the numbers, add in your head for a ballpark | 29 + 41 ≈ 70 |
Six questions to lock it in. Tap the answer you think is right.
This lesson develops 3.NBT.A.1 (use place-value understanding to round whole numbers to the nearest 10 and 100) and 3.OA.D.8 (estimation and assessing the reasonableness of answers, including rounding). The round-half-up convention is stated explicitly so children apply one consistent rule, and the ≈ versus = distinction is kept sharp so estimates stay honest. Encourage your learner to verbalize the rule — "the dropped digit is less than 5, so round down" — and to use a quick ballpark as a check on later exact arithmetic.