ARETE

Why you keep making the same mistakes in mocks, and how to stop

You check the solution, you understand it, and two mocks later the same kind of question goes wrong again. It is one of the most common ways marks leak, and it is fixable once you can see it.

Why mistakes repeat

  • You fixed the answer, not the cause. Understanding one solution does not change the habit or the gap that produced the mistake.
  • There is no record. Without one, every mock feels new, and a mistake from three weeks ago is forgotten by the time it happens again.
  • The label is too vague. "Silly mistake" or "revise Physics" gives you nothing to do differently.
  • Nothing checks the fix. If you never look for the mistake in the next mock, you cannot tell whether your fix worked.

Keep a mistake log that is quick to fill

After each mock, write one line per wrong or skipped question: the chapter, the topic, and one cause.

  • Concept: you did not understand the idea the question tested.
  • Formula: you knew the idea but could not recall the formula, fact or rule at the moment you needed it.
  • Silly: you knew it and could do it, but slipped (a sign, a unit, a misread word, a copied number).
  • Time: you could have solved it, but ran out of time or rushed it.

That is enough. A log you actually fill after every mock beats a detailed one you give up on.

Use the rule of two

When the same chapter goes wrong for the same cause in two mocks, treat it as a pattern, not bad luck. Patterns go to the top of your week, ahead of new chapters, because each one is costing you marks in every mock until it is fixed.

Give each pattern a fix you can finish this week

  • Concept: relearn the topic, then solve previous-year questions on only that topic.
  • Formula or recall: one page of formulas or facts for the chapter, recalled from memory daily.
  • Silly: one checking step at the exact point the slip happens.
  • Time: a section order and a time limit per question, practised before the next mock.

Check it in the next mock

Before the next mock, read your open patterns once. After it, check whether any came back. A pattern that stays away for a few mocks is fixed; one that returns needs a different action, not just more of the same one.