The forty-minute mock-test debrief that turns a score into a plan
A mock score tells you almost nothing on its own. The forty minutes after the mock, spent the right way, are where the marks actually come from.
Here is a common and expensive habit. A candidate sits a full mock, marks it, sees 58 per cent, feels either relieved or deflated depending on temperament, writes the number in a notebook, and moves on to the next mock. Two weeks later they sit another, score 60, and conclude they are slowly improving. They have learnt one thing from each two-hour paper: a single number. That is a catastrophic exchange rate.
The score is the least useful thing a mock produces. It is a summary that hides everything you actually need. Two candidates can both score 58 for completely different reasons — one ran out of time with a page unanswered, the other finished early and got things wrong — and those two candidates need opposite advice. The number cannot tell them apart. Only the debrief can.
The one question every wrong answer must answer
The heart of the method is boring and it is the whole thing: for each mark you lost, ask why you lost it, and be honest. Not "what was the right answer" — the mark scheme gives you that. The question is which of a small number of causes was at work, because the cause is what determines the fix. A knowledge gap and a careless slip look identical on the score sheet and require entirely different responses.
Why a wrong answer was wrong
- Didn't know it40%
- Misread the question24%
- Ran out of time22%
- Careless slip14%
An illustrative breakdown of one candidate's lost marks by cause: material they had not learnt, questions they misread, questions left unfinished on time, and careless slips on things they knew.
The moment you draw that picture, the plan writes itself. A candidate losing forty per cent of their marks to genuine knowledge gaps has a revision problem and should go back to the syllabus. A candidate losing that same share to time pressure has a pacing problem and needs no more revision at all — they need to practise finishing. Same score, different disease, different medicine.
| Cause | What it really means | The fix that matches |
|---|---|---|
| Didn't know it | A genuine gap in the syllabus. You could not have got it with more time or more care. | Go back to the material. Learn it, then space it so it survives to exam day. |
| Misread the question | You knew the content but answered a question the paper did not ask. | Slow the reading, not the solving. Underline what is actually being asked before you start. |
| Ran out of time | You could have got it but never reached it, or rushed it under the clock. | Pacing practice. Learn the seconds-per-question budget and drill leaving hard items for later. |
| Careless slip | You knew it, read it right, and still got it wrong through a rushed or automatic error. | A checking habit, not more study. Build a final pass for the errors you keep repeating. |
Notice that only the first row sends you back to revision. The other three are exam-craft problems, invisible to anyone who only records the score, and they are frequently where the fastest marks live. A candidate spending every evening revising content while quietly losing a quarter of their marks to misreading is working hard on the wrong thing, and the debrief is the only tool that would ever tell them.
The forty minutes, spent in order
The debrief has a shape, and the order matters. Do not start by reading model answers; that produces the same warm fluency as rereading a textbook and teaches almost nothing. Start by retrieving.
How to run the debrief
Do this while the paper is still fresh, ideally the same day. A debrief a week late has lost the one thing that makes it work: your memory of what you were thinking.
- 1
Re-attempt every wrong answer cold, first
Before looking at any solution, try each missed question again with no time limit. The ones you now get were never knowledge gaps — they were time or care. That distinction is worth protecting.
- 2
Assign a single cause to each lost mark
Didn't know it, misread it, ran out of time, careless slip. One cause each. Resist the urge to file everything under 'silly mistake', which is a way of avoiding the real category.
- 3
Tally the causes and read the shares
Add them up. The biggest slice is your priority for the next fortnight, full stop. Do not let a dramatic single mistake distract you from the quiet pattern.
- 4
Write one action per cause, not per question
You cannot act on forty individual mistakes. You can act on 'I keep misreading multi-part questions' or 'I never reach the last five'. Turn causes into a short, doable list.
- 5
Add it to the running log
Carry the tallies forward. When the 'didn't know it' slice shrinks and the 'ran out of time' slice grows, your problem has changed and your plan should change with it.
How often, and how much
You do not need a mock every day. You need every mock you do sit to be fully debriefed, because an undebriefed mock has taught you a number and cost you two hours. It is genuinely better to sit half as many mocks and debrief every one than to sit twice as many and debrief none. The debrief, not the mock, is where the learning happens; the mock just generates the raw material.
There is a deeper reason this works, and it is the testing effect. The act of retrieving an answer — including a wrong one you then correct — strengthens memory more than passively restudying the same material. A well-run debrief is not admin around the real work. It is some of the most effective studying you will do all week, disguised as marking.
Frequently asked questions
- How long should a debrief actually take?
- Budget roughly the length of the paper, or a little less. A two-hour mock deserves something in the region of forty to ninety minutes of debrief, depending on how many questions you missed. If you are spending five minutes, you are recording a score, not debriefing.
- What if almost everything is a knowledge gap?
- Then you are sitting mocks too early, before you have covered the material. Step back to learning and spacing the syllabus, and use mocks more sparingly until the knowledge gaps stop dominating the tally.
- Do I need to debrief the questions I got right?
- Usually no, with one exception: a right answer you reached by a lucky guess is a knowledge gap in disguise. If you were not sure, treat it as a miss and debrief it, or it will catch you on the real paper.
- Should I keep the error log on paper or an app?
- Whichever you will actually maintain. The value is in the tallies accumulating across mocks so patterns surface, not in the tool. A single sheet with four columns and a row per mock is enough.
The mock is the cheap part. Anyone can sit a paper and mark it. The candidates who improve fastest are the ones who treat the score as a question rather than an answer, and spend the forty minutes it takes to find out what the number was actually made of.
Free tool
Study plan generator
Check whether your plan fits the weeks you have.
Try it- Reading time
- 7 min
- Length
- 1,460 words
- Topic
- Method