Demo environment — data may be reset without notice. Not for production use.
VanillaPM
Sign in Get started free Dashboard
Pr1 Process · 41%

Develop the integrated PM plan

In the app: Project → Planning → Overview · Planning → Change & Config · Control → Change requests

PMP ECO · Process (41%) · Task Pr1. Bring the subsidiary plans and the three baselines together into one plan whose parts agree with each other, then control every change to it.

Every plan approved, and still no plan — the short version

What it is

The project management plan is not one document. It is the set of plans that together say how the project will be executed, monitored and controlled:

  • Subsidiary plans: scope, schedule, cost (financial), quality, resources, communications, risk, procurement and stakeholder engagement. Each one says how that area is managed.
  • Three baselines: scope (the approved scope statement, WBS and WBS dictionary), schedule (the approved dates) and cost (the time-phased budget, including the contingency reserve). Together they form the performance measurement baseline: the thing progress is measured against.
  • The development approach: predictive, adaptive or hybrid, and how the plan is tailored to this project.
  • Change and configuration management: the change management plan sets up the change control board (CCB) and how changes are decided; the configuration management plan says which items are version-controlled and how.

Integration is the project manager's own job. Specialists can write a good risk plan or a good schedule. Only the PM is accountable for making the parts fit: the schedule allows for the procurement lead times, the cost baseline carries a reserve sized to the risks, and the whole set rests on an approved charter.

Before the baselines are set, the plan is a working draft that you can edit as often as needed. Once it is baselined, it changes only through integrated change control: a change request, assessed against all three baselines and decided by the authority the plan names.

Note the difference between the plan and the project documents. The risk register, the communications matrix and the change log are project documents: working records that change every week. The plan says how they are managed; it is approved, and it changes only through change control.

Why it matters

  • Plans written in isolation contradict each other. A schedule that ignores a long procurement lead time. A cost plan blind to the risk register. Integration is how you catch those before execution does.
  • Without baselines there is no variance. "Are we late?" only has an answer if there is an approved date to be late against, and it stays put until a decision moves it.
  • Without change control, the plan is whatever the last email said. Every change should be visible, priced, and decided by someone with the authority to decide it.

Where you do it in VanillaPM

  • Planning → Overview is the integrated plan. It reads the governed plans and baselines from their own workspaces and checks them against each other: the recorded approach, the baselines, whether each plan is approved, twelve integration checks, and the change-request tally.
  • Planning → Change & Config holds the baseline history (every version, and the change request behind it), the change and configuration management plans, and an in-depth guidance tab.
  • Control → Change requests is the change log: each request carries its impact on the baseline (scope, days, cost), its decision and its audit trail.
  • Every plan is a governed document in the Knowledge Base: drafted, submitted, approved, and frozen once approved.

Walked example — Coral Ridge Resort

Coral Ridge is mid-build. Its approach is recorded as a decision: hybrid. Scope, the finish date and the cost are fixed with the owner, the lender and Corvane, so they are baselined and changed only through the CCB; site work runs in two-week sprints. All eleven governed plans are approved, and the baseline is at v3: the original at plan approval, the rooftop pool (CR-02, +USD 0.4M), and the monsoon delay (CR-03, +62 days to 31 August 2028).

Yet only four of twelve integration checks pass. The charter is still a draft: its objective says "before the winter tourist season" instead of a date (P1), and VanillaPM won't let it be submitted until it has one. The risk register has grown: the expected loss from active threats is now USD 3.25M, but two approved changes have already drawn on the USD 2.4M contingency, and only USD 1.75M is left: 54% of the exposure (Pr6). The second loan tranche lands a month after the spending it pays for, and the facade water tests the quality plan needs aren't in any budget (Pr7). The landscaping and external works are in the scope but in neither the schedule nor the budget, and the working schedule now finishes 12 days after the baseline (Pr8). And the resource plan can't staff the schedule in some weeks: two crews are booked beyond their capacity (Pr4), and the chillers haven't been ordered although their order-by date has passed (Pr5). Each plan is fine on its own. The problems only show up when you read them together, and that is the point of this task.

The workspace — the theory behind each screen

Every screenshot is the actual sample project, not a mock-up.


1 · Integration means checking that the parts agree

The theory: integration management and tailoring. The PM plan is approved as a whole, and the PM is accountable for its consistency. The checks that matter are at the joins: does each plan rest on an approved charter, is the approach decided and followed, are the baselines set and changed only through change control, is the reserve sized to the risks?

Coral Ridge — the integrated plan's tiles and integration checks
Coral Ridge — the integrated plan's tiles and integration checks

Reading the screenshot: Hybrid, decided by Nadia Rahman with a recorded reason (click the tile to change it; the change goes into the Decision Log). 3 / 3 baselines, 11 / 11 plans approved, 4 / 12 checks. The eight amber rows are the integration findings: the charter is a draft, and the reason it can't be submitted is printed; the working finish is 12 days past baseline v3; two crews are over capacity in some coming weeks; the HVAC order is late; planned spend runs ahead of funding before tranche 2; landscaping is neither scheduled nor budgeted, and project management and commissioning have no budget line; the facade water testing has no budget; the contingency left covers 54% of the expected loss. The green rows show what is working: the approach matches how the project runs, the baselines changed only through approved requests (CR-02, CR-03), and all eleven plans are approved.

✅ Do record the approach as a decision, with the reason, before you plan around it.
❌ Avoid treating "every plan is approved" as "the plan is integrated". Eleven approved plans can still disagree.


2 · Baselines are set together and changed only by decision

The theory: the performance measurement baseline. Scope, schedule and cost are baselined together, because each depends on the others. The cost baseline includes the contingency reserve (for identified risks); the management reserve (for unknown unknowns) sits outside it. After the first baseline, a new version needs an approved change request, and old versions are kept so variance against the original plan stays visible.

Coral Ridge — the baseline history
Coral Ridge — the baseline history

Reading the screenshot: v1 was set when the plan was approved at M2: finish 30 June 2028, USD 45.4M. v2 cites CR-02, the rooftop pool: +USD 0.4M, same date. v3 cites CR-03, the monsoon: +62 days to 31 August 2028. Working plan vs baseline: Matches. Two other approved changes (CR-01 and CR-04) were paid from contingency, so they don't appear here: drawing on contingency doesn't change the baseline, because the money was already inside it.

✅ Do keep every baseline version. "Late against what?" needs the original answer too.
❌ Avoid re-baselining to make the dashboard green. That hides the variance instead of deciding it.


3 · Subsidiary plans: approved, then controlled

The theory: subsidiary plans and the project documents they govern. Each knowledge area gets a plan saying how it will be managed, as much as this project needs. Once approved, a plan is frozen like the baselines; editing it starts a revision that must be approved again.

Coral Ridge — the subsidiary plans and their approval state
Coral Ridge — the subsidiary plans and their approval state

Reading the screenshot: eleven governed plans, all Approved, including the change and configuration management plans. Under each is the working record it governs: 8 communication lines, 8 active risks, 6 procurement packages, 5 change requests, 3 baseline versions. The records change weekly; the plans don't. The stakeholder engagement plan shows as a Register, because in VanillaPM it lives as the stakeholder register and engagement matrix (P4–P6).

✅ Do tailor: produce the plans the project needs, at the depth it needs.
❌ Avoid shelf-ware: a plan approved at kickoff and never used to make a decision.


4 · Integrated change control: from request to baseline

The theory: Perform Integrated Change Control. Any stakeholder may request a change, but it is written down, its impact on scope, schedule and cost is assessed before the decision, and the authority named in the change management plan approves, defers or rejects it. An approved change that moves a baseline produces a new baseline version, and the decision is communicated.

Coral Ridge — CR-03 applied to the baseline
Coral Ridge — CR-03 applied to the baseline

Reading the screenshot: CR-03 states its impact (+62 days, cost held by re-sequencing), and the tag Applied → baseline v3 ties the decision to the version it produced. The audit trail shows the path: created, submitted, reviewed, approved by the owner board (it moved the opening date, which only the owner board can decide; see B1), and verified once implemented. Anyone asking "why did the finish date move?" gets the answer in one place.

✅ Do assess the impact on all three baselines before anyone says yes or no.
❌ Avoid a side deal: work agreed outside change control never reaches the baseline, so the plan stops describing the project.

Best practices & pitfalls

  • Do start from the approved charter. Everything in the plan should trace back to it.
  • Do baseline scope, schedule and cost together, and keep the reserves explicit: contingency inside the cost baseline, management reserve outside.
  • Do re-check the joins whenever a register grows. A bigger risk register can make a correctly sized reserve too small.
  • Pitfall: confusing the plan with the registers. Updating the risk register is normal work; changing the risk plan is a change.
  • Pitfall: a change process so slow that people bypass it. Thresholds let small changes move fast and big ones get the CCB.

VanillaPM flags a working plan that drifts from the baseline rather than blocking edits, and the integration checks are the ones the data can prove. Some contradictions (a resource plan that can't staff the schedule) still need a person to read the plans side by side; more checks arrive with the lessons that own them.

On the PMP exam

Expect questions on what the PM plan contains (subsidiary plans, the three baselines, the development approach, change and configuration management) and on tailoring: the right answer fits the plan to the project rather than producing every document by rote. Know that the cost baseline includes contingency but not management reserve, and distinguish the plan from project documents such as the change log and risk register. When a scenario adds work, changes a date or shifts the approach, the answer is integrated change control: assess the impact first, raise a change request, let the named authority decide, then update the plan and baselines and tell the stakeholders. Never a side deal, and never a quiet edit to the baseline.

Check your understanding a short quiz — pass to mark the task complete