Week 10 · TIME PRESSURE · 20–30 hrs

Timed sprints & when to guess

Estimation as a deliberate method

Quantitative

On GMAT Focus Quant, estimation is a deliberate bound, not a lazy shortcut. The exam rarely asks you to estimate explicitly. Instead it spaces answer choices widely enough that exact computation is optional — and includes questions where that spacing is a trap, because two choices differ by less than the error your rounding introduces.

The disguise is a word problem with messy numbers: profit margins, mixture ratios, rates with decimals. You can eliminate three choices by order of magnitude in seconds. But the same technique fails when the question asks for an exact property — a remainder, a unit digit, whether a value is an integer — because approximation can suggest exactness but cannot confirm it.

Three decisions separate correct from tempting. First, compare the gap between adjacent choices to your expected rounding error; estimate only if that error is less than half the smallest gap. Second, round factors in opposite directions so errors cancel. For $a\times b$, if you raise $a$ by $p\mathrm{\%}$ and lower $b$ by $q\mathrm{\%}$, the product changes by roughly $(p-q)\mathrm{\%}$; $19.8\times 5.1$ is better as $20\times 5=100$ than as $20\times 5.2=104$. Third, in Data Sufficiency, estimation can show a statement is insufficient by yielding two different plausible values, but it cannot prove sufficiency.

The mechanical loss: strong candidates round every number the same way, compound the error, and land on a distractor that differs from the true value by exactly that compounded amount.

Pacing benchmarks per section

Exam skills

GMAT Focus does not test whether you can solve a question quickly. It tests whether you can allocate a fixed clock across a section whose questions vary wildly in cost. The benchmark is not a per-question cap. It is a checkpoint: a time-remaining figure at a known question number that tells you whether the current question is affordable.

The published section clocks give you the only averages you need. Quant: $45\mathrm{/}21\approx 2:09$ per question. Verbal: $45\mathrm{/}23\approx 1:57$. Data Insights: $45\mathrm{/}20=2:15$. Treat these as the slope of a line, not a rule. By the halfway question you want roughly 22 minutes left; by the three-quarter question, roughly 11.

The disguise is a question that feels fast — a short Quant prompt or a single-paragraph Verbal — but requires a full algebraic solve or a subtle scope shift, eating three minutes against a two-minute benchmark. The reverse disguise: a dense Data Insights set early that makes you think you are behind, when the checkpoint at question 5 shows you are ahead.

The decisions that separate scores: check the clock only at fixed question intervals, never continuously; abandon a question when its elapsed time exceeds its budget and your checkpoint says you cannot recover; spend surplus time only on questions you are certain you can solve. The mechanical loss is enforcing the average as a cap: rushing a three-minute question at two minutes, getting it wrong, then burning the saved minute on a question you cannot solve anyway.

When to guess and move on

Exam skills

Guessing on GMAT Focus is not what you do to questions you cannot solve. It is a decision you make about questions you could eventually solve, before they take a second question down with them. There is no wrong-answer penalty, so every question must end with a selection; the only variable is what that selection costs you.

The real test is triage under sunk cost. A guess at ninety seconds and a guess at four minutes score identically. The second one also compresses everything after it. That escalation — not ignorance — is where strong candidates bleed: they refuse to abandon a question they are nearly finished with, guess anyway, and start the next question rattled and behind.

Triggers are mechanical, not emotional: you have re-read the same sentence twice with no new information; you can name two answers but no reason to prefer either; you are doing work the question did not ask for; the setup looks familiar but your first step is not converging.

Two decisions separate the useful guess from the expensive one. Guess on your own terms — before the clock decides, while you can still read the next question properly. And guess with an elimination, not blind: removing one option turns $1\mathrm{/}5$ into $1\mathrm{/}4$, which is often a full minute of work avoided. In Data Insights, partial selections earn nothing, so a half-built multi-part answer is worth exactly a blank — commit to a full guess.

Flag and return only if you finish the section with time and a specific new idea. A second look rarely changes the answer and always spends time you will want on the questions still ahead.

Timed sprints and how to run them

Exam skills

A sprint is four to six questions, one skill, a hard buzzer, and a post-mortem longer than the sprint itself. Skip the post-mortem and you have practised answering quickly, which is not the skill.

Sprint on one question type, or one decision — "does the second statement add anything?" — never a mixed set. Mixed sets produce a number, not a diagnosis. Use material you can already solve untimed at roughly 75–85%; harder questions make you slow for good reasons, and you will train yourself to abandon reasoning that was about to pay.

Set the clock from your own data: sprint minutes $=n\times m$, where $m$ is your recent untimed median for that question type. Hold the stop, then finish the question anyway and log the overrun. Whether the overrun changed the answer is the only evidence that speed, rather than knowledge, is your binding constraint.

The recurring error is scoring the sprint on time alone. Six correct in eight minutes is worse training than five correct with one candid loss. Score correct-at-target, and keep time-to-first-move separate from total time: most lost points in this range come from entering late, not from working slowly. A question you committed to at $t=40$s and closed at $t=140$s costs what one opened at $t=0$ and closed at $t=100$s costs — but only the first shows you where the time actually goes.

---

← Week 9 · Week 11: Harder questions & recovery →