ESAT guide
A 40-minute ESAT module strategy that actually survives the clock
How to pace a 27-question ESAT module: first pass, flagging, guessing, review time and the habits that keep one hard question from costing three marks.
Stop averaging the module
Forty minutes for 27 questions suggests about 89 seconds per question. That average is useful as a warning, but it is a poor plan. Some questions should take 25 seconds. Some may be worth 140. The skill is deciding which is which early enough.
Use the first pass to collect marks, not to prove toughness. If a question has not yielded a route after about a minute, select the most defensible option, flag it, and leave. The flag is a promise to future you, not a licence to burn the present.
A practical split
A simple target is to reach question 27 with five to seven minutes left. That does not mean rushing blindly. It means the first pass should be disciplined enough to leave a review window.
In that review window, return first to flagged questions where you have already eliminated options or found a partial route. Avoid reopening questions you guessed from nothing unless all higher-upside flags are done.
- 0-12 minutes: secure fast marks and avoid overworking early questions.
- 12-30 minutes: maintain pace; flag unresolved questions quickly.
- 30-40 minutes: finish the pass, then review the highest-upside flags.
Guessing is not giving up
Because incorrect answers are not penalised, a blank question has no strategic value. The point is not random guessing as a lifestyle. It is preserving a chance at the mark while protecting time for questions you can solve.
Use option shape. Are the answers positive and negative? Are they ordered? Do units eliminate some? Does an extreme case make one answer impossible? Even a weakly informed choice is better than a blank.
Measure the strategy, not just the score
After a mock, look at three numbers: questions correct, questions correct but slow, and questions wrong after excessive time. The last two are where strategy improves fastest.
Noetra's timing view is built for that distinction. A 7/9 topic with slow responses needs speed work. A 3/9 topic with fast wrong answers needs knowledge repair. They should not lead to the same revision plan.