Guide
How to analyse a mock test (the 30 minutes that matter)
By the MyAbhyasa team ·
Most students take a mock, read the score, feel something, and move on. The score is the least useful number a mock produces — the attempt log is a per-topic diagnostic, if you spend thirty minutes reading it properly.
Why is the total score the wrong thing to focus on?
A single mock score mixes paper difficulty, topic luck, and your actual preparation into one number, so score swings between mocks mostly measure the paper, not you.
What is stable across mocks is the pattern of errors — which topics leak marks and why. That pattern is what analysis extracts.
How should errors be classified?
Sort every lost mark into one of four bins: concept gaps (did not know it), application errors (knew it, could not use it under this question's framing), silly mistakes (calculation slips, misread questions), and time casualties (never reached or rushed it).
Each bin has a different cure — concept gaps need study, application errors need mixed practice, silly mistakes need a checking ritual, and time casualties need attempt-order strategy. Treating them all as 'revise more' wastes the diagnosis.
What does a good post-mock routine look like?
Same day, ~30 minutes: classify every error into the four bins, then write down the three topics that cost the most marks and the single biggest non-topic issue (timing, checking, panic on a section).
Feed the three topics into your revision queue at high priority, and set one process experiment for the next mock — a different attempt order, a flagging rule for review, a hard time cap per section. One experiment at a time, or you cannot tell what worked.
How many mocks are enough?
Fewer, analysed properly, beat many taken raw. A mock without analysis costs three hours and teaches almost nothing; a mock with analysis costs three and a half and redirects a week of study.
Frequency should rise as the exam approaches — but only as fast as your ability to actually act on each mock's findings between attempts.