Adding and subtracting decimals is something you already do constantly — every time you check your change, calculate a split bill, or measure something in centimeters. The numbers involved () are decimals, and combining them correctly requires one key discipline: keeping the right digits in the right columns.
Here's why this lesson exists: when students move from whole numbers to decimals, a very specific error pattern appears. They line up the digits from the right — the same habit that works perfectly for whole numbers — and get completely wrong answers. Adding and by right-aligning gives you treated as if it were . The digits end up in the wrong columns, and the answer is nonsense.
The fix is simple but non-negotiable: align decimal points, not right edges. Once you do that, every rule you already know about adding and subtracting whole numbers applies exactly. This lesson is really about understanding why that one alignment rule is the key that makes everything else work.
Before you can add or subtract decimals correctly, you need to be clear about what each digit in a decimal actually represents — because addition is only valid between digits that represent the same kind of thing.
In , the 3 means three whole units, the 4 means four tenths (), and the 7 means seven hundredths (). These three digits are not interchangeable — a 4 in the tenths column is worth ten times more than a 4 in the hundredths column. The position carries the meaning.
This matters for arithmetic because you can only add like quantities to like quantities. You add tenths to tenths, hundredths to hundredths — exactly the same logic as adding ones to ones and tens to tens with whole numbers. If you accidentally add a tenths digit to a hundredths digit, you're mixing units, like trying to add 4 meters to 7 centimeters by writing and calling it done. The answer is wrong because the units don't match.
Here's a contrasting example to make this concrete: in , the 4 is four tenths and the 7 is seven hundredths. They can't be directly added — you first convert: four tenths is the same as forty hundredths, so . If you ignored place value and just added the digits, you'd get , which is completely wrong.
Mental model: think of each decimal place as a different denomination of currency. Tenths are like 10-cent coins, hundredths are like 1-cent coins. You wouldn't add 4 tens-coins and 7 ones-coins and call the total 11 of something. You'd count them separately and combine the totals. Place value in decimals works exactly the same way.
Each digit's value is set by its position — you can only add digits that occupy the same place, because only they represent the same-sized piece.
Aligning decimal points is the single most important step in decimal arithmetic — and it's the step that makes everything else simple. Here's why it works: when you line up decimal points, every column automatically contains digits of the same place value. Tenths land next to tenths. Hundredths land next to hundredths. Once that's true, you can proceed exactly as you would with whole numbers.
Compare these two setups for :
Wrong (right-aligned like whole numbers):
2.5
+ 0.75
This puts the 5 (tenths) above the 7 (tenths) — wait, actually that happens to work here, but for right-alignment puts the 5 above the 3 (hundredths), mixing units. The method is unreliable.
Right (decimal-point aligned):
2.50
+ 0.75
Now every column is clean: 0 hundredths above 5 hundredths, 5 tenths above 7 tenths, 2 ones above 0 ones. Add each column and the answer is correct.
The zero added to to make is not cosmetic — it's a placeholder that makes the column structure explicit and prevents you from accidentally shifting digits during subtraction. The value hasn't changed (), but the calculation is now protected from a common error where a missing digit gets treated as nothing and skipped entirely.
Mental model: vertical alignment in decimal arithmetic is like lining up columns in a spreadsheet. If one row is offset, the formulas produce garbage. The decimal point is the anchor — every digit positions itself relative to that anchor, and correct answers require every anchor to be in the same column.
Line up decimal points, not right edges — this is what guarantees every column contains same-place-value digits, making the arithmetic valid.
3.25
Once your decimals are aligned and padded with zeros, addition works identically to whole number addition. Start in the rightmost column, add those digits, carry if the sum reaches 10 or more, then move one column to the left. Repeat until you've processed every column, including the ones to the left of the decimal point.
The decimal point in the answer sits directly below the decimal points in the problem — it never moves, and you never calculate where it goes. If your alignment was correct, the decimal point's position in the answer is automatic.
Let's work through . First, pad: becomes . Now the setup is:
4.36
+ 2.80
Hundredths column: . Tenths column: — write 1, carry 1. Ones column: (carried) . Answer: .
The mistake students most commonly make here: skipping the padding step and then "guessing" where the decimal goes at the end. Without the padding, a problem like might get set up with the 8 under the 3 (instead of the correct position under the 6's column), producing a wrong answer — and then the student places the decimal point wherever seems reasonable, compounding the error. The decimal point's position is determined by the alignment, not decided at the end.
Mental model: adding decimals is like stacking trays of different sizes. You align them at the center post (the decimal point), fill any gaps with empty space (zeros), then count what's in each column from bottom to top. The post stays fixed — everything organizes around it.
After aligning and padding, add column by column right to left — the decimal point in the answer sits directly below the aligned points above, never calculated separately.
7.16
Subtraction follows the exact same setup as addition — align decimal points, pad with zeros, then subtract column by column from right to left. The only extra complexity is borrowing, which works identically to how it does with whole numbers.
The zeros you add when padding are especially critical in subtraction. Consider . Without padding, the hundredths column of is blank. A blank isn't zero — or rather, it is zero, but if you don't write it, you might forget to borrow from it or borrow into it incorrectly. Rewrite as before starting:
5.20
- 1.85
Now: hundredths column . Can't do it — borrow from the tenths column. The 2 in tenths becomes 1, and the 0 in hundredths becomes 10. Now . Tenths column: . Can't do it — borrow from ones. The 5 becomes 4, the 1 becomes 11. . Ones column: . Answer: .
The most common error in decimal subtraction: treating a missing decimal place as if the number just ends there, rather than padding it with a zero. Students subtract and set it up as if simply doesn't have a hundredths place — then they either ignore the 5 in 's hundredths column or handle it incorrectly. The zero in makes explicit that there is a hundredths column; it just contains nothing. And nothing minus something requires borrowing.
Mental model: think of each decimal column as a cup that must contain something — even if that something is zero. An empty cup and a missing cup look the same at a glance, but they behave differently when you try to subtract from them. Writing the zero converts 'missing' into 'empty', which you know how to handle.
Pad with zeros before subtracting — an empty column and a missing column look the same, but only an explicit zero reminds you to borrow correctly.
3.35
Estimation isn't a fallback for when you can't do the exact calculation — it's an active error-detection tool. The habit of estimating first (or immediately after) tells you what neighborhood your answer should be in. If your exact answer lands outside that neighborhood, something went wrong and you catch it before moving on.
The technique: round each decimal to the nearest whole number (or nearest tenth for more precision), perform the simplified calculation mentally, and compare to your exact answer. For : round to . Your exact answer should be close to 6. If you got , that's fine — close to 6. If you got or , the estimate catches the error immediately.
Estimation is especially powerful for catching the most common decimal mistake: a misplaced decimal point. If somehow produces , your estimate of tells you instantly that the answer is off by a factor of 10 — which is exactly what a decimal point one position wrong would cause.
For subtraction, the same principle applies. For : estimate . Your exact answer should be near 8. Getting passes the check; getting or fails it.
The common mistake with estimation: doing it after you've already committed to your exact answer and then adjusting the estimate to match. That defeats the purpose. Estimate independently first, write it down, then compare. The estimate only catches errors if it's formed without peeking at your exact answer.
Mental model: estimation is a sanity gate. Before your exact answer gets accepted, it has to pass through the gate. The gate is coarse — it won't catch every small error — but it reliably catches the big ones: wrong column, missing carry, misplaced decimal point.
Round first, calculate mentally, then compare — estimation catches misplaced decimal points and missing carries before they become accepted wrong answers.
about 6
A notebook costs and a pen costs . What is the total cost?
The total amount to pay
You pay for an item that costs . How much change do you receive?
The amount of change
Decimal addition and subtraction are only valid when same-place-value digits are in the same column — which is why alignment matters, not as a formality, but as the mathematical requirement that makes the arithmetic correct.
Always align decimal points vertically before calculating, not the right edges of the numbers. Right-edge alignment works for whole numbers but produces wrong answers for decimals with different numbers of decimal places.
Pad shorter decimals with zeros on the right before subtracting — a missing decimal place and a zero placeholder look the same visually, but only the written zero correctly triggers borrowing when you need it.
The decimal point in your answer sits directly below the aligned decimal points in the problem. It is never calculated or estimated — correct setup makes its position automatic.
Estimate by rounding to whole numbers before or immediately after calculating. This catches the most consequential error in decimal arithmetic — a misplaced decimal point — because a point one position off changes your answer by a factor of ten, which even a rough estimate will flag.
Mastering decimal addition and subtraction unlocks the arithmetic behind almost every quantitative situation in everyday life — budgeting, cooking measurements, sports statistics, scientific data. More immediately in your math education, these skills feed directly into multiplying and dividing decimals, where the same place value discipline applies in a more complex way. They also underpin percentage calculations (since percentages are hundredths) and unit conversion in science, where small decimal errors compound into large measurement mistakes. The habit of careful alignment you build here is the same habit that prevents errors in algebra when you're combining like terms and in calculus when you're tracking significant figures.
Practice setting up problems only — not solving them. Take ten decimal addition or subtraction pairs, write each one vertically with decimal points aligned and zeros padded, then check your setup before doing any arithmetic. Separating setup from calculation as a deliberate step builds the habit that prevents most errors.
Create a set of 'trap problems' — specifically pairs where one number has one decimal place and the other has two or three — and practice only those until zero-padding and alignment are automatic. Examples: , , . These are the configurations that expose misalignment errors.
After every calculation, spend five seconds estimating: round each number to the nearest whole, compute mentally, compare to your exact answer. Do this even when you're confident. The goal is to make estimation a reflex rather than a fallback — it only catches errors if it's done every time, not just when you're unsure.
Calculate .
Calculate .
Find .
Explain why decimal points must be aligned when adding numbers.
This is an exploration question. Write your thoughts and discuss with others!
A rope is meters long. You cut off meters. How much rope remains?
Estimate to the nearest whole number.
How do you value this lesson?
3.47
Practice borrowing across zeros specifically. Problems like and force borrowing chains through zero columns — the hardest mechanical part of decimal subtraction. Work through ten of these, narrating each borrowing step out loud ('the tenths column is zero, so it borrows from the ones, making tenths nine and ones one less'), until the chain feels automatic.