The Mock Test Analysis System
The score on the mock-result page is the output. The input is the error log that produced it, and what you act on is the category of mistake, not the chapter.
A strategy guide laying out the mock test analysis workflow that turns a practice score into a targeted study plan, including the four mistake categories and the 48-hour correction loop.
How this actually works
Score is a lagging indicator
The number on the result page tells you where you were. It does not tell you what to do next, and treating it as if it does is why many candidates feel they are working hard and going nowhere. A student who "lost 20 marks in physics" has learned nothing useful. A student who lost 12 of those to calculation error and 8 to concept has a plan, and the plan is different for the two.
The four-category tag
Sort every wrong answer into one of four buckets. Concept means the formula was unknown or misapplied. Memory means the fact was there and forgotten. Reading means the question was misread, usually a diagram, a negative sign, or a unit in the stem. Calculation means the setup was right and the arithmetic slipped. The distribution across the buckets, not the total score, sets the next four study blocks.
The 48-hour loop
After every mock, review the four buckets, write one rule for each, and run a four-day cycle to retest them. Day one is concept, day two is memory, day three is reading, day four is calculation, and day five is a fresh chapter test scored against the same buckets. The system works because it attacks the pattern rather than the symptom, and because the retest converts a rule into a habit — a rule that is written but never tested is a rule that gets lost in the next chapter.
What to skip
Do not spend mock-review time on the questions you got right. It feels productive and it is not: the questions you got right are already correct, and the review hour is the scarcest resource you have. Mark them with a single tick and move on.
How many mocks before the system works
Three. The first is a baseline and nothing else. The second shows you where the leak is. The third confirms whether the four-day cycle actually held. After the third mock, the bucket distribution should have moved by no more than one category per block — if it has not, the problem is the review quality rather than the practice volume, and more mocks will not help.
The Mock Test Analysis System: the facts to keep
| What the score means | The result page says where you were, not what to do next |
|---|---|
| The four buckets | Concept, memory, reading, calculation - the distribution sets the next four study blocks, not the total score |
| Reading errors | Usually a misread diagram, a missed negative sign, or a unit in the stem |
| The 48-hour loop | Review the buckets, write one rule for each, and run a four-day cycle to retest them |
| What to skip | Do not spend review time on the questions you got right |
| How many mocks | Three: the first is a baseline, the second shows the leak, the third confirms the cycle held |
| The expected shift | After the third mock the bucket distribution should move by no more than one category per block |
Questions students ask about this
How many mocks should I take before the analysis pays off?
Three. The first is a baseline, the second shows the leak, and the third confirms whether the four-day cycle held. After the third, the bucket distribution should shift by no more than one category per block.
What if my score keeps dropping but my accuracy is improving?
That is a speed problem, not an accuracy problem, and the two need opposite treatment. Keep the same accuracy and add time pressure practice — timed section tests — rather than doing more concept work you have already mastered.