Rounding and Estimation

Learning goals

Round to a place by snapping to the nearer multiple of it
Justify why only the digit right of the rounding place decides
Carry a nine that rounds up, so $2.96$ becomes $3.0$
Name the exactly-five tie as a convention, not a forced result
Estimate by rounding before computing, and say what accuracy it costs
Check an exact answer for size, catching a misplaced decimal point

Rounding means snapping to the nearest

A number that is awkward to work with can be swapped for the nearest easy one.

Take $3.7$ and round it to the nearest whole number. The two whole numbers on either side are $3$ and $4$ . Since $3.7$ is past the midpoint $3.5$ , it is closer to $4$ , so $3.7$ rounds to $4$ . Round $3.2$ the same way and it lands on $3$ , because $3.2$ has not yet reached the halfway mark.

The midpoint $3.5$ splits the gap between $3$ and $4$ into two equal halves. From $3.7$ , past that midpoint, the shorter trip is forward to $4$ . From $3.2$ , short of it, the shorter trip is back to $3$ .

To round a number to a given place means to replace it with the nearest multiple of that place’s value. The same goes at every place: the nearest multiple of one tenth, or of one hundredth. Every rounding question is this same question in disguise: of the two nearest multiples, which one is the number closer to?

Rounding 3.7 to the nearest whole number. The midpoint is 3.5. Because 3.7 sits past the midpoint, it is closer to 4, so it rounds up to 4.

Why you only look at one digit

You never have to measure the two distances. One digit settles it.

Round $8.4917$ to the nearest tenth. The neighbors are $8.4$ and $8.5$ , and the midpoint between them is $8.45$ . The hundredths digit is $9$ , which puts the number past $8.45$ , so it rounds to $8.5$ . The $17$ trailing that $9$ never came into it.

Look at the single digit just to the right of the rounding place. If it is $5$ or more, round up; if it is less than $5$ , round down (leave the rounding digit as it is). The surprising part is that one digit is enough.

Why the next digit alone decides which way to round#

Round $6.2749$ to the nearest tenth. The two nearest tenths are $6.2$ and $6.3$ , and the midpoint between them is $6.25$ . The deciding digit is the hundredths digit $7$ , and $7$ hundredths is more than the $5$ hundredths that reach the midpoint. The digits past it, the $49$ ten-thousandths, add $0.0049$ , which is less than one whole hundredth. So $6.2749$ sits past $6.25$ and rounds to $6.3$ , and the $49$ never got a vote.

Change that $7$ to a $3$ and the same reading settles it the other way. Now $6.2349$ holds $3$ hundredths, two hundredths short of the midpoint, and the tail can still add less than one hundredth. So the number stays below $6.25$ , and it rounds to $6.2$ .

Nothing there depended on the digits chosen. Fix the place you are rounding to and look at the two nearest multiples of that place. One is the number with the rounding digit left as it is, which is the round-down result. The other is the next multiple of that place going up, which is the round-up result. The exact midpoint between those two multiples is the lower one plus half a unit of the rounding place. Half a unit is a $5$ in the next place down with nothing after it.

The digit right after the rounding place reaches the value of that midpoint $5$ precisely when it becomes $5$ itself. For a decimal that ends, everything to the right of that digit adds up to less than one full unit of its place. It can reach a hair under that unit, and never the whole of it. So a digit of $5$ or more puts the number at or past the midpoint, no matter what follows. A digit of $4$ or less leaves it short of the midpoint, even at the most the tail can add. The single digit immediately to the right is therefore enough to settle which multiple is nearer. Landing exactly on the midpoint is the one case distance cannot settle, and a convention decides it instead.

Rounding to the nearest tenth is something you can see rather than compute. That is because on the grid below, a complete row of ten squares is one tenth. Shade a count that does not finish a row and ask which of the two nearest whole-row counts the shading is closer to.

Hunt for a count whose unfinished row is exactly half full. Set $45$ : the midpoint $0.45$ sits the same distance from $0.4$ and $0.5$ , so the picture refuses to decide. A half-full row is a half-full row wherever it falls. So every count ending in $5$ does the same thing: $5$ , $15$ , $25$ , and so on up to $95$ . That tie is settled by a convention this lesson comes to shortly. Move one square either side of any of them and the picture picks a winner on its own. Then try $96$ : nine full rows and most of a tenth, near enough to a full grid. That count rounded to the nearest tenth therefore fills the grid completely, giving $1.0$ , which is the carry a $9$ makes when it rounds up.

Why the leftover squares decide the tenths digit

Squares shaded

47 squares of 100 shaded. That is 4 complete rows and 7 spare squares. Rounded to the nearest tenth, 0.5.

One whole as 100 squares, filling row by row. A complete row of ten is one tenth of the whole, and a single square is one hundredth.

The squares left over past the last complete row are the hundredths digit. So “is the leftover $5$ or more” and “is the unfinished row past half full” are the same question asked twice.

Worked example 1 Round $46.83$ to the nearest whole number

Rounding to the nearest whole number, so the rounding place is the ones place, holding the $6$ . The digit just to the right of it is the tenths digit, which is $8$ .

Since $8$ is $5$ or more, round up: raise the ones digit from $6$ to $7$ and drop everything after the point.

46.83 \approx 47.

The hundredths digit $3$ never mattered. Once the tenths digit is $8$ , the number is already past the midpoint $46.5$ , so it is closer to $47$ than to $46$ .

Worked example 2 Round $5.7142$ to the nearest hundredth

The hundredths place holds the second digit after the point, which is the $1$ in $5.71\underline{4}2$ . To decide which way to round, look at the very next digit, the thousandths digit, which is $4$ .

Since $4$ is less than $5$ , round down: keep the hundredths digit as it is and drop everything after it.

5.7142 \approx 5.71.

The trailing $42$ together is less than one hundredth, so it cannot pull the number up to the midpoint $5.715$ . The answer keeps exactly two decimal places, because that is what “to the nearest hundredth” asks for.

When a nine rounds up

Rounding a $9$ up takes one extra move.

Worked example 3 Round $2.96$ to the nearest tenth

The tenths place holds the $9$ , and the next digit, the hundredths $6$ , is $5$ or more, so round the tenths up. Raising $9$ tenths by one gives ten tenths, which is one whole:

2.96 \approx 3.0.

The ten tenths roll over into the ones place: the $9$ turns into $0$ and the $2$ ones become $3$ . The answer is $3.0$ , not $2.10$ , and the trailing zero shows you rounded to the tenths place.

Raising any $9$ by one makes ten, and ten does not fit in a single place. So it carries into the place on its left, exactly like carrying in addition. The $9$ becomes a $0$ and the digit beside it goes up by one.

Check your understanding

Round $12.359$ to the nearest tenth.

12.4

12.3

12.36

12.0

The exactly-five case is a convention

There is one case the “5 or more rounds up” rule sweeps past without comment. What happens when the number is exactly at the midpoint, like $2.5$ rounded to the nearest whole number? Here $2.5$ is the same distance from $2$ as it is from $3$ , so “nearest” does not pick a winner. No single neighbor is nearest; it is a genuine tie.

A tie has to be broken by a rule we simply agree on. The most common such rule is round half up: when the number lands exactly on the midpoint, round it up. Under this convention $2.5$ rounds to $3$ , $0.5$ rounds to $1$ , and $7.85$ to the nearest tenth rounds to $7.9$ . This is the convention used throughout these lessons, and it is the one that makes the clean “5 or more rounds up” wording correct.

This is a choice, not a logical necessity. Half could just as reasonably be rounded down, or rounded to whichever neighbor is even. In fact statisticians and many calculators use “round half to even” to avoid a slight upward bias when rounding many numbers. Remember, though, that the exactly-five rule is settled by agreement, while every other case is forced by which multiple is actually nearer.

Worked example 4 Round $2.5$ and $3.5$ to the nearest whole number

Both numbers sit exactly halfway between two whole numbers, so neither has a strictly nearer neighbor. This is the tie case, and the round-half-up convention settles it by sending the number to the upper neighbor.

For $2.5$ , the neighbors are $2$ and $3$ , and round half up sends it up:

2.5 \approx 3.

For $3.5$ , the neighbors are $3$ and $4$ , and again it goes up:

3.5 \approx 4.

Had we agreed on round-half-down instead, these two would have landed on $2$ and $3$ . That is why this case is a convention rather than something forced by distance.

Estimation: round first, then compute

Rounding can make a calculation easier before you even start it.

Suppose you want $312 + 489$ in a hurry. Round each number to the nearest hundred first, then add the easy numbers:

312 + 489 \approx 300 + 500 = 800.

The exact sum is $801$ , so the estimate of $800$ is excellent, and it took no paper. Rounding moved $312$ down by $12$ and $489$ up by $11$ , so the two changes very nearly cancel each other out.

Estimation turns rounding into a calculating tool. Instead of working with the exact numbers, you round each one to something easy, then do the now-simpler arithmetic. The answer is approximate, but you get it quickly, often in your head, and that speed is the whole point. The same idea works with decimals. To estimate $6.83 \times 4.1$ , round to $7 \times 4 = 28$ , which is close to the exact product $28.003$ . You decide how rough to be by choosing the place you round to. Rounding to the nearest ten is faster but cruder than rounding to the nearest one.

A quick variation is front-end estimation, where you keep only the leading (front) digit of each number and treat the rest as zeros. For $312 + 489$ , the front digits give $300 + 400 = 700$ . Front-end estimation is even faster because you never stop to decide which way to round. Front-end estimation tends to run low, though, since chopping the trailing digits only ever throws value away. When you are adding, this makes it a quick lower estimate of the total, useful when you mostly want the size.

Worked example 5 Estimate $48.7 + 23.4 + 31.9$ by rounding each to the nearest ten

Round every number to the nearest ten before adding anything. Look at the ones digit of each to decide which way it rounds.

The number $48.7$ has ones digit $8$ , so it rounds up to $50$ . The number $23.4$ has ones digit $3$ , so it rounds down to $20$ . The number $31.9$ has ones digit $1$ , so it rounds down to $30$ . Now add the easy numbers:

48.7 + 23.4 + 31.9 \approx 50 + 20 + 30 = 100.

So the sum is about $100$ . The exact total is $104.0$ , so rounding to the nearest ten landed within a few units. That rounding also replaced three messy decimals with round numbers you can add in your head.

Check your understanding

Estimate $397 \times 6$ by rounding $397$ to the nearest hundred first.

2400

1800

2100

600

Estimation as a reasonableness check

After you compute an exact answer, by hand or on a calculator, a quick estimate tells you whether that answer is even the right size.

Suppose you multiply $19.6 \times 5.2$ and your calculator reads $10.192$ . Estimate: $20 \times 5 = 100$ . The exact answer should be about $100$ , but $10.192$ is about $10$ , ten times too small. So a digit or the decimal point went in the wrong place. (The correct product is $101.92$ .)

That catches the most common and most dangerous decimal mistake of all: a misplaced decimal point. A misplaced point throws the answer off by a factor of ten, a hundred, or more. The estimate did not give you the exact answer, but it flagged that something was wrong, which is often more valuable.

Worked example 6 A bill of $6.45$ dollars for each of $8$ tickets rings up as $5.16$ dollars. Is that reasonable?

Each ticket is about $6$ dollars and there are $8$ tickets, so round and multiply:

6.45 \times 8 \approx 6 \times 8 = 48.

The total should be about $48$ dollars. The rung-up figure of $5.16$ dollars is roughly $5$ dollars, nearly ten times too small, so it cannot be right. The decimal point landed one place too far left.

Working it out exactly confirms the estimate caught a real error:

6.45 \times 8 = 51.60.

The true total is $51.60$ dollars, close to the estimate of $48$ , while the original $5.16$ was off by a factor of ten.

Check your understanding

A student computes $42.8 \div 4$ and writes $1.07$ . A quick estimate shows the answer should be about which value, and is $1.07$ reasonable?

A About

10

, so

1.07

is too small B About

1

, so

1.07

is reasonable C About

100

, so

1.07

is too small D About

40

, so

1.07

is reasonable

Common mistakes

Rounding digit by digit from the right. To round $4.46$ to the nearest tenth, look only at the hundredths digit ( $6$ ), which sends it to $4.5$ . Do not first round $4.46$ to $4.5$ and then claim the $5$ pushes the tenths up again. One digit, the one immediately to the right of the rounding place, decides it.
Looking at the wrong digit. Round to the place named, then check the single next digit. For “nearest tenth” the rounding digit is the tenths digit and the deciding digit is the hundredths, not the ones.
Dropping the place you rounded to. Rounding $5.7142$ to the nearest hundredth gives $5.71$ , which keeps two decimal places. Writing $5.7$ rounds to the wrong place, and writing $5$ throws away the decimal entirely.
Forgetting the carry, or the trailing zero. A $9$ that rounds up carries, so $2.96$ to the nearest tenth is $3.0$ , not $2.10$ . Keep the trailing zero, since rounding to the nearest cent means two decimal places: $3.8$ dollars to the nearest cent is written $3.80$ .
Rounding too early inside a calculation. When you need an exact answer, do the arithmetic first and round the final result. Rounding each number first is for estimates, where the small errors are the price you knowingly pay for speed.
Trusting an answer that fails the size check. If your exact result is ten times bigger or smaller than a quick estimate, recheck it. A misplaced decimal point is the usual culprit, and the estimate is what catches it.

Key takeaways

Rounding to a place means choosing the nearest multiple of that place’s value (nearest whole, nearest tenth, nearest hundredth). So choosing that nearest multiple snaps the number to the closer of its two neighbors.
You only need the single digit just to the right of the rounding place: $5$ or more rounds up, less than $5$ rounds down. The shortcut works because everything farther right adds less than one unit of that next place and cannot change which neighbor is nearer.
A $9$ in the rounding place carries when it rounds up: $2.96$ to the nearest tenth is $3.0$ .
The exactly-five tie is broken by a convention. These lessons use round half up, which is what makes “5 or more rounds up” exactly correct; the choice is an agreement, not a forced result.
Estimation rounds the numbers in a calculation before computing, trading a little accuracy for a fast, in-your-head answer. Front-end estimation keeps only the leading digits and tends to run low.
An estimate is also a reasonableness check: it confirms the size of an exact answer. The estimate also catches a misplaced decimal point, which is off by a factor of ten or more.

Rounding and Estimation

Learning goals

Rounding means snapping to the nearest

Why you only look at one digit

When a nine rounds up

The exactly-five case is a convention

Estimation: round first, then compute

Estimation as a reasonableness check

Common mistakes

Practice

Multiple Choice Questions (MCQ)

Free Response Questions (FRQ)