Quick answer: first review every question without a timer, then classify each miss as a concept, execution, time-management, or selection problem. Finally, choose one or two concrete rules to test in your next mock. Do not turn analysis into a second attempt at the paper.

What a CAT mock analysis should answer

Most students already know whether an answer was right or wrong. That is the starting point, not the conclusion. Your review should explain the decision behind the answer: why you chose the question or set, what you understood, where time went, and whether the same situation is likely to repeat.

After a good review, you should be able to answer these four questions:

  • Which marks were realistically available to me?
  • Did I lose them because I did not know the method, made an avoidable error, spent too long, or chose poorly?
  • What was my strongest decision in each section?
  • What will I do differently in the first 10–15 minutes of my next mock?

This shifts your attention from a single score to a repeatable improvement system. A low score can still be a productive mock if it exposes one pattern clearly. A high score can hide a weak habit if you never inspect how it happened.

The five-step CAT mock-analysis workflow

1Record the score, attempts, and time while the mock is fresh

Before checking detailed solutions, write down how each section felt. Which questions looked tempting? Where did you feel rushed? Which set or passage did you leave too early or too late? These notes preserve decision-making details that disappear once you know the correct answers.

Log section-level data too: attempts, correct answers, incorrect answers, score, and any major time sinks. This gives you a baseline that you can compare across mocks instead of relying on memory.

2Re-solve every incorrect or skipped question without a timer

Work through the question again before opening the solution. If you can solve it calmly now, the gap may be selection, execution, reading accuracy, or time pressure—not a missing concept. If you still cannot solve it, identify the exact concept or method that blocked you.

For questions you got right, review the unusually slow ones as well. A correct answer that consumed too much time can be as important as a wrong one, especially in DILR and QA.

3Give each useful review item one clear tag

Tags prevent a vague conclusion such as “I need to improve Quant.” Keep the list small enough that you will actually use it. A practical starting set is:

  • Concept gap: you did not know the underlying topic or method.
  • Execution error: you knew the approach but made a calculation, interpretation, or marking mistake.
  • Question selection: you invested in a question, set, or passage that was not a good choice for you at that point.
  • Time management: you had a workable path but did not stop, switch, or return at the right time.
  • Careless reading: you missed a condition, unit, qualifier, or word in the question.

A question can have more than one issue, but select the first cause you would need to fix to change the outcome. That makes the tag actionable.

4Find the highest-impact pattern, not every possible flaw

Do not create a study plan from every single mistake. Look for clusters. For example, three lost QA questions from percentage changes may be one concept gap. Two DILR sets abandoned after ten minutes may point to selection. Four wrong VARC answers from one passage may be a reading-precision issue rather than a need to practise every question type.

Ask a harder question: if I could replay this mock with only one improvement, what would have added the most reliable marks? That is usually the priority for the next few practice sessions.

5Write an experiment for the next mock

A conclusion is useful only if it changes behaviour. “Improve DILR” is not an experiment. “Spend the first four minutes ranking all sets, then leave any set that has no viable entry after six minutes” is an experiment. You can test it, observe it, and keep or revise it after the next mock.

Before you close your analysis, write:
  • one topic to revise,
  • one timed drill to do before the next mock, and
  • one decision rule to apply in the next mock.

What to look for in each CAT section

VARCSeparate comprehension from answer selection

For every wrong reading-comprehension question, check whether you misunderstood the passage, overlooked a qualifier in the question, or chose an option that was attractive but too extreme. Track passage choice as well: a difficult passage is not automatically a bad choice, but repeatedly spending too long on one often is.

For verbal questions, record the specific reason an option failed. Was it outside the scope, too absolute, reversed in meaning, or unsupported? This builds a sharper elimination process than simply reading more solutions.

DILRReview set selection before solution steps

DILR rewards the choice of a solvable set as much as the ability to solve it. Note how long you spent scanning each set, why you chose the first one, and whether an easier entry point was visible elsewhere. For sets you left, check if the issue was genuinely complexity or a missing representation such as a table, grid, or case split.

When you solve a set after the mock, do not just read the official route. Ask which first observation would have made the set manageable during the test.

QADistinguish a missing method from a poor investment

In QA, label the topic and the decision separately. You may know arithmetic but still spend too long on an algebra question with an awkward setup. Equally, a wrong answer after a clean method may reveal a calculation habit rather than a chapter to relearn.

For every question that took too long, write the point at which you should have switched, skipped, or used a simpler representation. Over time, this creates a personal library of “leave it” signals.

A simple CAT mock-analysis template

Use one row per important question or set

  • Section and question/set: QA Q12, DILR Set 2, VARC RC 3
  • Result: correct, wrong, skipped, or unreviewed
  • Time spent: your best estimate
  • What I did: one sentence on the approach or decision
  • Root cause: concept, execution, selection, time, or reading
  • Better action: the method or rule you would use next time
  • Follow-up: revision task, drill, or next-mock rule

The table should make future decisions easier, not become a diary of every solution. Keep complete notes for patterns that could recur; keep short notes for one-off mistakes.

How to turn review into a next-mock plan

End every analysis by limiting your focus. Pick one primary weakness and one supporting task for the week. For example:

  • Primary focus: percentage and ratio applications in QA.
  • Practice: two untimed concept sessions, then two short timed drills.
  • Mock rule: if a QA question has no setup after about two minutes, mark it and move on.

At the next mock, evaluate the experiment—not just the score. Did you actually follow the rule? Did it create better opportunities? This feedback loop is how mocks stop being score reports and become a training system.

Frequently asked questions

How long should I spend analysing a CAT mock?

Spend enough time to understand the decisions behind meaningful errors and to create a focused plan. For a full mock, that commonly takes longer than the test itself; prioritise the questions, sets, and passages that can change future decisions.

Should I analyse questions I got right?

Yes—especially questions that took too long, felt uncertain, or were solved using an inefficient route. They often reveal time-management and question-selection patterns that a score report cannot show.

What if I have too many mistakes to review?

Start with questions that were close, costly, or repeated a familiar pattern. Then identify the two or three themes with the largest likely payoff. You can return to the remaining questions later; do not let an enormous review prevent you from taking the next useful action.