Exam Time Management: Improve Speed Without Losing Accuracy

Improve exam time management by measuring attempts and correct answers separately rather than by the total score, then setting a time budget per question and a fixed rule for abandoning the ones that overrun. A raw score cannot tell you whether you were too slow or wrong, and the two have opposite repairs.

Speed is trained after accuracy, not alongside it. This guide covers how to measure the trade-off, set per-question budgets, when to skip, and how an error log turns running out of time into a list of fixes.

Why does a raw score hide the real problem?

Because two candidates with the same score can have opposite problems. One attempts 60 questions out of 100 and gets 55 right. The other attempts 95 and gets 57 right. Their scores look similar; their preparation for next month should look nothing alike.

The first candidate knows the material and cannot get through the paper, so the fix is pace: tighter budgets, a skip rule, and drilling the question types that eat time. The second is fast and unreliable, so the fix is method accuracy, and under negative marking their speed is actively costing marks.

Work out which one you are before changing anything. Those are example figures illustrating the split, not benchmarks to aim at, and you should calculate your actual score using the official marking rules for your exam rather than assuming a percentage of correct answers is your result.

How do I measure speed and accuracy separately?

Record three numbers from every mock test: questions attempted, questions correct, and time spent per section. Everything else is derived from those.

Attempt rate is attempts divided by total questions; attempt accuracy is correct answers divided by attempts. A low attempt rate with high attempt accuracy is a speed problem. A high attempt rate with low attempt accuracy is an accuracy problem. Both low is a preparation problem rather than a timing one, and no pacing strategy will fix it.

Add one habit: note the time at each section boundary, or every twenty questions if the paper is not sectioned. A single end-of-paper total hides the fact that you spent half the time on the first third. The full recording process is in the guide to analysing mock tests with an error log, and the error log CSV already has the columns.

What is a per-question time budget?

A per-question time budget is a target working time for each question type, set in advance so that pace decisions are made before the exam rather than during it. Start from the arithmetic: section time divided by number of questions gives the average you cannot exceed overall. Then vary it deliberately, because treating every question as average is what causes overruns.

Two rules make the budget usable: build it from your own timed data rather than an ideal figure, and express it in whole numbers you can check against a clock without arithmetic. Adjust it after every mock, because a budget you consistently miss is a wish, not a plan.

What is the skip-and-return rule?

The skip-and-return rule is a pre-agreed cut-off: when a question exceeds a set multiple of its budget, commonly twice, you mark it, move on, and come back only if time remains after the paper is complete.

It works because the decision is made in advance. Mid-paper, four minutes into a question, abandoning it feels like wasting those four minutes, so you spend two more. That sunk-cost trap costs more marks than almost anything else in a timed paper.

Three details make the rule practical:

• Mark skipped questions in two ways: ones you could probably finish quickly, and ones you should not return to at all. On the second pass you only want the first group.
• Keep the answer sheet aligned. If your exam uses a separate answer sheet, skipping risks misalignment, so check the numbering after every skip.
• Decide in advance whether to guess. That depends on the official marking rules for your exam, including whether wrong answers carry a penalty. Look them up rather than assuming.

Should I train speed or accuracy first?

Accuracy first, in almost every case. Speed applied to a method you get wrong produces wrong answers faster, and where negative marking applies it converts effort into lost marks. There is no version of exam strategy where being quickly wrong is an advantage.

The sequence that works: get the method correct untimed, make it reliable across varied examples, then tighten the clock in stages. Accuracy that only appears with unlimited time is not yet accuracy; it is a method you can reconstruct rather than execute.

The exception is an attempt rate so low that whole sections go untouched. Pace work is then urgent, but the response is still not to rush everything: identify which question types consume your time, and either drill them or skip them by rule.

How do I train speed once accuracy is stable?

Tighten the clock deliberately, in a sequence, and check accuracy at each stage rather than only at the end.

1. Establish your untimed baseline. Solve ten questions of one type with no clock, and record both accuracy and the time each actually took.
2. Set the first target at your own median time, not at an ideal. If your median is 110 seconds, the first target is 110 seconds, which you will already meet half the time.
3. Run a timed set of ten at that target. Record attempt accuracy. If it holds, tighten by a small step, perhaps ten seconds.
4. Stop tightening the moment accuracy falls. That is your current ceiling for this question type, and pushing past it trains errors.
5. Return to untimed practice for the types that broke, because the failure is method reliability, not pace.
6. Repeat with mixed sets. Speed on a labelled set is easier than speed on a real paper, since identification takes time too. Mixed sets are covered in the guide to interleaved practice schedules.
7. Confirm in a full-length mock. Section-level pace is the only measurement that includes fatigue and section transitions.

An example progression for one question type might run three weeks: untimed to fix the method, then timed at the median, then timed in mixed sets. Adapt it to your own baseline rather than copying the weeks.

How does an error log separate "too slow" from "got it wrong"?

By forcing a second, untimed attempt before you write anything down. Reattempt every wrong or unattempted question with no clock. If you now solve it comfortably, the original failure was timing or pressure. If you still cannot, it is knowledge or method. Record which, because the repairs share nothing.

The last row matters. A question you correctly chose not to attempt is a good decision, not a failure, and treating every blank as a loss is how candidates talk themselves into abandoning the skip rule.

Track the counts in each category across several mocks. If "too slow, solved untimed" dominates, your knowledge is fine and pace is the project. If "wrong, still wrong untimed" dominates, no amount of timing practice will help. That distribution is part of tracking study progress metrics.

How should I plan the order I attempt sections in?

Only where the exam permits it, and always the same way twice before you commit. Check your exam's rules on section locking and navigation first, since many computer-based tests do not allow free movement between sections.

Where you do have a choice, a common approach is to take a section you are quick and reliable at early, to bank marks and settle nerves, then move to the heavier section while fresh, leaving your weakest for last with a firm time limit. Test that order in two mocks before adopting it, and compare section-level accuracy rather than how it felt.

Whichever order you choose, rehearse it as a whole paper in one sitting. A full-length mock is one continuous block in the calendar, with a second block immediately after for analysis, as argued in the comparison of Pomodoro and time blocking. In MyStudyPlanner, the mock test and its analysis can sit as two linked to-do items on the planner calendar, so the analysis is scheduled rather than optional.

What are the most common time-management mistakes?

• Chasing the sunk cost. Continuing a question because of the time already spent. The skip rule exists precisely to override this.
• Training speed on unreliable methods. Fast and wrong is worse than slow and right, especially under negative marking.
• Only measuring the total score. Without attempt rate and attempt accuracy, you cannot tell which problem you have.
• Ignoring the clock until the last section. Check the time at fixed points, not when panic prompts it.
• Guessing without knowing the marking rules. Whether a blank beats a wrong answer is an exam-specific fact you should look up, not estimate.
• Practising only untimed. Accuracy without a clock does not transfer automatically to a timed paper.
• Changing strategy after one bad mock. One test is a noisy sample. Look at the pattern across three before rebuilding your approach, especially in the final month of preparation.

Frequently Asked Questions

How do I measure speed and accuracy separately?

Record three numbers from every mock test: questions attempted, questions correct, and time spent per section. Attempt rate is attempts divided by total questions, and attempt accuracy is correct answers divided by attempts. A low attempt rate with high accuracy is a speed problem; a high attempt rate with low accuracy is an accuracy problem.

Should I train speed or accuracy first?

Accuracy first, in almost every case. Speed applied to a method you get wrong simply produces wrong answers faster, and in exams with negative marking it actively costs marks. Once you can solve a question type correctly without time pressure, start tightening the clock in stages rather than all at once.

What is the skip-and-return rule?

Set a cut-off for each question, commonly twice its time budget. When you hit it, mark the question, move on, and return only if time remains at the end. The rule works because it is decided before the exam, when you are calm, rather than mid-paper when sunk time makes abandoning a question feel wasteful.

How much time should I spend per question?

Divide the section time by the number of questions to get an average, then vary it deliberately by type. Short factual or vocabulary items should take well under the average, multi-step calculations more, and comprehension needs reading time budgeted separately. Build the budget from your own timed data rather than an ideal figure.

How do I tell a timing problem from a knowledge problem?

After the test, reattempt every wrong or unattempted question without a clock. If you now solve it comfortably, the original failure was timing or pressure. If you still cannot solve it, it is a knowledge or method gap. The two need completely different repairs, so record which one applies.

Why does my accuracy drop when I speed up?

Usually because the method is not yet automatic, so speed removes the checking steps you were relying on. The fix is not to slow down permanently but to make the method reliable through focused practice, then reintroduce time pressure in stages, watching whether accuracy holds at each stage.

Your next step

Take your most recent mock test and calculate three numbers: attempt rate, attempt accuracy, and the minutes spent on questions you never answered. Then reattempt every wrong and unattempted question untimed, sorting them into "too slow" and "got it wrong". That sorted list, not the score, tells you what to practise this week.