How to Solve CAT Quant Faster Without Skipping Steps

QUANT

Most speed advice in CAT preparation amounts to doing the same thing in a hurry, which is why it produces so many careless errors. An aspirant told to move faster writes less down, skips the verification step, and discovers at minute nine that the setup was wrong.

Real speed in quant does not come from compressing a method. It comes from arriving at the right method sooner, from having a standard way to set up each question family, and from not spending time on questions that were never going to resolve. None of those involves rushing, and all three are trainable.

Where the Time Actually Goes

Time a few questions honestly and the distribution surprises most aspirants.

Very little of a question is arithmetic. A far larger share is the phase before any writing happens, where you are working out what kind of question this is and which approach applies. That decision phase is where a slow candidate is slow.

A second large block is re-reading. Going back to the question to check what was being asked, or which quantity the answer refers to, is routine and it is almost entirely avoidable with one careful reading at the start.

The third is recovery. Time spent redoing a question because the setup was wrong dwarfs anything saved by writing less down, and rushed setups are the main cause of it.

The Four Real Speed Levers

Each of these reduces time without touching the quality of the method.

Recognition Is Built by Depth, Not Breadth

An aspirant who has done four hundred arithmetic questions sees a ratio problem and knows it is a ratio problem before finishing the sentence. One who has sampled six chapters lightly spends thirty seconds orienting, on every question. That gap is the difference between a comfortable section and a rushed one, and it was built by staying in chapters rather than by moving faster.

A Standard Setup Removes a Decision

Decide once how you lay out a time and work problem, or a mixture problem, and use it every time. Inventing the layout fresh on each question costs time and introduces errors. The gain here is larger than it sounds, because it converts an act of judgment into an act of recall.

Approximation Beats Computation More Often Than You Think

Many questions can be settled by deciding roughly what the answer should be and eliminating the options far from it. That is faster than any exact route and it is what a large share of multiple choice questions are built to reward. Practise it deliberately, because it feels unrigorous until it becomes reliable.

Phase of a question	Typical share of time	How to shorten it
Deciding what kind of question it is	Large	Depth in recurring chapters
Setting it up	Moderate	One standard layout per type
Computing	Small	Approximate where possible
Re-reading the question	Moderate	One careful first reading
Recovering from a wrong setup	Variable, often huge	Do not rush the setup

The Steps You Must Never Skip

Three parts of a solution look like overhead and are load bearing, and cutting them is what turns speed into errors.

The first is identifying what the question is actually asking for. A solved question answered for the wrong quantity is a complete loss, and this error is common precisely because it happens at the start when you are moving quickly.

The second is the written setup. Whatever your standard layout is, write it. The three seconds it costs are the insurance against the two minutes of recovery when a step goes wrong.

The third is the sanity check at the end. Does the answer sit in a plausible range? A ten second check catches the sign error and the misplaced decimal, both of which otherwise produce a confident wrong answer with a negative mark attached.

The Biggest Saving Is a Decision

Everything above is worth a few seconds per question. This is worth minutes.

Run the arithmetic on a real section. Take a paper of 66 questions worth 198 marks, with three marks for a correct answer and one negative mark for a wrong MCQ. A candidate attempting 63 of them at 41 percent accuracy gets roughly 26 right, worth 78 gross, and nets 54. The 37 wrong attempts cost 24 marks against leaving those questions blank.

Those 37 attempts also cost time, and that is the part relevant here. Minutes spent on questions that were never going to resolve are minutes taken from questions that would have. No amount of faster solving recovers them.

That is not an argument for a specific attempt count, since the right number depends on you and on the paper. It is an argument that speed and selection are the same conversation, and that treating them separately is why so much speed work produces nothing.

A Drill That Builds It

Speed responds to a specific kind of practice, and it is not simply doing questions under a timer.

Take twenty questions from a chapter you know. For each, spend fifteen seconds deciding the approach and writing only the first line of the setup. Do not solve. Then go back and solve them all, and check how often your first line was the right starting point.

That drill isolates the decision phase, which is where the time is, and gives you feedback on it directly. Solving questions end to end trains the whole process at once and gives you almost no information about which part was slow.

Run it once a week for a month and the recognition phase compresses noticeably. It is also short, which matters, because drills that take an hour get dropped.

The Second Method Habit

After solving a question correctly, ask whether a shorter route existed, and if it did, write down the trigger that should have pointed you to it. That trigger is the transferable part. A candidate who has collected fifty such triggers recognises routes that others have to derive.

Timing Your Own Phases

Once, deliberately, time ten questions in two parts: seconds until you began writing the setup, and seconds from there to the answer. Most aspirants find the first number much larger than they expected, which redirects the training. Our guide on building speed and accuracy together covers how to hold accuracy while the pace improves.

What to Do When a Question Runs Long

Even with good recognition, some questions will overrun, and having a rehearsed response to that is worth more than shaving seconds elsewhere.

Set a personal ceiling and know it before the section starts. When a question passes it, the decision is not whether you can still finish; it is whether finishing is worth what the remaining minutes would buy elsewhere. Those are different questions and only the second one has a useful answer.

The instinct that makes this hard is sunk cost. Three minutes into a question, a partly built solution feels close, and abandoning it feels like wasting the three minutes. Those minutes are already gone. The only live question is what the next three should buy, and a fresh question from a chapter you handle well is almost always the better purchase.

What Faster Should Feel Like

The end state is worth describing, because it is not what aspirants expect.

It does not feel rushed. It feels like fewer pauses. You read a question and the approach is already there, you write a setup you have written many times, you compute or approximate, and you check. The individual steps are not performed faster; there are fewer moments of hesitation between them.

It also feels calmer, because a candidate who recognises a question is not deciding under pressure whether they can handle it. Most of the stress in a timed section comes from uncertainty about the current question rather than from the clock itself.

If your speed work is making sections feel more frantic, it is the wrong kind of speed work. The right kind removes decisions rather than compressing them.

If your sections feel rushed despite reasonable solving speed, the constraint is usually selection or recognition rather than pace. A CAT preparation strategy review will separate them, and a personalised CAT preparation plan can keep the weekly drill in place.