1.2 Mental Math, Estimation & Non-Calculator Strategies

Why Mental Math Is Part of the Official Test

GMAC's exam-content pages are explicit: Quantitative Reasoning has no calculator. The on-screen calculator is a Data Insights tool. That rule is not a trivia fact; it is why a tester who can only multiply 48 × 52 with long arithmetic will run out of the 128.5-second budget, while a tester who sees (50 − 2)(50 + 2) = 2,500 − 4 = 2,496 will not.

Official Guide Estimation (OG Math Review 3.4) is the companion skill. Estimation is not "sloppy math." It is a licensed method for deciding when an approximate value is enough to select an answer, and when the choices are too close to risk rounding. The first move on almost every computation-heavy item is therefore: read the spread of the answers, then choose a method.

Method Gate (Do This Before You Compute)

• Wide spread (answers differ by 20%+ or by an order of magnitude): round to 1–2 significant digits, keep track of rounding direction, and eliminate.
• Last digits disagree (396 vs. 405 vs. 414): compute only the units digit of the exact expression.
• Tight spread (48.2 vs. 48.6 vs. 49.0, or consecutive integers): compute exactly with an identity or careful paper work.
• Fractions or percents: convert to a convenient form first; do not launch into long division if a benchmark or cross-product will do.

Fraction, Decimal, and Percent Fluency

Long division of 1 ÷ 8 during the section is a pacing leak. You need the common conversions as recall, not as procedures.

Trap: 1/6 is not 0.16. The repeating 6 makes 16 2/3%. If an answer is 0.16 and another is 0.167, the conversion error selects the wrong one. Trap: 1/8 = 0.125, not 0.12. On a tight-spread item those two mistakes are designed distractors.

Comparing two fractions is often faster than converting either one. To compare 5/12 and 7/16, cross-multiply: 5 × 16 = 80 and 7 × 12 = 84. Because 84 > 80, 7/16 is larger. No decimals required.

"Of" with a friendly denominator is cancellation, not multiplication of messy numbers. 3/8 of 56: 56 ÷ 8 = 7, then 3 × 7 = 21. 5/6 of 84: 84 ÷ 6 = 14, then 5 × 14 = 70. If the denominator does not divide the integer, factor first: 2/15 of 45 = 2 × 3 = 6 because 45/15 = 3.

Percentage Benchmarks Instead of Long Decimals

Rebuild any percent from 50%, 10%, 5%, 1%, and 0.1%:

• 10% of a number: move the decimal one place left (10% of 480 = 48).
• 5%: half of 10% (24).
• 1%: move the decimal two places left (4.8).
• 50%: half (240).
• 25%: divide by 4 (120).
• 20%: double 10% (96).

Worked example: 27% of 640. 27% = 25% + 2%. 25% of 640 = 640/4 = 160. 1% of 640 = 6.4, so 2% = 12.8. Total 172.8.

Worked example: 15.5% of 360. 10% = 36, 5% = 18, 0.5% = 1.8. Sum 55.8.

Sequential percent trap (do not add the percents). A price rises 20% and then falls 20%. Starting at 100: 100 → 120 → 96. Net change is a 4% decrease, not 0%. The second percent uses a new base. The same trap appears as +10% then −10% (net −1%) and as +15% then −20% (net −8%). Always chain the multipliers: (1 + r)(1 + s) − 1, with r and s as signed decimals.

Factoring Arithmetic and Other Fast Products

When two factors sit equally far from a round number, use the difference of squares: (m − d)(m + d) = m² − d².

• 39 × 41 = (40 − 1)(40 + 1) = 1,600 − 1 = 1,599
• 48 × 52 = (50 − 2)(50 + 2) = 2,500 − 4 = 2,496
• 77 × 83 = (80 − 3)(80 + 3) = 6,400 − 9 = 6,391
• 19 × 21 = 400 − 1 = 399

Double-and-halve when one factor is even: 35 × 44 = 70 × 22 = 140 × 11 = 1,540. 2.5 × 68 = 5 × 34 = 10 × 17 = 170.

Friendly 5-powers:

• ×5 = ×10 then ÷2
• ×25 = ×100 then ÷4 (because 25 = 100/4)
• ×125 = ×1,000 then ÷8 (because 125 = 1,000/8)

Example: 36 × 25 = 3,600/4 = 900. Example: 48 × 125 = 48,000/8 = 6,000.

Squares ending in 5: n5² = n(n+1) followed by 25. 15² = 1×2 then 25 = 225. 25² = 2×3 then 25 = 625. 35² = 3×4 then 25 = 1,225.

Keep a compact power list in memory, not a 30-row wall of unused cubes. Squares through 20² and 25², cubes through 10³, and powers of 2 through 2¹⁰ = 1,024 cover almost every Quant simplification. 12² = 144, 13² = 169, 14² = 196, 15² = 225, 16² = 256, 18² = 324, 24² = 576, 25² = 625 are the ones that appear in factoring and radical questions later in this guide.

Last-Digit (Units) Cycles

When answers differ only in the last digit, or when an exponential is far too large to expand, compute only the units digit. The units digit of a product depends only on the units digits of the factors. Powers of a single digit cycle:

Algorithm for bⁿ: take the units digit of b, find remainder r = n mod (cycle length), and if r = 0 use the last entry of the cycle.

Worked example: units digit of 7⁸³. Cycle of 7 is 7, 9, 3, 1. 83 ÷ 4 = 20 remainder 3, so use the third entry: 3 (because 7³ = 343).

Worked example: units digit of 3⁴ × 7². 3⁴ ends in 1 (full cycle), 7² ends in 9, and 1 × 9 ends in 9. You never need 81 × 49.

Estimation vs. Exact Computation (Official Guide Estimation)

OG Estimation asks you to replace ugly numbers with nearby convenient numbers, then track whether you rounded the result up or down. The goal is to box the true value between a lower bound and an upper bound that still hit only one remaining answer.

Worked example. Estimate (48.7 × 21.2) / 9.8. Round to (50 × 21) / 10 = 105. Direction check: 48.7 is a little under 50 (pulls down), 21.2 is a little over 21 (pulls up), 9.8 is a little under 10 (dividing by a smaller number pulls up). The estimate 105 is slightly high but in the right neighborhood. If the answers are 52, 105, 210, and 980, you select 105 and move on. If the answers are 103, 105, 107, and 109, estimation is not enough — compute more carefully or factor.

Bounding a quotient. For A/B, an upper bound comes from rounding A up and B down; a lower bound from rounding A down and B up. 397 / 19.6 sits below 400/19.6 ≈ 20.4 and above 397/20 = 19.85, so the value is about 20. If answers are 4, 20, 40, and 200, you are done in 15 seconds.

When you must be exact: consecutive integer answers; dollar amounts that differ by 1 or 2; remainder questions; "which of the following is closest" with a 1% grid; any item where two answers sit inside your rounding error. On those items, use an identity (difference of squares, factoring, last digit) rather than rounding.

Keep scratch work aligned. Write the rounded model on one line and the direction arrows on the next: "used 50 instead of 48.7 → too big." That one note prevents selecting a neighbor of your estimate when you already know the estimate is high.