How to Analyse a CAT Mock Test (The Right Way)

Most aspirants take 30–40 mocks before CAT and still plateau. The reason is almost never a lack of mocks — it is a lack of analysis. A mock you don't review is just three hours spent confirming what you already knew. This guide gives you a repeatable framework to squeeze every mark out of every mock.

Why analysis matters more than the mock itself

A mock has two jobs: (1) build exam stamina and (2) generate data about how you think under pressure. The score is only the headline. The real value sits in the questions you got wrong, the ones you got right by luck, and the ones you skipped that you should have attempted. Analysis turns that raw data into a study plan.

Rule of thumb: spend at least as long analysing a mock as you spent taking it. A 2-hour mock deserves a 2–3 hour review.

The 5-step mock analysis framework

1. Start with the overall report — before you look at solutions

Note four numbers for each section: attempts, accuracy, time spent, and net score. Ask:

• Did I over-attempt (low accuracy) or under-attempt (left marks on the table)?
• Which section leaked the most time for the least reward?

2. Bucket every question into four types

Go through the paper and tag each question:

The Wrong and lucky/slow buckets are where your next 5 percentile points live.

3. Do a root-cause on every wrong answer

For each mistake, write down why it happened. Almost every error is one of:

• Concept gap — you didn't know the method → add it to revision
• Silly/calculation slip — knew it, misread or miscalculated → track the pattern
• Selection error — attempted a hard question and skipped an easy one
• Time pressure — rushed and guessed

When you tag mistakes this way over 5–6 mocks, a pattern appears. Maybe 40% of your losses are silly slips in Quant, or you consistently pick the wrong DILR set first.

4. Fix your test-taking strategy, not just the topics

DILR especially is won by set selection. Review which sets you chose and whether a better choice existed in the first 3 minutes. For VARC, check whether your accuracy drops on inference questions vs direct ones. Read our CAT DILR strategy guide and VARC strategy guide alongside your analysis.

5. Log every mistake in one place

Keep a running mistake notebook — one line per error with its root cause and the correct approach. Before the next mock, re-read it. This single habit compounds faster than any amount of new practice.

Turn analysis into a metric you can track

The point of analysis is improvement you can see. Track accuracy per section and per topic across mocks — if your Quant accuracy climbs from 55% to 75% over ten mocks, your method is working. Athena's Error Logbook and Mock Tracker do exactly this: they capture every mistake with its cause and chart your accuracy trend over time, so you always know what to fix next. And when you take mocks on Athena, the analysis is generated for you automatically — attempts, accuracy, time-per-question and topic breakdown in one screen.

The bottom line

Don't chase mock count — chase mock quality. One deeply analysed mock beats three rushed ones. Build the review habit early, keep a mistake log, and let the data pick your next study target. That is how a stuck score starts moving again.

Ready to practise the smart way? Take a true-to-exam mock and get full analysis — start free on Athena.