How to Analyse a CAT Mock Test: 30-Minute Framework + Free Analysis Template

By Abhishek Anand, Founder, Mentors Capital, MBA, IIM Bangalore

Abhishek has spent over a decade mentoring 5,000+ CAT aspirants, helping hundreds secure seats at IIMs and other top-tier B-schools with his 99.9+ percentile insights. He teaches test strategy the way he took the test: as a series of small decisions made under a clock. This is that method, section by section, with the numbers behind it.

Most CAT aspirants check their score, feel something between relief and dread, and move on to the next mock. That habit is the single biggest reason mock scores plateau. The score tells you where you stand. It does not tell you why, and why is the only thing that actually changes your next attempt.

A 30-minute analysis, done immediately after every mock, is enough to extract the two or three things that matter most from that test. Here is the exact framework, followed by a template you can copy and reuse for every mock between now and CAT 2026.

If you have not yet registered for CAT, note that the process and any updates are only official at: iimcat.ac.in

Why the first 30 minutes after a mock matter more than the next mock itself

Taking another mock without analysing the last one is like running the same practice drill on repeat without checking whether your form is correct. You accumulate hours. You do not necessarily accumulate improvement.

Analysing a mock while it is fresh, ideally the same day, means you still remember why you hesitated on a question, which set you skipped and regretted skipping, and where you felt the clock pressing. A week later, that memory is gone and all you have left is the score. The framework below is built to run in 30 minutes precisely so it fits realistically into a prep schedule that also needs to leave room for actual studying.

The 30-minute CAT mock analysis framework

Minutes 0-5: Section-wise time and attempt audit

Start with the numbers, not the questions. For each section, VARC, DILR, and QA, note three things: how many questions you attempted, how much time you spent, and how that compares to your planned allocation. If you planned 13 minutes for a DILR set and spent 22, that is worth flagging before you even look at whether you got the answers right.

This step is fast because it is mechanical. You are not analyzing yet. You are gathering the raw material the rest of the framework will use.

Minutes 5-20: Classify every wrong and skipped question

This is the core of the analysis, and it deserves the most time. Go through every question you got wrong and every question you skipped, and assign each one to exactly one category:

• Concept gap: you did not know the underlying concept or method needed to solve it.
• Silly error: you knew the method, but made a calculation, reading, or transcription mistake.
• Timing: you understood the question but ran out of time before finishing or attempting it properly.
• Wrong set selection: in DILR specifically, you spent time on a set that turned out to be harder than it looked, at the cost of an easier set you did not get to.

Resist the urge to lump everything into ‘I just didn’t get it.’ The category matters because each one has a completely different fix. A concept gap needs content revision. A silly error needs a slower, more careful pass through similar questions. A timing issue needs pacing practice, not more content study. Misdiagnosing the category means you spend your next week’s study time on the wrong problem.

Minutes 20-25: Find the pattern, not just the list

With every question categorized, step back and look for repetition. Are your concept gaps clustering in one specific QA topic, like Geometry or Time and Work? Are your silly errors happening mostly in the final 10 minutes of a section, when time pressure is highest? Are you consistently picking the wrong DILR set to start with?

One mock rarely reveals a reliable pattern on its own. But if you have been running this analysis consistently, this is the step where three or four mocks start telling a coherent story: not ‘I am weak at QA,’ but ‘I am weak specifically at Geometry under time pressure.’ That level of specificity is what actually changes how you spend your next study session.

Minutes 25-30: Write down two to three specific actions

End every analysis with a short, concrete list, not a vague resolution. ‘Study more DILR’ is not an action. ‘Practice 5 timed DILR sets this week, specifically games and tournaments type puzzles, and track completion time per set’ is an action.

Two or three specific, trackable actions per mock is enough. More than that, and the list becomes aspirational rather than something you will actually do before the next mock.

The mock analysis template

Copy this structure for every mock. Fill one row per section per mock. Track it over time in a spreadsheet so patterns across mocks become visible, not just patterns within one test.

For a deeper version of this template, add one row per DILR set (rather than one row for the whole section) and one row per QA topic area (Arithmetic, Algebra, Geometry, and so on), since section-level tracking alone can hide exactly where within a section your time and accuracy problems are concentrated.

Common mistakes people make when analysing their own mocks

A few patterns show up repeatedly in how aspirants self-analyse, and each one quietly undermines the process.

Only reviewing wrong answers, and skipping the questions you got right but took too long on. A correct answer that costs you four minutes is not a success story. It is a timing problem wearing a passing grade.

Reviewing immediately after the mock, while still emotionally reactive to the score. A rushed, frustrated 10-minute glance is not the same as a structured 30-minute analysis. If you cannot do the full framework the same day, do the time-and-attempt audit immediately and save the deeper question-by-question classification for later that evening, once the initial reaction has settled.

Treating every mock as a fresh start instead of building a running log. The real value of this framework compounds across mocks, not within a single one. A spreadsheet that tracks mistake types and accuracy trends across 10 mocks tells you far more than any single test’s analysis in isolation.

How this fits into your broader CAT prep

Mock analysis is not a replacement for content study or timed practice. It is the mechanism that tells you where to point that study and practice. A candidate who takes fewer mocks but analyses each one properly typically outperforms a candidate who takes twice as many mocks with only a glance at the final score.

If you are early in your CAT 2026 preparation and have not yet built this habit, start with your next mock. Thirty minutes of structured analysis, done consistently, is a small time investment relative to the hours you are already putting into practice, and it is the piece most aspirants skip.

FAQs

Q: How long should I spend analysing a CAT mock test?
Around 30 minutes is enough for a structured analysis: 5 minutes reviewing section-wise time and attempts, 15 minutes classifying every wrong or skipped question by mistake type, 5 minutes identifying patterns across questions, and 5 minutes writing down specific actions for your next study session.

Q: What should I track in a CAT mock analysis sheet?
For each section, track questions attempted, correct and incorrect counts, accuracy percentage, time spent versus planned time, the type of mistake for each wrong or skipped question (concept gap, silly error, timing, or wrong set selection in DILR), and one or two specific actions for your next mock.

Q: Why is my CAT mock score not improving even though I keep taking mocks?
Taking mocks without a structured analysis process is one of the most common reasons scores plateau. The score alone does not tell you why a question was missed. Categorizing mistakes by type, whether they are concept gaps, careless errors, or timing issues, is what actually points you toward the right fix, since each mistake type needs a different kind of practice to address.

Q: Should I review questions I got right, not just the ones I got wrong?
Yes. A correct answer that took significantly longer than it should have is a timing problem, even though it shows up as a success on your scorecard. Reviewing only wrong answers misses this category of issue entirely.

Q: How soon after a mock should I do the analysis?
As soon as possible, ideally the same day, while you still remember why you hesitated or skipped specific questions. If a full 30-minute session is not possible immediately, do the section-wise time and attempt audit right away, and save the deeper mistake classification for later the same day.