September 8, 2026 · 9 min read
TL;DR: Options that begin do nothing, wait, continue, proceed, allow, let or accept appear 151 times in this bank and are keyed 9 times, about 6%. We read all nine. They divide cleanly into four situations: the authority is not yet granted, the team owns the decision, the scope is genuinely finished, and the disagreement is doing useful work.
Every PMP candidate learns early that the exam rewards action. Do not wait. Do not ignore. Do not proceed as planned. The advice is sound: across this bank, inaction options are wrong 142 times out of 151.
But nine of them are correct, and unlike most 6% findings, these nine are not noise. They are the most concentrated statement in the bank about where a project manager's authority stops.
1. The authority does not exist yet. A sponsor tells you verbally to start pulling people onto the project while the paperwork is finalised. You have not been named project manager in writing, and nothing yet states the project's objectives or your authority to assign resources.
The keyed answer waits for the charter to be signed. Not because waiting is prudent, but because the charter is the document that grants the authority the other options are busy exercising. Every wrong option, including asking functional managers to informally lend staff, is an act performed without the mandate to perform it. Waiting is the compliant move, and the only one available.
2. The team owns the decision. Four of the nine sit here, which makes it the largest group.
In all four, the more energetic options are the wrong ones: speak to individuals, escalate to the functional manager, override the design, announce the performance issue in the team meeting. Each would work in a directive setting. Each removes something the scenario has explicitly established the team holds.
Note the last of the four especially. The keyed option is continue, a word that is keyed once in 40 appearances elsewhere in this bank. It is correct here because the coaching is already the right intervention and the scenario is asking whether you will abandon it under social pressure.
3. The work is genuinely finished. After a client confirms the agreed scope, designing and producing 200 signs, has been met, the installation company asks the project manager to help install them. Keyed: do nothing, since the project's scope is officially fulfilled and approved.
The distractors are all forms of helpfulness: submit a change request, pitch in as a favour, create a separate charter for installation support. Installation is a different project. Accepting it is scope creep with a friendly face, and raising a change request against a closed, accepted scope is process theatre.
4. The conflict is doing the work. Two senior developers argue for a fortnight over whether to carry an existing booking database forward or replace it. The exchanges have turned personal, junior members have stopped posting, and the product director wants it shut down. No current work depends on the choice, which the team has agreed to settle two iterations out.
Keyed: allow the design disagreement to continue and act only on the personal remarks.
That is the most instructive of the nine. Two people arguing hard about a database the agency will live with for a decade are doing exactly what they should. A decision that size ought to be contested. What has gone wrong is the manner, not the argument, and the options that separate the developers or take the decision away solve the visible problem by destroying the useful one.
Common trap: "Inaction is always a distractor, so eliminate it first." It is wrong 142 times out of 151, which makes that a good heuristic and a costly one. The 9 exceptions cluster in People and Business Environment questions about authority, and they are precisely the questions where a candidate running the eliminate-inaction rule has already discarded the answer before reading it. This bank explains why each of the busier options overstepped rather than just marking it wrong.
The nine share a property that the 142 do not: the scenario supplies the reason the inaction is correct. It is always stated, never inferred.
| The keyed inaction | The stated reason in the stem |
|---|---|
| Wait for the charter | You have no written authority to assign resources |
| Let the team self-correct | The team is self-organizing and performing |
| Let the decision stand | No constraint, standard or risk threshold is violated |
| Do nothing on installation | The client has confirmed the agreed scope is met |
| Allow the argument to continue | No current work depends on the choice |
Now compare the shape of the 142 distractors. They appeal to disruption ("continue with the current middleware so that the schedule is not disrupted"), to optimism ("continue, on the basis that alignment will improve as the product matures"), or to convenience ("continue with the existing figures, since they are probably still close enough"). None of them can point at a sentence in the stem that authorises doing nothing. They are hoping.
So the test is one question: can I name the clause in the scenario that makes this the right choice? If yes, the inaction is a decision. If you are reaching for a general principle instead of a specific sentence, it is the trap.
Because the failure mode is real and expensive. A project manager who cannot stop themselves acting will override a self-organizing team, absorb work belonging to someone else, and commit resources before holding the authority to commit them.
All three are common, and all three feel like leadership from the inside. That is why four of these nine questions are filed under People rather than Process, and why two more sit in the business environment domain, where authority and governance live.
The exam's model of a project manager is someone who acts constantly and knows the four places where acting is the error. That is a harder thing to test than a formula, which is why it shows up as nine quiet questions rather than a chapter heading.
Is doing nothing ever the right answer on the PMP exam? Rarely, but yes. In this bank, options opening with do nothing, wait, continue, proceed, allow or let are keyed 9 times against 142 distractors, about 6 percent. The nine are not random exceptions; they cluster into four recognisable situations.
When is waiting the correct action? When the thing you would be waiting for is what authorises the action. One keyed option waits for the project charter to be signed, because until it is signed the project manager has no documented authority to assign resources at all. Waiting there is compliance, not passivity.
Why is letting the team handle it sometimes correct? Because on a self-organizing team, stepping in removes the ownership the team is supposed to hold. Four of the nine keyed inaction options are this shape: let the team raise it, allow them to self-correct in the retrospective, let their decision stand.
How do I tell real inaction from the trap version? Ask what makes the inaction correct. If the scenario supplies a reason (the scope is signed off, the team owns this decision, the charter is unsigned), it is a deliberate choice. If the only appeal is avoiding disruption or waiting for things to improve, it is the trap.
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, including which of the busier options overstepped. Start the free 20-question sample - no card, no signup required to try it.
Is doing nothing ever the right answer on the PMP exam?
Rarely, but yes. In this bank, options opening with do nothing, wait, continue, proceed, allow or let are keyed 9 times against 142 distractors, about 6 percent. The nine are not random exceptions; they cluster into four recognisable situations.
When is waiting the correct action?
When the thing you would be waiting for is what authorises the action. One keyed option waits for the project charter to be signed, because until it is signed the project manager has no documented authority to assign resources at all. Waiting there is compliance, not passivity.
Why is letting the team handle it sometimes correct?
Because on a self-organizing team, stepping in removes the ownership the team is supposed to hold. Four of the nine keyed inaction options are this shape: let the team raise it, allow them to self-correct in the retrospective, let their decision stand.
How do I tell real inaction from the trap version?
Ask what makes the inaction correct. If the scenario supplies a reason (the scope is signed off, the team owns this decision, the charter is unsigned), it is a deliberate choice. If the only appeal is avoiding disruption or waiting for things to improve, it is the trap.