How to Review a TMUA Paper Properly

Finishing a TMUA paper gives you a score. What you do afterwards determines how much you learn from it.

It is tempting to mark the answers, read a few solutions and move on. But recognising someone else’s reasoning is not necessarily the same as being able to use the idea yourself.

This guide reflects how I review work with my own students. It applies wherever you find your practice papers, with a section towards the end explaining how JZMaths supports the process.

1. Look beyond the wrong answers

There are several kinds of question worth reviewing:

• Questions you answered incorrectly or left unanswered.
• Questions you got right through guessing or uncertain reasoning.
• Questions you solved correctly but took too long over.
• Questions whose solutions contain an idea or method you could learn from.

A correct answer is useful information, but it does not tell us everything about your understanding.

An educated guess may have been a sensible decision under time pressure. Nevertheless, if you narrowed the options down to two and happened to choose correctly, investigate what prevented you from deciding between them.

Equally, a question that took ten minutes may deserve as much attention as one you got wrong. Under exam conditions, that time has a cost elsewhere in the paper.

You do not need to turn every correct answer into a lengthy investigation. If your reasoning is secure and your approach is effective, a brief review may be enough.

2. First, reflect on what happened

Before reading the solution, look at your original working and ask where the difficulty began.

Was there something you did not know? Did you misunderstand the wording? Did you have a promising idea but make an algebraic error? Or did you spend too long on an approach that was going nowhere?

Distinguish what you know from what you suspect. “I think I misunderstood the condition” is a useful starting point; you can investigate it during the correction.

Try to be more precise than “careless mistake”. For example:

• I forgot to check whether the value was in the permitted domain.
• I reversed the implication.
• I divided by an expression without considering whether it could be zero.
• I kept expanding when a factorised form would have been more useful.

The purpose is to identify something you can change, rather than simply give the mistake a name.

3. Try again without the clock

Where practical, reattempt the question before opening the worked solution.

Removing time pressure helps you distinguish a gap in understanding from a difficulty applying your knowledge quickly. If you can now solve it, ask what was different: did you notice a condition you missed, find another approach, or simply need more time?

If you are stuck, do some actual exploring. Draw a diagram, try a simpler case, rewrite the expression or ask what would be sufficient to reach the conclusion.

You do not need to remain stuck indefinitely. A small hint may be enough to get you moving. If you need the full solution, use it—but study the reasoning actively.

If marking has already revealed the correct option, remember that it may now guide your thinking. Solving the question at this stage is valuable learning, but not an independent test of your original ability.

4. Read the solution for more than the answer

This is particularly important for solutions I have written.

I spend a considerable amount of time writing them because I want them to have learning value beyond completing one question. There are often several possible approaches; I try to present an efficient method and explain ideas that may help you elsewhere.

Where I discuss alternative approaches, it is generally because I think there is something useful to learn from comparing them.

As you read, ask:

• What is the central idea?
• What feature of the question might have suggested this approach?
• Why is each important step valid?
• Is this more efficient than my method, and if so, why?
• Where else might the idea apply?

You do not need to abandon your own method merely because it differs from the written one. A different approach can be equally sound and efficient. Compare them thoughtfully rather than assume that matching the solution is the goal.

Sometimes there will be little more for you to learn from a particular solution. That is completely fine. Just give yourself the opportunity to find out.

5. Investigate correct but slow answers

“Right, but very slow” is a useful diagnosis, not a completed correction.

Look at where the time went. Did you struggle to choose a starting point? Carry out more algebra than necessary? Miss a useful graph or symmetry? Repeatedly check because you were unsure your argument was valid?

The remedy depends on the cause. Slow manipulation may call for fluency practice. A long, inefficient route may call for comparing methods. Difficulty recognising the idea may call for focused work on that skill.

On JZMaths, you can compare your recorded question time with the median time taken by students who answered correctly on their first attempt. This gives you a reference point for what other successful attempts looked like.

Use it as a prompt to investigate, not an instruction to beat the median every time. Students differ in experience, and interruptions or untimed learning can affect recorded times. But if you took twice as long under comparable conditions, it is worth asking why.

The aim is to become more efficient through understanding and fluency, rather than simply hurry.

6. Check that the understanding is yours

Here is a useful question to ask yourself:

Can I explain what this question is testing, why the method works, and what might help me recognise the idea in a different problem?

If the answer is “maybe” or “I’m not sure”, there is probably something worth revisiting.

Close the solution and reconstruct the reasoning. Explain the decisive step in your own words. Where appropriate, consider what would change if a condition or value were different.

This need not become an elaborate exercise for every question. Focus your attention on the ideas that were new, uncertain or difficult.

Feeling that a solution makes sense is a good beginning. Being able to explain it without looking provides stronger evidence. Using the idea later in an unfamiliar question is a further check.

7. Turn the correction into a useful next step

A correction should leave you with something more specific than a copied solution.

For example:

After several papers, look for recurring difficulties. If the same skill keeps causing problems, pause the paper routine and study it in more depth.

A short correction record can help: the problem, the idea you missed, and what you will do next. It does not need to become a second essay-writing qualification.

8. How JZMaths supports the review

The JZMaths attempt-review process lets you go through your questions and optionally tell us what you think went wrong. Prompts can help you recognise a difficulty you could not initially describe, and the process provides pointers.

This is the stage of identifying what needs attention. You still need to work through the corrections to resolve it.

Your reflections give the system information beyond whether an answer was right or wrong. That helps it interpret your progress and refine suggestions. If you are unsure, do not force a confident explanation.

The review process is an addition developed after the October 2026 cohort; it was not available during their preparation.

TMUA Skills grew out of the same need to address difficulties more precisely. These skills are smaller than broad topics but still substantial: similar triangles, ambiguous SSA triangles, or using even and odd functions, for example.

Focused teaching and practice let you work on such ideas together, rather than wait for them to appear occasionally across papers. You can then return to mixed questions to practise recognising the ideas without a skill heading telling you what to use.

For how this fits into the wider guidance cycle, see How to Prepare Efficiently for the TMUA with JZMaths PLUS.

9. Revisit and check progress

Return to selected questions after a gap. Aim to rebuild the solution from understanding rather than remember the sequence of steps.

A successful reattempt is useful, but it is not the same as succeeding on an unseen question. Look for opportunities to apply the idea in fresh material too.

At the end of each week, ask what your corrections have changed. Are recurring mistakes becoming less frequent? Are you recognising useful approaches sooner? Can you explain something that confused you last week?

If not, you may need a different explanation, simpler examples, more focused practice, or help identifying the actual difficulty.

For workload planning and balancing learning with timed papers, see How to Prepare for the TMUA.

The aim is not to produce a beautiful collection of corrected answers. It is to change what you can understand and do the next time you meet a problem.