There is a student who takes 40 mocks before CAT and scores 85 percentile on the actual exam. There is another student who takes 18 mocks and scores 99 percentile. The difference is not the number of mocks. The difference is what they did after each one.
A mock that is not analysed is not a mock. It is three hours of practice that produced no learning.
What a mock is actually for
A mock tests three things simultaneously. It tests your knowledge. It tests your decision making under time pressure. And it tests your pattern of errors. The score tells you nothing you cannot already guess. The error analysis tells you everything.
After every mock, you should be able to answer these questions precisely. Which questions did you get wrong that you should have gotten right? Which questions did you attempt that you should have left? How much time did you spend per set in DILR and was that allocation correct? In VARC, which question type had the worst accuracy?
If you cannot answer these questions after a mock, you did not analyse it. You glanced at it.
The three categories of wrong answers
Every wrong answer in a mock falls into one of three categories. Conceptual errors mean you did not know the underlying concept. These get fixed through study. Careless errors mean you knew the concept but made a calculation or reading mistake. These get fixed through slowing down slightly and checking work. Application errors mean you knew the concept and read carefully but applied the wrong approach. These get fixed through targeted practice of that specific question type.
Most students treat all wrong answers the same. They look at the solution, understand it, and move on. This is why they keep making the same mistakes across 30 mocks. The error category matters because the fix is different for each one.
How to analyse a mock properly
Spend at least 3 hours on mock analysis for every CAT mock you take. This is not optional. For every question you got wrong, identify the category. For every question you left blank, decide whether you should have attempted it. For every section, calculate your time per question and identify where you spent time that produced no correct answer.
Keep a running error log. Every conceptual error gets noted with the topic and the specific mistake. Every careless error gets noted with the type of mistake. Review this log before every subsequent mock. Your preparation between mocks should be driven by this log, not by a generic schedule.
How many mocks to take and when
Start full-length mocks only after you have completed at least 70% of the syllabus. Taking mocks before you have covered the content is counterproductive. You will get poor scores for knowledge reasons, which tells you nothing useful about your strategy or decision-making.
From August onwards, take one mock per week. In September and October, take two per week. In the final two weeks before CAT, take one every three days. Space them out enough that you have time to analyse each one properly before taking the next.
Do not take mocks on consecutive days at any point in your preparation. Analysis requires time and requires sleep.
What to do on the day before CAT
Take no mock on the day before CAT. Review your error log from the last three mocks. Revise your key formulas and shortcuts for QA. Sleep at least 8 hours. The students who perform below their ability on CAT day are usually the ones who attempted a mock on the day before and were mentally drained.
Post-mock analysis with ALP Sir
CATalysis includes structured post-mock analysis sessions after every mock. Not just a score report. A strategy session.
See CATalysis 2026 →