Mock Analysis in 45 Minutes: A Last 30 Days Template

Strategy

In the last month, you may have time for fewer mocks than you would like, and no time at all for a three hour review of each. Yet the review is where most of the learning sits. A mock without analysis is just a long test.

This guide gives you a template that takes 45 minutes: a quick scorecard, a sort of every lost mark into a bucket, a repair of the biggest bucket, and a single change for the next mock. It is built for the final stretch, when time is short and decisions matter.

Why a Template Beats an Open Ended Review

Open ended reviews drift. You start with the first wrong question, spend twenty minutes on it, run out of energy, and never reach the last section. The learning is uneven, and the second half of the mock gets less attention than the first.

A template fixes the order and the time. Each part has a job and a time limit, so the whole mock gets covered. It also forces you to look at patterns, not just individual questions. A single wrong answer is a puzzle. Ten wrong answers of the same kind are a signal.

The last month adds pressure. Mocks are fewer, days are busy, and the temptation is to take another mock instead of reviewing the last one. That is usually the wrong trade. A reviewed mock teaches more than two unreviewed ones, because only the reviewed one changes what you do next.

The 45 Minute Template

Minutes	Part	Output
0 to 5	Scorecard	One line per section: time, attempts, accuracy
5 to 20	Bucket sort	Every lost mark tagged to a bucket
20 to 35	Repair	Biggest bucket questions redone and understood
35 to 40	Pattern log	Two lines on what the mock showed
40 to 45	Next step	One change for the next mock

Set a timer and keep to it. If you run out of time in a part, stop and move on, and note what you left. The discipline of the template is more valuable than finishing every detail.

Part One: The Scorecard

Start with numbers, but only a few. For each section, note your attempts, your correct answers, and the time you used. Compute accuracy as correct over attempts. That is enough to see the shape of the mock.

Look at the shape, not the total. Was accuracy high with few attempts, which suggests selection was too cautious? Was it low with many attempts, which suggests guessing? Did you run out of time before the section ended? The scorecard tells you which of these happened without any deep analysis.

A word about percentile. A mock percentile is relative to the people who took that mock, and it is not a prediction of your CAT result. Use it as a trend across your own mocks. If you want a rough range for a target, a CAT percentile predictor can give an estimate, but treat it as a range, not a promise.

Part Two: Sort Every Lost Mark Into a Bucket

This is the core of the template. Go through every question you got wrong or left unattempted, and tag it with one of five buckets. Do not solve the question yet. Only decide why you lost the marks.

The five buckets are concept, calculation, misread, selection and time. Concept means you did not know the method. Calculation means you knew it and slipped. Misread means you answered a different question from the one asked. Selection means you should not have attempted it, or should have attempted something else. Time means you ran out before you reached it, or rushed it.

Use a quick test for each. Could you have solved it with unlimited time and a fresh read? If no, it is concept. If yes, was the slip arithmetic? Calculation. Was it reading? Misread. Was it a bad choice of what to attempt? Selection. Was the clock the problem? Time. Tagging takes under a minute per question, and you will get faster.

Bucket	What it means	Typical fix
Concept	Method not known	Learn it, then practise a short set
Calculation	Known method, slip	Slow down, write steps, check
Misread	Wrong question answered	Underline the ask before solving
Selection	Poor choice of question	Practise a triage rule
Time	Ran out or rushed	Rehearse a section clock

Part Three: Repair the Biggest Bucket

Count the tags. The bucket with the most lost marks is your repair target. Spend fifteen minutes on the questions in it, not on the whole mock. Redo each properly, and write down the one step that went wrong.

If the biggest bucket is concept, learn the method now, and do two or three similar questions to confirm. If it is calculation, redo the questions slowly and note where you slipped. If it is selection, write the rule you should have used, such as park any question that needs more than a certain number of steps. If it is time, plan a section clock for the next mock.

Do not try to fix every bucket after every mock. Fixing the top one or two is realistic in forty five minutes. The others will come up in later mocks, and the pattern across several mocks will show which ones are persistent.

Part Four and Five: The Pattern Log and the Next Step

In five minutes, write two lines in a log: what the buckets showed, and what you will do differently. For example, most losses were misreads in DILR, so underline the ask before solving each set. Keep the log in one place, and reread the last three entries before each mock.

The next step should be a single change, specific and checkable. Avoid vague goals like be more careful. Choose actions like write the target quantity at the top of each DI question, or leave any RC question where I cannot predict an answer in thirty seconds until the end. One change is easier to follow under exam stress than five.

A single change per mock is also easier to evaluate. If you change one thing and the next mock improves in that bucket, you know the change worked. If you change five, you cannot tell which helped.

Using the Template Across the Last 30 Days

In the last month, you may take a mock every few days. The template then becomes a loop: mock, review, one change, mock. By the third or fourth loop, you will see which buckets are shrinking and which are stubborn, and you can plan the remaining days around them.

Fit it into your calendar. Our guide to the final month day by day plan shows how mocks and reviews fit alongside revision, and the article on what is confirmed and pending for CAT 2026 helps you keep the facts straight.

In the last week, shorten the template. Shrink the repair part to the single biggest error, and focus on the pattern log and a calm next step. Your aim then is not to learn new methods but to protect what you know. A CAT study planner can hold the review slots.

If a mock lands badly in the last week, resist the urge to take another one at once. Do the template, write the one change, and rest. A bad mock late in the month often reflects fatigue or a single section, and the template will show which. Panic reviews that run for hours rarely help, and they cost sleep you need.

Section Specific Notes

For VARC, the buckets often come down to misread and selection. Reviewing RC by the passage, not just the question, shows whether you lose marks in one type of passage. Our guide on reviewing a wrong RC answer in five steps goes deeper, and the article on why RC accuracy drops late in the section helps if your errors cluster at the end.

For DILR, the biggest bucket is often selection, since set choice decides the section. Note which sets you started and abandoned, and why. For Quant, calculation and concept dominate, and a short list of topics where you lost marks gives a clear plan.

Across all sections, confidence matters. Our article on confidence calibration explains why knowing what you can and cannot solve is a skill in itself, and the review is where you train it.