How to Analyse a Mock Test: The Two-Hour Routine That Raises Scores

Record four numbers after every mock: total attempts, correct answers, wrong answers and accuracy percentage. Then set the score aside. The score is an outcome, and outcomes are not actionable. What you can act on are the three or four behaviours that produced it.

A useful benchmark for most objective examinations with negative marking is an accuracy of eighty-five per cent or higher. Below that, your problem is not knowledge — it is that you are attempting questions you should have skipped. Raising accuracy by ten points almost always adds more marks than raising attempts by ten questions.

Go through every wrong answer and every unattempted question, and label it. Bucket A is a concept gap: you did not know the method. Bucket B is a speed gap: you knew the method but ran out of time or abandoned it midway. Bucket C is an execution error: you knew it, had time, and still got it wrong.

Each bucket has a different remedy, which is why mixing them is so damaging. Bucket A goes back into your syllabus plan as a topic to relearn. Bucket B goes into calculation and shortcut drills. Bucket C — the one everybody dismisses as carelessness — goes into a written rule. 'I misread the word except' becomes the rule 'circle negative words in every question'. Carelessness is not a personality trait; it is a set of specific, fixable habits.

Most test platforms show time spent per question. Find the questions where you spent more than three times the average and ask a single question about each one: should I have left this? In almost every mock there are three to five questions that consumed six or seven minutes between them and returned nothing. Eliminating those alone is often worth eight to ten marks, because the time returns to questions you could definitely solve.

Develop an explicit skip rule and rehearse it: if you cannot see the path to a solution within twenty seconds, mark it and move on. Return only if time remains. Candidates resist this because abandoning a question feels like defeat, but the paper does not award marks for persistence.

Before reading any solution, try each wrong question once more without a time limit and without help. The questions you now solve were never knowledge problems — they were pressure or speed problems, which tells you the remedy is practice under a clock, not more theory. Only the questions you still cannot solve deserve the solution video or explanation.

This step is the single highest-return part of the routine and the one most often skipped, because reading the solution immediately is comfortable and re-attempting is not.

Write only bucket-B and bucket-C items in your notebook, one line each, with the date. Before your next mock, read the previous two entries. Once a week, count how many repeat errors appear. A falling repeat count is the clearest evidence that your preparation is improving, and it moves before your scores do.

On PadhakuMonk, every free mock test returns a subject-wise and question-wise breakdown with full solutions immediately after submission, so all four numbers and the per-question timing are available without extra work. Use the subject rings to decide next week's study split, and the question review to run the classification above.