The 2026 PMP exam gives you 240 minutes for 180 questions — 80 seconds each on paper. In practice, nobody spends 80 seconds on every question, and the people who fail on time don't fail evenly: they burn twenty extra minutes in the first hour, then guess through the last thirty questions. Pacing is a plan you make before you sit down. Here's the plan.
Know the shape of the exam
Three things define the 2026 clock:
- 180 questions, 240 minutes. Ten of the 180 are unscored pretest items, but you can't tell which, so every question gets treated as real.
- The case-based section comes first. The heaviest reading load on the exam sits in your freshest hour — and your slowest-feeling one, because case questions take longer by design.
- Two optional 10-minute breaks divide the exam into blocks. The clock stops during a break, but there's a catch: once you leave a block for a break, you cannot return to its questions. Flags don't survive the break.
75 free questions, scored against the new domain weights. No card required.
Per-question budgets by type
An even 80 seconds is the wrong model. Budget by question type and let the fast ones subsidize the slow ones:
| Question type | Budget |
|---|---|
| Short knowledge check | 30–45 sec |
| Standard situational stem | 60–90 sec |
| Calculation (EVM, float, EMV) | 90–120 sec |
| Multi-select ("choose two/three") | 90–120 sec |
| Case-section question | 90–120 sec, plus one-time case reading |
Target a running average of about 75 seconds rather than 80. Across 180 questions that banks roughly 15 minutes of buffer — enough to absorb a brutal case or a flag-review pass, instead of discovering at question 150 that the math no longer works.
The case-section-first clock strategy
The case section punishes two opposite mistakes: reading the vignette so carefully you memorize it, and skimming so lightly you re-read it for every question.
Do this instead:
- Skim the case once for structure — project type, approach (predictive, agile, hybrid), where it is in its lifecycle, what's going wrong. One minute, not five.
- Let each question send you back. Read the question, then scan the case for the specific facts it needs. Case questions are written to be answerable this way; deep-reading up front mostly loads details the questions never use.
- Give the section a hard exit time. Before exam day, decide your worst case — for example, "if the on-screen counter shows the first block still unfinished at minute 85, I answer the remainder with best guesses and take the break." A slow case section is survivable; an unfinished exam is not.
- Don't write a brain dump first. Every minute of writing comes off the same 240-minute clock the case section draws on — the 2026 brain dump rules changed this trade permanently. Two minutes for a personal top-five, maximum.
Checkpoints and break placement
Set three checkpoints at your 75-second pace and check them on the exam's question counter:
- Question 45 by 1:00 elapsed
- Question 90 by 2:00
- Question 135 by 3:00
Ahead of checkpoint: nothing changes. Behind by more than five questions: switch to triage mode — first instinct answers, no second-guessing, no luxury re-reads — until you're back on pace.
Take both breaks. Ten minutes of standing, water, and eyes-off-screen buys back more accuracy in hour four than ten extra minutes of grinding ever will; mental fatigue is real even when motivation isn't the problem. Two rules around them: clear your flags before leaving a block, since you can't come back, and don't try to study during the break — you have no access to notes, and rule-breaking risks the whole attempt. Our exam-day guide covers the full check-in and break procedure.
Flag-and-move discipline
The flag button is where pacing plans die. Use it under contract:
- Never leave a question blank. There's no penalty for wrong answers, and a blank is guaranteed wrong. Answer, flag, move.
- The 100-second rule. If you're torn between two options at 100 seconds, you're no longer reasoning — you're oscillating. Pick the one your gut ranked first, flag it, go.
- Cap flags at about one in ten. If you've flagged 15 questions in a 60-question block, you're using the flag as anxiety relief, not strategy. Flag only questions where more thought could genuinely change your answer — a calculation you can re-verify, a stem you may have misread.
- On review, change answers only for a reason you can state. "I misread the word NOT" is a reason. "The other one feels safer now" is fatigue talking.
Pacing is trained, not decided
None of this works if exam day is the first time you've felt the 240-minute clock. Full timed mocks — same length, same breaks, case section first — are where the budgets become instincts, and they're a core readiness signal besides. Between mocks, train the per-question clock: ExamElephant timed drills show your pace per question, and the test-retest method brings back every miss at 3 and 7 days — so the slow, shaky topics that wreck pacing become fast, settled ones before they can cost you minutes on exam day. The free 75-question tier is enough to measure your baseline speed this week. Skipping timed practice entirely is one of the classic PMP study mistakes; don't let it be yours.
Paid passes are coming soon
The full 2,100-question bank, timed 180-question mock exams and unlimited tutoring. Leave your email and we'll tell you the day they open. Unsubscribe anytime. Privacy
FAQ
Does the clock stop during PMP exam breaks?
Yes. The two 10-minute breaks are separate from your 240 minutes of testing time. The clock stops when you accept the break — but you must submit the current block first, and you can't return to its questions afterward.
Can I skip the breaks to save time?
You can — breaks are optional — but you don't gain exam time by skipping them, because break time isn't exam time. Four hours of sustained decision-making degrades accuracy; almost everyone nets positive by taking both.
What if I'm still slow after weeks of practice?
Diagnose where the time goes. Re-reading stems points to reading strategy (question first, then options). Slow calculations point to formula fluency. Oscillating between two options points to mindset gaps, not speed. Fix the cause; the pace follows.
Should I answer the case section faster to bank time?
No — budget it honestly at 90–120 seconds per question and bank time on short items instead. The case section rewards a settled, systematic read; rushing it early tends to produce cascading misses while you're still warming up.