10 TMUA Mistakes That Cost Marks Under Time Pressure

The TMUA gives you 3 minutes 45 seconds per question, no calculator, and a cohort where two extra correct answers per paper separate the median from the top 8%. At that margin, technique errors cost more than knowledge gaps. Here are the ten we see most in mock data, each with the fix.

Table of contents

• The pacing maths first
• Mistakes 1-5: decision errors
• Mistakes 6-10: execution errors
• How to actually train these out
• Frequently asked questions

Intro

Most TMUA advice is content advice: revise logs, learn the logic vocabulary, do past papers. Necessary, not sufficient. The students who plateau at 5.0 in mocks usually do not have content gaps. They have a repertoire of small, repeatable errors that only appear under the clock, which is why they never show up in untimed revision. This list is those errors. Every one is specific enough to check against your own mock working tonight.

The pacing maths first

75 minutes, 20 questions: 3:45 average. But the average is a trap, because TMUA questions are not equally priced in time. A realistic strong-candidate split is 90 seconds on the eight most accessible questions, three minutes on the middle eight, and the banked surplus, six minutes or more each, on the hardest four. If you spend 3:45 evenly, you overpay for easy questions and underpay for hard ones. Every mistake below gets worse when this budget is already broken.

Mistakes 1-5: decision errors

1. Answer-option anchoring. You read the five options before committing to your own approach, and the options quietly start steering the method. Distractors are engineered from the most common wrong methods, so anchoring walks you down a pre-built wrong path that conveniently ends at option C. Fix: read the stem, decide your approach, start working, and only consult the options to check form (integer? surd? interval?) or to eliminate. Exception: questions that are explicitly faster by testing the options, which brings us to the next point.

2. Premature algebra instead of testing values. Asked whether a statement holds for all x, or which inequality is consistent with given constraints, strong students reflexively reach for general algebra. Often plugging in two or three well-chosen values (0, 1, a negative, something between 0 and 1) settles it in 40 seconds. Fix: before any general manipulation, spend ten seconds asking "would a specific number kill this?" On always/never claims, one counterexample is a full solution.

3. Sunk-cost stubbornness. You are four minutes into a question, the algebra is getting uglier, and you keep going because leaving feels like wasting the four minutes. The four minutes are already gone. The next mark is cheapest somewhere else. Fix: a hard rule, decided before the exam: any question that stalls past your budget gets an elimination-informed guess, a flag, and an exit. Emotion does not get a vote at minute four.

4. Casework indiscipline on logic items. Paper 2 questions about necessary and sufficient conditions, or about which statements must be true, are usually finite casework in disguise. Under pressure, students enumerate cases in their head, skip the boring case, and miss the edge: the empty set, n = 1, x = 0, the constant sequence. Fix: cases go on the whiteboard, numbered, every time. The discipline costs 20 seconds and catches the exact edge case the question was built around.

5. Misreading negations and quantifiers. "Which of the following is NOT necessarily true", converse versus contrapositive, "exactly one" versus "at least one". The 2024-25 wordier style increased the reading load, and negation misreads are the most common casualty; we covered the format shift in detail in the new TMUA format post. Fix: rewrite the target statement on your whiteboard in your own symbols before evaluating anything. If the stem contains NOT, write the word down and box it. Mechanical, and it works.

Mistakes 6-10: execution errors

6. Whiteboard chaos. On-screen delivery means all working lives on an erasable board. Unlabelled fragments from three questions ago contaminate current working, and returning to a flagged question means redoing it from scratch because you cannot trust your own notes. Fix: label every block of working with its question number, keep flagged-question working until resolved, erase only on commitment.

7. Flag misuse on Pearson VUE. Two failure modes. Flagging nothing, so your second pass has no map. Flagging half the paper, so the flag means nothing. Fix: flag only questions where you have a concrete re-entry point ("eliminated A and D, try x = 2 next"). Note that re-entry point on the board. A flag without a plan is just deferred panic.

8. Ugly-number arithmetic when clean numbers were available. No calculator means every arithmetic choice has a price. Students expand brackets when factorising was available, or grind decimals when fractions cancel. Fix: before computing, scan for structure: difference of two squares, common factors, logarithm laws that collapse the expression. If your arithmetic is getting ugly, that is usually the paper telling you there is a cleaner route, not a demand for more grinding.

9. Answering the wrong question. You solve for x correctly and select the option matching x. The question asked for x squared plus one, or the sum of the roots, or how many such x exist. Distractor writers know this and the value of x is reliably among the options. Fix: last action on every question, no exceptions: re-read the final sentence of the stem, then check your selected option answers that sentence. Five seconds. This is the single highest-yield habit on this list.

10. Proving when you should be hunting counterexamples. On "must be true" items with several candidate statements, students try to prove each one in turn. Proving is expensive; refuting is cheap. Fix: invert the workflow. Attack every statement with your standard counterexample kit first (0, 1, negatives, non-integers, equal values, extreme values). Whatever survives the kit, then spend proof effort on. Usually only one statement survives.

How to actually train these out

Reading this list changes nothing by itself. These are habits, and habits only change under the conditions that trigger them.

1. Get a baseline. Our free diagnostic is timed and on-screen, so the time-pressure errors actually show up.
2. Audit your last three mocks against this list. For every dropped mark, write which of the ten it was, or "genuine content gap". Most students find three or fewer of the ten account for the majority of their losses.
3. Drill the top offenders in timed blocks. The mocks in TMUA Pro are auto-marked with per-question timing analytics, which makes mistakes 1, 3 and 7 visible in the data rather than a vague feeling. The question-level "why you got it wrong" breakdowns are built around exactly these error categories.
4. If one error survives three mocks of targeted effort, that is the point where an hour with a Cambridge tutor watching you work in real time beats any amount of solo drilling, because the habit is happening below your own awareness.

Related reading

• The New TMUA Format: Why Pre-2024 Past Papers Mislead You
• TMUA Score Conversion: Raw Marks to the 1.0-9.0 Scale
• The TMUA Specification, Broken Down
• How to Prepare for the TMUA in 16 Weeks (a Realistic Plan)

Closing

The TMUA punishes process errors more than knowledge errors because the margin at the top is so thin: roughly two to three questions per paper between the median and a competitive score. Every mistake on this list is worth at least one of those questions to somebody. Find your three, drill them under the clock, and you have done more for your October score than another untargeted past paper ever will.

Frequently asked questions

How long do you get per TMUA question? 75 minutes for 20 questions per paper, which is 3 minutes 45 seconds per question on average. In practice you should bank time on easy questions early so the hard ones can run to five or six minutes.

Should I guess on the TMUA? Always answer everything. There is no negative marking, so a blank is strictly worse than a guess. Eliminate options first; even removing two distractors turns a 1-in-multiple guess into much better odds.

What is the flag-and-return strategy on the TMUA? The Pearson VUE interface lets you flag questions and review them before submitting. Use it as a two-pass system: first pass for questions you can solve cleanly, flagging anything that stalls, then a second pass through the flags with the remaining time.

Why do I run out of time on TMUA papers? Usually not slowness at maths. The common causes are refusing to abandon a stalled question, choosing algebraic generality when testing values would do, and re-reading wordy stems because the first read was passive. All three are trainable.

Do these mistakes apply to both TMUA papers? Yes, but they bite differently. Pacing and arithmetic errors dominate Paper 1; casework discipline, negation misreads and counterexample errors dominate the logic items on Paper 2.

---

Error categories drawn from question-level mock analytics on TMUA Pro and the current computer-based exam format. Last updated 2026-06-10.