Dream Vision Classes
Travelling Across Nashik for JEE or NEET Coaching: Making the Commute Work
An hour a day on the road is hundreds of hours over two years. How families from Ozar, Pimpalgaon, Nashik Road and beyond plan around it — and when they should not.
How to Analyse a Mock Test (Most Students Only Read the Score)
The mock is not the practice. The two hours afterwards are the practice. Here is what that session should actually contain.
Students who sit twenty mocks and only look at the scores improve about as much as students who sit five. The paper is a diagnostic instrument, and almost nobody reads the diagnosis.
Sort every mistake into one of three boxes
| Type | What it looks like | What it needs |
|---|---|---|
| Knowledge gap | You could not have solved it with unlimited time | Go back to the concept |
| Speed | You could solve it, but not fast enough | More timed practice on that type |
| Careless | You knew it and got it wrong anyway | Process change, not study |
These need three completely different responses. Students who treat all errors as "revise more" fix only the first kind and stay stuck on the other two — which are usually the majority.
The questions worth asking after every mock
- Which questions did I get right but slowly? Those are tomorrow's careless errors under pressure.
- Which did I skip, and was skipping correct?
- Where in the paper did my accuracy drop? Usually a stamina or panic signal, not a knowledge one.
- Did I attempt in the order I intended?
- What one change would have gained the most marks?
That last question is the whole exercise. One change, applied next week.
Careless errors are a process problem
"Be more careful" does not work as an instruction. What works is a specific rule: underline what the question actually asks; write the unit before the number; re-read the question once after solving. Rules survive pressure. Intentions do not.
Keep a running error log
One page per subject. Date, question type, error box, and the fix. Review it weekly. Within a month the pattern is undeniable, and it is almost never what the student expected.
How many mocks?
Fewer than most students think, each analysed properly. Eight mocks with two hours of analysis each beat twenty-five with none, comfortably.
Frequently asked
Should I analyse a bad mock straight away?
Same day if you can face it, next morning if you cannot. Not a week later — you will have forgotten your reasoning, which is the most useful part of the data.
My scores are not improving despite mocks.
Almost always this. The mock measures; it does not teach. The teaching is in the analysis.
Does this apply to board prelims?
Yes, with presentation added as a fourth box: marks lost to incomplete answers rather than wrong ones.
Why the score is the least useful number on the page
A score tells you where you finished. It does not tell you anything about how you got there, and two students with the same score can need completely opposite corrections — one guessing well on shaky ground, the other losing time on questions they could have answered.
Treated as a verdict, the score is also actively harmful. A bad mock read as "I am not good enough" produces a day of low-grade despair and no corrections. Read as "here are eleven specific things that went wrong", it produces a week of useful work.
The ninety-minute review that is worth more than the test
Do it within two days, while you can still remember what you were thinking during each question.
- Mark every question you got wrong with a reason, not a correction. Careless, ran out of time, wrong method, genuinely did not know.
- Then mark the ones you got right but were unsure of. These are the ones that will not survive a harder paper, and almost nobody reviews them.
- Only now look at the solutions, and only for the questions in the last two categories. The careless ones do not need a solution; they need a process change.
- Write down three things you will do differently next time. Three. A list of twelve is a list you will not use.
When the scores stop moving
A plateau across several mocks almost always means the review is not reaching the real problem. Two common causes:
- Reviewing only the wrong answers. The unsure-but-correct pile is where the next ten marks live.
- Taking mocks faster than you can absorb them. Two a week with a proper review beats four with a glance at the score. If there is no time to review it, there was no point sitting it.
The same method works for board prelims and school tests. The exam changes; the fact that a score is a symptom and the review is the treatment does not.
Every programme we run includes a structured analysis session after each mock — see how the programmes are set up.
