Is Approximation Safe for CAT Quant TITA Questions?

QUANT

Approximation is the standard advice for CAT Quant, and it works because the options are usually far enough apart that a close answer identifies the right one. Then a Type In The Answer question arrives, there are no options, and the technique that has been saving you minutes all section suddenly has nothing to land on.

The honest answer is that approximation on these questions is not one thing. Some approximations are completely safe because the answer is an integer and your estimate lands nearest to it. Others are not safe at all, and the difference is knowable in advance rather than a matter of nerve. This piece draws that line precisely and gives you a decision rule for the moment you are holding an estimate and a blank box.

Why Approximation Works on MCQs and Not Here

The mechanism is worth stating because it explains the whole distinction.

On a multiple choice question you are not producing a value, you are selecting among five. If the options are spread widely, an estimate that is off by a few percent still points unambiguously at one of them. The options absorb your error, and the wider they are spread the more error they absorb.

A Type In The Answer question removes that cushion entirely. You type a value and it is either the value or it is not. There is nothing to round towards and no spread to exploit, so the same estimate that was decisive on an MCQ is now just a wrong number.

The Rule That Decides It

There is a single question that separates safe from unsafe, and it should be asked before you start computing rather than after.

Can the answer be anything other than a whole number? If the quantity being asked for is inherently an integer, a count of things, a number of people, a number of ways, then your estimate has somewhere to land. An estimate of 47.3 on a question whose answer must be an integer is telling you the answer is 47, provided your error is smaller than half a unit.

If the answer can be a decimal, there is nothing to round to. An estimate of 47.3 could be 47.2 or 47.4 and you have no way to tell. Approximation cannot be rescued here and the question needs exact computation or it needs leaving.

Error Compounds Faster Than It Feels

This is the part candidates underestimate, and it is why an estimate that felt careful arrives wrong.

Rounding once by a percent or two is small. Rounding at three successive stages, where each rounded value feeds the next, produces a total error considerably larger than any individual step, and multiplication compounds it faster than addition does. By the end of a four step chain an answer that needed to be within half a unit can easily be several units out.

The practical implication is that approximation is safest on short computations and least safe on long ones, which is the opposite of where candidates reach for it. The temptation to approximate is strongest precisely on the heavy multi-stage computation where it is least reliable.

Approximate to Decide, Compute to Answer

That distinction is the workable habit and it is worth building deliberately.

Early in a question, a quick estimate tells you whether the numbers will be manageable, whether a particular route will terminate, and roughly what magnitude the answer should be. All of that is decision support and none of it goes in the box.

Then, having chosen a route on the strength of the estimate, compute it properly. The estimate also gives you a free sanity check at the end: if your exact answer is nowhere near your estimate, one of the two is wrong and you have caught an error that would otherwise have shipped.

Situation	Approximation	What to do
MCQ, options far apart	Safe and fast	Estimate and select
MCQ, options close together	Unsafe	Compute, or eliminate on structure
TITA, answer must be an integer	Usable if error stays tight	Estimate carefully, round, enter
TITA, answer can be a decimal	Not usable	Compute exactly, or leave it
Any question, choosing a route	Always safe	Estimate freely, it never goes in the box

Check What Format the Answer Wants

A separate and entirely avoidable loss sits next to this one.

Type In The Answer questions sometimes specify a form: a whole number, a value to a certain number of decimal places, a particular unit. An answer that is mathematically correct and typed in the wrong form is scored as wrong, and candidates lose marks here through hurry rather than through mathematics.

Make the format check part of your one defined verification on every TITA question. It takes two seconds and it protects work you have already paid for.

Why an Uncertain Entry Always Beats a Blank

The marking here is asymmetric in a way that should change your behaviour, and many candidates know the rule without acting on it.

A correct answer is plus three, an incorrect MCQ is minus one, an unattempted question is zero, and Type In The Answer questions carry no negative marking at all. So an incorrect TITA response scores exactly what a blank scores, which is nothing, while a correct one scores three.

That means caution buys you nothing here. If you have worked a question and arrived at a value you are unsure about, entering it is free and leaving it blank guarantees zero. Candidates lose marks to a carefulness the marking scheme does not reward, and it is the cheapest habit in the section to fix.

What It Does Not Mean

One clarification, because the absence of a penalty gets over-read.

It does not mean Type In The Answer questions deserve priority in your attempt order, and it does not make them easier or faster. The asymmetry changes what you do at the end of a question you have already worked, not which questions you choose to work on.

Selection still runs on the same criteria as everywhere else: whether you recognise the type, whether you can see the end from where you are, and what the question will cost you inside a hard 40 minute sectional limit.

Building the Judgement in Practice

Knowing when an estimate is tight enough is a calibration skill, and calibration comes from feedback rather than from rules.

The drill is straightforward. On practice questions, write down your estimate before computing exactly, then compare the two. Over a few dozen questions you develop a real sense of how much your rounding habits actually cost, and that sense is what the exam needs rather than a general belief that you are careful.

Most candidates discover their estimates are tighter than they feared on short computations and much looser than they assumed on long ones, which is precisely the distinction this piece rests on. Having seen it in your own numbers, the rule stops being advice and becomes something you know.

Fluency Decides How Often This Comes Up

There is an upstream point worth making, because it reduces how often the question arises at all.

Candidates reach for approximation most when a computation is long, and computations are long partly because the route chosen was long. A candidate fluent in a question type frequently sees a shorter path where a less fluent candidate grinds, and the short path often needs no approximation.

Arithmetic and Algebra have historically been the largest contributors to QA, so concentrated work there reduces the number of questions where you are forced into a heavy multi-stage computation in the first place. That is a better fix than getting braver about rounding.

The Summary

Approximation works on multiple choice questions because widely spread options absorb your error. Type In The Answer questions remove that cushion, so the same estimate that was decisive becomes a wrong number.

The rule that decides safety is whether the answer must be an integer. If it must, a tight estimate rounds to the right value provided your total error stays under half a unit. If the answer can be a decimal, there is nothing to round to and the question needs exact computation or leaving. Remember that error compounds across steps, so approximation is safest on short computations and least safe on the long ones where the temptation is strongest.

Approximate to choose a method and to sanity check, then compute exactly to produce the value. Check the format the question asks for. And whatever you end up holding, enter it, because an incorrect Type In The Answer response costs exactly what a blank costs while a correct one is worth three marks.

If you have been carrying one approximation habit across both question formats, that is a cheap correction with an immediate return. A CAT preparation strategy review will show where your estimates are costing you, and a personalised CAT preparation plan builds the fluency that makes heavy computation rarer.