17.1 The Integrated Project Management Plan: Format and Contents
Key Takeaways
- The integrated project management plan brings multiple plans and processes into one coherent document that answers why, what, how, when, who, and how much.
- Typical contents cover objectives and scope, schedule, cost and budget, resources, risk, quality, communication, procurement, governance, and change control.
- Format matters as much as content: a plan nobody can navigate is not used, and an unused plan controls nothing.
- The plan is owned by the project manager and approved through governance, which is what makes it a baseline rather than a working note.
- It is a living document maintained through change control, not a document produced once for approval and then abandoned.
Integrated planning on the APM PMQ
Integrated planning is how the project manager builds and maintains a single, coherent management approach so that scope, time, cost, quality, risk, resources, communication, and related controls work together rather than as disconnected documents. On the PMQ it is learning objective 19 — Integrated planning in Area D (Planning and managing deployment).
Weak exam answers treat the project management plan as a folder of unrelated templates. Strong answers explain format and typical contents of an effective integrated plan and the importance of producing one that stakeholders can authorise, use, and update under control.
Exam frame: Integration is not "more paperwork." It is deliberate design of how decisions in one knowledge area affect the others — so the team works from one agreed baseline of intent.
Purpose of an integrated project management plan
An integrated project management plan (PMP) (also called a project plan or project management plan in organisational language) is the controlled document — or tightly linked set of baselines and approaches — that describes how the project will be executed, monitored, controlled, and closed to achieve agreed objectives.
Why produce an integrated PMP?
- Create a common baseline — everyone works from the same scope, dates, costs, and success criteria.
- Enable authorisation and governance — sponsors and boards approve a coherent package, not scattered slides.
- Support progress control — actual performance is compared to integrated baselines (scope, schedule, cost).
- Make change impact visible — a scope change can be assessed for schedule, cost, risk, quality, and resource effects together.
- Coordinate specialist plans — risk, quality, procurement, and communication sit inside one logic, not in silos.
- Communicate intent — teams, suppliers, and BAU understand how delivery will be managed.
- Support assurance and reviews — auditors and reviewers test whether the plan is complete, realistic, and followed.
- Link delivery to benefits and transition — the plan shows how outputs will be handed into operations so value can appear.
Without an integrated plan, projects improvise: the schedule promises dates the resource plan cannot staff, the budget omits risk contingency, and quality gates appear after the critical path has already been committed. Integration prevents that structural failure mode.
Format of an effective integrated PMP
Format varies by organisation size, life cycle, and sector. PMQ answers should describe features of effectiveness, not one branded template.
| Format feature | What good looks like | Why it helps |
|---|---|---|
| Hierarchical structure | Summary plan with subsidiary plans/baselines linked by reference | Readable at board level; detailed enough for delivery |
| Baselined and version-controlled | Approved baseline with change history | Distinguishes authorised plan from draft ambition |
| Traceable to business case / mandate | Objectives, constraints, and success criteria inherited and refined | Keeps delivery aligned to investment intent |
| Role-clear | Who owns plan sections, updates, and approvals | Avoids orphan sections and conflicting versions |
| Life-cycle aware | Linear, iterative, or hybrid planning approach stated | Matches how re-planning and baselines will work |
| Integrated, not pasted | Cross-references and consistent assumptions across sections | Surfaces conflicts early |
| Proportionate | Detail matches risk, complexity, and scale | Avoids bureaucracy that nobody maintains |
| Accessible | Stakeholders can find the current authorised version | Stops shadow plans on local drives |
In linear life cycles the PMP is often developed more fully early and baselined before major delivery. In iterative or hybrid approaches the integrated plan still exists, but detailed work packages may be planned in waves or increments while higher-level baselines and approaches remain controlled.
Typical contents of an effective integrated PMP
Organisations label sections differently. For PMQ, recognise a coherent set of contents that together form integration:
| PMP content area | Typical inclusions | Integration link |
|---|---|---|
| Project context and objectives | Background, objectives, success criteria, constraints, assumptions, exclusions | Anchors every other plan to "why" and "done means" |
| Scope baseline | Scope statement, product breakdown / WBS, acceptance criteria, deliverables | Defines what schedule and cost must deliver |
| Schedule baseline | Network logic, milestones, critical path, calendars, dependencies | Times the work and interfaces with BAU and suppliers |
| Cost / budget baseline | Cost estimates, budget, contingency treatment, funding profile | Prices the timed scope and risk responses |
| Quality management approach | Standards, acceptance, reviews, testing, quality roles | Ensures "done" is fit for purpose, not only finished |
| Risk management approach | Process, risk appetite links, escalation, contingency use | Protects objectives; risk responses need time and money |
| Resource management approach | Skills, roles, acquisition, allocation principles | Makes schedule feasible |
| Procurement / commercial approach | Make-vs-buy, packages, lead times, contract types (as applicable) | External supply sits on the same timeline |
| Stakeholder and communication approach | Audiences, methods, frequency, escalation | Information flow supports control and engagement |
| Governance, roles, and authority | Decision rights, reporting, gates, financial authority | Who can approve plan changes and spend |
| Change control approach | How baselines are changed and impact-assessed | Protects integration when reality shifts |
| Issue and configuration approaches | Issue handling; configuration/baselines for products | Stops uncontrolled product and document drift |
| Health, safety, security, sustainability (as relevant) | Mandatory constraints and methods | Non-negotiable constraints reshape options |
| Transition and benefits links | Handover/readiness, benefits measures and owners (high level) | Connects delivery plan to value and BAU |
Not every project needs equal depth in every section. A small internal change may have a light procurement section; a regulated build may emphasise quality, safety, and configuration. Effectiveness means the plan is complete for this project’s risk and context — not that every section is the same length.
Scope, schedule, and cost as the classic triple baseline
Many exam scenarios revolve around the integrated baselines for scope, schedule, and cost. They must be consistent:
- Scope defines the work and products.
- Schedule sequences and times that work.
- Cost prices resources and materials for that timed work.
If one baseline moves without re-integrating the others, the plan becomes fiction. Change control and re-estimating (see later sections) exist to restore consistency.
What is the primary purpose of an integrated project management plan (PMP)?