This Schedule Management Plan example shows how Alex Morgan, PMP, defined the approach for developing, monitoring, and controlling the 89-day schedule of Project Phoenix — a $72,250 website launch managed using the PMBOK Guide 8th Edition. The project absorbed an 11-day hosting migration delay and a 4-day design delay, yet delivered on exactly the planned completion date of June 13, 2025. This example shows the schedule management framework that made that outcome possible.

What Is a Schedule Management Plan?

A Schedule Management Plan is a subsidiary component of the Project Management Plan that defines the approach for developing, managing, and controlling the project schedule. It specifies the scheduling methodology, tools, estimating techniques, schedule control procedures, performance thresholds, and the rules for updating and re-baselining the schedule. In PMBOK 8, schedule management is addressed within the Planning and Measurement Performance Domains. The Schedule Management Plan ensures that all team members understand how the schedule works, what their obligations are for updating progress, and at what point a schedule deviation escalates from a team-level concern to a sponsor-level issue.

What's Inside This Schedule Management Plan Example

This Schedule Management Plan example for Project Phoenix includes:

• Scheduling tool: Microsoft Project for baseline schedule and critical path analysis, with a GitHub project board used for sprint-level task tracking during the development phase
• Estimating technique: analogous estimating for overall phase durations (based on MCG's 2022 website project) combined with expert judgment from Sam Lee (backend) and Priya Patel (design) for activity-level estimates
• Work calendar: Monday to Friday, 8 hours per day; public holidays and Sam Lee's Week 10 leave documented in the resource calendar; BrightFrame's external availability windows incorporated
• Critical path: Design -> Architecture Freeze -> Development -> UAT -> Go-Live — six milestones on the critical path spanning 62 working days of the 89-day project timeline
• SPI thresholds: SPI below 0.90 triggers a recovery plan (PM-initiated); SPI below 0.80 escalates to Sponsor (Riley Park) with a mandatory recovery proposal within 48 hours
• Schedule change control: schedule changes affecting activities on the critical path by more than 3 days require CCB approval; changes to non-critical activities within float can be approved by the PM alone
• Outcome: SPI of 1.00 at project close — Project Phoenix was delivered on exactly the June 13, 2025 target date despite absorbing 15 days of cumulative delay through deliberate buffer management

How Alex Morgan Used This Schedule Management Plan

When ISS-005 (hosting migration delay) pushed the infrastructure migration from May 3 to May 14 — an 11-day slip on a near-critical-path activity — Alex Morgan followed the Schedule Management Plan's recovery protocol: the SPI dropped to 0.84 in Period 2, triggering the recovery plan process. Alex identified 11 days of schedule buffer in non-critical activities (primarily documentation tasks in the QA phase) and reallocated them to cover the hosting delay. The recovery plan was presented to Riley Park within 24 hours, and the revised schedule was approved without a formal re-baseline. By Period 4, SPI had recovered to 0.97 and the June 13 completion date was back on track.

Download and Customize

This Schedule Management Plan example is available as a free download. Use it as a reference to build your own plan, or start with the blank template and fill it in for your project.

• Download the Schedule Management Plan Template — PMBOK 8 (blank, ready to use)
• Read the article: Schedule Management Plan in PMBOK 8 — Guide and Best Practices

Schedule Management Plan Example: Key Takeaways

The most important lesson from this Schedule Management Plan example is that schedule resilience is built during planning, not during execution. The 11 days of buffer that Alex Morgan used to absorb the ISS-005 delay were not created in the moment — they were deliberately built into the schedule during planning, distributed across non-critical activities so they would not create complacency while still being available for reallocation under pressure. This is the practical application of the PMBOK 8 principle of optimism bias management: plan for uncertainty by building in explicit schedule margin, govern that margin with clear criteria for use, and measure schedule performance honestly throughout execution.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.