This guide covers everything you need to know about the project management plan in PMBOK 8. The project management plan is the master document that defines how the project will be executed, monitored, controlled, and closed — it is the single integrated planning artifact that brings all subsidiary plans together into a coherent governance framework.
What Is the Project Management Plan?
The project management plan is a comprehensive document (or collection of integrated documents) that defines how the project will be planned, executed, monitored, controlled, and closed. It includes all subsidiary management plans — scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement — as well as the project baselines (scope, schedule, and cost) and any additional documents needed to guide project execution.
The project management plan is not a schedule or a task list. It is the governance document that answers the question: “How are we going to manage this project?” It establishes the rules, processes, and authority structures that the team will follow throughout the project lifecycle.
The project management plan must be formally approved by the project sponsor before execution begins. Once approved, any significant changes to it require formal change control. It is a living document updated throughout the project as plans are refined and approved changes are incorporated.
Project Management Plan in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the project management plan belongs to the Governance Performance Domain and is produced during the Integrate and Align Project Plans process. PMBOK 8 treats the project management plan as the integration point for all performance domain plans — the document that ensures all planning elements are internally consistent and aligned to project objectives.
The project management plan is the primary reference document for the entire project team throughout execution. It feeds into every monitoring and control process, every change control decision, and the closure process.
Key Elements of the Project Management Plan
A well-structured project management plan typically includes:
- Subsidiary Management Plans — scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder plans
- Baselines — approved scope, schedule, and cost baselines against which performance is measured
- Change Management Approach — how changes will be identified, documented, reviewed, and approved
- Configuration Management — how project documents and deliverables will be version-controlled
- Performance Measurement Approach — metrics, thresholds, and reporting cadence
- Tailoring Decisions — how PMBOK processes have been adapted for this project’s context
Project Management Plan Example — Project Phoenix
The Project Phoenix Project Management Plan was a 38-page document approved by Riley Park on January 20, 2024, two weeks after the project charter was signed. It incorporated eight subsidiary plans: scope, schedule, cost, quality, resource, communications, risk, and stakeholder engagement. The plan established a biweekly status reporting cadence, a CPI/SPI threshold of 0.90 triggering mandatory corrective action reporting, and a change control process requiring written CCB review for all baseline changes.
The plan was updated twice during the project: once when CR-001 was approved (updating the scope and cost baselines) and once when ISS-004 required an adjustment to the resource plan. Alex Morgan used the plan as the daily reference document throughout execution, and the project’s clean audit trail at closure was directly attributable to the discipline of following the plan’s governance framework.
You can download the complete filled-in example below — it shows exactly how the project management plan was structured for a real project.
Download Free Project Management Plan Template and Example
We have prepared two free resources to help you build a project management plan for your own projects:
- Download the Project Management Plan Template — PMBOK 8 (blank, ready to fill in)
- Download the Project Management Plan Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Project Management Plan — Best Practices and Common Mistakes
Right-size the plan for the project. A 200-page plan for a 12-week project adds overhead without value. Focus on the decisions that matter: what are the baselines, who approves changes, how will performance be measured, and how will risks be managed? Get sponsor approval before execution begins — a plan that has not been formally approved is not a baseline, it is a draft.
The project management plan is most effective when it is treated as the active governance document it is meant to be, not filed away after approval and never consulted again. Teams that skip or rush this document often find themselves making ad hoc decisions throughout execution that could have been defined upfront.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Project Management Plan Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management