Minutes 0–5: read the numbers, not just the score
Look at four figures: attempts, accuracy, time used per section, and marks lost to negative marking. A low score with 95% accuracy is a speed problem; a high attempt count with 60% accuracy is a judgement problem. They need different fixes.
Minutes 5–20: sort every miss into one of four buckets
- Didn't know it — a content gap. Goes on your study list.
- Knew it, got it wrong — a careless or misread error. Note the pattern (units, "NOT", sign errors).
- Knew it, ran out of time — a pacing problem, not a knowledge one.
- Guessed right — count these as misses too. You don't actually know them yet.
Minutes 20–25: find your two biggest leaks
Group the misses by topic. Usually two or three topics account for most of the lost marks. Fixing those is worth more than revising everything a little.
Minutes 25–30: plan the next week
- Schedule focused practice on the top two weak topics.
- Add every wrong question to a review list to retry in a few days, without looking at the solution first.
- Set one specific target for the next mock, e.g. "under 90 seconds per physics question".
Keep an error log
A simple log — question, topic, bucket, what you'll do differently — turns isolated mocks into a trend. After three or four mocks you'll see which mistakes repeat. Wrexa Edge builds this automatically: every mock records topic, time and the option you chose, and flags topics under 70% accuracy.