How to analyse a mock test: the review that raises your score, not the test itself

The most common mistake in the final months of preparation is taking mock test after mock test and watching the score refuse to move. The tests are not the problem; the missing analysis is. A mock is a measurement, and a measurement you do not act on changes nothing. What follows is how to turn each test into a week of precise practice.

The test measures; the analysis improves

Budget your time the other way round from most candidates. The test is the cheap part. Block out at least as long again for the review immediately afterwards — not “later that week”, when the memory of why you chose each answer has gone. If you only have time for one, do a mock every three days and analyse each fully, rather than one a day analysed never.

Sort every mistake into one of three causes

Go through every wrong answer and label it with exactly one cause:

1. I did not know the concept. A genuine knowledge gap. This feeds your study list.
2. I knew it but made an error. A calculation slip, a misread, a wrong assumption. This feeds your calculation drill and your habit of re-reading the question.
3. I should never have attempted it. The question was too long or too uncertain for the marks, and attempting it cost time and possibly a negative mark. This feeds your attempt strategy.

Then count the three piles. The largest one tells you what actually lost you marks — and for most candidates near their target score, it is the third, not the first. You do not need to know more; you need to choose better.

Find the marks you left on the table

Now look at the questions you skipped. For each, ask whether it was genuinely hard or simply came later in the paper than your patience did. Easy questions abandoned because you ran out of time in an earlier section are pure lost marks, and they usually point at a sequencing problem: you spent too long somewhere before reaching them.

Weigh time against marks, section by section

For each section, note the time spent and the marks gained. A section that took fifteen minutes for four net marks is telling you something a raw score never will. This is how you discover that, say, a single hard puzzle set ate the time that ten easy questions elsewhere needed. Adjust the order you attempt sections and question types accordingly — that reordering is often worth more than any amount of new studying.

Write it into the error log

Every mistake worth learning from goes into a single running error log, with the question type, why you got it wrong in your own words, and the correction. This is the same log described in how to build a study plan, and the mock analysis is its main feeder. Reread it weekly; within a month the same three or four habits will account for most of your losses, and those are fixable in a way that “get better” is not.

Turn the analysis into next week’s plan

Close each review by writing the three things you will do differently: one concept to study (from pile one), one error habit to drill (from pile two), and one attempt rule to follow next time (from pile three). That is the entire output of the analysis — three concrete actions, not a vague resolve to improve — and it is what makes the next mock better than the last.

The mindset

Stop reacting to the score and start reading the decisions behind it. Two candidates can score the same 45 with completely different problems, and only the analysis reveals which is yours. Pair this habit with a clear negative-marking strategy so your attempt decisions have a rule behind them, and take your next full-length mock test knowing exactly what you are trying to change.