Mock tests aren't just practice — they're data. A mock without structured analysis afterward is a wasted three hours.
Every mock test should generate actionable insight, not just a score to feel good or bad about.
| Step | Action | Frequency |
|---|---|---|
| Take under real conditions | Full 3-hour test, no breaks, phone off, at the same time of day as your actual exam | Weekly, from 6 months before exam |
| Score analysis | Calculate raw score; identify which chapters generated the most errors | Same day, after the mock |
| Error categorisation | Log each wrong answer as: silly mistake / conceptual gap / time pressure / not studied | After every mock |
| Error book update | Add conceptual errors to a dedicated Error Book with the correct solution | Within 24 hours |
| Revision trigger | Any chapter with >2 errors in a mock gets immediate re-revision | Before the next mock |
| Progress tracking | Plot your score trend over time — look for the upward trend, not single-mock fluctuations | Monthly |
Weekly full-length mocks under real exam conditions, starting at least six months out — roughly 20–30 mocks minimum. Frequency matters less than what you do with each one afterward: without error analysis, a mock is just practice, not a diagnostic.
Categorise every wrong answer — silly mistake, conceptual gap, time pressure, or simply not studied — and log conceptual errors into a dedicated error book with the correct solution, within 24 hours. Any chapter with more than 2 errors in a single mock should get immediate re-revision before your next mock.
A structured mock series beats scattered self-testing.