Review method
How to Maintain a Mock-Test Mistake Log
Create a short mistake log that turns wrong answers into repeated revision actions instead of dead notes.
Audience: All mock-test users. This guide is public preparation material written to help students review mock-test results and choose a focused next study action.
What belongs in a mistake log?
A mistake log should record the topic, cause and correction. It should not become a storage place for entire questions. A useful entry looks like: percentage comparison, wrong base chosen, write original value before applying percentage change. The correction matters more than the question text.
How often should it be reviewed?
Review the log before each new mock. If the same correction appears again, the student has not repaired the habit. Weekly review should remove fixed issues and highlight repeated ones. A mistake log that only grows larger becomes discouraging.
How does a report help?
A report provides the raw material for the log: wrong questions, skipped questions, topics and timing. The student's job is to convert that material into two or three actions. Without action, a detailed report becomes another scorecard.
Next step: open the sample question explanations to see how a correct answer should be reviewed, or return to the study guide library.