Exam Pacing Calculator

Per-question pace and checkpoints from exam minutes and count.

School and GradesUpdated 2026-10-112 min read
Exam Pacing Calculator
Held back at the end for review.
Per question
...
Half checkpoint...
Buffered pace...

What it does

Exams are time budgets before they are knowledge tests. A 60 minute paper with 50 questions allows 72 seconds each, and students without that number drift: ten slow minutes early become a rushed final page. One division sets the pace for the whole sitting.

The tool above runs that division plus checkpoints. Enter minutes, questions, and a review buffer, and it prints per-question time, the half checkpoint, and the buffered pace. Defaults give 1 min 12 sec each with Q25 by 0:30, tightening to 1 min 6 sec with review held back.

College Board timing validates the math. Its SAT structure gives Reading and Writing 64 minutes for 54 questions and Math 70 for 44, and its blog states 1:11 and 1:35 per question. Both figures reproduce exactly: 3,840/54 = 71.1 and 4,200/44 = 95.5 seconds.

Checkpoints beat clocks. Knowing Q25 by 0:30 turns a vague hurry into a binary check: ahead or behind, move or stay. Michigan study guides advise rough schedules per section with review time planned, which is exactly the buffer line here.

How to use

  1. Enter total exam minutes.
  2. Enter the question count.
  3. Enter the review buffer to hold back.
  4. Read seconds per question first.
  5. Memorize the half checkpoint: question and time.
  6. At the checkpoint, move on if behind.

Formula

Sec per question = minutes x 60 / questions. Half: Q(questions/2) by minutes/2. Buffered pace = (minutes minus buffer) x 60 / questions.
minutes
Total exam minutes, 5 to 600.
questions
Question count, 1 to 1,000.
buffer
Minutes held back for review at the end.

College Board checks: 64x60/54 = 71.1 sec (1:11) and 70x60/44 = 95.5 sec (1:35), matching its published figures exactly.

Worked example

Example: 60 minutes, 50 questions

Defaults: 60 minutes, 50 questions, 5 minute buffer.

  1. Inputs: 60 minutes, 50 questions, 5 minute review buffer.
  2. Per question: 60 x 60 / 50 = 72 sec = 1 min 12 sec.
  3. Half: Q25 by minute 30.
  4. Buffered pace: 55 x 60 / 50 = 66 sec = 1 min 6 sec.
  5. Tool shows 1 min 12 sec, Q25 by 0:30, 1 min 06 sec with review.

Reference table

Pace benchmarks
ExamTime / QsEachHalf
SAT Reading/Writing64 / 541:11Q27 by 0:32
SAT Math70 / 441:35Q22 by 0:35
Classroom test60 / 501:12Q25 by 0:30
Final exam120 / 801:30Q40 by 1:00

Limits

  • Even pacing assumed. Mixed difficulty needs section splits.
  • Ignores reading load differences across subjects.
  • Buffer is a flat holdback, not a review plan.
  • Essay and multi-part items pace separately.

Common mistakes

  • No per-question number going in.
  • Burning buffer minutes on stuck items.
  • Skipping the half checkpoint glance.
  • Pacing the whole paper as one block.
  • Leaving zero review time at the end.

Try it yourself

Quick checks. Answers sit tucked under each question.

SAT Math: 70 minutes, 44 questions?

70 x 60 / 44 = 95.45 sec, shown as 1 min 35 sec. Half Q22 by 0:35.

Final: 120 minutes, 80 questions, 5 min buffer?

120 x 60 / 80 = 90 sec = 1 min 30 sec. Half Q40 by 1:00. Buffered 115 x 60 / 80 = 86 sec = 1 min 26 sec.

Questions

How is per-question pace figured?

Total minutes times 60 over questions. A 60 minute, 50 question test gives 72 seconds each.

What is the half checkpoint?

Half the questions by half the time. At 60 minutes and 50 questions: Q25 by 0:30.

How does the review buffer change pace?

Pace against total minus buffer: 55 minutes over 50 questions is 1 min 6 sec each.

What is SAT timing per question?

Reading and Writing 64 min / 54 (1:11 each); Math 70 min / 44 (1:35 each), per College Board.

What if a question sticks?

Skip and return. Banked easy points beat stuck minutes; the checkpoint tells you when to move.

Do sections pace separately?

Yes. Weight-heavy sections deserve proportionally more time; pace each section separately.

Sources

How this page was checked. The formula above was matched against the cited sources, and the worked example was run through the tool on this page before publishing. If you spot an error, contact us so we can fix it and note the correction.