Common Mistakes in Numbers & Quantities
192 common pitfalls across 48 concepts, including 48 recurring stuck points
These are the pitfalls students hit across all 48 numbers & quantities concepts, from Counting, Number Sense and Place Value 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 counting is the easy part; the trap is counting an object twice or skipping one. Asking "Did I touch each object exactly once and is the last number I said the total?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Counting an object twice or skipping one - touch each object exactly once, one number per object.
Saying the last object's name instead of the count - the final number word is the total, not a label for that object.
Losing track of where you started in a scattered pile - move counted items aside or count in a fixed path.
The procedure for number sense is the easy part; the trap is treating 'is it reasonable?' as a request for the exact answer. Asking "Am I judging the size or reasonableness of a number rather than computing an exact value?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating 'is it reasonable?' as a request for the exact answer - number sense judges plausibility, not precision.
Ignoring the size of the answer after computing - always ask whether the result is in the right ballpark.
Thinking a longer number is automatically a much bigger quantity without checking - compare the leading digits and their places.
The procedure for place value is the easy part; the trap is adding the digits instead of weighting them by place. Asking "Does the worth of this digit depend on which column it sits in?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding the digits instead of weighting them by place - multiply each digit by its column value before combining.
Forgetting zero as a placeholder so 305 collapses to 35 - a zero holds an empty column open.
Lining up multi-digit numbers carelessly so ones sit under tens - align by place value, ones under ones.
The procedure for more and less is the easy part; the trap is judging more by how spread out the objects are. Asking "Am I deciding which of exactly two quantities is greater or smaller?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Judging more by how spread out the objects are - line them up one-to-one or count, not by length of the row.
Comparing without a one-to-one match in early counting - pair items off to see which group has leftovers.
Confusing which way the words point - 'more' means greater amount, 'less/fewer' means smaller amount.
The procedure for equal is the easy part; the trap is reading = as 'the answer goes here'. Asking "Am I claiming two things have exactly the same value (a balance), not just computing the next number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reading = as 'the answer goes here' - it means both sides balance, so 8+4 = 10+2 is perfectly valid.
Changing only one side of an equality - whatever you do to one side you must do to the other to keep balance.
Writing run-on chains like 3+4=7+2=9 - each = must hold, and 7 does not equal 9.
The procedure for integers is the easy part; the trap is thinking -3 is greater than -1 because 3 > 1. Asking "Is the value a whole amount that can be positive, negative, or zero (no fraction part)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Thinking -3 is greater than -1 because 3 > 1 - on the number line, farther left is less, so -3 < -1.
Including fractions or decimals as integers - integers are whole amounts only, no parts.
Dropping the negative sign during operations - track the sign as carefully as the digit.
The procedure for rational numbers is the easy part; the trap is calling every decimal rational. Asking "Can this number be written as one integer divided by another (with the decimal ending or repeating)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling every decimal rational - only terminating or repeating decimals are; non-repeating infinite decimals are irrational.
Allowing zero in the denominator - b must be nonzero for a/b to be a rational number.
Thinking a number must look like a fraction to be rational - integers like 7 are rational too (7/1).
The procedure for irrational numbers is the easy part; the trap is thinking irrational means impossible or fake. Asking "Can this number be written exactly as a ratio of integers?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Thinking irrational means impossible or fake — irrational numbers are exact real numbers.
Calling every square root irrational — perfect square roots like are rational.
Rounding and treating the rounded decimal as exact — approximations are not the exact irrational value.
The procedure for real numbers is the easy part; the trap is excluding irrationals from the reals. Asking "Can this value be located as a single point on the ordinary number line (no imaginary part)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Excluding irrationals from the reals - and are real numbers on the line.
Calling a real number - it is imaginary, off the number line, so not real.
Assuming every real number has a decimal that ends - repeats forever, and irrationals like never end or repeat.
The procedure for complex numbers is the easy part; the trap is forgetting and leaving it unsimplified. Asking "Does the problem require the square root of a negative number, ?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Forgetting and leaving it unsimplified - replace with -1 every time.
Writing as - it is ; the negative comes out as a factor of .
Multiplying as - convert to form first, since the radical rule fails for negatives.
The procedure for quantity is the easy part; the trap is giving a number with no unit for an amount of stuff. Asking "Am I naming 'how much' of something there is, an amount paired with what it is of?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Giving a number with no unit for an amount of stuff - a quantity is an amount OF something, name the unit.
Confusing the amount with the act of counting it - quantity is the 'how much'; counting is how you pin it down.
Assuming every quantity must be a whole count - amounts of liquid or length are measured, not counted.
The procedure for number as measure is the easy part; the trap is dropping the unit from a measurement. Asking "Is the number describing the size of a measured amount that needs a unit to mean something?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dropping the unit from a measurement - a measure is a number AND a unit; 7 alone is incomplete.
Adding measures with different units - convert to the same unit before combining (no adding feet to meters).
Treating measured stuff like countable objects - length and weight are measured, not counted one by one.
The procedure for base-ten system is the easy part; the trap is thinking places grow by +10 instead of x10. Asking "Is each place worth exactly ten times the place to its right?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Thinking places grow by +10 instead of x10 - each place to the left is ten TIMES the one to its right.
Forgetting the pattern continues rightward past the decimal point - tenths, hundredths are x(1/10) each step.
Failing to regroup when a column reaches 10 - ten in one place bundles into one of the next place left.
The procedure for zero is the easy part; the trap is dropping the placeholder zero so 105 becomes 15. Asking "Am I representing the absence of an amount or holding an empty place open?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Dropping the placeholder zero so 105 becomes 15 - a zero holds an empty column and changes the number's size.
Dividing by zero - division by zero is undefined, not zero or infinity.
Thinking multiplying by zero leaves a number unchanged - wipes it out; only leaves it unchanged.
The procedure for magnitude is the easy part; the trap is reporting a magnitude as negative. Asking "Am I asking how big or how far, with the sign or direction thrown away (so the answer can't be negative)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Reporting a magnitude as negative - size and distance are never negative; drop the sign.
Forgetting magnitude discards direction - 5 east and 5 west have the same magnitude.
Adding vector components instead of using - magnitude of is the Pythagorean length, not .
The procedure for ordering numbers is the easy part; the trap is ordering fractions by denominator size. Asking "Am I sequencing three or more numbers into a full ordered list (not just comparing two)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Ordering fractions by denominator size - convert to a common form (common denominator or decimals) and compare actual sizes.
Mishandling negatives so -5 lands after -2 - more negative means smaller, farther left on the line.
Comparing mixed forms without converting - turn fractions, decimals, and percents into one form first.
The procedure for comparison is the easy part; the trap is pointing the symbol the wrong way. Asking "Am I relating two values with one symbol, with the open end facing the larger?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Pointing the symbol the wrong way - the open end always faces the larger number ().
Comparing different forms without converting - put fractions, decimals, percents in one form first.
Using > or < when the values are equal - if they match exactly, the symbol is =.
The procedure for unit fraction is the easy part; the trap is thinking 1/8 > 1/4 because 8 > 4. Asking "Does the fraction have a 1 on top, naming exactly one equal part of the whole?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Thinking 1/8 > 1/4 because 8 > 4 - a larger denominator means smaller pieces, so 1/8 < 1/4.
Calling 3/4 a unit fraction - only a numerator of exactly 1 makes it a unit fraction.
Forgetting the parts must be equal - 1/4 is one of FOUR equal parts, not just any one piece.
The procedure for decimal representation is the easy part; the trap is comparing decimals by digit count so 0.45 beats 0.5. Asking "Are the digits after a point standing for tenths, hundredths, thousandths of a whole?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Comparing decimals by digit count so 0.45 beats 0.5 - line up place values; 0.50 > 0.45.
Misnaming 0.34 as 'thirty-four' - it is thirty-four hundredths, a fractional amount.
Misaligning the decimal points when adding - stack points over points so like places line up.
The procedure for percent as ratio is the easy part; the trap is using the percent number as the amount. Asking "Is the value a comparison stated per 100 (a rate), not a raw count?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Using the percent number as the amount - 20% of 50 is 0.20x50 = 10, not 20.
Forgetting to divide by 100 when converting - as a decimal is (35% = 0.35).
Comparing percents of different wholes as if equal - 50% of 10 and 50% of 100 are very different amounts.
The procedure for scaling is the easy part; the trap is adding a fixed amount instead of multiplying. Asking "Is every part multiplied by the same factor (not increased by a fixed amount)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding a fixed amount instead of multiplying - scaling multiplies every part by the SAME factor.
Using a factor below 1 expecting growth - shrinks; you need to enlarge.
Scaling only some parts - to keep proportions, every part must be multiplied by the same k.
The procedure for proportionality is the easy part; the trap is calling any growing pair proportional. Asking "Is the same number for every pair, and is when ?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling any growing pair proportional - check that is the SAME constant for every pair, not just that both increase.
Ignoring the start-up amount - a relationship with a nonzero -intercept is linear but not proportional.
Confusing the constant with a single value - is the ratio , the per-unit rate, not one output.
The procedure for inverse quantity is the easy part; the trap is holding the ratio constant instead of the product. Asking "Does the product stay the same when one quantity grows and the other shrinks?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Holding the ratio constant instead of the product - inverse relationships fix , so when doubles, must halve.
Adding workers and expecting more time - for a fixed job, the product workerstime is constant, so time goes down.
Mixing up with - division gives the inverse curve, multiplication gives the straight proportional line.
The procedure for rounding is the easy part; the trap is looking at the wrong digit. Asking "Is there a named place value to snap to, and one digit to its right deciding the direction?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Looking at the wrong digit - check only the single digit immediately to the right of the rounding place.
Rounding the deciding digit first then rounding again - decide in one step from the original digit, no chaining.
Forgetting place holders - rounding to the nearest hundred is , not ; keep the zeros.
The procedure for estimation is the easy part; the trap is rounding so hard the estimate is useless. Asking "Am I rounding the numbers and then computing to get a close-enough answer, not an exact one?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Rounding so hard the estimate is useless - round just enough to compute mentally while staying close.
Treating the estimate as the exact answer - an estimate is a check, not a final result when precision is required.
Always rounding both numbers up - that biases the estimate high; round one up and one down to balance.
The procedure for precision is the easy part; the trap is treating precision as accuracy. Asking "Is the question about how finely a value is measured or reported, regardless of whether it is correct?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating precision as accuracy - precise means finely recorded, accurate means close to true; a value can be one without the other.
Reporting more digits than the tool measures - never write from a ruler that only reads to .
Adding trailing zeros to look more precise - extra zeros claim measurement detail the instrument did not provide.
The procedure for approximation is the easy part; the trap is forgetting the error exists. Asking "Am I deliberately using a near value for a hard-to-write exact one while caring how far off it is?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Forgetting the error exists - an approximation always carries a gap; ignoring it lets small errors compound.
Confusing it with estimation - approximation deliberately controls a known error, estimation just gets close fast.
Reusing a rounded stand-in as if exact - ; carry enough digits or keep the symbol.
The procedure for number line is the easy part; the trap is spacing integers unevenly. Asking "Am I placing or comparing numbers as ordered, equally spaced points on a single line?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Spacing integers unevenly - consecutive integers must sit the same distance apart or order and distance are wrong.
Putting negatives on the right - negative numbers go LEFT of zero, getting smaller as you move left.
Confusing distance with difference of position - distance between and is , always nonnegative.
The procedure for density of numbers is the easy part; the trap is asking for the next real number. Asking "Is the question about whether infinitely many numbers fit between two given values, with no smallest gap?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Asking for the next real number - reals have no next number; you can always find one closer.
Thinking close numbers have no room between - the midpoint always lands strictly between any two distinct reals.
Confusing density (packing inward) with infinity (growing outward) - density subdivides, infinity extends.
The procedure for infinity intuition is the easy part; the trap is treating infinity as a reachable number. Asking "Does this describe an endless process with no final value, rather than a specific reachable number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Treating infinity as a reachable number - you can never count to infinity; it has no final value.
Saying infinity plus one is larger - there is no last number to add to, so this is not how endlessness works.
Confusing endless growth with endless subdivision - infinity grows outward; density packs inward between two values.
The procedure for finite vs infinite is the easy part; the trap is calling a huge set infinite. Asking "Could you, in principle, reach the last element — or does it never end?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling a huge set infinite - finite means it ends, even if the count is astronomically large.
Trying to total an infinite set by adding - endless sets need limits or series, not direct addition.
Reading the ellipsis as 'a few more' - means it continues without end, so the set is infinite.
The procedure for discrete vs continuous is the easy part; the trap is labeling by how a value is reported. Asking "Could the quantity take a value strictly between two adjacent readings? Yes is continuous, no is discrete." first is what keeps a correct-looking calculation from being attached to the wrong concept.
Labeling by how a value is reported - ask what values are POSSIBLE, not whether it was rounded to whole numbers.
Calling counts continuous - number of people, pets, or cars takes only whole values, so it is discrete.
Drawing the wrong graph - discrete data gets separate dots, continuous data gets a smooth line or curve.
The procedure for parity (even/odd) is the easy part; the trap is judging parity by size or digit count. Asking "Does the integer split into two equal whole groups with nothing left over?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Judging parity by size or digit count - only divisibility by decides, shown by the last digit.
Forgetting zero is even - splits into two equal empty groups, so it is even.
Assuming all primes are odd - is even and prime; only that one prime is even.
The procedure for divisibility intuition is the easy part; the trap is writing the divides bar backwards. Asking "Does the larger number split into equal whole groups of the smaller with nothing left over?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Writing the divides bar backwards - means goes into , smaller into larger.
Accepting a small remainder as 'close enough' - divisibility requires remainder exactly .
Confusing 'divisible by' with 'divides' - is divisible by ; divides ; same fact, opposite phrasing.
The procedure for factors is the easy part; the trap is listing multiples when asked for factors. Asking "Does this number multiply with another whole number to make the target?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Listing multiples when asked for factors — factors multiply to the target; multiples are made from the target.
Forgetting factor pairs — if 3 is a factor of 24, 8 is paired with it.
Ignoring 1 and the number itself — every positive whole number has those as factors.
The procedure for multiples is the easy part; the trap is listing factors instead of multiples. Asking "Can the number be written as the given number times a whole number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Listing factors instead of multiples — multiples are products of the given number.
Stopping at the number itself — the list continues forever.
Forgetting zero can be a multiple in some contexts — check whether the class is using positive multiples only.
The procedure for prime numbers is the easy part; the trap is calling 1 prime. Asking "Does this number bigger than have exactly two factors — and itself — and no others?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling 1 prime - a prime needs exactly two factors; has only one, so it is neither prime nor composite.
Assuming all odd numbers are prime - , , and are odd but composite.
Forgetting is prime - is the only even prime; its only factors are and .
The procedure for composite numbers is the easy part; the trap is calling 1 composite. Asking "Does this number bigger than have at least one factor other than and itself?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Calling 1 composite - has no factorization into smaller integers above , so it is neither prime nor composite.
Assuming even means composite - is even but prime; it has only two factors.
Thinking composite means odd or large - is the smallest composite; size and parity are irrelevant.
The procedure for greatest common factor is the easy part; the trap is picking the LCM by mistake. Asking "Am I looking for the largest number that divides every given value with no remainder?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Picking the LCM by mistake - GCF is the largest shared FACTOR (at most the smaller number), not a multiple.
Stopping at a common factor that is not the greatest - divides and , but is larger.
Multiplying the numbers - GCF divides into them; it never exceeds the smaller number.
The procedure for least common multiple is the easy part; the trap is picking the GCF by mistake. Asking "Am I looking for the smallest number that every given value divides into evenly?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Picking the GCF by mistake - LCM is the smallest shared MULTIPLE (at least the larger number), not a factor.
Always multiplying the two numbers - overshoots unless the numbers are coprime; divide by the GCF.
Stopping at a common multiple that is not the least - is a common multiple of but is smaller.
The procedure for numerical structure is the easy part; the trap is assuming subtraction or division is commutative. Asking "Am I relying on a named property to reorder or rewrite an expression while keeping it equal?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Assuming subtraction or division is commutative - only addition and multiplication can be reordered freely.
Confusing properties with the order of operations - properties say what stays equal; PEMDAS says what runs first.
Distributing where there is no sum - ; distribution applies over addition, not multiplication.
The procedure for exponent rules is the easy part; the trap is adding exponents when terms are added. Asking "What operation is happening to the powers?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding exponents when terms are added — exponent addition is for multiplying same-base powers.
Using product rule with different bases — needs a different structure.
Forgetting negative exponents mean reciprocal factors — for nonzero .
The procedure for scientific notation is the easy part; the trap is choosing a first factor outside . Asking "Is the first factor at least 1 and less than 10?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Choosing a first factor outside — move the decimal until the factor is in range.
Using the wrong sign for the exponent — small numbers less than 1 use negative powers of 10.
Counting decimal moves without checking reasonableness — positive exponent should make the number larger.
The procedure for scientific notation operations is the easy part; the trap is adding exponents when adding the numbers. Asking "Are both numbers in form, and is the operation multiply/divide (combine exponents) or add/subtract (match exponents first)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Adding exponents when adding the numbers - addition needs the same power of ten first, then you add only the coefficients.
Forgetting to renormalize so the coefficient stays - must become .
Subtracting exponents in the wrong order when dividing - it is top minus bottom, , not .
The procedure for cube roots is the easy part; the trap is using square root because the radical looks familiar. Asking "What number multiplied by itself three times gives this value?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Using square root because the radical looks familiar — check the small index 3.
Dividing by 3 instead of undoing a cube — , not 9.
Forgetting that the cube root of a negative number exists and is negative — .
The procedure for significant figures is the easy part; the trap is counting leading zeros as significant. Asking "Does this digit carry real information from the measurement, or is it just placing the decimal point or padding the calculator?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Counting leading zeros as significant - leading zeros only locate the decimal point; has 2 s.f.
Reporting all calculator digits - keep only as many as the least-precise measurement justifies.
Treating trailing zeros as never significant - has 3 s.f. because the zero shows measured precision.
The procedure for prime factorization is the easy part; the trap is stopping before all factors are prime. Asking "Is every factor in my answer a prime number that can't be broken down any further?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Stopping before all factors are prime - keep splitting any composite factor until only primes remain.
Including as a prime factor - is not prime and adds nothing to the product.
Mixing up factors and multiples - factorization goes downward into smaller primes, not upward into bigger multiples.
The procedure for negative numbers is the easy part; the trap is thinking because 5 looks bigger. Asking "Is there a meaningful zero point, and does this value sit on the opposite side of it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.
Thinking because 5 looks bigger - on the number line the value farther left is smaller, so .
Confusing the negative sign with subtraction - in the sign labels a value below zero; in it is an operation.
Treating distance as the value - the depth of is from zero, but the number itself is still .