September 7, 2026 · 6 min read
TL;DR: Overtime appears as an answer option 18 times in this question bank and is keyed zero times. Not rarely. Never. It spans all three ECO domains and shows up in schedule recovery, resource shortage, morale and process-improvement scenarios alike. The exam treats "ask people to work more hours" as a remedy chosen before the cause is known, and it keys the option that establishes the cause or changes the work instead.
Most exam traps are a matter of degree. Training is right sometimes and wrong more often. Escalation is right sometimes and wrong more often. Overtime is different. We swept about fifty candidate themes across this bank looking for lopsided keyed-versus-distractor splits, and overtime came back with the most extreme one in the whole sweep: eighteen appearances as an option, zero as a key.
That is worth sitting with, because overtime is not an absurd option. Real projects run it. Real sponsors ask for it. It is not the reckless-sounding answer an item writer plants to be obviously discardable, which is what makes it effective as a distractor.
Because of what the option skips rather than what it costs. Look at what surrounds it in the stems.
A project manager is given eight people, no more exist anywhere in the company, the work would normally take twice as long, and management will not move the date. The options are relax quality, train the team, ask for overtime, or look for scope that can be cut. The keyed answer is cutting scope. The explanation is blunt about the others: relaxing quality is unprofessional, training assumes a skill gap the stem never mentions, and overtime "is never the first resort because it harms morale and the project manager's credibility and can create cost impacts or harm other work."
An agile team is on track, and mid-execution the sponsor pulls a large part of the team onto a higher-priority project. One option is to agree an overtime allowance with the sponsor so the people left can finish. The keyed answer is to submit a change request so the impact can be assessed. The reason given is that overtime "commits to one solution before anyone knows" what the loss actually does to the baseline.
A print works has watched turnaround slide from six days to eleven, and an improvement session has produced four competing theories about the cause. One option adds an overtime shift at the station where the backlog is visible. The keyed answer tracks cycle time and work in progress stage by stage to find where jobs actually wait. Adding hours at the visible pile treats the symptom that is easiest to see.
Three domains, three completely different scenarios, one shared shape. In each, overtime is an action taken instead of a diagnosis.
The replacement is never a single technique. It follows from what the stem says is actually broken, which is why memorising "never pick overtime" gets you only halfway. Here is the pattern across the bank's overtime questions.
| What the stem describes | What overtime would do | What the bank keys |
|---|---|---|
| Fixed date, fixed team, work too big | Buy hours against an unmovable constraint | Cut scope |
| Team pulled onto another project | Absorb the loss informally | Change request, assess the impact |
| Turnaround sliding, cause unclear | Add capacity at the visible pile | Measure cycle time and WIP by stage |
| Morale drop after a four-month extension | Punish the team for a decision it did not make | Rebuild the shared, intrinsic reason to care |
| Iteration capacity being estimated | Plan on eight hours, cover the gap later | Plan on roughly six productive hours |
| Profit falling while revenue rises | Push the same backlog harder | Benchmark, find the process gap |
Read the right-hand column as a group and the logic is consistent. Every keyed answer either changes what the work is, or finds out something the project manager did not know. Overtime does neither. It holds the work constant and the understanding constant and turns up the effort, which is why it survives as a plausible-looking option in scenario after scenario without ever being the one.
Common trap: "The date cannot move and the team cannot grow, so the only lever left is hours." That framing is exactly what the distractor is built on, and it is wrong because it treats scope as fixed when the stem usually has not said so. In the eight-person scenario above, three of the four options accept the impossible triangle and try to squeeze it; the keyed one questions the scope. This bank flags overtime by name in several explanations as a first-resort error rather than a cost error, which is a different criticism than most candidates expect.
Slightly, and only in one narrow case. Monetary incentives measure 2 keyed against 11 distractors here, so the odds are still poor, but they are not zero the way overtime is.
The scenario that keys an incentive has a very specific shape. A project is near completion, the contingency time is fully consumed, the project manager has imposed a more rigorous process, and the team is pushing back. The other options are explaining tools and techniques, arguing for a methodology, and crashing plus overtime. The keyed answer offers incentives for finishing on time, because the team already knows how to do the work. Nothing is unclear. What has drained away is willingness, and this is the rare stem where willingness is the only thing broken.
Contrast that with the water-treatment project whose schedule was extended by four months, where the team's mood drops sharply. A completion bonus is offered as an option there and it is a distractor. The explanation reaches for Herzberg: money is a hygiene factor, so its absence demotivates while adding more of it does not motivate. The keyed answer builds something the team shares outside the schedule pressure.
Same lever, opposite verdicts, and the difference is whether the stem describes unwillingness or genuine demoralisation. Working through enough of these is how the distinction stops being subtle, especially when every wrong option comes back explained rather than just marked wrong.
Capacity planning carries the quiet version of the overtime trap, dressed as arithmetic rather than as effort.
A hybrid project's PMO asks how much capacity the team will have next iteration. One option says to plan on a full eight-hour day for each person, with any shortfall picked up as overtime. It sounds like arithmetic. The keyed answer plans on roughly six productive hours a day, because ceremonies, refinement, questions from other teams, administration and ordinary interruptions all come out of the same eight hours.
The eight-hour option does not merely overestimate. It builds the overtime into the plan as the mechanism for absorbing its own error, then hands the team a shortfall they will be held responsible for. That is the same defect as the schedule-recovery questions, moved earlier in the project and dressed as an estimating decision.
Is overtime ever the correct answer on the PMP exam? In this bank of 2,141 questions, no. Overtime appears as an answer option 18 times and is keyed zero of those times. It shows up across all three domains, in schedule, resource, morale and process-improvement scenarios, and every one of them keys something else.
What does the exam want instead of overtime when the schedule slips? It depends on what the stem says is broken. If scope can move, cut scope. If the baseline is affected, raise a change request and let the impact be assessed. If the delay is a queue problem, measure where work is waiting. Overtime is rejected because it commits to one remedy before anyone has established the cause.
Why is offering a bonus also usually wrong? Money is a hygiene factor under Herzberg's two-factor theory: its absence demotivates, but adding more of it does not motivate. In this bank, monetary incentives appear in 2 keyed answers and 11 distractors. The exception is a scenario where the team already knows what to do and the problem is purely willingness.
How should I estimate iteration capacity if not on an eight-hour day? On productive hours. One bank question keys roughly six productive hours a day per person, because ceremonies, questions, interruptions and administration consume the rest. The distractor is the full eight-hour day with any shortfall picked up as overtime, which builds the over-commitment into the plan.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong, which is how patterns like this one become visible in the first place. Start the free 20-question sample, no card and no signup required to try it.
Is overtime ever the correct answer on the PMP exam?
In this bank of 2,141 questions, no. Overtime appears as an answer option 18 times and is keyed zero of those times. It shows up across all three domains, in schedule, resource, morale and process-improvement scenarios, and every one of them keys something else.
What does the exam want instead of overtime when the schedule slips?
It depends on what the stem says is broken. If scope can move, cut scope. If the baseline is affected, raise a change request and let the impact be assessed. If the delay is a queue problem, measure where work is waiting. Overtime is rejected because it commits to one remedy before anyone has established the cause.
Why is offering a bonus also usually wrong?
Money is a hygiene factor under Herzberg's two-factor theory: its absence demotivates, but adding more of it does not motivate. In this bank, monetary incentives appear in 2 keyed answers and 11 distractors. The exception is a scenario where the team already knows what to do and the problem is purely willingness.
How should I estimate iteration capacity if not on an eight-hour day?
On productive hours. One bank question keys roughly six productive hours a day per person, because ceremonies, questions, interruptions and administration consume the rest. The distractor is the full eight-hour day with any shortfall picked up as overtime, which builds the over-commitment into the plan.