A score is the least useful thing a mock gives you
The number at the end of a mock tells you where you stand, but not why. The value is in the breakdown underneath it: which sections leaked marks, which topics you got wrong, how long you spent per question, and whether your errors were knowledge gaps or careless mistakes.
Treat every mock as a diagnostic. The goal of test number three is to make test number four better.
The loop that works
Four steps, repeated:
- Take it like the real thing — full length, real timing, real marking, no pauses.
- Analyse every mistake — sort wrong answers into 'didn't know' and 'knew but slipped'. The second pile is the fastest to fix.
- Target the gaps — use topic-wise tests to rebuild the specific weak areas the mock exposed.
- Repeat — take another full-length mock to confirm the fix held under pressure.
Careless errors are the cheapest marks you own
Most aspirants underestimate how many marks they lose to misreading a question, mis-clicking an option, or rushing the last section. These are not knowledge problems, so they are the quickest to fix — often just by slowing down on the final option and reading the full question. Track them across mocks and watch them fall.
Rank, not raw score, is the target
For most competitive exams, your rank relative to other candidates decides the outcome, and scores bunch near the top. That means a few extra marks can move you by a large number of ranks. Set a target score that maps to the rank you want, and measure every mock against that target rather than against your last attempt.
Key takeaways
- Improvement comes from analysis after the mock, not the mock itself.
- Sort errors into knowledge gaps vs careless slips; fix the slips first.
- Use topic tests to rebuild the specific weaknesses each mock exposes.
- Target a rank, not a raw score.