How to analyse a CAT mock: what most students get wrong

The single most underutilized hour of any CAT student’s prep week is the hour immediately after the mock. Most aspirants check their percentile, scan the score breakdown, feel either relief or panic, and move on. They have just wasted the most valuable feedback signal in their prep cycle.

Mock analysis done correctly takes longer than the mock itself. A 2-hour mock deserves 4 hours of analysis. That ratio sounds extreme. It is the right ratio. Without it, you are paying for diagnostic data and throwing the diagnosis away.

Why the standard approach fails

Walk through what most students do after a mock. They open the answer key. They scan the questions they got wrong. They read the solution for each, nod, think “ah okay,” and close the tab. Total time: 30 minutes. They feel productive.

Three problems with this. First, “reading the solution” doesn’t produce learning — it produces familiarity with the solution, which feels like learning. The next mock, they get a similar question wrong because they didn’t internalize the method, just recognized the explanation. Second, this approach ignores the questions you skipped — which are actually the more informative diagnostic signal than the ones you got wrong. Third, it ignores time allocation entirely — the most fixable variable in CAT performance.

The four-pass framework

Pass 1 — Questions you got wrong despite knowing the concept

Sort your incorrect answers into two categories. Concept-gap: you got it wrong because you didn’t know how to solve it. Execution-gap: you got it wrong because you knew the concept but made a mistake.

Execution-gaps are where the gold is. Each execution-gap is telling you something specific about how you behave under exam pressure — calculation errors at minute 95, mis-reading the question prompt under stress, mis-bubbling, anchoring to the first answer that “feels right.” Categorize each execution-gap. Keep a running log. After three mocks, the patterns become visible — you’ll find one or two failure modes accounting for 60% of your execution losses.

Concept-gaps go on a separate list. These are real learning needs. But don’t fix them by reading the solution to that specific question — fix them by going back to the underlying topic and re-mastering it. One missed Time-Speed-Distance question means you need a TSD refresher, not just an understanding of that problem.

Pass 2 — Questions you skipped

This is the pass most students skip. Big mistake. The questions you skipped tell you whether your set-selection was correct — which is a more important skill than your concept mastery.

For each skipped question, ask: “Was the skip correct?” A correct skip is one where the question was genuinely time-consuming and you used those minutes for higher-EV questions. A wrong skip is one where the question was actually solvable in 90 seconds and you misjudged it.

Track skip-accuracy over time. Strong CAT performers have 80%+ correct-skip rates by the time they hit the mock-cadence phase of prep. Weak performers skip wrongly 40-50% of the time. Skip-accuracy improves only through this analytical pass. It does not improve by writing more mocks alone.

Pass 3 — Time allocation errors

Get the section-by-section, problem-by-problem time data from your mock interface. Most mock platforms (including the IMS SimCAT interface) record time-per-question. Look at it.

What you’re looking for: did you spend 6+ minutes on a single QA question? That’s a leak. Did you finish VARC with 8 minutes still on the clock? You skipped questions you could have attempted. Did your DI-LR time distribute evenly across sets, or did one set eat 35 of your 60 minutes? Set-anchoring is one of the most common time errors.

Build a time-budget per section, then per problem type within each section. Most students don’t set explicit time budgets and don’t track against them. The students who do — and who adjust their time discipline based on what the data shows — improve faster than any other intervention I can name.

Pass 4 — Pattern recognition across three mocks

After every third mock, do a meta-analysis. Open your error log and your time data from the last three mocks side by side. Look for patterns.

Are your execution errors clustered in a specific topic? In a specific time window of the test? In a specific section after a specific section (e.g., VARC fatigue after DI-LR)? Are your wrong skips concentrated in a particular set type? Are your time-blown questions concentrated in problems with specific structural features?

Pattern recognition is what produces breakthrough improvement. The first three mocks teach you the basics. Mocks 4-6 should produce a clear picture of your individual failure modes. From mock 7 onward, you should be running targeted interventions — extra practice on the specific topic where execution-errors cluster, time-discipline drills on the section where you over-spend, mental-prep work on the failure mode that surfaces when you’re tired.

How long this actually takes — be realistic

First mock analyzed this way: 6 hours. Yes, six. The volume of new learning is high, the categorization is unfamiliar, and you’ll find errors you didn’t know you had. Plan for it.

By mock 5-6, the same analysis takes 3 hours. Categorization is fluent, you know your error patterns, and the log entries are quick.

By mock 15-20, full analysis is 2 hours — equal to the mock itself. That’s the floor. Going below that is when analysis stops paying back, but it’s also when you’ve internalized the patterns enough that the analysis happens naturally during the mock itself, which is exactly what you want.

What this looks like in practice

A student in our CAT-25 cohort — I’ll keep her anonymous, but she converted IIM-Indore PGP — kept a single Google Doc through her prep year. Each mock got its own section with four sub-sections: concept-gaps, execution-gaps, skip-analysis, and time-data. After every third mock she wrote a 200-word meta-analysis.

Her starting percentile in PreSimCATs was 78. Her final SimCATs averaged 96. The improvement was not from new concept mastery — she had finished the syllabus by mock 4. The improvement was from systematic identification and patching of execution-gaps and time-allocation errors, mock by mock. Twenty mocks. Each one written and analyzed properly. That is the path.

Related: When to start full-length mocks (FAQ) · What CAT toppers do differently · The full methodology.