The error notebook that makes your next mock useful

Review before taking another test

A mock is a measurement and a practice session. Its value shrinks when you only check the score and immediately attempt another. Set aside review time while your decisions are still memorable. Include questions you answered correctly by guessing; they may hide the same gap as a wrong answer.

Write a short diagnosis in your own words. Useful entries say “I confused an increase in percentage points with a percentage increase” or “I ignored the word except.” “Silly mistake” names no mechanism and gives you nothing to change.

Give each error one correction

For a concept gap, write the key relationship and solve one fresh example without the explanation. For a process error, make a checklist or alter the order of steps. For a reading error, underline the constraint and rewrite the requested quantity before solving.

Keep entries short: question reference, cause, corrected method and retest date. Copying pages of worked solutions can feel productive while leaving the decision unchanged. Add only enough explanation to reconstruct the reasoning later.

Retest with a different example

Revisit the skill after a gap, using a fresh question with changed numbers or context. A remembered answer is weak evidence that you learned the method. If the same error returns, narrow your diagnosis. You may know the formula but struggle to identify when it applies.

Archive an error only when you can explain the fix and apply it independently. Periodically look for repeated patterns across subjects: rushing, unit conversion and unsupported guessing often travel together. Choose one pattern to address in the next timed set.

Compare yourself fairly

Scores from different mock providers are not directly comparable unless difficulty and marking match. Track your own accuracy, time, unanswered count and recurring error types. Use improvement to decide what to study next; avoid treating one bad paper as a final verdict on your preparation.