How to Use Mock Tests for CAT Preparation: A Practical Guide

The short answer: use CAT mocks to run experiments on your own strategy, not to collect scores. After every mock, record attempts and accuracy for each section, sort every wrong answer by cause, redo what you skipped without a clock, and change one thing before the next mock. This guide shows how, with a worked example and checklists.

Why a CAT mock is not like other mocks

In many exams a mock shows you how much you know. CAT's three sections are each limited to 40 minutes, with 24, 22 and 22 questions in CAT 2025 and no way back once a section ends. The score therefore depends on choices you make during the section: which passages, which sets, which questions. A mock is the only safe place to practise those choices. If you use mocks only to see a number, you waste most of what they offer. (For the format itself, see the CAT exam pattern.)

What to record after every mock

Keep a log with one row per section per mock. These columns are enough:

The last column is the one most candidates omit, and it is the one that turns a log into a learning tool.

A worked example: three mocks, one decision

The numbers below are illustrative, to show how to read a log. Suppose a candidate records these for the Quantitative Ability section across three mocks:

Reading the table: in mock 1 the candidate attempted 14 questions at 57% accuracy and lost five marks to wrong MCQs. In mock 2 they attempted three fewer questions and scored three marks more. In mock 3 they attempted one more question than in mock 2, with the same number of wrong answers, and gained three more marks. The candidate's accuracy rose from 57% to 73% to 75% while attempts fell and then rose slightly. A candidate looking only at attempts would think they were doing worse in mock 2; one looking at net score and accuracy sees a clear improvement.

The decision this supports: hold the same selection discipline and test one change, for example allowing yourself one extra question in the second pass if time permits. If accuracy stays above 70% with the extra question, keep it. If it falls, revert. That is how a log guides action.

Sort every wrong answer by cause

A wrong answer is only useful if you know why it happened. Use these categories:

• Concept gap. You did not know the method. Action: study the topic and solve 10 to 15 questions on it within a week.
• Calculation error. The method was right and the arithmetic wrong. Action: daily calculation drills and written steps.
• Reading error. You missed a condition or answered the wrong question. Action: underline the ask and the constraints before solving.
• Selection error. You spent too long on something not worth it, or skipped something you could have solved. Action: time ceilings and practice abandoning.
• Guessing error. You marked an MCQ without any elimination. Action: a rule that you guess only after eliminating at least one option.
• Pressure error. You knew it, but rushed near the end of the section. Action: practise stopping on the clock, with a two-minute buffer.

Count the categories across your last three mocks. If one dominates, that is your next week's work. If errors are spread evenly, the likely problem is generic fatigue or pace, and the fix is to adjust the time plan rather than to study.

Review each section differently

VARC: review the passages, not just the answers

For each wrong RC answer, find the line in the passage that makes the right option correct and the line that rules out yours. Write one sentence on why you were drawn to the wrong option: was it too extreme, true but not stated, or out of scope? If you can name the pattern, you will recognise it next time. Then look at passages you skipped and ask whether they were genuinely dense or only unfamiliar. The detailed method is on the VARC page.

DILR: redo the sets you skipped

The most valuable DILR review is to take a set you abandoned or skipped, and solve it without a clock. Note how long it takes and what the entry point was. Often you will find that the set was solvable and that a cleaner diagram or a case analysis would have opened it up. Compare your prediction at the time ("looks hard") with the reality; over ten mocks this calibrates your triage. See the DILR page for a worked set.

QA: tag each question by family

Tag every QA question with a family (percent chains, remainders, counting, algebraic identities, geometry). After four mocks, tally your errors by family. You will typically find that two or three families account for most of your lost marks. Then spend a week on topic tests for those families, as outlined on the Quantitative Aptitude page.

Experiments worth running

Because the best strategy is individual, use mocks to test decisions one at a time:

Change one variable per mock. If you change two at once, you cannot tell which helped. For an example of a month of such experiments, see our CAT mock test strategy.

How often to take mocks

Early in preparation, mocks are less useful than topic and sectional tests, because you do not yet have the material to apply under pressure. Take one diagnostic mock in the first month or two. Then use sectionals while you study. About four months before the exam, move to one full mock a week and give each a full day of review. In the last three weeks you can increase to two a week, but no more. See how many mock tests you should take for the general argument.

Common mistakes to avoid

• Treating the mock percentile as a forecast. It compares you with the people who took that mock. Use it, at most, as a rough signal.
• Taking a mock every day. You will not have time to review, and the same errors will repeat.
• Reviewing only the wrong answers. Questions you guessed correctly, and questions you solved slowly, are future errors.
• Not enforcing the clock. If a test has one 120-minute clock, practise stopping each section at 40 minutes yourself.
• Changing strategy after one bad mock. A single paper is noisy. Look at a three-mock average.
• Skipping the debrief notes. Write how each section felt within an hour of finishing, before you look at solutions.

A checklist for the 24 hours after a mock

1. Within one hour: note how each section felt, which questions you guessed, and where you lost time.
2. Fill in the log for each section.
3. Classify every wrong answer by cause, and mark right answers that were lucky or slow.
4. Redo skipped DILR sets and QA questions without a clock.
5. Re-read the passages you got wrong, finding the supporting lines.
6. Write the one change you will test in the next mock.
7. Add distinct lessons to your error log and schedule topic repair for the top two causes.

Free and paid mocks: how to choose

For a baseline and to sample an institute's style, start with a free test; our free CAT mock tests page explains how to use one. For volume, look for a series that enforces sectional timing, mixes MCQs and type-in questions and provides explanations that show methods. The guide on how to choose a test series and the list of tests on the CAT mock test hub can help you compare. Check the current pattern and rules in the official CAT notification; TestMint's tests are independent practice papers and not official IIM papers.