You’ve taken a CAT mock. You have a score, a percentile, and a mix of relief and worry. Now what?
Most aspirants either glance at the percentile and move on, or read through the solutions and nod along at their mistakes. Neither is CAT mock test analysis. Mocks are steps in your preparation. They do not show whether you can do well in the actual test — and definitely not who you are. They are simply preparatory tools for your betterment.
This article gives you a repeatable operating system for turning a mock into improvement — a method you can run after every mock, whether it’s your first or your twentieth.
What Does CAT Mock Test Analysis Actually Mean?
These are six different activities, and most students stop after the third:
| Activity | What it involves | Is it enough alone? |
|---|---|---|
| Taking the mock | Sitting the test under timed conditions | No — this only generates data |
| Checking the score | Looking at score and percentile | No — tells you what, not why |
| Reviewing solutions | Reading correct methods for missed questions | No — explains the question, not your behaviour |
| Analysing the mock | Diagnosing why each outcome happened | This is where analysis begins |
| Correcting weaknesses | Choosing and executing a targeted fix | Necessary follow-through |
| Verifying improvement | Testing whether the fix actually worked | Closes the loop |
Reading solutions tells you how to solve a question you already saw. It doesn’t tell you why you personally missed it, whether that reason will recur, or whether you’ve fixed it. That gap is what mock test analysis exists to close.
The PREPON Analyse → Review → Correct → Verify Method
This four-stage cycle is the backbone of the method, and it’s worth internalising as a sequence rather than a one-time checklist.
Analyse — What happened? Measure score, attempts, accuracy, time, section performance, and Easy–Medium–Difficult outcomes. This stage is purely descriptive.
Review — Why did it happen? Diagnose the cause: concept gap, practice gap, poor selection, weak strategy, execution error, misreading, calculation slip, poor decision-making, or a correct answer reached through unreliable reasoning.
Correct — What should change? Choose the intervention that matches the diagnosis, rather than reflexively booking another full mock. A concept gap needs relearning; a pacing problem needs sectional drilling; they are not the same fix.
Verify — Did the correction actually work? This is the stage most students skip, and it’s the one that matters most. An error logged but never re-tested is an error that may simply repeat. Verification can come from targeted practice, a topic test, a sectional test, or performance in a later mock — but it has to be checked, not assumed.
Start With the Big Picture: Your CAT Mock Dashboard
Before diagnosing individual questions, look at the shape of the mock as a whole. Good CAT mock test analysis starts with this dashboard before it moves to individual errors.
| Metric | What it tells you |
|---|---|
| Score & percentile | Relative standing — context-dependent, not a fixed measure of ability |
| Attempts | Whether you’re over- or under-attempting relative to your accuracy |
| Accuracy | Whether selection or execution is the bigger issue |
| Section-wise performance | Where the mock was won or lost |
| Time distribution within each section | Since CAT sections are separately timed, this looks at how time was used inside a section, not moved between sections |
| Time per question or DILR set | Whether particular questions or sets consumed disproportionate time |
| Time lost on unproductive attempts | Time spent on questions or sets that were ultimately abandoned or wrong |
| Questions/sets not reached | Whether pacing prevented you from even seeing later material |
| Easy-question misses | Often the most fixable and highest-priority errors |
| Repeated error types | Signals a pattern rather than a one-off slip |
A single score or percentile compresses all of this into one number. Two students can land on the same percentile through completely different mocks — one through balanced execution, another through a lucky section and a disastrous one. The dashboard is where you stop looking at the outcome and start looking at the mock’s structure.
Use the Easy–Medium–Difficult Error Log
Classify each question you attempted (or didn’t) as Easy, Medium, or Difficult — based on your own post-mock judgment of how accessible it was to you. This is a subjective classification, not an objective property of the question. What feels Easy to one aspirant may be Medium to another, depending on conceptual familiarity, the number of reasoning steps involved, and how the test conditions affected you that day. Don’t force a rigid definition; classify honestly, in hindsight.
The value of E–M–D isn’t a timing formula — it’s a lens for spotting patterns: did you convert the opportunities you should have, waste time on ones you shouldn’t have chased, miss solvable questions, or make sensible skips? In CAT mock test analysis, this prevents difficulty labels from becoming arbitrary time rules.
E–M–D × Outcome Matrix
| Difficulty | Correct | Incorrect | Unattempted |
|---|---|---|---|
| Easy | Usually reliable conversion; still check efficiency. | Often execution, reading or calculation slip. | Often scanning or pacing miss. |
| Medium | Reasonable command; check method efficiency. | Often application, misreading or execution issue. | Strategic skip or missed opportunity; review selection. |
| Difficult | Strong command or lucky correct; verify reasoning. | Often poor selection/opportunity cost rather than urgent content gap. | Often a good strategic skip; verify the decision. |
Easy — Correct. May indicate: solid fundamentals converting reliably. Does not automatically mean: the question was solved efficiently — check time spent. Investigate: time taken relative to other Easy-correct questions. Likely action: usually none, unless time was disproportionate.
Easy — Incorrect. May indicate: a careless or execution-level slip rather than a knowledge gap. Does not automatically mean: you don’t understand the concept. Investigate: was it a reading error, calculation slip, or rushed selection? Likely action: execution drills, slower first-pass reading — usually not concept relearning.
Easy — Unattempted. May indicate: a scanning miss or a pacing problem earlier in the section. Does not automatically mean: the question was hard to find. Investigate: did you see it and skip it, or never reach it? Likely action: review scanning strategy and section pacing.
Medium — Correct. May indicate: reasonable command of moderately complex material. Does not automatically mean: the method was optimal. Investigate: was there a faster route you missed? Likely action: method-efficiency practice if time was high.
Medium — Incorrect. May indicate: a genuine gap in application rather than pure concept. Does not automatically mean: the underlying concept is unknown. Investigate: concept vs. application vs. misreading. Likely action: targeted application practice.
Medium — Unattempted. May indicate: a reasonable, strategic skip — or a missed opportunity. Does not automatically mean: it was unsolvable for you. Investigate: could you have solved it with time you spent elsewhere less productively? Likely action: selection-strategy review.
Difficult — Correct. May indicate: strong command — or a lucky guess. Does not automatically mean: the reasoning was sound. Investigate: could you reconstruct the logic confidently, or were you guessing? Likely action: if lucky, treat the underlying skill as still unverified.
Difficult — Incorrect. May indicate: the question was genuinely a poor selection for you that day. Does not automatically mean: you need to learn this topic urgently. Investigate: opportunity cost — what did the attempt cost you elsewhere? Likely action: often a selection-strategy fix, not a content fix.
Difficult — Unattempted. May indicate: an appropriate, strategic skip. Does not automatically mean: a weakness. Investigate: was it correctly identified as low-value, or avoided out of anxiety? Likely action: usually none — this is often the correct call.
Analyse Every Part of Your CAT Mock
Analyse Correct Answers Too
This is where CAT mock test analysis becomes much more revealing. A correct answer isn’t automatically a well-executed one.
| Type | How to spot it |
|---|---|
| Efficient Correct | Solved quickly, using a sound method |
| Inefficient Correct | Correct, but took far longer than the question warranted |
| Lucky Correct | You can’t reliably reconstruct why the answer was right |
| Correct through unreliable reasoning | The method used was flawed but happened to land on the right option |
| Excessive-time Correct | Correct, but at a time cost that likely displaced other questions |
| Poor-opportunity-cost Correct | Correct, but the time spent would have earned more elsewhere |
Correct ≠ automatically well executed. A student who logs only their wrong answers is missing half the story — and often the more expensive half, since time lost on inefficient correct answers is invisible on the scorecard.
Analyse Every Unattempted Question
Not every skip is the same, and treating them all identically hides useful information. CAT mock test analysis should therefore classify unattempted questions by the decision behind the skip.
| Category | Identifying signal | Action |
|---|---|---|
| Good Skip | Correctly judged as low-value relative to time cost | None — reinforce the judgment |
| Bad Skip | Solvable question skipped for no good reason | Selection-strategy review |
| Not Reached | Time ran out before the question was seen | Pacing review |
| Overlooked During Scanning | A solvable question was in view but missed during scanning | Scanning-technique practice |
| Abandoned Appropriately | Started, correctly judged unproductive, exited | None — this is good decision-making |
| Abandoned Prematurely | Exited too early on a question that was actually tractable | Persistence/selection calibration |
| Conceptually Inaccessible | Genuinely beyond current knowledge | Concept relearning |
| Strategically Deprioritised | Consciously set aside to protect time for higher-value questions | None, if the trade-off was sound |
Build a CAT Error Taxonomy
| Error type | Symptom | Likely cause | Corrective action | Verification method |
|---|---|---|---|---|
| Concept | Consistent wrong answers on a topic | Underlying theory not understood | Relearn the concept | Topic test |
| Practice/Application | Concept known, application fails | Insufficient varied practice | Untimed then timed practice sets | Sectional test |
| Selection | Time spent on low-value questions | Weak judgment of question value | Selection drills using past mocks | Next mock’s selection pattern |
| Strategy | Section approach doesn’t match strengths | Mismatched overall plan | Redesign section approach | Sectional test |
| Execution | Right approach, wrong final answer | Slip under time pressure | Timed simulation drills | Repeat similar question set |
| Calculation | Arithmetic/algebraic errors | Rushed or careless computation | Slow-down and double-check practice | Timed accuracy drill |
| Reading/Interpretation | Misread question or passage intent | Skimmed too fast | Deliberate slow-reading practice | Comprehension-focused set |
| Time/Pacing | Section time badly distributed | No time checkpoints used | Practice with checkpoint targets | Sectional test with timing log |
| Unreliable Guess | Correct but can’t explain reasoning | Pattern-matched without understanding | Re-derive the logic from scratch | Similar question without answer choices |
| Sunk-Cost/Decision | Stayed too long on one question/set | Reluctance to abandon invested effort | Practice deliberate exit rules | DILR set drills with exit checkpoints |
| Method Inefficiency | Correct but slow | Using a longer method than necessary | Learn faster alternative methods | Timed re-attempt |
A single symptom can have more than one cause — a wrong answer on a Medium question could be a concept gap, a misreading, or a rushed calculation. The taxonomy is a starting checklist, not a lookup table with one right answer per row.
Is the Problem Knowledge, Strategy or Execution?
Once you’ve diagnosed a pattern, decide what kind of fix it needs. This is where CAT mock test analysis turns diagnosis into a specific intervention:
- Relearn — if the concept itself is missing
- Practise — if the concept is known but application is shaky
- Change question selection — if the issue is judgment about what to attempt
- Adjust pacing — if time distribution within a section is off
- Improve execution — if the approach is right but slips occur under pressure
- Do nothing yet — avoid overhauling your strategy on the basis of one anomalous result unless the underlying problem is already clear. A single unusual mock can be noise as easily as it can be a genuine signal.
Analyse Each CAT Section Separately
How to Analyse VARC After a CAT Mock
For a deeper section-level method, see PREPON’s CAT VARC strategy. Look at passage selection (did you pick passages that suited your reading style?), question selection within a passage, and whether your errors came from reading the passage or answering the question. Common patterns include inference errors (reading beyond what the passage states), scope errors (an option is true but doesn’t answer the specific question), and weak option elimination. Also check VA performance separately, since it often has a different error profile from RC.
Illustrative VARC example: An aspirant answers an inference question about a passage’s central argument by selecting an option that is true based on the passage but doesn’t address what the question actually asks — a scope error, not a comprehension failure. In the same mock, they correctly answer a detail-based question but take nearly twice as long as their average, re-reading two paragraphs unnecessarily — an inefficient correct answer worth flagging for scanning practice.
How to Analyse DILR After a CAT Mock
PREPON’s guide to attempting DILR in CAT explains the scan-and-select process in more depth. In DILR, CAT mock test analysis centres on decisions made before solving: which sets you scanned, which you chose to attempt, how you represented the information, and whether you correctly read the constraints. Then look at commitment behaviour — did you abandon unproductive sets, or stay too long? Check for solvable sets that were skipped entirely, and whether accuracy dropped after you’d already committed significant time to a set (a sign of rushing to recover time elsewhere).
Illustrative DILR example: An aspirant scans four sets, picks one that looks familiar, and spends a large share of the section on it before realising the constraints were more complex than expected. A second, more straightforward set is never attempted. This is a set-selection and sunk-cost pattern, not a knowledge gap — the corrective action is a selection drill and a practiced exit rule, not more DILR theory.
How to Analyse QA After a CAT Mock
Separate topic-level gaps (a formula or concept not known) from application gaps (the concept is known but not applied under pressure). Check calculation accuracy, method choice (was there a faster approach, such as option substitution, that wasn’t used?), and question selection — particularly Easy misses and Difficult-question time traps.
Illustrative QA example: An aspirant solves a percentage-based question correctly but through a long algebraic setup, when option substitution would have taken a third of the time — a method-inefficiency case. Separately, they miss an Easy arithmetic question due to a sign error under time pressure — an execution/calculation issue, not a conceptual one. Treating both as “needs more practice” would miss that they need two different fixes.
Understand the Decision-Making Behind Your Mock
Sunk-Cost Behaviour
Arkes and Blumer’s 1985 research, “The Psychology of Sunk Cost,” established that people tend to continue investing in a decision because of resources already committed, even when continuing is no longer rational. That research examined general decision-making behaviour — it did not study CAT aspirants specifically.
Applying this to a student who refuses to leave an unproductive DILR set or a Difficult question because they’ve “already put in ten minutes” is a PREPON application of that broader principle, not a claim from the original research. The practical takeaway holds regardless: time already spent is not a reason to keep spending it if the marginal return has dropped.
Mock-Taking Psychology
Certain behaviours show up repeatedly across mocks and are worth naming without over-interpreting: panic after a difficult opening section, carrying a poor section’s frustration into the next one, chasing attempt count instead of accuracy, refusing to abandon a question once started, confidence swings after seeing the percentile, changing strategy after almost every mock, and comparing yourself directly against leaderboard toppers.
A noticeable gap between how you perform in untimed practice and how you perform in a timed mock can have several explanations — pacing, selection habits, unfamiliarity with full-length conditions, or genuine stress. It shouldn’t be treated as proof of anxiety or any other condition; that’s a determination for a professional, not a mock-analysis inference.
Turn CAT Mock Analysis Into Improvement
What Should You Do After Identifying the Problem?
| Diagnosis | Intervention |
|---|---|
| Concept problem | Concept revision + focused practice |
| Application problem | Untimed practice, then timed practice |
| Selection problem | Question/set-selection drills |
| Pacing problem | Sectional practice |
| Execution problem | Timed simulation |
| Repeated, unexplained problem | Mentor review |
Not every error has one universal remedy — the same symptom (say, a wrong Medium QA question) might call for a different fix depending on what the Review stage actually uncovered.
Topic Test vs Sectional Test vs Full Mock
The reflex after a bad mock is often “take another mock.” That’s frequently the wrong instrument. CAT mock test analysis should tell you which verification tool to use next. A topic test verifies whether a specific concept fix worked. A sectional test verifies pacing or selection changes within one section, without the noise of a full three-hour test. A full mock verifies whether everything — including stamina and cross-section decision-making — holds together, but it’s a blunt tool for checking one narrow fix. Match the verification tool to the size of the thing you’re verifying.
When Should You Analyse the Mock?
There’s no scientifically fixed waiting period. As a general approach: review while your reasoning process is still memorable — often the same day, while specific question-level decisions are fresh. If you’re emotionally or cognitively fatigued right after the mock, a short break before reviewing is reasonable. Avoid pushing analysis off for days, since the specific “why” behind a decision fades quickly, even if the “what” (the score) doesn’t.
Should You Retake the Same CAT Mock?
These are different activities, and conflating them causes bad conclusions:
- Retaking the entire mock as a performance benchmark — of limited value, since you now partly remember the questions and answers
- Re-solving individual questions — useful for practising method, not for benchmarking
- Revisiting DILR sets — useful for confirming a set was solvable with a different approach
- Delayed re-solving — useful for spaced practice
- Retrieval practice — has genuine learning value
The key distinction: prior exposure and memory of questions and answers make a second full-mock score less comparable with your performance on genuinely unseen material. Retrieval practice can still help you learn — but that’s a separate question from whether the retake score tells you anything reliable about your current standing.
Read Your Performance Across Multiple CAT Mocks
How Mock Analysis Changes Through Preparation
For the wider preparation context, see PREPON’s CAT 2027 preparation strategy. Broadly, the focus shifts across three conceptual phases:
- Early: diagnosis and learning — figuring out what you don’t know
- Middle: selection, strategy, and conversion — turning knowledge into results under test conditions
- Final: execution, stability, and repeat-error prevention — tightening what’s already mostly working
These are conceptual phases, not tied to an exact, validated mock count.
How Often Should You Take CAT Mocks?
The central principle: do not take mocks faster than you can analyse, correct, and verify what you learned from the previous one. Common coaching schedules (roughly weekly, for example) can work as a starting point, but they should flex around whether your analysis cycle has actually completed. There’s no single universal timetable that fits every aspirant.
The 20-Mock Trend Method
| Mock | Score | 3-Mock Avg | Accuracy | Easy Misses | Selection Errors | Actions Closed |
|---|---|---|---|---|---|---|
| 1 | 42 | 62% | 9 | 6 | 0 | |
| 2 | 45 | 63% | 9 | 6 | 1 | |
| 3 | 44 | 43.7 | 64% | 8 | 5 | 1 |
| 4 | 49 | 46.0 | 65% | 8 | 5 | 2 |
| 5 | 51 | 48.0 | 67% | 7 | 5 | 2 |
| 6 | 48 | 49.3 | 66% | 7 | 4 | 2 |
| 7 | 54 | 51.0 | 69% | 6 | 4 | 3 |
| 8 | 56 | 52.7 | 70% | 6 | 4 | 3 |
| 9 | 52 | 54.0 | 68% | 7 | 5 | 2 |
| 10 | 58 | 55.3 | 72% | 5 | 3 | 4 |
| 11 | 60 | 56.7 | 73% | 5 | 3 | 4 |
| 12 | 57 | 58.3 | 72% | 5 | 3 | 4 |
| 13 | 63 | 60.0 | 75% | 4 | 3 | 5 |
| 14 | 65 | 61.7 | 76% | 4 | 2 | 5 |
| 15 | 62 | 63.3 | 75% | 4 | 2 | 4 |
| 16 | 68 | 65.0 | 78% | 3 | 2 | 6 |
| 17 | 70 | 66.7 | 79% | 3 | 2 | 6 |
| 18 | 67 | 68.3 | 78% | 3 | 2 | 6 |
| 19 | 72 | 69.7 | 80% | 2 | 1 | 7 |
| 20 | 75 | 71.3 | 82% | 2 | 1 | 7 |
In CAT mock test analysis, one mock is a single data point — it can be noisy, affected by an off day, an unfamiliar paper, or one bad section. Multiple mocks, tracked over time, reveal a pattern. The PREPON tracker uses 20 mocks as a practical longer-horizon view of preparation. Twenty is not a scientifically required number, and useful patterns can emerge much earlier. The 20-mock format is simply a convenient structure for tracking preparation over an extended period.
Within that horizon, look for: immediate warning signals (a sudden, sharp drop), repeated problems (the same error type across several mocks), short-term movement (the last two or three mocks), medium-term trends (the last six to eight), and the longer trajectory. A 3-mock moving average — a PREPON tracker feature, not a validated CAT metric — smooths out single-mock noise so you can see the underlying direction more clearly than a jagged score-by-score line shows.
A Fictional 20-Mock Journey
To see the method in action, imagine a fictional aspirant working through 20 mocks over a preparation cycle (this is an illustrative construct, not real PREPON student data). Their scores don’t rise in a straight line — they fluctuate, including one stretch where performance temporarily dips after a strategy change. Their accuracy improves before their overall score stabilises, since converting existing knowledge more reliably takes time to show up as points. Easy-question misses decline steadily as execution tightens. Some interventions work; at least one doesn’t, and gets revised after verification shows no improvement. A 3-mock moving average, plotted alongside the raw scores, makes the underlying upward trend visible even in the mocks where the raw score dipped.
The lesson isn’t the specific numbers — it’s that progress through this method is rarely linear, and the trend matters more than any single mock.
CAT Score and Percentile Variability
If you are also working backwards from a percentile goal, use PREPON’s CAT 99-percentile guide for that separate planning question. It’s worth distinguishing two related but different things:
- Actual CAT percentile — your relative performance within the official CAT candidate population, calculated through CAT’s own scoring and normalisation process.
- Mock-provider percentile — your relative performance within that provider’s participating test-takers, which is a different population calculated differently.
For both, raw-score distributions vary with test difficulty and how the specific candidate group performed — a harder paper, or a stronger cohort, shifts how a given raw score maps to a percentile, but difficulty alone doesn’t directly determine percentile in a fixed or predictable way.
Any specific historical raw-score-to-percentile figure should be treated cautiously: it should be independently verifiable, attributed to its source, and identified as third-party analysis unless it comes from an official CAT/IIM publication. It should never be presented as a prediction for a future exam.
Comparing Mock Providers
Comparing scores or percentiles across different mock providers is often less reliable than it looks, because providers differ in participant population, cohort strength, number of test-takers, paper difficulty, calibration methods, and how their percentile distributions are constructed. This doesn’t mean cross-provider comparison is worthless — but it should be read with real caution, and no ranking of providers or fixed number of providers is being recommended here.
Peer and Leaderboard Comparison
Comparing yourself to others has a narrow useful zone and a wide unhelpful one. It’s potentially useful for understanding broad relative performance, or for recognising when a paper was unusually difficult across the board. It’s potentially unhelpful when it turns into obsessing over individual toppers, or assuming that another student’s strategy — built around their own strengths — will automatically suit you. There’s no meaningful rule about comparing yourself only to someone a fixed number of percentile points above you; the comparison that matters most is against your own trend.
When Should a Student Ask a Mentor for Help?
CAT mock test analysis can usually be self-directed, but certain patterns are reasonable signals to bring in a mentor for a diagnostic second opinion:
- The same error pattern keeps returning across mocks despite attempted fixes
- Strategy keeps changing without clear evidence that the previous change failed
- One section remains consistently unstable while others improve
- You genuinely cannot identify the root cause of a recurring problem
- Practice performance and timed-mock performance remain substantially different over multiple mocks
- Interventions repeatedly fail to verify as effective
This is meant as a genuine diagnostic escalation point — a second, more experienced set of eyes when self-diagnosis has stalled — not a prompt to sell a programme.
If You Are Reviewing a Student’s Mock Performance
Look at the trend, not the latest number. Check recurring errors, whether corrective work was actually completed, consistency across mocks, section balance, and the quality of decisions made during the test — not just the outcome. Avoid reacting to a single percentile in isolation.
What Not to Do After a Bad CAT Mock
| Don’t | Do Instead |
|---|---|
| Immediately take another full mock | Complete the error log and run targeted verification first |
| Overhaul the entire strategy | Change one variable and verify it before changing more |
| Obsess over one percentile | Look at the trend across several mocks |
| Abandon a section entirely | Diagnose the section’s specific failure pattern |
| Try to fix every weakness at once | Prioritise the top one or two error types |
| Ignore the mock and move on | Run the full Analyse → Review → Correct → Verify cycle |
| Compare indiscriminately with toppers | Compare against your own trend; use peers only for broad context |
Use the PREPON CAT Mock Analysis Tracker
| Tracker Area | What It Records | What It Helps You See |
|---|---|---|
| Mock Summary | Score, percentile, attempts, accuracy | Overall trend without overreacting to one mock |
| Section Dashboard | VARC, DILR and QA performance | Section stability and recurring imbalance |
| Question/Set Log | E–M–D, outcome, time, error type | Easy misses, poor selection and inefficient correct answers |
| Correction Plan | Cause, corrective action, revisit date | Whether analysis turns into scheduled work |
| Verification Log | Topic/sectional/mock retest result | Whether the chosen fix actually worked |
| Progress Dashboard | Moving averages, repeated errors, actions closed | Longer-horizon improvement and unresolved patterns |
Running CAT mock test analysis by hand, mock after mock, gets unwieldy fast. The PREPON CAT Mock Analysis & 20-Mock Progress Tracker is a downloadable tool built to hold it all in one place: mock summaries, section-wise diagnostics, a full question/set error log, an improvement plan linking each diagnosis to a verification step, and a dashboard tracking trends, moving averages, and how many corrective actions have actually been closed out. It’s built to support the exact process this article describes, so you’re not rebuilding a spreadsheet from scratch after every mock.
If you want mentor-led CAT preparation with structured mocks, analysis and correction planning, explore PREPON’s CAT & OMETs Sampurna Programme.
After Every CAT Mock: Checklist
- Record the result.
- Classify E–M–D outcomes.
- Review correct, incorrect, and unattempted questions.
- Diagnose root causes.
- Select priority corrections.
- Schedule targeted work.
- Define how improvement will be verified.
- Update the trend tracker.
Frequently Asked Questions
Is it better to take more mocks or analyse each one more deeply?
Mock frequency should leave enough time for meaningful analysis, correction and verification. Taking more mocks is useful only when the learning from earlier mocks is being converted into changes in preparation and execution.
What is a good accuracy in CAT mocks?
There's no fixed percentage that defines or guarantees CAT performance; accuracy needs to be read alongside attempts, question difficulty, and section context, not in isolation.
What if my mock score is high but percentile is low?
A high raw score can still produce a lower-than-expected percentile if many participants scored similarly or higher. Check the score distribution, your section-wise performance and the provider's participating population rather than interpreting the raw score in isolation.
How long should CAT mock test analysis take?
There is no universal number of minutes or hours for CAT mock test analysis. The analysis is complete when you have reviewed the important correct, incorrect and unattempted questions, diagnosed the main causes, selected corrective actions and decided how those actions will be verified. Early in preparation this may take longer because more errors need diagnosis; later, a cleaner process can become faster.
Should I analyse every question after a CAT mock?
Review every question or set that can teach you something, but the depth of review can vary. Incorrect answers, easy misses, inefficient correct answers, doubtful correct answers and potentially solvable unattempted questions deserve the closest attention. A clean, efficient correct answer usually needs much less review.
Should I analyse correct answers in a CAT mock?
Yes. A correct answer can still hide weak reasoning, a lucky guess, an unnecessarily long method or poor opportunity cost. Marking such answers separately helps you distinguish reliable performance from results that may not repeat in the next mock.
How should I analyse unattempted questions in a CAT mock?
Do not treat every unattempted question as a mistake. Classify it: a good strategic skip, a solvable question you should have attempted, a question you never reached, one overlooked during scanning, one abandoned appropriately or prematurely, or one that was genuinely beyond your current knowledge. The category determines whether any correction is needed.
What is the Easy–Medium–Difficult error log method?
It is a way to classify each reviewed question or DILR set by perceived difficulty and outcome. Combining Easy, Medium or Difficult with Correct, Incorrect or Unattempted creates a 3 × 3 diagnostic matrix. An easy incorrect answer, for example, usually deserves a different response from a difficult question that was correctly skipped.
How do I identify an easy miss in a CAT mock?
First classify difficulty after the mock using your current preparation level rather than an arbitrary time rule. An easy miss is then an easy question or set that you answered incorrectly, failed to notice, did not reach because of pacing, or skipped despite being realistically solvable. Repeated easy misses are especially useful diagnostic signals.
How do I know whether a CAT mock error is conceptual or strategic?
Ask whether you could solve the question correctly without the original time pressure. If the underlying concept is still unclear, the problem is mainly knowledge-related. If you know the concept but chose the wrong question, stayed too long, used a poor section approach or allocated attention badly, the problem is mainly strategic. A correct approach ruined by a slip is primarily an execution problem.
What should I do after identifying an error in a CAT mock?
In CAT mock test analysis, match the correction to the diagnosis. Relearn missing concepts, practise application gaps, use selection drills for poor question choice, use sectionals for pacing problems and timed simulation for execution errors. Then verify the correction in later practice or a subsequent mock instead of assuming that recognising the error has fixed it.
Should I take another CAT mock immediately after a bad mock?
Usually, not before extracting the useful information from the first one. Complete the analysis, choose the highest-priority corrections and do the relevant targeted practice or sectional work first. Another full mock is most useful when it can test whether those corrections are transferring to timed performance.
Should I change my CAT strategy after one poor mock?
A single poor result is not automatically evidence that the whole strategy is wrong. Diagnose what actually failed and change the smallest relevant variable first. Larger strategy changes are better supported by a recurring pattern across mocks or by a clearly identified structural problem.
How should I analyse VARC after a CAT mock?
Separate passage selection, question selection, reading errors, inference or scope errors, option elimination and Verbal Ability performance. Also inspect correct answers that depended on uncertain reasoning. The aim is to find whether the main problem was comprehension, answering the question, selection, pacing or execution.
How should I analyse DILR after a CAT mock?
Start with set selection. Review which sets you scanned, which you chose, how you represented the information, whether you read constraints correctly and whether you exited an unproductive set at the right time. Solvable sets that were never attempted can be as informative as sets answered incorrectly.
How should I analyse QA after a CAT mock?
Separate concept gaps from application, calculation, selection and pacing errors. For each wrong or skipped question, check whether you knew the concept, selected an efficient method and executed it accurately under time pressure. Correct but unnecessarily slow solutions should also enter the review.
Is retaking the same CAT mock useful?
It can be useful for learning, but it is weak as a fresh performance benchmark because prior exposure can affect the result. Re-solving individual questions, revisiting DILR sets or doing a delayed re-attempt can verify methods and retention. Treat the retake as practice rather than comparing its score directly with a first attempt.
How many CAT mocks should I track before judging a trend?
There is no scientifically required number. Useful patterns can appear after only a few mocks, while a longer series helps separate recurring behaviour from one-off fluctuations. PREPON's 20-mock tracker is a practical longer-horizon structure, not a rule that you must wait for 20 mocks before acting.
Should I compare CAT mock percentiles across different providers?
Use caution. A mock percentile is relative to that provider's participating test-takers, and providers can differ in population, difficulty and scoring context. Cross-provider comparisons can therefore be misleading. Your own recurring error patterns, section behaviour and longer-term trend are usually more comparable signals.
When should I ask a mentor to review my CAT mocks?
Mentor review becomes useful when the same error pattern keeps returning despite attempted fixes, one section remains persistently unstable, strategy keeps changing without evidence, practice and timed performance stay far apart, or you cannot identify the root cause yourself. The purpose is diagnosis and correction, not simply reassurance after a low score.
Conclusion
A mock is valuable not because of the percentile it displays immediately after submission, but because of what you learn and change before the next test. Run the cycle — Analyse, Review, Correct, Verify — after every mock, and let the trend across mocks, not any single result, tell you whether it’s working.
Mocks are steps in your preparation. They do not show whether you can do well in the actual test — and definitely not who you are. They are simply preparatory tools for your betterment.