September 7, 2026 · 8 min read
TL;DR: The project charter appears as an answer option 55 times in this bank. It is keyed 15 times and wrong 40 times, and the boundary is not fuzzy. Ask whether the question is about authority or about detail. Authority means the charter. Detail means something else.
Most of the lopsided patterns in this bank are traps, options offered dozens of times and keyed almost never. The charter is not one of those. It is genuinely two-sided, and that makes it harder, because you cannot fall back on a rule of thumb like "never pick this one." You have to read what the question is actually asking.
Three things, and only three, across the 15 keyed appearances.
Authorization to exist. A sponsor tells the project manager verbally to start pulling people onto a project while the paperwork is finalized. Nobody has been named project manager in writing and no document states the objectives. The keyed answer waits for the charter to be signed, because until it is, the project has no documented existence and the project manager has no documented authority to draw on organizational resources.
Authority over resources. A functional manager tells a team lead their department will no longer supply two developers, because nobody ever showed the department it was formally committed. Both the project management plan and the schedule list the developers as assigned. The keyed answer points at the charter. The dispute is about entitlement, not scheduling detail, and the charter is what grants the entitlement. The distractors, the plan, the WBS, and the activity list, all describe what the developers would do once assigned, which answers a question the functional manager is not asking.
What the project was authorized to deliver. A replacement project manager joins a national licensing programme already under way. The keyed first action is to read the charter to establish what the project was authorized to deliver and why. Everything else, the schedule, the procurement records, the budget, acts on one part of a project before establishing what the whole of it was for.
Detail. The 40 distractor appearances cluster tightly:
| The question asks for | The keyed answer is | The charter distractor reads |
|---|---|---|
| The development approach and any tailoring | The project management plan | "Review the project charter as the original agreed document" |
| What to do next after the scope baseline is done | Define, sequence, and estimate activities | "Reread the project charter for the high-level scope, schedule, and costs" |
| Closing procedures | The organizational process assets | "Consult the project charter for the closing procedures" |
| How to proceed on an adaptive project | Timebox the top backlog items | "Review the project charter for the high-level scope and use it to start delivering quickly" |
| What to do about a scope statement management wants skipped | Explain the consequences to management | "Begin the project using the project charter as the input, to save time" |
The failure mode is the same in every row. The charter is a summary document by design, and a summary is the wrong altitude for a question about how, when, or in what order. Candidates reach for it because it is the earliest document and feels foundational, and foundational reads as safe.
Common trap: "The charter came first, so start there." Sequence is not the test. Altitude is the test. This bank's charter distractors are overwhelmingly the ones that would send you to a two-page summary for information that only exists in a subsidiary plan. When a scenario asks for a cadence, a duration, a procedure, or a sequence, the charter is being offered precisely because it plausibly could not answer it.
The sponsor. The project manager does not write, revise, or approve it alone.
The exam tests this directly. In one bank question a project manager reviewing a hospital pharmacy automation charter finds that the scope it defines omits work the project cannot succeed without, including staff training and decommissioning the old system. Four options. Widening the scope exceeds the project manager's authority. Working to the known incomplete scope guarantees the shortfall. Submitting a change request to the change control board presumes a baseline the charter has not properly established yet. The keyed answer raises the discrepancy with the sponsor and agrees the changes with them.
That ownership question is worth carrying into the exam as a second filter. If an option has the project manager writing, revising, or approving the charter unilaterally, it is a distractor regardless of how sensible the content sounds. Several of the 40 do exactly that: "Write the project charter and get the executives to sign off on it," "Revise the project charter after discussing it with the sponsor," "Create a separate project charter for installation support."
The charter is keyed there, because a summary is exactly what a charter is for.
One keyed case does look like a detail question at first glance, and it marks the edge of the rule. A department head asks for a quick picture of a mobile-app project: high-level scope, schedule, major risks, and who authorized it. The keyed answer is the charter, then the stakeholders it names.
The reason it works there is that all four requested items are summary-level, and one of them, who authorized the project, exists nowhere else. That is the charter doing its actual job. Compare it with the distractor rows above, where a scenario asks for one specific operational fact, and the difference is clear enough to use under time pressure.
Two-sided patterns are where a bank with explained wrong answers earns its keep. Knowing that the charter is keyed 15 times tells you almost nothing on its own. Knowing which 15 is what turns it into a decision you can make in twenty seconds.
When is the project charter the right answer on the PMP exam? When the question is about authorization or authority: who said this project may exist, what it was authorized to deliver, and whether the project manager may claim organizational resources. Across this bank the charter is keyed 15 times, and almost every keyed case turns on one of those three.
When is the project charter a distractor? When the question asks for execution detail. The charter is offered as a wrong answer 40 times in this bank, and the pattern is consistent: the scenario wants a cadence, a sequence, a closing procedure, a set of durations, or a development approach, and the charter operates at too high an altitude to carry any of them.
Can the project manager change the charter? No. The charter belongs to the sponsor. One bank question has a project manager find that the charter omits work the project cannot succeed without. Widening the scope is a distractor and so is raising a change request. The keyed answer takes the discrepancy to the sponsor and agrees the changes with them.
Is the charter still current under PMBOK 8? Yes. The charter remains the document that formally authorizes the project and records the project manager's authority. What changed in the July 2026 exam update was the surrounding structure, not the charter's role.
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. Start the free 20-question sample - no card, no signup required to try it.
When is the project charter the right answer on the PMP exam?
When the question is about authorization or authority: who said this project may exist, what it was authorized to deliver, and whether the project manager may claim organizational resources. Across this bank the charter is keyed 15 times, and almost every keyed case turns on one of those three.
When is the project charter a distractor?
When the question asks for execution detail. The charter is offered as a wrong answer 40 times in this bank, and the pattern is consistent: the scenario wants a cadence, a sequence, a closing procedure, a set of durations, or a development approach, and the charter operates at too high an altitude to carry any of them.
Can the project manager change the charter?
No. The charter belongs to the sponsor. One bank question has a project manager find that the charter omits work the project cannot succeed without. Widening the scope is a distractor and so is raising a change request. The keyed answer takes the discrepancy to the sponsor and agrees the changes with them.
Is the charter still current under PMBOK 8?
Yes. The charter remains the document that formally authorizes the project and records the project manager's authority. What changed in the July 2026 exam update was the surrounding structure, not the charter's role.