How to Analyse a Mock Test and Decide What to Practise Next
Use a worked accuracy example to separate knowledge gaps, execution errors and poor question choices, then set measurable decisions for your next mock.
Practice Mocks · Study skills · 3 min read
Published · All posts
Start with attempts, not just the score
A mock score tells you the outcome, but not the cause. Before reading solutions, record the questions attempted, answered correctly, answered incorrectly and left unanswered. Note where you spent time without reaching an answer. If the test has penalties or sectional rules, interpret the score using that test's stated scheme.
Attempt-based accuracy is correct answers divided by attempted questions, multiplied by 100. It doesn't measure syllabus coverage or explain whether you avoided difficult material. Use it alongside the unanswered questions and your time record, not as a complete judgement of readiness.
Work through an accuracy example
Consider a hypothetical mock containing 60 questions. An aspirant attempts 40, gets 30 correct and 10 wrong, and leaves 20 unanswered. Attempt-based accuracy is 30 ÷ 40 × 100, or 75%. This is an illustrative practice example, not the format of any particular recruitment examination.
Now suppose six wrong answers came from uncertain attempts and four from misreading or calculation slips. Reducing uncertain attempts may protect the score where incorrect answers attract a penalty, but it won't repair the four execution errors. Likewise, simply attempting more could increase mistakes. The same accuracy figure can therefore lead to several different practice decisions.
Retry before looking at the explanation
Reattempt wrong and unanswered questions without seeing the solution. Mark whether you can solve each independently, need a hint or still don't know how to begin. This separates material you understand but couldn't execute during the test from material you haven't learnt sufficiently.
Give each problem a primary cause: concept gap, faulty method, execution slip, misreading or poor selection. Be specific. 'Careless' is too broad to act on; 'copied the denominator incorrectly' suggests a checking habit. If more than one cause applies, record the first error that led the solution off track.
Inspect unanswered questions and expensive successes
An unanswered question isn't automatically a weakness. You may have sensibly skipped unfamiliar material. But if you solve it quickly during review, ask why it wasn't recognised as accessible during the test. That may indicate a scanning or selection problem rather than a knowledge gap.
Also inspect correct answers that consumed disproportionate time. Compare your method with a clearer alternative only after understanding your own steps. The aim isn't to memorise every shortcut. It's to identify unnecessary work and recognise when moving on would have preserved time for other questions.
Set two decisions for the next test
Convert the review into a small repair plan. In the example, the aspirant might practise checking copied values and adopt a rule against attempting questions with no defensible method. Separately, one recurring concept gap could receive a lesson followed by fresh questions.
For the next mock, track just two behavioural measures, such as repeated copying errors and time spent on unresolved attempts. Compare similar practice conditions where possible. A higher score is welcome, but evidence that the diagnosed problem has reduced tells you whether the intervention worked.