Common Mistakes in Arithmetic Operations
256 common pitfalls across 64 concepts, including 64 recurring stuck points
These are the pitfalls students hit across all 64 arithmetic operations concepts, from Addition, Subtraction and Multiplication onward. Each entry names the concept it comes from, so you can tell a slip from a genuine gap and go straight to the explanation.
The procedure for addition is the easy part; the trap is adding digits without lining up place value. Asking "Am I joining amounts together to find how many there are in all?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding digits without lining up place value - put ones under ones and tens under tens before you add.
Forgetting to carry when a column makes ten or more - regroup ten ones into one ten in the next column.
Adding when the problem says how many more - 'more than' that asks a comparison is subtraction, not addition.
The procedure for subtraction is the easy part; the trap is subtracting the smaller digit from the larger in each column regardless of position. Asking "Am I removing an amount or finding the gap between two amounts?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Subtracting the smaller digit from the larger in each column regardless of position - borrow from the next place when the top digit is too small.
Forgetting to reduce the regrouped column after borrowing - the place you borrowed from drops by one.
Subtracting in the wrong order - is not the same as , so keep the starting amount on top.
The procedure for multiplication is the easy part; the trap is multiplying any two numbers that appear in a word problem. Asking "Are all the groups the same size?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Multiplying any two numbers that appear in a word problem — first prove the story has equal groups.
Reading as unrelated symbols — read it as 4 groups of 6 or a 4-by-6 array.
Forgetting that either factor can describe the groups — and have the same total but different stories.
The procedure for division is the easy part; the trap is dividing because the problem says "each". Asking "Is there a total being broken into equal parts?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dividing because the problem says "each" — check whether the total is known; "each" can also signal multiplication.
Swapping divisor and dividend without thinking — identify the total first, then decide what equal part is known.
Ignoring the meaning of a remainder — in context, a remainder may become an extra group, a fraction, or leftovers.
The procedure for order of operations is the easy part; the trap is doing addition before multiplication because it comes first left to right. Asking "Does this expression have more than one operation that needs an agreed order?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Doing addition before multiplication because it comes first left to right - multiply and divide outrank add and subtract.
Treating multiplication as always before division - they share a rank, so go left to right between them.
Skipping the innermost parentheses - always resolve the deepest grouping before anything outside it.
The procedure for exponents is the easy part; the trap is multiplying base by exponent. Asking "Is the base being used as a factor again and again?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Multiplying base by exponent — expand as repeated multiplication.
Forgetting parentheses with negative bases — and differ.
Treating zero exponent as zero — nonzero bases to the zero power equal 1.
The procedure for square roots is the easy part; the trap is dividing by 2 instead of finding a self-product. Asking "What number multiplied by itself gives the radicand?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dividing by 2 instead of finding a self-product — , not 18.
Forgetting non-perfect squares need estimates or radical form — is not a tidy decimal.
Ignoring the principal root convention — means 6, even though .
The procedure for absolute value is the easy part; the trap is keeping the negative sign inside absolute value. Asking "Is the sign direction important, or only the distance?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Keeping the negative sign inside absolute value — distance from zero is nonnegative.
Thinking equals always — order matters before absolute value removes sign.
Using absolute value when direction matters — a temperature of -7 degrees is not the same situation as +7 degrees.
The procedure for addition as combining is the easy part; the trap is counting the parts again after combining. Asking "Are two real parts being physically joined into a single whole?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Counting the parts again after combining - once joined, count only the single whole.
Thinking the whole can be smaller than a part - combining always makes the whole at least as big as each part.
Mixing up units of the parts - only combine parts measured in the same unit.
The procedure for subtraction as difference is the easy part; the trap is adding the two amounts because both are present. Asking "Am I finding the gap between two amounts rather than removing one?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding the two amounts because both are present - a 'how many more' question subtracts to find the gap.
Subtracting in the wrong order so the gap comes out negative - take larger minus smaller for the distance.
Thinking nothing was removed so it cannot be subtraction - comparison is still subtraction.
The procedure for multiplication as scaling is the easy part; the trap is assuming multiplying always enlarges. Asking "Is one amount being resized by a factor instead of counted in equal groups?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming multiplying always enlarges - a factor between 0 and 1 shrinks the amount.
Multiplying by a percent without converting it - scale 8 by 50% as , not .
Forgetting that scaling by 1 changes nothing - the multiplicative identity preserves the amount.
The procedure for multiplication as area is the easy part; the trap is adding length and width instead of multiplying. Asking "Am I counting the unit squares that fill a rectangle of given length and width?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding length and width instead of multiplying - that gives a perimeter piece, not area.
Forgetting the squared unit - area is in , not .
Counting only the border tiles - area counts every unit square inside the rectangle.
The procedure for division as sharing is the easy part; the trap is reporting the number of groups when asked for the share size. Asking "Is the number of groups known, and am I finding how many go in each?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reporting the number of groups when asked for the share size - sharing gives how many per group.
Sharing unequally - the partitive model requires every group to get the same amount.
Ignoring leftovers - if it does not divide evenly, name the remainder or split it as a fraction.
The procedure for division as inverse is the easy part; the trap is dividing by the product instead of the known factor. Asking "Am I undoing a multiplication to find a factor that makes the product?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dividing by the product instead of the known factor - to find the missing factor, divide the product by the factor you have.
Forgetting you can check by multiplying back - the recovered factor times the divisor should equal the product.
Dividing by zero - no factor times 0 gives a nonzero product, so is undefined.
The procedure for inverse operations is the easy part; the trap is undoing multiplication with subtraction. Asking "Am I applying an operation to cancel a previous one and return to the start?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Undoing multiplication with subtraction - multiplication's inverse is division, not subtraction.
Applying the inverse to only one side of an equation - do it to both sides to keep balance.
Forgetting division by zero is barred - has no inverse because it loses the original value.
The procedure for commutativity is the easy part; the trap is assuming subtraction or division commute. Asking "Can I swap these two operands of or and still get the same result?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming subtraction or division commute - is not , so order matters there.
Confusing it with associativity - commutativity swaps order, associativity changes grouping.
Believing it lets you reorder terms across a subtraction freely - move the sign with the term.
The procedure for associativity is the easy part; the trap is regrouping a subtraction. Asking "Can I move the parentheses among these or operands without changing the result?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Regrouping a subtraction - is not , so subtraction is not associative.
Confusing it with commutativity - associativity changes grouping, not order.
Thinking it lets you mix operations - it only regroups one operation, not across and .
The procedure for distributive property is the easy part; the trap is multiplying only the first term in the parentheses. Asking "Is a single factor multiplying a sum where it must reach every term inside?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Multiplying only the first term in the parentheses - the factor must multiply every term inside.
Dropping a sign when distributing a negative - , not .
Distributing across a multiplication inside - distribution spreads only over addition or subtraction.
The procedure for identity elements is the easy part; the trap is using 0 as the multiplicative identity. Asking "Does this number leave every other number unchanged under the given operation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Using 0 as the multiplicative identity - multiplying by 0 gives 0, not the original; the identity is 1.
Using 1 as the additive identity - adding 1 changes the number; the identity is 0.
Thinking every operation has an identity in the obvious place - check which value truly leaves numbers unchanged.
The procedure for operation closure is the easy part; the trap is declaring closure from a few examples. Asking "Does combining any two members of the set always give a result still in the set?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Declaring closure from a few examples - it must hold for every pair, so look for a counterexample.
Forgetting which set is in question - whole numbers are closed under addition but not subtraction.
Ignoring division by zero - the rationals are not closed under division because dividing by 0 is undefined.
The procedure for operation hierarchy is the easy part; the trap is treating exponentiation as repeated addition. Asking "Am I describing one operation as the repetition of a simpler one?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating exponentiation as repeated addition - it is repeated multiplication, so .
Thinking all levels grow at the same speed - each higher level grows far faster than the one below.
Forgetting the hierarchy is why exponents are evaluated before multiplication - rank follows the buildup.
The procedure for repeated operations is the easy part; the trap is compressing unequal terms. Asking "Is the identical operation applied to the same number several times in a row?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Compressing unequal terms - only identical repeated values collapse into multiplication or a power.
Compressing repeated addition into a power - repeated addition becomes multiplication, repeated multiplication becomes a power.
Miscounting the repetitions - the exponent or multiplier equals how many times the number appears.
The procedure for square vs cube intuition is the easy part; the trap is labeling a volume in square units. Asking "Does the exponent count the number of dimensions ( for a flat area, for a solid space)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Labeling a volume in square units - a cube's measure is cubic units because three lengths multiply.
Computing as - the is a power, so it means three factors of , not a multiplier.
Assuming is just a bit bigger than - cubing grows far faster: but .
The procedure for roots as inverse growth is the easy part; the trap is treating as . Asking "Am I given a power's output and asked for the base that produced it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating as - the index is a power to reverse, not a divisor.
Forgetting a square root of a positive number has a negative partner too - , but also allows .
Taking an even root of a negative number as if it exists in reals - has no real value because no real squared is negative.
The procedure for unit rate is the easy part; the trap is dividing the smaller number by the larger to keep it 'simple'. Asking "Am I scaling the comparison so the bottom quantity is exactly one unit?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dividing the smaller number by the larger to keep it 'simple' - divide so the chosen unit lands on ().
Comparing two deals by total price instead of per-one - reduce each to cost per one item first.
Dropping the unit label - alone is meaningless; it must be miles per hour or $20 per ticket.
The procedure for proportional reasoning is the easy part; the trap is adding the difference instead of multiplying by the factor. Asking "When one quantity multiplies by a factor, does the other multiply by the same factor?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding the difference instead of multiplying by the factor - check whether doubling the input doubles the output.
Assuming every relationship is proportional - it only is if equal multiplications give equal multiplications (and it passes through ).
Setting up the proportion with mismatched units across the fraction bar - keep like units lined up top-with-top, bottom-with-bottom.
The procedure for constant of proportionality is the easy part; the trap is computing as a difference . Asking "Does give the same number for every pair in the data?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Computing as a difference - it is the ratio , which must be constant across all pairs.
Calling a line proportional when it has a -intercept - must pass through the origin to have one .
Solving for from one pair without checking the others - verify matches for every pair before trusting it.
The procedure for linear relationship is the easy part; the trap is assuming any increasing pattern is linear. Asking "Does each equal step in add the same fixed amount to ?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming any increasing pattern is linear - require a constant difference between equal steps, not just growth.
Ignoring the -intercept - the starting value shifts the whole line up or down even when the rate is right.
Reading the rate from a single point - compute it as change-in- over change-in- across two points.
The procedure for nonlinear relationship is the easy part; the trap is fitting a straight line to two points and declaring it linear. Asking "Do equal steps in give changing (not constant) changes in ?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Fitting a straight line to two points and declaring it linear - check that every equal step changes by the same amount, not just two.
Confusing 'increasing' with 'linear' - many curves increase; linearity needs a constant difference.
Assuming all nonlinear graphs look alike - quadratics, exponentials, and rationals curve in distinct ways.
The procedure for direct variation is the easy part; the trap is calling any straight line direct variation. Asking "When is , and does doubling double ?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling any straight line direct variation - it must pass through the origin ().
Confusing direct with inverse variation - direct keeps the quotient constant; inverse keeps the product constant.
Forgetting to check is the same for all pairs - if drifts, it isn't direct variation.
The procedure for inverse variation is the easy part; the trap is finding as instead of . Asking "When doubles does halve, keeping the product the same?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Finding as instead of - for inverse variation the constant is the product.
Expecting the output to grow when the input grows - inverse variation moves them in opposite directions.
Treating a steady subtraction as inverse variation - inverse keeps a constant product, not a constant difference.
The procedure for constraints is the easy part; the trap is replacing an inequality constraint with an equation and giving one value. Asking "Does the condition limit or forbid certain values rather than compute one?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Replacing an inequality constraint with an equation and giving one value - the constraint allows a range, so keep the or .
Ignoring hidden real-world constraints - quantities like time or count must be even if unstated.
Flipping the inequality when multiplying or dividing by a negative incorrectly - reverse the sign only for negatives, and remember it applies to the whole constraint.
The procedure for balance principle is the easy part; the trap is operating on only one side. Asking "Am I applying the identical operation to both sides to preserve equality?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Operating on only one side - any add, subtract, multiply, or divide must hit both sides equally.
Multiplying one term instead of the whole side - apply the operation to the entire side, every term.
Dividing both sides by an expression that could be zero - that can destroy solutions; only divide by nonzero quantities.
The procedure for equality as relationship is the easy part; the trap is reading as 'the answer comes next'. Asking "Does the assert two expressions share one value (not just signal a result)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reading as 'the answer comes next' - it means both sides are the same value, in either direction.
Chaining equalities that aren't equal - every in a chain must join equal values, so is false.
Assuming the variable must be alone on the right - is just as valid as .
The procedure for inequality intuition is the easy part; the trap is forgetting to flip the symbol when multiplying or dividing by a negative. Asking "Does the statement order two quantities (strictly smaller or larger) rather than equate them?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Forgetting to flip the symbol when multiplying or dividing by a negative - reverse to in that case.
Reading the symbol backward - the open side faces the larger quantity, so means is smaller.
Confusing strict with inclusive - strict excludes the boundary value, inclusive includes it.
The procedure for bounds is the easy part; the trap is stating only one limit. Asking "Is the value pinned by both a smallest and a largest allowed amount?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Stating only one limit - bounds need both a lower and an upper value to define the range.
Mixing strict and inclusive ends carelessly - includes but not ; match the brackets accordingly.
Reversing the order so the lower bound exceeds the upper - always write the smaller value first: .
The procedure for monotonicity is the easy part; the trap is judging direction from one interval. Asking "Does larger input always give a same-direction change (always up, or always down) with no turn-around?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Judging direction from one interval - monotonicity must hold across the entire domain, not a piece.
Confusing 'large values' with 'increasing' - a function can have big outputs while still going down.
Mixing up strictly monotonic with non-strict - allowing flat stretches makes it non-strict, which can break invertibility.
The procedure for symmetry in operations is the easy part; the trap is assuming every operation is symmetric. Asking "Does exchanging the two inputs leave the result exactly the same?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming every operation is symmetric - addition and multiplication are, but subtraction and division are not.
Confusing swapping order (commutative) with regrouping (associative) - symmetry is only about exchanging the two inputs.
Reordering inside subtraction or division - that changes the answer, so keep the order fixed.
The procedure for invariants is the easy part; the trap is assuming any unchanged-looking quantity is the invariant. Asking "Is there a property that holds equal before and after the transformation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming any unchanged-looking quantity is the invariant - verify (before)(after) for the actual transformation.
Confusing the invariant with the thing being transformed - the invariant is what survives, not what moves.
Overlooking parity or count invariants - sometimes what's preserved is a remainder or oddness, not an obvious total.
The procedure for cancellation is the easy part; the trap is canceling across addition. Asking "Is there a factor that divides the entire numerator and the entire denominator?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Canceling across addition - you can only cancel a factor of the whole top and bottom, never a single addend.
Canceling a factor from only one part - dividing the top by requires dividing the bottom by too.
Canceling a zero factor - the shared factor must be nonzero, or the operation isn't valid.
The procedure for equivalence is the easy part; the trap is judging value by appearance. Asking "Do the two expressions name the exact same value in every context?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Judging value by appearance - , , and are equal despite looking different.
Confusing 'equivalent' with 'approximately equal' - equivalence is exact sameness, not rounding.
Forgetting equivalence is interchangeable both ways - if , either can replace the other.
The procedure for telling time is the easy part; the trap is reading the long hand's number as that many minutes. Asking "Am I naming the time a clock shows right now (not how much time has passed)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reading the long hand's number as that many minutes - multiply the clock number by for minutes.
Swapping the hands - the short hand is the hour, the long hand is the minutes.
Forgetting the hour hand drifts past its number - near the end of an hour it sits between numbers, so name the hour it just passed.
The procedure for elapsed time is the easy part; the trap is borrowing 100 from the hours column. Asking "Am I given a start time and an end time and asked how much time passed between them?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Borrowing 100 from the hours column - when minutes won't subtract, borrow 60, not 100.
Subtracting digits straight (5:10 - 2:45 done as 510 - 245 = 265, which is not a time) - keep hours and minutes in separate base-60 columns.
Forgetting AM/PM crossings - count carefully across noon and midnight rather than ignoring the half-day.
The procedure for money counting is the easy part; the trap is counting coins as 1 each. Asking "Am I adding up amounts of money by each coin or bill's value to get a total?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Counting coins as 1 each - count each coin by its value, so a dime adds 10, not 1.
Counting smallest coins first and losing track - sort and count from largest value down to smallest.
Mixing cents and dollars in one running count - keep cents together until you trade up 100¢ for a dollar.
The procedure for making change is the easy part; the trap is computing cost minus paid. Asking "Did someone pay more than the price, and am I finding the money returned to them?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Computing cost minus paid - change is always paid minus cost, never the reverse.
Misaligning the decimal points when subtracting - line up dollars under dollars and cents under cents.
Forgetting to pad cents (treating $5 as $5.0) - write both amounts with two decimal places before subtracting.
The procedure for length measurement is the easy part; the trap is leaving gaps or overlaps between units. Asking "Am I counting equal-size units along an object, or finding end mark minus start mark?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Leaving gaps or overlaps between units - units must touch end to end with no space and no overlap.
Reading the end mark instead of end minus start - if you start at 1, subtract that 1 from the end reading.
Mixing unit sizes (some big clips, some small) - every unit in one measurement must be the same length.
The procedure for weight measurement is the easy part; the trap is assuming bigger size means more weight. Asking "Am I measuring how heavy something is by balancing it against known weight units?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming bigger size means more weight - size alone does not decide; a big foam ball can be lighter than a small steel marble, so use the balance or scale.
Reading a scale that isn't zeroed - make sure the empty scale reads 0 before placing the object.
Mixing units within one weight (some grams, some pounds) - convert to a single unit before adding (1 kg = 1000 g).
The procedure for simple patterns is the easy part; the trap is looking only at the last element to predict next. Asking "Does a fixed chunk repeat unchanged so I can predict by the cycle?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Looking only at the last element to predict next - find the whole repeating core first, then continue the cycle.
Calling an increasing sequence a repeating pattern - if values grow each time, it's a growing pattern.
Misjudging the core length - check that the same chunk actually recurs (AB vs ABB) before extending.
The procedure for growing patterns is the easy part; the trap is assuming the rule is always addition. Asking "Is the change between consecutive terms a constant amount or a constant factor?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming the rule is always addition - check whether terms add a constant or multiply by a factor.
Using a wrong common difference - subtract consecutive terms and confirm the same gap repeats.
Counting steps wrong in the formula (off by one) - the nth term uses (n-1) steps from the first term.
The procedure for skip counting is the easy part; the trap is changing the jump size midway. Asking "Am I jumping forward by the same fixed amount each time to list its multiples?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Changing the jump size midway - keep the same step from start to finish.
Starting at 0 when the multiples should start at k - counting by 5 begins 5, 10, 15 (the multiples).
Confusing the number of hops with the value landed on - 3 hops of 5 lands on 15, not 3.
The procedure for picture graphs is the easy part; the trap is ignoring the key and counting icons as 1. Asking "Are categories shown as icons with a key telling each icon's value?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Ignoring the key and counting icons as 1 - multiply the picture count by the key's value per icon.
Missing half icons - a half icon counts as half the key value (e.g., half of 2 is 1).
Comparing categories without applying the key to each - apply the scale to every row before comparing.
The procedure for bar graphs is the easy part; the trap is reading every gridline as 1. Asking "Are quantities shown as bars whose height I read against a numbered axis?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reading every gridline as 1 - check the scale unit; gridlines may step by 2, 5, or 10.
Comparing bar heights when scales differ - only compare bars on the same numbered axis.
Confusing the category axis with the value axis - categories sit on one axis, the number scale on the other.
The procedure for tally charts is the easy part; the trap is drawing 5 uprights instead of crossing the fifth. Asking "Am I recording counts as marks bundled in fives for fast totaling?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Drawing 5 uprights instead of crossing the fifth - the fifth mark goes diagonally across the first four.
Counting bundles by ones instead of fives - read each crossed bundle as 5, then add leftovers.
Forgetting the leftover marks after the bundles - total is (bundles × 5) plus the loose marks.
The procedure for multi-digit addition and subtraction is the easy part; the trap is misaligning columns by left-justifying. Asking "Am I stacking large numbers by place value and regrouping by tens to add or subtract?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Misaligning columns by left-justifying - line up by place value (ones under ones), not by the leftmost digit.
Forgetting to carry the regrouped ten - when a column exceeds 9, write the ones digit and carry the ten.
Borrowing without reducing the next column - taking 10 means the column you borrowed from drops by 1.
The procedure for multi-digit multiplication is the easy part; the trap is forgetting the zero or place shift in a tens partial product. Asking "Can I split a factor by place value without changing the product?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Forgetting the zero or place shift in a tens partial product — name the tens value before multiplying.
Multiplying digits without place value — 4 in 45 means 40, not 4.
Trusting a product without estimating — estimate first so a misplaced digit stands out.
The procedure for long division is the easy part; the trap is dropping a digit without asking what place it represents. Asking "Is a large total being split into equal groups, too big for a times-table fact?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dropping a digit without asking what place it represents — say hundreds, tens, or ones at each step.
Writing a remainder bigger than the divisor — keep dividing until the remainder is smaller than the divisor.
Not checking by multiplication — verify divisor times quotient plus remainder equals the dividend.
The procedure for adding and subtracting decimals is the easy part; the trap is right-justifying digits instead of aligning points. Asking "Do the numbers have decimal points I must line up before adding or subtracting?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Right-justifying digits instead of aligning points - line up the decimal points, then pad with zeros.
Dropping the decimal point in the answer - place it directly below the aligned points.
Forgetting trailing zeros while subtracting - write 3.5 as 3.50 so every column has a digit.
The procedure for multiplying decimals is the easy part; the trap is aligning decimal points like addition. Asking "Am I multiplying decimals by computing the whole-number product then counting decimal places?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Aligning decimal points like addition - don't align; multiply as whole numbers, then count places.
Miscounting total decimal places - add the decimal-place counts of both factors (0.3 and 0.4 give 2).
Expecting the product to be bigger - two factors below 1 give a smaller product.
The procedure for dividing decimals is the easy part; the trap is shifting only one number's point. Asking "Is the divisor a decimal I should make whole by shifting both points equally?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Shifting only one number's point - move both decimal points the same number of places.
Shifting unequal numbers of places - shift exactly enough to make the divisor whole, same shift on both.
Misplacing the decimal in the quotient - line the answer's point up above the dividend's shifted point.
The procedure for decimal place value is the easy part; the trap is saying the 6 in is six tenths. Asking "Can I name the place of the digit I am using?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Saying the 6 in is six tenths — it is six hundredths.
Lining up decimal operations by the right edge — line up decimal points so places match.
Thinking is smaller than because it has fewer digits — compare tenths first.
The procedure for integer operations is the easy part; the trap is treating subtracting a negative as subtracting. Asking "Does a negative number enter the operation so I must track sign as well as size?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating subtracting a negative as subtracting - subtracting a negative adds: .
Making a product of two negatives negative - same signs give a positive product.
Adding two negatives toward zero - two negatives sum to a more-negative number: .
The procedure for operations with rational numbers is the easy part; the trap is dropping the sign while finding common denominators. Asking "Are the signed numbers also fractions or decimals, needing fraction rules with sign tracking?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dropping the sign while finding common denominators - keep each term's sign attached as you rewrite.
Flipping the wrong fraction when dividing - to divide, multiply by the reciprocal of the divisor.
Forgetting the sign rule on products - a negative times a positive fraction is negative.
The procedure for word problems is the easy part; the trap is operating on numbers before modeling. Asking "Must I translate a worded scenario into an equation or expression before I can compute?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Operating on numbers before modeling - define the unknown and write the relationship first.
Misreading comparison phrases - 'more than' and 'less than' set order; '3 less than x' is x − 3, not 3 − x.
Answering the wrong quantity - re-read what the question asks and report that, not an intermediate value.
The procedure for unknown factor problems is the easy part; the trap is multiplying the product by the known factor. Asking "Is one factor hidden in a multiplication equation with the product known?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Multiplying the product by the known factor - divide the product by the known factor instead.
Misidentifying which number is the product - the product is the result on the equals side.
Forgetting to check by multiplying back - confirm your answer times the known factor equals the product.