When to skip a GMAT Quant problem
Targeted preparation for GMAT Quantitative Reasoning, from item families and pacing to scoring logic and the algebra patterns that decide a strong quant performance.
Berk Sağlam · Senior GMAT & GRE Quant Instructor / TestPrep QBank Author · since 2014
Reviewed by: Murat Özdemir · Senior GMAT & GRE Quant Instructor / Data Insights Specialist · since 2014
In this article (16 sections)
GMAT Quantitative Reasoning is the shortened, reworked quant section of the current GMAT, and it sits at the heart of every serious MBA admissions file. TestPrep Europe treats it as a distinct subject, not a retitling of the older Quantitative section, because the question count, the content and the scoring have all changed: the section is now 21 Problem Solving questions, Data Sufficiency has moved to Data Insights, geometry is gone, and there is still no calculator. A candidate who walks in expecting the legacy exam will lose time on item types they never drilled. This article walks through the structure of the section, the six item families you can be asked to solve, the algebra and number-property patterns that carry the heaviest load, and the pacing logic that separates an 80 from an 85.
What the section actually contains: format, length, and scoring weight
The Quantitative Reasoning section of the GMAT contains 21 questions to be completed in 45 minutes, which gives a working budget of roughly 2 minutes and 8 seconds per item before reading time. In practice, reading the stem and the answer choices will eat 60 to 90 seconds on most items, so the arithmetic itself has to resolve inside a window closer to 30 to 60 seconds. The section feeds directly into the Quant score on the 60-to-90 scale used for the GMAT, and the Quant score is the single most heavily weighted input in most admissions algorithms after the cumulative GPA. Unanswered questions are not a free pass either: any question still unanswered when the clock runs out lowers your section score, because the number of questions answered is one of the three factors GMAC uses to score a section.
Every item is a Problem Solving question with five options, and there is no calculator in this section; the on-screen calculator is available only in Data Insights. That shapes the way candidates should think about arithmetic: heavy long division and square-root work are a time tax you have to avoid by hand, and the test is engineered to reward candidates who recognise the underlying structure of a problem before reaching for digits. The section adapts question by question: the first question is of medium difficulty, and after each answer the engine updates its estimate of your ability and chooses the next question accordingly. The implication for preparation is simple — a run of careless errors early on pulls the difficulty down, and you then have to climb back with the questions that remain, so accuracy matters from the very first item.
A second consequence of question-level adaptivity is that the difficulty you see is not a clean ascending curve. Because each question is chosen from your running ability estimate, you cannot use the perceived difficulty of a problem as a reliable signal of how well you are doing. Candidates who try to game the section by rushing through the 'hard-looking' items almost always hurt their score, because a streak of wrong answers pulls the next questions down to an easier level, and the score then has to be rebuilt from a lower base. Treat every item as if it counts, because it does.
The six item families and how to recognise each one on sight
GMAT Quantitative Reasoning draws on a fixed repertoire of question formats, and the first tactical job is to identify which family you are looking at before you read a single number. Most candidates lose 30 to 45 seconds per item to misclassification, and over 21 items that compounds into the loss of two to three correct answers. The families break down into six recognisable types: problem solving with algebraic setup, arithmetic and number properties, word problems with rates or work, percentages, ratios and proportions, statistics and probability, and counting, sets and sequences. Geometry is no longer tested in this section, and chart and table reading now lives in Data Insights.
Algebraic problem-solving items present a clean equation or expression and ask you to evaluate, simplify, or solve. They are the most numerous, and they are also the family where careless arithmetic costs the most. The trick is to set up a clean algebraic frame on your scratch pad before plugging in numbers, because the test is engineered to punish candidates who try to compute their way through a problem that reduces to a single line of factorisation. Number property items ask about divisibility, remainders, primes, factors, or parity. These test conceptual grip more than computational speed, and they are often the source of the fastest wins on the section, because the right framing collapses a 90-second calculation into a 20-second reasoning chain.
Word problems involving rates, work, mixtures, or ages are the family that most often trips up strong readers. The trap is not the math but the units — minutes versus hours, dollars versus thousands, per cent versus percentage points. Percentage, ratio and proportion items look routine, but they hinge on the base of each comparison — per cent of what, ratio of which part to which whole — and a quick sketch of the quantities on the noteboard is the single most efficient time investment a candidate can make. Statistics and probability items test combinations, conditional probability, and the standard deviation concept, and higher-scoring candidates tend to meet them in their harder forms as the adaptive engine raises the difficulty. Counting, sets and sequences items — overlapping sets, arrangements and selections, terms of a sequence — reward candidates who organise the information in a small table or Venn sketch before they compute anything.
- Algebraic problem solving: solve, simplify, or evaluate an expression or equation; the highest-volume family, dominated by linear and quadratic manipulation.
- Number properties: divisibility, remainders, factors, primes, parity; the family where a 20-second conceptual read beats a 90-second brute force attempt.
- Rates, work, and mixture word problems: the test of unit discipline; always convert before you compute.
- Percentages, ratios and proportions: percentage change, ratio mixtures, parts and wholes; name the base of every comparison before you compute.
- Statistics and probability: combinations, conditional probability, mean and median reasoning; appears more often in its harder forms as the adaptive engine raises the difficulty.
- Counting, sets and sequences: overlapping sets, arrangements, selections and sequence terms; a small table or Venn sketch beats holding the numbers in your head.
A 30-second classification routine
Build a personal triage reflex. Read the last line of the stem first, before you read the body. If the last line asks 'which of the following could be the value of x', you are looking at an algebraic problem-solving item, and your job is to find one valid option, not to solve for x in closed form. If the last line asks 'which of the following must be true', you are looking at a must-be-true or number-property item, and your job is to test each option against a counterexample. If the last line asks about a per cent change, a ratio, or a difference between two quantities, you are looking at a percentage or ratio item, and naming the base of the comparison is where you should spend your first 15 seconds, not the arithmetic. This classification reflex is, for most candidates reading this, the single highest-leverage habit to install before the next practice test.
Algebra: the patterns that carry the heaviest load on the section
Algebra is the load-bearing wall of the section. Roughly four out of every seven items you see will resolve to an algebraic frame, and the most common frames are linear equations, quadratic expressions, systems of two equations in two unknowns, and inequalities with absolute value. The first habit to install is to write the original equation in its most reduced form before you start manipulating. Candidates who rearrange on the fly inside their head lose track of sign and sign-flip errors become the single most common reason an otherwise strong algebra answer gets crossed out at the last minute.
Quadratic expressions reward a specific technique: look for a way to factor by inspection before you reach for the quadratic formula. The test is engineered so that most quadratics factor cleanly into two integer binomials, and a candidate who reads the coefficients carefully can usually see the factorisation inside 10 to 15 seconds. The discriminant check — does b² − 4ac yield a perfect square? — is the backup move when factoring is not obvious. For systems of two equations, the decision rule is to pick the elimination path that removes the smaller coefficient first, and to avoid substitution unless one of the variables is already isolated. Substitution in an untidy system costs 30 to 45 seconds and is the most common reason a system-of-equations item eats more than its share of the budget.
Inequalities with absolute value are the family where most candidates lose points they should be keeping. The test is engineered to test two distinct traps: the case-split when the expression inside the absolute value changes sign, and the direction of the inequality when you multiply or divide by a negative. A clean workaround is to translate the absolute value into two cases on the scratch pad, solve each, and check the candidate answer against the original stem before selecting. For most candidates, the cost of doing this in writing is 20 seconds; the cost of getting it wrong and re-reading the stem is 60 to 90 seconds.
Three concrete algebra patterns you should drill until they are automatic
The first pattern is the linear equation that hides inside a word problem. A candidate reads about a price increase of p per cent, a quantity doubling over n years, or a sum split into two parts, and the algebra reduces to a single linear equation. The drill is to translate the prose into the equation first, then solve. The second pattern is the quadratic that can be rewritten as a perfect square. The test loves expressions of the form (x − a)² = b, because they collapse to a one-line solution if you recognise the structure. The third pattern is the system of two equations where one variable is expressed in terms of the other, and the substitution move is genuinely faster than elimination. Drilling these three patterns until they are reflex actions is, in my experience, the most efficient two-week investment a candidate can make in the algebra side of the section.
Number properties: the family that rewards conceptual grip over arithmetic
Number property items are where the section's design philosophy shows most clearly. The test is not asking whether you can divide 4,578 by 13 — there is no calculator in this section, and a well-built item rarely needs that kind of arithmetic. It is asking whether you understand what divisibility, remainder, and primality mean as concepts, and whether you can use those concepts to eliminate wrong answers faster than you can compute the right one. A typical item gives you a constraint, asks which of five options must be true, and expects you to test the options in under 60 seconds by reasoning about structure rather than grinding out arithmetic.
The first concept to lock in is divisibility. A number is divisible by 2 if its last digit is even, by 3 if the sum of its digits is divisible by 3, by 4 if the last two digits are divisible by 4, by 5 if its last digit is 0 or 5, by 9 if the sum of its digits is divisible by 9, and by 11 if the alternating sum of its digits is divisible by 11. These six rules cover roughly 80 per cent of the divisibility reasoning the test will ask of you, and they are the difference between a 30-second answer and a 90-second answer. The second concept is the prime factorisation, because every multiple, every least common multiple, and every greatest common divisor question reduces to a prime factorisation in disguise.
Remainder problems are the third pillar, and they reward a specific technique: write the dividend as divisor times quotient plus remainder, and reason about the structure of the remainder class. The test is engineered so that the right answer often hinges on a single observation — for example, that a remainder of 3 when dividing by 7 means the number is congruent to 3 mod 7, and that adding or subtracting 7 preserves the remainder class. Once you see the problem in modular terms, the answer falls out in 15 to 20 seconds. Parity — even versus odd — is the fourth pillar, and it shows up more often than candidates expect, usually as a quick elimination tool. If a question asks which option must be odd, you can eliminate any option that is even on inspection without computing anything else.
Common pitfalls in number properties — and how to avoid them
The first pitfall is to grind out long arithmetic. With no calculator in this section, brute-force division will not tell you quickly whether a number is prime, whether it is divisible by 7, or whether a remainder is consistent with a stated constraint. Candidates who compute their way through these items often end up doing more work, not less, and they lose the time they should have saved on the easy arithmetic. The second pitfall is to confuse 'must be true' with 'could be true'. The test uses both phrasings, and they demand opposite reasoning directions. For 'must be true' items, the wrong answer is one that fails in a single case; for 'could be true' items, the wrong answer is one that fails in every case. Reading the verb in the last line of the stem is, for most candidates reading this, the single highest-leverage habit to install on this family. The third pitfall is to ignore the trap options that the test plants to catch candidates who confuse factors with multiples, or who treat a remainder of 0 as a special case rather than as 'divisible with no remainder'.
For your GMAT prep
Chart and table reading: a Data Insights skill, not a Quant one
Chart, table and graph questions do not appear in the Quantitative Reasoning section; they sit in Data Insights, in item types such as Graphics Interpretation, Table Analysis and Multi-Source Reasoning, where an on-screen calculator is available. They draw on the same arithmetic you drill for Quant, so it pays to train the reading routine alongside your Quant work. These visual items are among the most time-pressured on the test, because the eye has to read the visual twice — once for structure, once for the specific numbers the question is asking about. Candidates who read the prose first and the visual second almost always end up scrolling back to the visual, and each scroll costs 8 to 12 seconds. The correct reading order is visual first, prose second, options third.
The first move on a data interpretation item is to anchor the axes. What is the scale? Are the units in thousands, millions, or raw counts? Are the bars stacked or grouped, and which category does each colour represent? This is the information that, if missed, makes the question literally unanswerable, because every answer choice is calibrated to a specific misreading of the chart. The second move is to identify the specific data point or comparison the question is asking about, and to read that point off the chart before looking at the prose for context. The third move is to estimate rather than compute, because the answer choices are written to reward candidates who can see that a value is closer to 12 than to 13 without doing the long division.
Estimation is the under-used weapon on this family. The test is engineered so that the right answer is rarely the one that requires exact computation, and the wrong answers are clustered close to the right answer to catch candidates who round in the wrong direction. A clean estimate, written on the scratch pad in 10 seconds, will eliminate three of the five options and leave you with a single comparison to verify. The trap to avoid is to trust the calculator on a visual item: the calculator will give you a number to three decimal places, but the chart is accurate to within five per cent, so the calculator's precision is illusory. The right answer is the one that is consistent with the chart's resolution, not the one that is consistent with the calculator's output.
| Reading step | Time budget | What you should have on your scratch pad |
|---|---|---|
| Anchor axes and units | 10 to 15 seconds | Scale, unit, legend, and the category each colour represents |
| Locate the data point | 10 to 15 seconds | The specific bar, line, or row the question is asking about |
| Estimate the value | 10 to 15 seconds | A range, not a point estimate, that lets you eliminate three options |
| Compare to options | 10 to 15 seconds | The single option that falls inside your estimated range |
| Verify against prose | 10 to 15 seconds | Confirmation that the prose and the visual point to the same quantity |
Pacing: the minute-by-minute budget that holds across 21 items
Pacing on this section is not about speed for its own sake. It is about preserving accuracy under time pressure, and the two metrics that matter are the rolling accuracy rate over the last five items and the time spent per item relative to a 2:08 budget. Candidates who finish the section with time to spare but with an accuracy rate below 80 per cent have made a strategic error: they have spent their time on the wrong items. The goal is to spend more time on items you can solve correctly and less time on items that are draining your accuracy.
A workable pacing rule is the 90-second cap. If you have not made meaningful progress on an item inside 90 seconds of reading the stem, enter your best guess, bookmark it, and move on. Once every question is answered, the Question Review & Edit screen lets you revisit bookmarked items and change up to three answers in the section, so a bookmarked guess is not a lost cause. A candidate who cuts two stalled items at 90 seconds and uses the saved minutes to secure three correct answers elsewhere has made a clear net gain, and it shows up in the eventual Quant score.
The pacing trap to avoid is the late-section slowdown. Candidates who reach the halfway point with minutes in hand often relax their reading pace to use up the spare time. This is the wrong move. If you have been answering well, the adaptive engine is already serving harder questions, and those take longer by design. Slowing down does not help; it only lengthens the time you spend on items that will take you longer anyway. A better rule is to keep a steady 2:00 to 2:15 pace per item across the whole section, and to spend banked time only on the one or two items that genuinely require it or on the review screen at the end.
Common pacing pitfalls and how to avoid them
The first pitfall is the early-section perfectionism trap. Candidates who spend 3 to 4 minutes on each of the first three items to make sure every answer is perfect are over-investing in items that the engine treats as routine. The result is a compressed time budget for the harder items later in the section, and a higher likelihood of careless errors under time pressure. The second pitfall is the late-section guessing trap. Candidates who arrive at item 18 with three minutes left often try to solve each remaining item in 30 seconds, which is below the threshold at which the section's design can reward careful reasoning. The right move is to pick the option that survives a 30-second sanity check, mark it, and move on. The third pitfall is the banked-time misallocation trap. Candidates who finish with 5 minutes to spare often spend them re-checking items they already answered correctly, instead of returning to the items they bookmarked. The expected value of returning to a bookmarked guess is much higher than the expected value of re-checking a solved one, because the guessed item is by definition the one you are most likely to have got wrong, and with only three answer changes allowed per section, those changes belong where they can turn a wrong answer into a right one.
Preparation strategy: a four-week build that respects the section's design
A four-week build is the right window for a candidate who is starting from a clean slate. The first week should be diagnostic: take a full-length practice test under timed conditions, score it, and isolate the two item families where your accuracy is lowest. The second week should be remedial on those two families, with daily drilling on the underlying patterns and a weekly timed mini-section of seven items. The third week should be integrative: mix all six families inside timed mini-sections, and start practising the 90-second cap and the rolling-accuracy habit. The fourth week should be consolidation: full-length timed practice tests, with a careful post-mortem on every wrong answer, and every Quant set worked without a calculator, exactly as on test day.
The single most important preparation habit is the wrong-answer journal. After every practice block, write down each item you got wrong, the family it belongs to, the specific error you made (conceptual, arithmetic, or pacing), and the one move you will make next time to avoid the same error. Candidates who keep a wrong-answer journal improve their accuracy at roughly twice the rate of candidates who simply re-do missed items, because the journal forces a specific diagnosis rather than a vague intention to 'be more careful'. The second most important habit is the timed mini-section. A candidate who drills 50 items in 100 minutes will retain less than a candidate who drills 14 items in 30 minutes, four times a week, with a strict 90-second cap on each item. The test is a time-pressured exam, and the practice has to be time-pressured as well.
The third preparation lever is the official question bank. It is the only bank that is calibrated to the section's actual scoring engine, and it is the only bank that will give you a reliable score prediction. Third-party banks are useful for pattern drilling, but they should not be used for score prediction, because their difficulty distribution is not aligned to the current exam's adaptive logic. A workable split is roughly 60 per cent official-bank practice and 40 per cent third-party drilling, with the official bank reserved for timed full-length simulations and the third-party banks used for untimed pattern work.
Spotting a time-eating Quant problem in the first seconds
Some Quant problems announce that they will be slow before you write a line. Common signs: three or more unknowns with no obvious link between them, fractions nested inside fractions, "in terms of" wording that asks for rearrangement rather than a number, and word problems that mix units, rates or time windows. None of these makes a problem impossible, but two or three together usually mean a long solve.
In the first seconds, read the question at the end of the stem, then the givens, then the restrictions ("positive integer", "between 0 and 1"). Name the topic and the first move you would make. If no first move comes to mind, the problem is likely to be expensive.
What "skipping" means on the GMAT
You cannot leave a GMAT question blank and come back later: every question has to be answered before you can move on, and unanswered questions at the end of a section are penalised. "Skipping" therefore means choosing quickly. Eliminate what you can, make an educated guess, bookmark the question, and protect your time for the questions you can solve. If time remains at the end, Question Review & Edit lets you revisit bookmarked questions and change up to three answers per section.
Train recognition separately from solving
Once a week, take a mixed set and spend a short, fixed time on each problem without solving it: write down the topic, the first move, and whether you expect it to be quick or slow. Then check your expectations against the solutions. Keep a running list of the features of the problems that actually cost you time; after a few weeks that personal list will predict your slow problems better than any generic one.
Putting it together: what separates an 80 from an 85 on this section
The gap between an 80 and an 85 on GMAT Quantitative Reasoning is not raw intelligence. It is the consistent application of three habits: a 30-second classification reflex on every item, a 90-second cap on every item, and a rolling-accuracy check every five items. The 80-level candidate usually has the conceptual grasp to solve most items, but loses points to misclassification, to over-investment in hard items, and to careless arithmetic under time pressure. The 85-level candidate has installed the three habits, and the result is that the section's adaptive engine feeds them a steady stream of items at the upper end of the calibration range.
The path from one band to the other is not glamorous. It is hundreds of timed practice items, a daily wrong-answer journal, and a willingness to drill the three highest-leverage patterns — algebraic setup, number-property reasoning, and percentage and ratio framing — until they are reflex actions. For most candidates reading this, the bottleneck is not the math; it is the discipline to install the habits that the section's design rewards. The test will meet you halfway, but only if you do the work.
TestPrep Europe's diagnostic assessment is a natural starting point for candidates building a sharper preparation plan around the six item families of GMAT Quantitative Reasoning.