• Practice
  • About 13 min
  • 5 practice questions

Spotting time-sink questions and cutting your losses

Recognise questions likely to take far more than your budget, tell a worthwhile set from a trap, and stop on a question before it costs you several others.

If something looks wrong, please tell us.

Every paper has a few questions that take three, four or five times the average. They are not always the hardest in the paper; often they are just long. A student who can recognise them within the first few seconds and decide calmly what to do with them gains minutes that others lose. This lesson sharpens the skip rule from the Foundation course into a practical skill.

Signals of a time sink

Common time-sink signals
SignalQuick testUsual Round 1 decision
Long setup with many conditionsMore than about five conditions to hold in mindMark; return if time allows
Heavy arithmetic with awkward numbersSeveral multiplications or divisions with no shortcut visibleMark unless you see a shortcut
Data spread across tables or chartsYou must combine figures from two or more placesMark, or attempt if it is a set
Several statements to verifyEach statement needs its own checkAttempt only if most statements are familiar
A type you have never practisedNo method comes to mindMark
Your answer is not among the optionsYou have already worked it onceMark; do not redo it now

A set is different from a single question

A reading passage, a puzzle or a data table often carries several questions. The setup takes time, but that time is shared. A long single question has no such sharing. Before skipping a set, do the arithmetic.

Worked example 1: Sameer weighs a puzzle

Sameer, a BA student in Ranchi, works on an illustrative paper with a 36-second budget. He meets a seating puzzle with 5 questions, and later a single long question.

  1. The puzzle: he estimates 2 minutes (120 seconds) to set up the arrangement, then about 24 seconds per question. Total: 120 + 5 × 24 = 120 + 120 = 240 seconds = 4 minutes.
  2. Per question: 240 ÷ 5 = 48 seconds. The budget for 5 questions is 5 × 36 = 180 seconds, so the set is 60 seconds over budget.
  3. The single question: it looks like 3 minutes = 180 seconds, which is 180 ÷ 36 = 5 questions' worth of budget for 1 question.
  4. Decision: he attempts the puzzle in Round 1 because he is comfortable with this type and the cost per question is only 12 seconds above budget. He marks the single question for Round 2.

Cutting your losses

The hardest moment is not recognising a time sink before you start, but leaving one you have already begun. Two minutes in, it feels wasteful to stop. But the two minutes are spent either way; the only real decision is about the next minute. Use the double-budget rule: once you are at about twice your budget, write down where you reached, mark the question and move on. Your note means Round 2 does not start from zero.

Worked example 2: Lata reads her mock log

Lata, a B.Ed. graduate in Kolhapur, records how long each question took in an illustrative 60-minute, 100-question mock (budget 36 seconds). She finds that 4 questions took 12 minutes in total, and she got only 2 of them right. At the end, 15 questions were never seen.

  1. Cost in budgets: 12 minutes = 720 seconds. 720 ÷ 36 = 20 questions' worth of time.
  2. Cost per mark earned: 12 minutes ÷ 2 correct = 6 minutes per correct answer.
  3. What the unseen questions needed: if even 10 of the 15 were average, 10 × 36 = 360 seconds = 6 minutes, half of what the 4 questions took.
  4. Her fix for the next mock: a hard cap of 72 seconds (twice the budget), after which she marks the question and moves on.

Time already spent is gone. The only question is whether the next minute is better spent here or elsewhere.

Key takeaways

  • Learn the signals: long setups, heavy arithmetic, scattered data, many statements, unfamiliar types, an answer not in the options.
  • Work out the cost of a set per question before skipping it; shared setup can make it worthwhile.
  • A single question at five times the budget is rarely worth it in Round 1.
  • Stop at about twice your budget, note where you reached, and mark it.
  • Use a mock log to find your own time sinks and set a personal cap.

Check your understanding

  1. 1. Which of these is a strong signal that a question is a time sink?

    1. It is a one-line question on a familiar topic
    2. It asks for a definition you know
    3. You worked it once and your answer matches none of the options
    4. It is the first question of a section
    Show answer

    Answer: C. An answer not in the options means an error somewhere; finding it can take a long time, so mark it rather than redoing it at once.

  2. 2. A data set has 5 questions. Setting it up takes 100 seconds and each question then takes 20 seconds. What is the average time per question for the set?

    1. 40 seconds
    2. 20 seconds
    3. 100 seconds
    4. 60 seconds
    Show answer

    Answer: A. Total = 100 + 5 × 20 = 200 seconds, and 200 ÷ 5 = 40 seconds a question.

  3. 3. With a 45-second budget, 3 questions took you 9 minutes. How many questions' worth of budget is that?

    1. 3
    2. 9
    3. 20
    4. 12
    Show answer

    Answer: D. 9 minutes = 540 seconds, and 540 ÷ 45 = 12.

  4. 4. Why can a set of questions be worth attempting when a single long question is not?

    1. Sets always carry extra marks
    2. The setup time is shared across several questions
    3. Sets are always easier than single questions
    4. Sets cannot be skipped and returned to
    Show answer

    Answer: B. One setup serves several questions, so the time per question can stay near the budget.

  5. 5. Your budget is 40 seconds. Under the double-budget rule, when should you stop and mark a question you are stuck on?

    1. At about 40 seconds
    2. At about 2 minutes
    3. At about 3 minutes
    4. At about 80 seconds
    Show answer

    Answer: D. Twice the budget is 2 × 40 = 80 seconds.

Privacy · Terms · Refunds · Delivery