Key takeaways
- Spend as long analysing a mock as you spent writing it.
- Sort every question into one of four buckets; each bucket has a different fix.
- Silly mistakes are a pattern, not bad luck: log them.
- End every analysis with three actions for the next mock.
The four buckets
| Bucket | What it means | The fix |
|---|---|---|
| Right, and confident | You know it | Nothing; move on |
| Right, but guessed | Lucky | Revise the concept as if you got it wrong |
| Wrong, but knew it | Silly mistake | Log the type: misread, calculation, rushed |
| Wrong or skipped, didn't know | Gap | Study the concept, then do 10 practice questions |
Look at time, not just marks
Compare time spent per section with the marks you earned there. A section that took 40% of the time for 20% of the marks is costing you. Also look for questions where you spent several minutes and still got them wrong: those are the ones to skip next time.
Use the class data
If most of the class got a question right and you didn't, that's an easy mark you gave away. If most got it wrong, don't panic: it was hard for everyone. The option-wise percentages in your report tell you which.
Turn it into three actions
- One concept to study before the next mock.
- One silly-mistake habit to fix (for example: underline what the question asks).
- One time rule (for example: skip any question after two minutes on the first pass).
Where Examezy fits
Examezy reports give students the raw material for this method: question-wise review with explanations, time per section, what percentage of the class chose each option, and an AI report with strengths, misconceptions and a learning path.