How to analyse a mock test properly instead of just checking your score

It's tempting to finish a mock, look at the score or percentile, feel good or bad about it for a few minutes, and move on to the next one. But a score is a single summary number that hides the actual information a mock test contains: which specific concepts you don't understand, which question types you consistently misjudge, and where your timing breaks down. Taking ten mocks without analysing any of them properly teaches you almost nothing beyond stamina.

Go through each question you got wrong or skipped and assign it to one of four categories, because each one needs a completely different fix. A concept gap means you didn't know the underlying fact or method — the fix is to study that topic again. A silly mistake means you knew the concept but made an error in reading, calculation or marking — the fix is a slower, more careful pass on similar questions, not re-studying the topic. A timing problem means you knew the answer but ran out of time to attempt or verify it — the fix is speed practice specifically on that question type. A guessing error means you attempted without real knowledge and got it wrong — the fix is to recognise when to leave a question rather than attempt it in the actual exam.

A single mock's mistakes might just be bad luck on a hard day. The signal appears when you log this categorisation across four or five mocks and look for repetition — if 'time-value-of-money' problems or 'reading comprehension inference' questions show up as concept gaps in three consecutive mocks, that's no longer noise, it's a genuine syllabus weakness that deserves dedicated study time before your next attempt.

Keep this log in one place, even a simple spreadsheet: mock number, question topic, category of mistake, and a one-line note on what specifically went wrong. Over time this log becomes far more valuable than the scores themselves, because it tells you exactly what to study next instead of leaving you to guess.

Occasionally review a correct answer where you weren't fully confident while attempting it. Getting the right answer through partial guessing or elimination, rather than genuine knowledge, is a hidden risk — it inflates your score without reflecting real understanding, and a slightly different version of that question in the real exam may not go your way.

After analysis, resist the urge to try to fix everything at once. Pick the one or two categories or topics that appeared most often, study or drill specifically on those, and check in your next mock whether that specific weakness improved. This turns your mock series into a genuine improvement loop rather than a repeated measurement of the same static ability.