How to Analyse a CAT Mock Test Properly: A Framework That Produces a Next Step

How to Analyse a CAT Mock Test Properly: A Framework That Produces a Next Step

A CAT mock takes around two hours.

The useful part often begins after those two hours.

Many students believe they are analysing a mock because they read the solutions to questions they got wrong. That is only one layer.

A proper CAT mock analysis should answer three questions:

1. What happened?
2. Why did it happen?
3. What will I change before the next test?

   If your analysis ends without a specific change, it is probably incomplete.

   Step 1: Do not begin with percentile

   Percentile is emotionally powerful and diagnostically limited.

   A strong percentile can hide sloppy decisions in an easier mock. A weak percentile can make a solid attempt look worse in a difficult test.

   Start with your own paper.

   Record:

   • Score by section
   • Attempts
   • Correct answers
   • Incorrect answers
   • Accuracy
   • Unattempted questions you could solve later
   • Time spent on questions that produced no marks

     Now you have the raw material.

     Step 2: Review every attempted question

     For each attempted question, classify it.

     Correct and efficient

     Ideal. You recognised it and converted it.

     Correct but inefficient

     You got the marks but spent too much time. This can still hurt the overall section.

     Incorrect due to knowledge

     Concept gap or method gap.

     Incorrect due to execution

     Calculation, reading, notation, assumption or careless error.

     Incorrect due to decision

     You should not have attempted it in the first place.

     This final category is underrated.

     CAT performance is not only about solving. It is about refusing low-return questions.

     Step 3: Review every unattempted question

     This is where hidden marks live.

     After the test, solve unattempted questions without the timer and ask:

     Could I realistically have solved this during the exam?

     If yes, why did you miss it?

     Maybe:

     • You never reached it
     • You misjudged difficulty
     • Your scanning process was weak
     • You had already lost time elsewhere
     • The topic label looked intimidating

       These are strategy problems, not syllabus problems.

       Step 4: Analyse VARC differently

       In VARC, avoid vague labels such as “RC accuracy issue”.

       Write down the option-level reason.

       Examples:

       • Chose an option broader than the passage
       • Confused author's view with an example
       • Added outside knowledge
       • Rejected the correct option because wording felt weak
       • Missed a qualifier in the question
       • Overthought between two close choices

         Patterns become visible only when the error descriptions are specific.

         Step 5: Analyse DILR from the first five minutes

         For DILR, resolving a set after the mock does not tell you whether it was a good set to choose.

         Revisit the selection stage.

         Ask:

         • What information was available immediately?
         • Was the structure easy to represent?
         • Was there a clear entry point?
         • How many cases seemed necessary?
         • Did the set become clearer after two minutes or more confusing?
         • When should I have left?

           One bad set choice can shape the entire section.

           Step 6: Analyse QA by conversion value

           For each QA question, estimate:

           • Was it conceptually familiar?
           • Was there a shorter route?
           • Could options have been used?
           • Did calculation become unnecessarily long?
           • Was the question worth the time?

             The aim is not to solve every question elegantly after the test.

             The aim is to become better at identifying which questions are marks for you.

             Step 7: Build an error log that changes behaviour

             Your error log should not become a museum of past mistakes.

             Each entry should include:

             Question / topic
             What went wrong
             Why it happened
             What rule will prevent it
             What practice will repair it

             For example:

             DILR scheduling set
             Spent 11 minutes and abandoned.
             No clear starting condition, but continued because I had already invested time.
             Rule: if representation is still unclear after 4–5 minutes, reassess and leave.
             Repair: practise set selection on 10 mixed DILR sets.

             That entry can improve a future mock.

             Step 8: Decide only three actions

             Do not finish analysis with a list of 19 weaknesses.

             Pick the highest-return three.

             For example:

             1. Revise ratios and mixtures
             2. Do two timed DILR selection drills
             3. Reduce speculative VARC attempts

                These become the preparation plan until your next full test.

                Where On Your Mocks can remove some of this manual work

                You can maintain this entire process in a spreadsheet or notebook. In fact, understanding the framework manually is useful.

                The On Your Mocks Test Series applies the same underlying idea inside the testing journey: do not stop at score and accuracy; investigate why marks were lost, identify what deserves attention and carry that learning into the next attempt.

                If several analysed mocks show that the recurring problem is specifically slow solving, poor selection or inefficient methods rather than missing concepts, the CAT Speed & Shortcuts Live Program is the more targeted OYM course.

                Use the test data first. Let the pattern tell you whether you need more practice, a concept repair or strategy coaching.

                A final test of your analysis

                After reviewing a mock, close the score page and answer this:

                What will I do differently in the next mock because of what I learned today?

                If you can answer clearly, the mock has done its job.