After every mock, you do everything right.
You go through the questions you got wrong. Check the solutions. Mark the topics — electrochemistry, rotational motion, p-block. Tell yourself you'll revise them before the next mock.
And then the next mock comes. The same kinds of errors are there.
Not identical questions. But the same kind of wrong.
Most students assume mock review isn't working because they're not being thorough enough — they need to spend more time on the solution, go deeper into the chapter, solve more problems from that topic before the next test.
So they do. And the errors persist.
Here's what's actually going wrong.
Mock review, done the usual way, tells you two things: what you got wrong, and what the right answer is. Both are useful. Neither tells you the thing that actually matters — which specific decision step, inside your reasoning, produced the error.
A student gets a question on current electricity wrong. They look at the solution. They understand it — the approach is clear, the calculation makes sense.
The solution feels familiar. It makes sense immediately. It feels like something they could have done — so it doesn't feel like a real mistake.
They note "current electricity — weak." They move on.
What they never isolate is the moment their reasoning diverged. Was it the setup — how they assigned the current directions? An assumption about the circuit the problem didn't justify? A calculation step, or a conceptual one?
Without knowing which step broke, review tells you where you ended up —
not where your reasoning diverged.
The next current electricity question will bring the same decision point. And without having trained that specific step, the error has every reason to repeat.
This is where most mock analysis stops. The score tells you which questions. The solution tells you the right path.
But neither shows you the fork in your reasoning — the exact moment your thinking diverged from what the problem was testing.
Reviewing without isolating that step is like re-reading a map after getting lost, without identifying where you first took the wrong turn. You see where you ended up. You don't see the decision that took you there.
Mock tests aren't the problem. They show you where you finished —
they don't show you where your thinking broke.
The limitation is in what review surfaces on its own. Scores and solutions are the end of the story. The decision step that caused the error is the beginning — and it stays invisible unless something is specifically designed to find it.
That's the part of preparation most students never get access to.