Guide
Time management inside a 3-hour paper
By the MyAbhyasa team ·
Most candidates lose more marks to the clock than to the syllabus — questions they could solve but never reached, or rushed in the final ten minutes. Exam time management is a small set of rules, all trainable in mocks.
What actually goes wrong with time in an exam?
The classic failure is sequencing, not speed: ten minutes sunk into one stubborn early question while several one-minute questions at the end of the paper go unseen. The marks lost are not on the hard question — they are on the easy ones the clock took.
The fix is accepting that a paper is not meant to be attempted in printed order. Question papers mix difficulties; your attempt order should sort them.
How does a multi-pass strategy work?
Pass one: move through the whole paper attempting only what yields quickly, flagging anything that resists. This banks the easy marks early, guarantees every question gets seen, and builds momentum instead of early-paper panic.
Pass two: return to flagged questions with the remaining time, now knowing exactly how much is left and with the easy marks already secured. A final few minutes go to transfer checks — and in a no-negative exam like MHT-CET, to ensuring nothing is left blank.
What is a per-question time cap?
A hard rule set before the exam: if a question exceeds roughly twice its fair share of time and the end is not in sight, flag it and move. The decision is made in advance precisely because mid-exam judgement is what sunk cost corrupts.
A question's fair share is simply time divided by questions — about 54 seconds in a 200-question CET paper, a minute flat in NEET's 180-question, 3-hour paper. The cap is not abandoning marks; pass two exists to come back with a calmer head.
How do you train pacing before the real exam?
Only in full-length timed mocks — pacing is a physical skill, and untimed practice does not exercise it. Apply the same pass structure and cap rule in every mock until checking the clock at section boundaries becomes automatic rather than anxious.
After each mock, audit the time casualties: unseen questions, rushed endings, any single question that ate multiple shares. One pacing experiment per mock — a different attempt order, a stricter cap — and keep what measurably reduces the casualty count.