A schedule baseline template captures the approved version of the project schedule model that serves as the official reference point against which all schedule performance is measured throughout the project. According to the Project Management Institute (PMI), the schedule baseline is a key output of the Develop Schedule process in the Schedule Performance Domain of PMBOK 8 and a component of the project management plan. Changes to the schedule baseline can only be made through formal change control procedures, ensuring that any deviation from the approved timeline is deliberate, documented, and evaluated for its impact on cost, scope, and project objectives.

What is a Schedule Baseline?

In PMBOK 8, the schedule baseline is the approved version of a schedule model that can be changed using formal change control procedures and is used as the basis for comparison to actual results. The schedule baseline is accepted and approved by the appropriate stakeholders as the baseline for the schedule, with baseline start dates and baseline finish dates. During monitoring and controlling, the approved baseline dates are compared to the actual start and finish dates to determine if variances have occurred. The schedule baseline is a component of the project management plan and forms part of the performance measurement baseline (PMB) together with the scope baseline and the cost baseline. The schedule baseline may also include the project schedule's associated milestones, work packages, and planning packages.

What's Included in This Schedule Baseline Template?

• Baseline Approval Information - The date the baseline was approved, the approving authority, and the version number, establishing the formal starting point for schedule performance measurement.
• Baseline Start and Finish Dates - Approved start and finish dates for each schedule activity, work package, and milestone, against which actual dates will be compared during monitoring and controlling.
• Critical Path Activities - Identification of all activities on the critical path with zero or negative float, representing the sequence of activities that determines the minimum project duration.
• Milestone Schedule - All key milestones with their baseline dates, including mandatory milestones (contract deliverables, regulatory submissions) and informational milestones (management reviews, phase gates).
• Summary Schedule by Phase or WBS Level - A high-level view of the baseline schedule organized by project phase, WBS level, or responsible team, supporting stakeholder communication and progress reporting.
• Float Analysis - Total float and free float for each activity, identifying which activities have flexibility and which are at risk of delaying the critical path if they slip.
• Baseline Change History - A log of all formally approved changes to the schedule baseline, including the change request reference, date approved, reason for change, and the impact on the project completion date.

How to Use This Schedule Baseline Template (PMBOK 8)

1. Finalize the baseline only after stakeholder approval - The schedule baseline becomes the official reference point the moment it is approved. Ensure that all key stakeholders, including the sponsor, have reviewed and accepted the baseline before it is locked.
2. Never modify the baseline without a formal change request - In PMBOK 8, changes to the schedule baseline are processed through the Assess and Implement Changes process using integrated change control. Informal adjustments to baseline dates, even with good intentions, undermine the integrity of performance measurement.
3. Use the baseline as the denominator in schedule variance calculations - Schedule Variance (SV = EV − PV) and Schedule Performance Index (SPI = EV/PV) both use planned value derived from the schedule baseline. Accurate EVM requires an accurate and unchanged baseline.
4. Document the rationale for all baseline changes - When the baseline must change (approved change requests, scope changes, major risk events), the change history log provides the audit trail needed for lessons learned and future project planning.
5. Review the baseline at phase gates and major milestones - At phase boundaries, assess whether the remaining schedule baseline remains realistic given actual performance to date. If not, prepare a change request to rebaseline rather than continuing to report against an unachievable plan.
6. Archive the original baseline even after rebaselining - The original approved baseline represents the initial project commitment. Retaining it alongside any approved revisions preserves the complete history of the project's schedule evolution.

When to Create This Document (PMBOK 8)

The schedule baseline is created as an output of the Develop Schedule process during the Planning Focus Area in PMBOK 8. It is formally established when the project schedule model has been reviewed, all resource constraints have been accounted for, schedule risks have been identified, and the schedule has received approval from the appropriate stakeholders. The schedule baseline must be in place before the project enters the Executing Focus Area, as it is a required input to Monitor and Control Schedule and the performance measurement baseline.

Related Templates

• Project Schedule Template
• Schedule Management Plan Template
• Schedule Data Template
• Scope Baseline Template
• Work Breakdown Structure Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Schedule Baseline in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.