How to Analyse a CAT Mock Properly

--- page_id: R0517 route: /resources/preparation-guides/how-to-analyse-cat-mock title: "How to Analyse a CAT Mock Properly" card_description: "A mock is useful only if analysis produces 2–3 changes for the next test." content_status: humanized_v6 ---

# How to Analyse a CAT Mock Properly

Finishing a mock is not the end of the test. In many weeks, the analysis matters more than the score. If the next mock is taken with the same question-selection habits, the same RC traps and the same rushed calculations, you have collected another number—not trained.

Give the mock a job

A mock is useful only if analysis produces 2–3 changes for the next test.

Early mocks can diagnose. Later mocks can test pacing, selection, endurance or a change from the previous test. A mock without a purpose is easy to misuse.

Read the score backwards

Suppose you score 42 in a mock. Do not immediately set a target of 60 and add new chapters. First find where the marks leaked. Four poor MCQ attempts, one stubborn DILR set and an RC chosen despite weak comprehension can explain a large part of the gap. The next score increase may come from deleting bad decisions.

Go through the paper in four buckets: good attempts, bad attempts, missed easy questions and genuine knowledge gaps. Those four buckets point to different fixes.

Cadence

Analysis should often take at least as long as the mock; deep reviews can take 2–4 h.

Frequency should rise only when analysis quality survives. If taking another mock means skipping the review of the last one, the extra test is usually the wrong choice.

What belongs in the analysis sheet

• Easy misses
• Avoidable negatives
• Time sinks
• Selection mistakes
• Repeated error tags

Record only what can change behaviour.

Why mock plans fail

• Reading solution immediately. Ask what in the plan makes this behaviour easy to repeat, then change that condition.
• only noting topic weakness. Ask what in the plan makes this behaviour easy to repeat, then change that condition.
• tracking 15 metrics with no action. Ask what in the plan makes this behaviour easy to repeat, then change that condition.

Recovery rule

If analysis feels overwhelming, analyse wrong+skipped-easy first, then one section deeply.

The objective after a poor mock is not to feel better. It is to make the next mock meaningfully different.

One useful discipline

Before the next mock, write the two behaviours you are testing. After the mock, check those first. This prevents the score from hijacking the entire review.

Separate score from diagnosis

Two mocks with the same score can tell very different stories. One may have strong accuracy but too few attempts; another may have enough attempts but poor selection.

Track the mechanism behind the score. The moment you know whether the bottleneck is knowledge, selection, speed or accuracy, the next week's plan becomes much easier to design.

This is also why mock count alone is a poor badge of preparation. Twenty well-analysed mocks can be more useful than forty rushed ones.

Related next steps

• OYM Analysis
• Low Mock Score
• Accuracy

Do not turn the resource library into another syllabus. Read what you need, apply it, then return to practice.