A schedule data template is the structured document that captures the collection of information used to describe and control the project schedule model, including all milestones, activities, attributes, assumptions, and constraints that underpin the schedule. According to the Project Management Institute (PMI), schedule data is a key output of the Develop Schedule process in the Schedule Performance Domain of PMBOK 8. It serves as a critical supporting document that provides the context, assumptions, and alternatives behind the project schedule, giving schedule analysts and project managers the information they need to understand how the schedule was built and how to manage it.

What is Schedule Data?

In PMBOK 8, schedule data for the project schedule model is the collection of information for describing and controlling the schedule. Schedule data includes, at a minimum, the schedule milestones, schedule activities, activity attributes, and documentation of all identified assumptions and constraints. The amount of additional data varies by application area. Information frequently supplied as supporting detail includes resource requirements by time period, often in the form of a resource histogram; alternative schedules such as best-case or worst-case, not-resource-leveled or resource-leveled, or with or without imposed dates; and applied schedule reserves. Schedule data may also include items such as resource histograms, cash flow projections, and order and delivery schedules.

What's Included in This Schedule Data Template?

• Schedule Milestones - Key milestone dates with descriptions and the deliverable or decision point each milestone represents, distinguishing mandatory milestones (contractual or regulatory) from informational ones.
• Activity List and Attributes - The complete list of schedule activities with attributes including activity identifier, WBS code, predecessor relationships, leads and lags, resource assignments, and estimated duration.
• Assumptions and Constraints - All assumptions made in building the schedule (e.g., resource availability, external dependency dates) and constraints imposed on the schedule (e.g., must-start or must-finish dates from contracts or stakeholder commitments).
• Resource Requirements by Time Period - A breakdown of resource demand across the project timeline, typically represented as a resource histogram showing peak demand periods and potential over-allocation points.
• Alternative Schedules - Best-case and worst-case scenarios, resource-leveled and not-resource-leveled versions, and schedules with and without imposed dates that provide the basis for schedule risk analysis.
• Applied Schedule Reserves - The schedule contingency reserve allocated at the activity or summary level, with the rationale for the reserve amount and the risks it is intended to address.
• Cash Flow Projections - Time-phased resource costs derived from the schedule, providing an early estimate of cash flow requirements before the formal cost baseline is developed.

How to Use This Schedule Data Template (PMBOK 8)

1. Populate schedule data as an output of the Develop Schedule process - As the schedule model is built in the scheduling tool, capture the underlying assumptions, constraints, and supporting data in this template so the schedule can be understood and maintained by anyone on the team.
2. Document every assumption that affects schedule dates - Undocumented assumptions become invisible risks. If a schedule date depends on an external vendor delivering by a certain date, that dependency must be documented in the assumptions section.
3. Maintain alternative schedules for risk analysis - The best-case and worst-case schedule alternatives enable what-if analysis and support schedule risk quantification during the Perform Risk Analysis process.
4. Use resource histograms to identify over-allocation early - Before the schedule baseline is approved, review the resource histogram to identify periods where resource demand exceeds availability. Address over-allocation through resource leveling or scope negotiation.
5. Update schedule data whenever the schedule changes - Schedule data is an output of Monitor and Control Schedule. When the approved schedule changes, the underlying assumptions and constraints must be reviewed and updated to reflect the revised model.
6. Use schedule data as input to the risk register - Identified schedule assumptions and constraints that carry uncertainty should be logged as risks in the risk register with appropriate probability-impact assessments.

When to Create This Document (PMBOK 8)

Schedule data is created as an output of the Develop Schedule process, which is part of the Planning Focus Area in PMBOK 8. The initial schedule data package should be completed before the schedule baseline is submitted for approval, ensuring that reviewers can evaluate not just the dates but the assumptions and constraints behind them. Schedule data is updated as an output of Monitor and Control Schedule whenever the project schedule is revised, and the update history provides a traceable record of how the schedule evolved throughout the project life cycle.

Related Templates

• Project Schedule Template
• Schedule Baseline Template
• Schedule Management Plan Template
• Work Breakdown Structure Template
• Resource Requirements Template

Complete Guide & Filled-In Example

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

• Schedule Data 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.