Domain: Schedule

The Schedule performance domain in the PMBOK® Guide, Eighth Edition, from PMI®, has only three processes, fewer than any other domain. The work has not shrunk. Defining activities, linking them, estimating durations and calculating dates now sit inside one process, Develop Schedule. For an owner, the domain is really about two schedules: the owner's master schedule and the contractor's construction schedule, and the rules that keep them telling the same story.

Learning outcomes

• Name the three processes of the Schedule performance domain and show where the 6th edition's six schedule processes went.
• List what an owner's schedule management plan should decide before any contractor schedule is reviewed.
• Read a summary schedule for the critical path and total float.
• Explain how an owner monitors and controls a contractor's Oracle Primavera P6 schedule from a master schedule in Microsoft Project.

The lesson

What the Schedule domain covers

The Schedule domain is one of the seven performance domains PMI lists for the 8th edition, alongside Governance, Scope, Finance, Stakeholders, Resources and Risk. It covers timelines, the sequence of the work and the coordination of activities, tailored to the life cycle you chose (see lesson 4). Its outcomes are practical: a schedule management plan, a schedule, a baseline to measure against, and forecasts that people trust.

Three processes instead of six

The 6th edition (2017) split schedule work into six processes. The 8th edition keeps the first and last and folds the middle four into one. Figure 1 shows the mapping. The tools have not gone anywhere: you still define activities, sequence them with logic, estimate durations and run the critical path calculation. The change tells you that these steps are one loop, repeated as the design matures, not four hand-offs.

Plan Schedule Management: the rules before the dates

The schedule management plan decides how the schedule will be built, checked and used. For an owner it is the part of the domain with the most leverage, because it is the only part the owner writes. At minimum it should settle:

• Method and tools. Critical path method, the contractor's software and file format, and the owner's own tool.
• Calendars. Working days, hours and non-working holidays, so both schedules count time the same way.
• Level of detail. How finely work packages are broken into activities, and the longest activity duration you will accept.
• Logic rules. Every activity has a predecessor and a successor except the start and finish; constraints are explained, not used to force dates.
• Baseline rules. What makes a baseline, who accepts it, and when it can be re-baselined.
• Update cycle and measures. The status date, what is reported, and which measures trigger action.

Develop Schedule: one loop

Develop Schedule takes the work packages from the Scope domain's structure and turns them into a schedule model: activities, relationships (finish-to-start and the others covered in the Microsoft Project dependencies lesson), durations, calendars and, where needed, resources. The software calculates early and late dates. The longest path through the network sets the finish date; that is the critical path. Total float is how far an activity can slip before it delays the project finish or a constrained milestone. Activities on the critical path usually have zero float.

The same process covers analysis and approval: checking the logic, testing what-if cases, compressing the schedule by crashing (adding resources) or fast-tracking (overlapping work), and agreeing the baseline. On adaptive work, Develop Schedule produces a release plan and iteration cadence instead of a full network, and the same domain still applies.

Monitor and Control Schedule

Monitoring means statusing the schedule at a status date (P6 calls it the data date), recording actual starts, finishes and remaining durations, recalculating, and comparing the result to the baseline. Controlling means acting on what you find. Useful measures for an owner are the variance on each key milestone, the trend in total float on the critical and near-critical paths, and the schedule performance index from earned value, which lesson 20 covers. When the forecast threatens a contractual date, the response is either a recovery plan inside the existing scope or a change request that goes through Governance (see lesson 17).

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan for Northgate Logistics Inc. (fictional), built by Halvorsen Builders Ltd. (fictional) under CCDC 2-2020, with Ridgeline Architects Inc. (fictional) as Consultant. The work week is Monday to Friday, 8 hours a day, with Ontario statutory holidays off. See the Northgate fact sheet.

Two schedules, one set of milestones

The owner's master schedule is kept in Microsoft Project desktop and starts at contract execution, M0, on Monday January 11, 2027. It carries the owner's own work: permits, owner decisions, the separate racking contract and move-in. Halvorsen's construction schedule is in Oracle Primavera P6, submitted as XER files, and starts at mobilization, M3, on Monday March 1, 2027. Figure 2 shows both against the twelve baseline milestones. The milestones are the contract between the two schedules: if Halvorsen's P6 dates for M4 to M9 differ from the owner's master schedule, one of them is wrong.

View the data

ID	Milestone	Date	In P6 schedule?
M0	Contract executed	Mon Jan 11, 2027	No
M1	Kickoff meeting	Tue Jan 19, 2027	No
M2	Building permit issued	Fri Feb 26, 2027	No
M3	Site mobilization	Mon Mar 1, 2027	Yes (start)
M4	Foundations and slab complete	Fri May 14, 2027	Yes
M5	Tilt-up panels erected	Fri Jun 25, 2027	Yes
M6	Roof complete, weathertight	Fri Sep 3, 2027	Yes
M7	Permanent power	Fri Oct 1, 2027	Yes
M8	Commissioning starts	Mon Nov 1, 2027	Yes
M9	Ready-for-Takeover / Substantial Performance	Fri Jan 14, 2028	Yes
M10	Racking and occupancy start	Mon Jan 17, 2028	Owner's work
M11	Final completion	Fri Mar 31, 2028	Yes

Applying the plan

Northgate's schedule management plan, confirmed with Halvorsen at the M1 kickoff, should cover the points listed above. Both schedules use the same calendar: Monday to Friday, 8 hours, Ontario statutory holidays off (see P6 lesson 5 and Microsoft Project lesson 4). Halvorsen's P6 WBS maps to the ten level 2 elements on the fact sheet. M4 to M9 appear in both schedules with the same names and IDs, and the owner's master schedule links its own work, such as the racking start at M10, to Halvorsen's M9.

Reading the critical path

Figure 3 is a summary of the second half of the job, between M5 and M9. The logic between milestones is illustrative; Halvorsen's detailed P6 schedule would set it. Here the critical path runs through the roof, permanent power and commissioning. The office mezzanine interiors run in parallel and have about four weeks of total float before they would push commissioning or M9.

View the data

Bar	Start	Finish	Status
Roof and envelope	Mon Jun 28, 2027	Fri Sep 3, 2027 (M6)	Critical
Permanent power	Tue Sep 7, 2027	Fri Oct 1, 2027 (M7)	Critical
Pre-commissioning (illustrative)	Mon Oct 4, 2027	Fri Oct 29, 2027	Critical
Commissioning	Mon Nov 1, 2027 (M8)	Fri Jan 14, 2028 (M9)	Critical
Mezzanine interiors (illustrative)	Tue Sep 7, 2027	Fri Nov 26, 2027	About 4 weeks total float, to Fri Dec 24, 2027

A monthly control cycle

Each month Halvorsen statuses its P6 schedule and submits the XER with its narrative. The owner's representative checks the update before accepting it: actual dates match site records, no logic was deleted, no constraints were added to hold a milestone, and remaining durations are believable. Then the owner updates the master schedule's links to M4 to M9 and compares each milestone with its baseline. If float on the mezzanine path falls from four weeks to one, it is now near-critical and joins the critical path in the monthly report. If M9 forecasts past January 14, 2028, the owner asks for a recovery plan, because the racking contractor's start on January 17 depends on it.

Owner's move

• Write the schedule rules first. The plan in this lesson belongs in the tender documents. If it is not there, agree it at kickoff and record it in the minutes.
• Make milestones the bridge. Use the same milestone IDs and names in the P6 schedule and the owner's master schedule.
• Review the update, not just the dates. Logic changes and new constraints hide in monthly updates. Compare each XER with the previous one.
• Watch float trends. A path losing float every month is tomorrow's critical path.
• Put owner work on the critical path. Permits, owner decisions and separate contracts can delay the job as easily as concrete.

Common mistakes

1. Accepting a baseline without checking logic. A schedule full of constraints and open ends calculates dates but not a real critical path.
2. Different calendars in the two schedules. A missing statutory holiday in one tool moves every date after it.
3. Re-baselining to hide delay. A new baseline needs an approved change, not a bad month.
4. Treating float as the contractor's buffer. How float is shared should be agreed in the plan, not argued after a delay.
5. Leaving owner activities out of the master schedule. The racking start at M10 cannot be protected if it is not linked to M9.

Quick quiz

1. How many processes does the Schedule performance domain have in the 8th edition?

   1. Three
   2. Four
   3. Six
   4. Seven

2. Which 8th edition process now covers sequencing activities and estimating their durations?

   1. Plan Schedule Management
   2. Develop Schedule
   3. Monitor and Control Schedule
   4. Define Scope

3. In Figure 3, the mezzanine interiors finish on November 26 and could finish as late as December 24 without delaying M9. What is that slack called?

   1. Lag
   2. Lead
   3. Total float
   4. Contingency

4. Where does Northgate's P6 schedule start?

   1. M0, contract executed
   2. M1, kickoff
   3. M3, site mobilization
   4. M4, foundations and slab

5. Halvorsen's monthly P6 update forecasts M9 two weeks late. What should the owner do first under the Schedule domain?

   1. Re-baseline to the new date
   2. Ask for a recovery plan or a change request through Governance
   3. Delete the racking start
   4. Add a constraint to hold M9

Show answers and explanations

1. A. Plan Schedule Management, Develop Schedule, and Monitor and Control Schedule.
2. B. Develop Schedule absorbs the 6th edition's Define Activities, Sequence Activities and Estimate Activity Durations.
3. C. Total float is how long an activity can slip without delaying the project finish or a constrained milestone.
4. C. The fact sheet says the contractor's schedule starts at mobilization; the owner's master schedule starts at M0.
5. B. The response is recovery inside the scope, or a change request decided through Governance. A constraint hides the delay; it does not fix it.

Key terms

Schedule performance domain

The PMBOK Guide 8 domain covering timelines, sequencing and coordination of work, through three processes.

Schedule management plan

The rules for building, checking, updating and reporting the schedule.

Schedule model

The activities, logic, durations and calendars from which dates are calculated. Gantt charts and milestone charts are views of it.

Critical path

The longest path of logically linked activities through the schedule; it sets the earliest finish date.

Total float

How long an activity can slip without delaying the project finish or a constrained milestone.

Status date

The date up to which progress is recorded in an update; P6 calls it the data date.

Schedule baseline

The approved version of the schedule used to measure performance, changed only through the change process.

References

1. Project Management Institute, PMBOK® Guide, Eighth Edition (product page: seven performance domains, November 2025 publication).
2. PMExams, The full PMBOK 8 process map in reader order (process names by domain).
3. Elizabeth Harrin, Rebel's Guide to Project Management, Project performance domains explained (updated for PMBOK 8) (2026).
4. 4PMTI, What is the PMBOK 8th edition? Principles, domains, focus areas, and what changed.
5. Ricardo Vargas, PMBOK Guide 8th edition processes flow.
6. BRC Academy, Northgate fact sheet (fictional case study).

Verified on November 6, 2026.

Next lesson in this trackDomain: Finance