Focus area: Planning

Planning is the largest of the five focus areas in PMI®'s PMBOK® Guide, Eighth Edition: 19 of its 40 processes sit there. That does not make it a phase you finish before the excavators arrive. On an owner's project, planning starts long before the tender, restarts every time the evidence changes, and keeps going until close-out. This lesson covers what the Planning focus area holds, how its outputs fit together, and how the owner team on Northgate uses it.

Learning outcomes

• Name the 19 Planning processes and the performance domain each one belongs to.
• Tell the difference between planning how a domain will be managed and producing that domain's baseline.
• Explain how Integrate and Align Project Plans turns separate plans into one project management plan.
• Map the owner's planning outputs for Northgate (fictional), including how the owner's master schedule lines up with the contractor's baseline.

The lesson

What the Planning focus area is for

In the Eighth Edition, the 40 processes are organized two ways. The seven performance domains (Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk) group them by subject. The five focus areas (Initiating, Planning, Executing, Monitoring and Controlling, and Closing) group them by the kind of management action. Lesson 3 laid out that structure, and lesson 12 covered Initiating, which authorizes the work. Planning picks up from there and answers two questions: how will we get to the outcome, and what will we hold ourselves to along the way?

Focus areas carry the same names as the old process groups, but they are not phases. You plan the next phase while executing the current one. On adaptive work you plan every iteration. PMI describes the processes as non-prescriptive, so a small project might cover several of them in one meeting and a large one might give each its own document. Lesson 5 explained how to make that choice.

View the data

Focus area	Processes	Share of 40
Initiating	2	5%
Planning	19	48%
Executing	8	20%
Monitoring and Controlling	10	25%
Closing	1	3%

Nineteen processes across all seven domains

Every performance domain has planning work in it, which is one reason Planning is so large. Figure 2 groups the 19 processes by domain. A few points stand out for owner-side readers:

• Scope has four. Plan Scope Management, Elicit and Analyze Requirements, Define Scope and Develop Scope Structure. The last one is where the work breakdown structure lives.
• Risk has four. Plan Risk Management, Identify Risks, Perform Risk Analysis and Plan Risk Responses. The Sixth Edition split analysis into qualitative and quantitative processes; the Eighth treats it as one process you tailor.
• Finance has three. Plan Financial Management, Estimate Costs and Develop Budget. The domain name changed from "cost" to "finance", which suits owners who care about funding and cash flow as well as estimates.
• Governance has two. Plan Sourcing Strategy covers make-or-buy decisions, source selection and contract type. Integrate and Align Project Plans pulls everything together.

One placement is not settled across commentators: most published maps put Identify Stakeholders in Initiating, but at least one puts it in Planning. If you see "20 planning processes" in a study guide, that is why.

Two kinds of planning: the rulebook and the baseline

Look at the orange dots in Figure 2. Seven processes start with "Plan" and end with "Management" or "Engagement". They produce rules, not content: how scope will be defined and accepted, which scheduling tool and method the team will use, how often progress is measured, who can approve what, what risk thresholds trigger escalation. The other twelve produce the content those rules govern: the requirements, the scope statement and work breakdown structure, the schedule, the estimate, the budget, the risk register and its responses.

Owners tend to skip the rulebook and go straight to content. Then the first schedule update arrives and nobody agreed on the data date, the update cycle, whether the contractor's float can be used by the owner, or how a delay will be shown. A one-page schedule management plan written before tender avoids most of that argument. The same is true for finance: decide how contingency will be drawn, and by whose signature, before anyone asks for it.

Integrate and Align Project Plans

This Governance process is where the separate plans become one project management plan. "Integrate" means bringing them into one place. "Align" is the harder part: checking that they agree with each other. The schedule's cash flow has to match the budget's phasing. Every risk response needs an owner, time in the schedule and money in the budget. The sourcing strategy has to match the contract that will actually be signed. The communications plan has to reach the stakeholders the engagement plan says matter. Figure 3 shows the flow.

Plans firm up over time

No owner can plan a building in full detail on day one. The Eighth Edition keeps the familiar idea of progressive elaboration: near-term work is planned in detail, later work in summary, and the detail is added as information arrives. Schedulers call this rolling-wave planning. It is not permission to plan loosely. The baseline milestones and the budget are fixed early and changed only through change control; what fills in over time is the detail underneath them.

Planning also loops with Monitoring and Controlling. When a forecast shows a milestone slipping or a cost trending over, the response is a planning act: re-sequence, re-estimate, or re-allocate contingency, then re-align the plans. Most building projects are hybrid, as lesson 4 showed, so you may see predictive baselines for construction sitting alongside short planning cycles for design development or fit-out decisions.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan for Northgate Logistics Inc. (fictional), procured design-bid-build on a CCDC 2-2020 stipulated price contract with Halvorsen Builders Ltd. (fictional). Ridgeline Architects Inc. (fictional) is the prime consultant under OAA 600. See the Northgate fact sheet.

The owner team's planning splits into two waves. Before tender closed on Tuesday December 8, 2026, the owner planned how the project would be bought and governed: the sourcing strategy (design-bid-build, stipulated price, owner's Supplementary Conditions), the rulebook for each domain and the milestone frame. After tender, the owner set its budget at the $34,950,000 Contract Price plus a $3,050,000 owner contingency, for $38,000,000 excluding HST, and moved into aligning its plans with Halvorsen's.

The table below maps a selection of Planning processes to what the Northgate owner team actually produces. Halvorsen does its own planning for means and methods; the owner's job is to plan its own work and set the rules the contractor's plan must meet.

Aligning the owner's schedule with the contractor's

The owner's master schedule in Microsoft Project starts at contract execution (M0, Monday January 11, 2027). Halvorsen's P6 schedule starts at mobilization (M3, Monday March 1, 2027). Integrate and Align Project Plans is where the owner checks that every contract milestone in its master schedule appears in Halvorsen's baseline with the same date and calendar (Monday to Friday, 8 hours, Ontario statutory holidays off), and that the owner's own activities are tied to the right contractor milestones.

The alignment check turns up one dependency that is entirely the owner's: the racking contractor cannot start on Monday January 17, 2028 (M10) unless Halvorsen reaches Ready-for-Takeover on Friday January 14, 2028 (M9). Only one working day sits between them. That makes the racking contract award and delivery date an owner risk, which Plan Risk Responses has to cover, and a schedule logic link the owner's master schedule must show.

Owner's move

• Write the rulebook before tender. Put schedule, finance and change rules in the tender documents so Halvorsen prices and plans to them.
• Keep the owner's plan to the owner's work. Plan what the owner does and decides; do not re-plan the contractor's means and methods.
• Run an alignment check, not a filing exercise. Test dates against money, risks against budget, contract against sourcing strategy.
• Baseline once, elaborate often. Fix milestones and budget early; add detail by rolling wave without moving the baseline outside change control.
• Link the owner's activities to contract milestones. M10 depends on M9; show it in the logic, not just in a note.

Common mistakes

1. Treating Planning as a phase. It recurs every time the evidence changes.
2. Skipping the "Plan … Management" processes. Without agreed rules, every update turns into a negotiation.
3. Stapling plans together. A binder of subsidiary plans is not an integrated plan until someone checks they agree.
4. Two schedules, no map. An owner master schedule that does not match the contractor's baseline milestones hides risk.
5. Using all 19 processes at full weight. They are non-prescriptive; tailor them to the project's size and risk.

Quick quiz

1. How many of the 40 PMBOK Guide 8 processes do most published maps place in the Planning focus area?

   1. 10
   2. 12
   3. 19
   4. 24

2. Which Planning process belongs to the Governance domain?

   1. Develop Budget
   2. Plan Sourcing Strategy
   3. Develop Scope Structure
   4. Perform Risk Analysis

3. Northgate's owner writes down how Halvorsen's P6 updates will be submitted and reviewed. Which process is that?

   1. Develop Schedule
   2. Plan Schedule Management
   3. Monitor and Control Schedule
   4. Integrate and Align Project Plans

4. What does Integrate and Align Project Plans add beyond collecting the subsidiary plans?

   1. A check that the plans agree with each other
   2. Contractor approval of the owner's budget
   3. The project charter
   4. Final acceptance of deliverables

5. Which statement about focus areas is correct?

   1. Planning must finish before Executing starts
   2. Focus areas are the same as project phases
   3. Planning recurs as the project learns and changes
   4. Planning applies only to predictive projects

Show answers and explanations

1. C. Most maps show 19 of 40. A minority place Identify Stakeholders in Planning, which gives 20.
2. B. Plan Sourcing Strategy and Integrate and Align Project Plans are the two Governance processes in Planning.
3. B. It sets the rules for scheduling; Develop Schedule produces the schedule itself.
4. A. Alignment means checking that dates, money, people, risk responses and the contract agree.
5. C. Focus areas are not phases; planning loops back whenever monitoring shows the plan needs to change, on any delivery approach.

Key terms

Planning focus area

The group of PMBOK Guide 8 processes that set out how the project will reach its outcomes and what it will be measured against.

Subsidiary plan

A plan for one domain or topic, such as schedule, finance or risk, that forms part of the project management plan.

Project management plan

The single, aligned plan that combines the subsidiary plans and the baselines.

Baseline

The approved version of scope, schedule or cost that performance is measured against; changed only through change control.

Sourcing strategy

The owner's decisions on what to buy, how to select suppliers and which contract form to use.

Progressive elaboration

Adding detail to plans as information becomes available; rolling-wave planning is one way to do it.

References

1. Project Management Institute, PMBOK® Guide, Eighth Edition (product page; published November 2025).
2. Ricardo Vargas, PMBOK® Guide 8th Edition processes flow (2025).
3. Project Together Office, PMBOK 8 focus areas: all 40 processes.
4. Mudassir Iqbal, PMBOK 8 focus areas and 40 processes explained.
5. Gold Standard Certifications, PMBOK 8 focus areas explained: what happened to process groups (October 2026).
6. PM Exams, The full PMBOK 8 process map.
7. Project Management Compass, Inside PMBOK® 8: Governance performance domain.
8. Elizabeth Harrin, Rebel's Guide to PM, Project performance domains explained (updated for PMBOK 8) (January 2026, updated July 2026).

Verified on November 6, 2026.

Next lesson in this trackFocus area: Executing