How to Review an ESAT Mock Without Wasting It
Most students finish a mock, check their score, look at the questions they got wrong, and move on. Then they sit another mock and wonder why they're not improving.
The problem isn't the mock. It's the review.
Done well, one review session is worth more than three additional papers. Here's how to actually get something out of it.
Understand What You're Reviewing For
The ESAT is not a knowledge exam. Almost every student sitting it knows enough to get every question right in principle. What they can't do is get it right in time.
The exam punishes hesitation. That thirty seconds where you know two approaches and can't commit — that's where marks are lost, not in ignorance, but in slowness.
So you're not asking "did I know this?" You're asking "why did I slow down?"
Step 1: Categorise Before You Look at Solutions
Go through the paper and mark every question as one of four things:
✅ Got it, felt fast
🟡 Got it, felt slow
🟠 Wrong — knew the method, made an error
🔴 Wrong — had no route in
Do this from memory before opening a single solution. It separates outcome from process. A question you got right in two minutes is a red flag. A sign error is a different problem from being completely stuck. Treating them the same means fixing the wrong things.
Step 2: Start With the Yellows
Counterintuitive, but the 🟡 questions — right answer, slow execution — are where the biggest gains hide.
If you're slow on questions you can do, that's hesitation. Hesitation is a pattern recognition problem. You're solving from scratch each time instead of recognising the shape of the question.
For each one, ask: what was the first thing I tried? When did I commit? What would I do differently in the first ten seconds?
You already got it right. The goal is to shorten the path from reading the question to starting confidently.
Step 3: Work Through the Reds Properly
Reading a solution and thinking "ah, I get it now" is almost useless. It tells you the answer, not how to find it without having seen it before.
After reading the solution, close it. Wait five minutes. Then attempt the question again from scratch. If you can reconstruct the reasoning independently, you've actually learned something. If you can't, you need more time with the underlying concept.
Also: good solutions explain why the wrong path was tempting, not just what the right one is. Pay attention to that. It's what stops you falling into the same trap twice.
Step 4: Track Patterns, Not Individual Questions
After working through the paper, zoom out. Are your 🔴 questions clustered in one module? Are you consistently slow on a particular question type? Are you getting caught by cross-topic questions, or ones with unfamiliar physical setups?
Individual mistakes are noise. Patterns across questions and mocks are signal. The review isn't finished when you understand each question — it's finished when you've identified where your hesitation lives.
Step 5: Return Before the Next Mock
A few days after your review, spend twenty minutes going back to the questions you struggled with. No solutions — just read each one and recall: what's the right approach? What was the trap?
If it's clear, you've retained it. If it's fuzzy, it wasn't as embedded as you thought. This is what makes mocks compound. Not doing more of them, but extracting everything from the ones you've done.
A Note on Difficulty Tiers
If you're working across tiered difficulty, your review focus should shift by tier.
Foundation: Mostly speed and fluency. If something went wrong, was it a knowledge gap or a careless error? Don't spend long here.
Exam-Level: Pattern recognition matters most. Focus on the 🟡 category — where you were slow and why.
Beyond the Exam: These questions are deliberately harder than the real exam, built to expose exactly the kinds of hesitation that cost you on the day: ambiguous phrasing, unfamiliar setups, cross-topic structure, deliberate traps. Getting one wrong and understanding the trap thoroughly is more valuable than getting an easier question right without thinking about it.
The Summary
Categorise before looking at solutions — fast/right, slow/right, wrong/had-a-method, wrong/no-route
Start with the slow-right questions — hesitation is the enemy
Reconstruct, don't just read — redo the question independently after reading the solution
Understand the trap — why were you confident the wrong path was right?
Find patterns — modules, question types, structural features that slow you down
Return before the next mock — brief recall makes the review stick
The students who improve fastest aren't the ones who do the most mocks. They're the ones who actually read what each mock is telling them.
