A schedule data template captures the detailed information used to develop, analyze, and update the project schedule, including the activity list, dependencies, durations, resource assignments, and critical path analysis. According to the Project Management Institute (PMI), schedule data is a key output of the Develop Schedule process within the Planning Performance Domain in PMBOK 8, providing the underlying dataset that drives all schedule analysis, performance measurement, and forecasting activities. The schedule data template is the technical foundation of the project schedule — while the Gantt chart is the visual representation stakeholders see, the schedule data template contains the precise activity attributes and network logic that make schedule analysis, critical path identification, and earned value calculations possible. Without accurate and complete schedule data, earned value management cannot function and schedule performance reporting is reduced to subjective assessment rather than objective measurement.

What is Schedule Data?

A schedule data template encompasses all information needed to describe and support the schedule model, including the activity list, activity attributes, network logic, resource assignments, durations, calendars, and constraints. It is the dataset from which the Gantt chart, milestone list, critical path analysis, and schedule reports are derived. Schedule data is maintained throughout the project lifecycle, updated as activities are completed and as remaining work estimates are refined based on actual performance and remaining scope. In PMBOK 8, the schedule data template is the source of truth for all schedule calculations including earned value schedule metrics (Planned Value, Earned Value, Schedule Variance, SPI), critical path float analysis, and schedule forecast calculations that project when the project will complete relative to the approved schedule baseline.

What's Included in This Schedule Data Template?

• Activity List — Complete catalogue of all schedule activities with unique IDs, descriptions, WBS mapping codes, responsible owners, and activity type classifications that provide the complete inventory of project work elements to be scheduled and tracked.
• Activity Attributes — Detailed attributes for each activity including planned duration, estimated effort, predecessor activities, successor activities, dependency type (FS, SS, FF, SF), lead and lag values, and any date constraints imposed by external factors.
• Network Logic Summary — Structured presentation of the activity dependency network showing how activities are sequenced, what drives the critical path, and where schedule float exists that can be used to optimize resource loading without impacting the project completion date.
• Critical Path Analysis — Early and late start and finish dates for each activity, total float, free float, and the identification of which activities are on the critical path with zero or near-zero float, requiring priority management to protect the schedule baseline.
• Schedule Baseline vs. Actual — Side-by-side comparison of baseline planned dates versus current actual and forecast dates for each activity, with remaining duration estimates that enable earned value schedule performance calculations each reporting period.
• Milestone Register — Key milestones with baseline dates, current forecast completion dates, variance from baseline in working days, and the status indicator (on track, at risk, or behind) that feeds directly into the schedule forecasts template and project status report.

How to Use This Schedule Data Template (PMBOK 8)

1. Populate the activity list from the WBS dictionary — Derive schedule activities from WBS work packages using the WBS dictionary as the source of work package descriptions and acceptance criteria. One work package typically generates multiple schedule activities at the execution level of detail.
2. Sequence activities using Precedence Diagramming — Document all activity dependencies using the four relationship types (FS, SS, FF, SF) with lead and lag values where appropriate. Every dependency should have a technical or contractual justification — discretionary dependencies that create unnecessary constraints should be eliminated.
3. Estimate durations using approved techniques — Apply the estimating techniques defined in the schedule management plan to each activity. Document the basis of each duration estimate in the basis of estimates template for auditability and future comparison with actual durations.
4. Calculate the critical path and identify zero-float activities — Use forward and backward pass calculations to identify the critical path and quantify total float for every activity. Prioritize management attention and risk mitigation toward activities on or near the critical path.
5. Update actual dates weekly for performance reporting — Record actual start and finish dates and remaining duration estimates for in-progress activities at each reporting cycle. Accurate actuals are the prerequisite for meaningful earned value schedule performance calculations.

When to Create This Document (PMBOK 8)

The schedule data template is created during the Planning Performance Domain as part of the Develop Schedule process. In PMBOK 8, it is the analytical dataset underlying the project schedule baseline and all subsequent schedule performance reporting. The schedule data is maintained continuously throughout execution, with actual performance data updated at each reporting cycle and remaining work estimates revised as needed to reflect current conditions and approved scope changes.

Related Templates

• Schedule Management Plan Template
• Schedule Forecasts Template
• Work Performance Information Template
• Basis of Estimates Template
• Project Calendars Template