A mock test produces two things: a score and a set of decisions. Most students look at the score, feel something, and move on to the next paper. The decisions are where the improvement lives.

Set aside 45 minutes after every timed paper. Not to re-read the whole paper — to find out why specific marks were lost and what you will do differently.

Review within 24 hours

Review while the attempt is still fresh. If you wait a week, you will remember the answers you changed, but not the reason you hesitated. The hesitation is the data.

Use the result page to locate the wrong and skipped questions, then work through them in this order:

  1. Questions you answered wrong.
  2. Questions you skipped but could have attempted.
  3. Questions you got right by guessing.

The third group matters because a lucky guess hides a gap. Mark it now, or it will reappear in a harder form later.

Sort every error into one bucket

Give each lost mark exactly one cause:

  • Concept gap — you did not know the idea or the method.
  • Process slip — you knew it but misread, mis-signed, rushed or changed a correct answer.
  • Time pressure — you could have solved it with more time.
  • Presentation or interface — you mis-clicked, missed a palette state, or did not see an instruction.

If an error fits two buckets, choose the one that would have prevented the loss. A misread formula is a process slip even if the concept is also shaky; fix the reading habit first because it is cheaper.

Re-solve without looking

Reading a solution feels like learning. Re-solving proves it. For each wrong question:

  1. Cover the solution and the correct option.
  2. Solve it again on paper.
  3. Say the reason for each step out loud.
  4. Only then check the answer.

If you cannot reproduce the solution, the error is a concept gap, not a careless mistake. That distinction changes what you study next.

Find the pattern, not just the question

One wrong question is an event. Three wrong questions from the same unit are a pattern. Count errors by unit and by cause.

A useful summary after each paper is four lines:

  • Unit that lost the most marks:
  • Most common cause:
  • The two questions I should have skipped:
  • The one habit I will change in the next paper:

If the same unit tops the list twice in a row, stop taking full papers until you have drilled it. More papers will only repeat the diagnosis.

Write two changes, not ten

A review that ends with a ten-point improvement plan usually ends with zero changes. Pick two behaviours for the next attempt. Examples:

  • "I will read the last line of every question before looking at the options."
  • "I will skip any calculation that needs more than two steps on the first pass."
  • "I will check the palette before the final five minutes."

Two specific changes are testable. Ten vague intentions are not.

Track the review, not just the score

After four or five papers, compare the review summaries. Are the same causes appearing? Is the "time pressure" bucket shrinking? Is accuracy improving while attempts stay stable?

The error log guide gives the one-page template for this. The paper library has the timed attempts, and the leaderboard shows where a first attempt stands. Neither number replaces the review.

A mock test is a diagnostic tool. The review is the treatment.