A mock test is useful only if something changes after you take it. Yet many candidates check the score, feel pleased or disappointed, and immediately open another paper. The questions they missed then remain missed for the same reasons. A short, consistent review turns an attempt into a diagnosis and a specific plan.
Start by recording more than the percentage. Note the test date, time used, questions attempted, correct answers, incorrect answers and questions left blank. If the test has sections, record those details for each section too. Use the rules in the latest official notification when deciding how to interpret marks or penalties; a practice score is not an official prediction.
Classify the reason, not just the subject
For each incorrect or uncertain answer, choose the main reason. A small set of categories is enough:
- Knowledge gap: you had not learned the fact, rule or concept.
- Recall gap: you studied it but could not retrieve it in time.
- Misread: a condition, qualifier, unit or instruction was overlooked.
- Method error: you chose a valid topic but used the wrong process.
- Execution slip: a calculation, marking or option-selection mistake changed an otherwise sound answer.
- Pacing decision: you spent too long, rushed the end or left a solvable question untouched.
Do not label every error “careless.” That label does not suggest a practice task. “Missed the word except in the question stem” points to a specific reading check you can rehearse.
Keep an error log small enough to use
A notebook or simple spreadsheet can have six columns: test and question, topic, what I chose, correct reasoning, cause of the miss, and next action. The next action should be concrete. “Study polity” is too broad; “compare the two provisions I confused, then answer five fresh questions” is testable.
Write the explanation in your own words after checking a trusted source or the supplied solution. If the explanation itself is unclear, mark it for verification instead of copying an answer you cannot defend. Keep only notes that will help you solve a future question.
Separate review from reattempting
First understand the mistake. Then close the solution and try to explain the correct reasoning from memory. Return to the topic after a short interval and solve a different question on the same idea. Repeating the exact question immediately can test short-term memory rather than understanding.
For a question you guessed correctly, review it too. A lucky option is not evidence that the concept is secure. Record what evidence should have supported the answer and whether your decision to attempt it matched the exam's current rules.
Use the evidence to plan the next week
At the end of a review, look for patterns across the paper. Are the misses concentrated in one topic, one question type or the final minutes? Are you accurate but slow, or fast but frequently wrong? Choose one or two changes, not a dozen.
- Pick the highest-impact topic or recurring error.
- Schedule a focused revision session and a small practice set.
- Choose one pacing behaviour to test in the next mock.
- After that attempt, check whether the specific error reduced.
If the number of attempted questions rises while accuracy falls, slow down and check how you select questions. If accuracy is steady but many are blank, practise timing and recognizing when to move on. If a score changes only slightly, compare the underlying error categories before changing your whole study plan.
Make mock tests sustainable
Leave enough time after a test to review it; do not schedule full papers so frequently that analysis disappears. Short topic sets can be better between full mocks, especially when they target a clearly identified weakness. Protect rest and normal revision too.
For signed-in practice, keep each submission distinct and return to its answer review from your test history. This makes it easier to compare what you marked on different attempts. You can also read our BPSC study-plan guide for a weekly structure, or our current-affairs revision guide for a focused way to manage notes.
The goal is not to produce the longest error log. It is to notice one repeatable pattern, practise a correction and see whether it holds in the next attempt. That is how a score becomes useful feedback.