CAT Preparation Strategy: The 4-Step Decision Protocol

Strategy

It is minute twenty two of a forty minute CAT section, and the question on screen is not hard, it is just unfamiliar. Two seconds ago you were moving well. Now you are rereading the same line for the third time while the timer keeps counting down.

That pause is not a knowledge problem. It is a decision problem, and it is the one part of CAT preparation strategy that most study plans never touch: how you choose, in real time, when to commit to a question and when to cut your losses and move. Get that call right, consistently, and the same syllabus knowledge starts turning into a noticeably higher attempt count.

The 40 Minute Pressure Curve

Decision quality in a CAT section does not fall in a straight line. It holds steady for the first ten to twelve minutes, drifts through the middle stretch as fatigue and time awareness build, and then drops sharply in the final eight to ten minutes as the clock becomes the loudest thing in the room.

That late drop is where good students lose marks they should have kept. Not because a question got harder, but because the part of the brain that weighs a call calmly is now competing with a countdown. The fix is not to think faster. It is to remove thinking from the moments that do not need it, and protect it for the ones that do.

Watch for these signals in your own mocks. They show up well before the section ends, and catching them early is what gives the protocol below room to actually work.

• You have reread the same line three or more times without extracting new information.
• You keep glancing at the timer instead of at the question in front of you.
• You cannot say, in one sentence, what your current approach to the question actually is.
• You are solving out of order but cannot explain why you picked this particular question next.

Why Pressure Distorts a Good Call

Three specific habits explain most of the time lost to pressure, and none of them are about being slow at maths or reading. They are about how the brain behaves once the clock feels louder than the question. Once you can name a habit while it is happening, it loses most of its grip, which is the entire point of walking through all three here in plain terms.

Anchoring on the First Number

The first value you notice in a Quant question or the first line you read in a passage tends to set your whole approach, even when it turns out to be the wrong starting point. Under pressure, going back and restarting from scratch feels expensive, so students keep pushing an approach that was flawed from the first step. The honest fix is small: treat the first read as information gathering only, and make the actual approach decision a separate, deliberate second step.

The Sunk Cost Reread

You have already spent ninety seconds on a question, so rereading it a fourth time feels like progress. It rarely is. The reread is usually the mind looking for permission to keep going rather than genuinely searching for new information. A useful test is to ask, honestly, whether the last read surfaced anything you did not already know. If the answer is no, the next read will not either.

The Panic Skip

The opposite failure is skipping too early, before the 20 second gate has actually run. A question that looked unfamiliar for two seconds gets abandoned, and a mark that was genuinely reachable is left on the table because the skip decision was made from anxiety, not from a real checkpoint. This is the failure the protocol below is built to catch first, because it costs marks silently, without ever feeling like a mistake in the moment.

How the Protocol Changes by Section

The four checkpoints stay fixed, but what counts as a visible approach looks different depending on the section you are in. Use this as a quick reference while you practice the protocol on real sets.

Section	What Commit Looks Like	What Cut Looks Like
Quant	You can name the formula or setup within 20 seconds	You are still deciding which concept even applies
VARC	You can locate the relevant line in the passage on one scan	You are rereading the whole passage a second time to find one detail
DILR	You have placed at least two data points on a rough grid	Ten minutes in, the grid still will not hold consistently

A Worked Example: Two Students, One Question

Two students, similar prep level, hit the same DILR set in the same mock. Student A reads the question once, cannot see a workable arrangement within 20 seconds, marks it and moves on. Ninety seconds later she is solving a set she can actually finish.

Student B rereads the same set three times, convinced the pattern is one more read away. He solves it eventually, four minutes later, and then has to rush the next two sets to make up the time. Same input, same difficulty, very different outcome, purely because of when each of them chose to commit.

Neither student is more talented than the other. The gap between them is entirely a decision gap, made in the first twenty seconds of the set, and it is the kind of gap that shows up on a scorecard as a section level dip even though nothing about their underlying DILR ability actually changed that day.

Common Mistakes That Break the Protocol

The protocol only works if you actually run it the same way every time. Two habits quietly undo it mid-section, even for students who know the four checkpoints by heart.

Rereading Because It Feels Safer

Rereading feels productive because you are doing something. But if Checkpoint 2 already told you the approach is not visible, a fourth read is not new information, it is a stall dressed up as effort.

Treating Every Question Like the Last One

Some questions genuinely deserve extra time because the payoff is high and you are close. The mistake is treating every question that way, as if this were the only one left in the section, when there are eighteen more waiting. Reserve genuine extra time for the two or three questions each section where you can already see you are close, not for every question that simply feels important in the moment.

Drilling the Protocol Before Test Day

Knowing the four checkpoints is not the same as being able to run them under real pressure. The protocol has to become automatic well before test day, which means practicing it deliberately rather than hoping it shows up on its own.

Before a Mock

Pick one section and run a timed set where you say each checkpoint out loud, even quietly, as you hit it. It feels slow at first. Within a few sessions it becomes background noise, which is exactly the point. Chapter level reps make this faster to internalise, so it helps to practice CAT questions by chapter with the protocol running in the background rather than only inside full mocks.

Before the Real Exam

In the final week, stop introducing new checkpoint variations. Run the same four steps on every practice set so the sequence feels boring and automatic by the time you are actually sitting the exam. If Checkpoint 2 keeps failing on the same handful of Quant formulas, a quick pass through the CAT formula and shortcut sheets the week before your mock closes that gap faster than a fresh reread ever will.

Fit the Protocol Into Your Larger CAT Preparation Strategy

The Commit or Cut Protocol solves what happens inside a single question. It does not replace the bigger questions your CAT preparation strategy still needs to answer: how many sections to attempt in what order, what your realistic attempt target is, and how that target maps back to the percentile you are actually chasing.

Those two layers work together. A clean decision protocol protects the minutes your section strategy has already budgeted for you, while a personalised CAT preparation plan makes sure those minutes are pointed at the right sections in the first place. If you already know your target score, running it through a CAT percentile predictor can tell you how much room the current plan actually leaves for a slow question here and there.

Before your next mock, run through this short checklist. It takes less than a minute and it catches most of the ways the protocol quietly slips during a real section.

1. Did you say each checkpoint to yourself, even silently, on the first five questions of the section.
2. Did you actually watch a clock for Checkpoint 2, rather than estimating twenty seconds in your head.
3. Did you log a one word note on every question you cut, so you are not solving the same call twice.
4. Did your last question of the section get the same four checkpoints as your first, with no shortcuts.