September 6, 2026 · 6 min read
TL;DR: The plan says how the work will be run. The charter says the work is allowed to happen at all. Across the 155 questions on this ECO task, the project management plan is a wrong answer nine times and the keyed answer four. The charter runs the other way. Ask what the stem is really asking.
A department head wants a quick picture of a project: scope, milestones, risks, who authorized it. Reach for the project management plan and you have picked the wrong document. The bank keys the charter, because a quick picture at summary level is exactly what a charter is built to be.
Three things: the subsidiary management plans (scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder engagement), the scope, schedule and cost baselines, and descriptive components such as the delivery approach and life cycle.
PMBOK 8 produces the plan in the Integrate and Align Project Plans process, which sits under the Governance performance domain.
One bank scenario has a project manager finishing the last subsidiary plan and consolidating everything into a single document. The question asks which activity is not part of consolidation. The keyed answer is updating schedules and budgets with the latest performance data, because that belongs to execution. Consolidation means looking for gaps between the plans, checking they still deliver business value, and making sure the right people have read them.
The plan is also where the tailoring lives. Another scenario hands a project manager a drifting project and asks them to find the development approach including any modifications. The charter, the schedule management plan and the stakeholder register are all offered. The keyed answer is the project management plan, because that is where a project records how it has adapted a standard approach to its own circumstances.
A baseline is an approved version of scope, schedule or cost that actual performance gets measured against. A plan says how you will manage something. A baseline is the number you are held to. The three combine into the performance measurement baseline.
The distinction that catches people is that a baseline is defined by its approval, not by its existence. A schedule sitting in a file is a schedule. The same schedule, approved and placed under change control, is the schedule baseline, and from that point it can only move through an approved change request.
| Artifact | What it answers | Changed by |
|---|---|---|
| Project charter | Is this project authorized, and what may the PM commit? | Reissue by the sponsor, rare |
| Subsidiary management plan | How will we manage scope, cost, risk, comms? | Approved change request |
| Baseline (scope, schedule, cost) | What are we measuring performance against? | Approved change request only |
| Project document (risk register, issue log, scope statement) | What is the current state of this? | Updated continuously, no approval |
Common trap: treating "project management plan" as the safe answer to any planning question. Measured across this bank's 155 records on integrated planning, the project management plan sits in the option list as a distractor nine times and as the key four times. The charter runs the other way, keyed eight times and a distractor five. In one record a functional manager withdraws two developers saying nobody ever showed his department the project was formally committed. Three of the four options are planning artifacts, including the plan itself. The keyed answer is the charter, because the manager is disputing authority, and the plan presumes the authority rather than granting it.
Whichever one answers the question the stem is asking. Authority and existence questions go to the charter. How-we-will-run-it questions go to the plan. Current-state questions go to a project document. Twenty-four of these 155 records ask what you do first or next, so the sequence matters as much as the content.
The order the artifacts appear in is stable and worth knowing cold. The business case argues the project is worth doing. The charter authorizes it and names the project manager. The plan says how the authorized work will be done. The project management information system holds the data while the work runs, and the final report closes the loop back to the business case.
That order explains most of the keyed answers here. A project manager joining an in-flight national platform migration is offered the schedule, the procurement records and the budget. The keyed answer is the charter, because everything else gets judged against what the project was authorized to deliver. A project manager inheriting a project where every plan and document has gone missing is keyed to rebuild them with the team, not to borrow a past project's or defer the work. And a project manager told to prepare a project management plan for a steel quality improvement programme is keyed to write the scope statement first, since nothing can be quality-planned before someone has said what the project covers.
That last one carries a vocabulary point the bank flags by name. The scope statement is a project document. The scope management plan is a component of the project management plan saying how scope will be defined and controlled. Two artifacts, keyed separately.
The project manager develops and owns it. The sponsor, or whichever body the charter names, approves it. The team builds it alongside the project manager, which is why one bank scenario keys "create the plans with the project team" over having stakeholders write them.
Ownership does not mean the plan is yours to quietly revise. Once approved, the components under change control (the three baselines above all) move only through the change process the plan itself defines. In one scenario stakeholders review the plan and say they cannot see what gets baselined or how changes will be measured. The keyed answer builds the missing configuration management plan, change management plan and performance measurement baseline with the team and adds them. The tempting wrong answer tells the stakeholders it is all in the subsidiary plans somewhere, which asserts nothing is missing after a review has just shown that something is.
Distractors like that are worth studying deliberately, since the reasoning that makes them wrong is the actual exam content. Getting them explained, not just marked wrong, is the difference between practice that teaches and practice that only scores.
What is in the project management plan? Subsidiary management plans for each area, the configuration and change management plans, the delivery approach and life cycle description, and the scope, schedule and cost baselines. It describes how the project will be executed, monitored, controlled and closed.
Who owns the project management plan? The project manager develops and owns it, building it with the team. The sponsor or the body named in the charter approves it, and after approval it changes only through change control.
What is a baseline on the PMP exam? An approved version of scope, schedule or cost that performance is compared against. The three together form the performance measurement baseline. Approval and change control are what make it a baseline rather than just a document.
What is the difference between the plan and project documents? The plan is baselined and says how work will be managed. Project documents are working records (risk register, issue log, scope statement) that update continuously without formal approval.
The 155 integrated planning questions in PMP Practice sit inside a bank of 2,141 re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer carries the reasoning that makes it wrong, explained rather than just marked. Start the free 20-question sample with no card and no signup.
Related: Project scope, requirements and the baseline · Cost baseline, budget and reserves · Process domain study guide
Sources: PMI — PMBOK Guide standards · PMI — PMP Examination Content Outline, 2026 (PDF)
What is in the project management plan?
The subsidiary management plans (scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder engagement), the configuration and change management plans, the delivery approach and life cycle description, and the three baselines for scope, schedule and cost. It says how the project will be run. It does not authorize the project.
Who owns the project management plan?
The project manager develops and owns it, building it with the team rather than for them. It is approved by the sponsor or the body the charter names, and once approved it only changes through the change control the plan itself defines.
What is a baseline on the PMP exam?
An approved version of scope, schedule or cost that actual performance is compared against. The three combine into the performance measurement baseline. What makes it a baseline is not that it is written down but that it is approved and can only be changed through change control.
What is the difference between the project management plan and project documents?
The plan says how the work will be managed and is baselined. Project documents (the risk register, stakeholder register, issue log, scope statement) are working records the project produces and updates continuously. Confusing the scope statement with the scope management plan is a keyed trap in this bank.