Schedule Baseline
Formalise the approved schedule model, lock target dates, and establish the metric against which all project performance will be measured.
§1 Purpose of the Schedule Baseline
The Schedule Baseline is the approved version of the schedule model. Once signed, it can be changed only through formal change-control procedures.
A schedule is highly fluid during the planning phase. Activities are added, durations are debated, and logic is rearranged. However, before execution begins, the Project Manager must draw a line in the sand. The Schedule Baseline formalises the agreement between the project team and the sponsor regarding when work will be completed.
It acts as the yardstick for performance measurement. If a milestone is missed, the delay is calculated as a variance directly against the dates established in this baseline document.
§2 Blank Template
A standardized sign-off framework consolidating the planning outputs into a single approved agreement.
SCHEDULE BASELINE
Purpose
Schedule Baseline Components
The Schedule Baseline encompasses the following approved artifacts:
- Activity List - defined activities derived from the WBS work packages.
- Activity Attributes - detailed attributes and dependencies for each activity.
- Duration Estimates - approved duration calculations for each activity.
- Milestone List - key project milestones with target dates.
- Project Schedule Network Diagram - sequenced activities with logical dependencies.
- Project Schedule - calendar-based schedule (Gantt) with start and finish dates.
- Project Calendar - working and non-working days governing the schedule calculation.
Baseline Key Dates
| Milestone | Approved Target Date |
|---|---|
| [Milestone 1 Name] | [YYYY-MM-DD] |
| [Milestone 2 Name] | [YYYY-MM-DD] |
| [Final Delivery Milestone] | [YYYY-MM-DD] |
Baseline Approval
§3 Worked Example: Mary's Consulting
A completed example demonstrating the formal lock-in of an 8-month digital implementation project timeline.
Notice that the baseline summarizes the key dates, but explicitly references the underlying documentation (like the Activity Attributes) as part of the total locked package. Approval by the Sponsor transitions the schedule from a planning draft to an executable baseline.
SCHEDULE BASELINE
Purpose
Schedule Baseline Components
The Schedule Baseline consists of:
- Activity List - defined activities derived from the WBS work packages.
- Activity Attributes - detailed attributes for each activity.
- Duration Estimates - approved duration for each activity.
- Milestone List - key project milestones with target dates.
- Project Schedule Network Diagram - sequenced activities with dependencies.
- Project Schedule - calendar-based schedule with start and finish dates.
- Project Calendar - working/non-working days governing the schedule.
Baseline Key Dates
| Milestone | Date |
|---|---|
| Project Start (Charter approved) | May 08, 2026 |
| Planning Complete; Baselines Locked | Jun 08, 2026 |
| Requirements Approved | Jul 02, 2026 |
| Design Approved | Aug 07, 2026 |
| Build Complete | Oct 09, 2026 |
| UAT Sign-off | Nov 19, 2026 |
| Production Go-Live | Nov 24, 2026 |
| Hypercare Complete | Dec 10, 2026 |
| Operations Handoff | Dec 15, 2026 |
| Project Closeout | Dec 29, 2026 |
Baseline Approval
Formal Change Control
Once both parties sign this document (on Jun 08), the dates cannot be changed simply by updating a Gantt chart. Any future shift to these dates requires an approved Change Request.
Variance Tracking
This document is the "control" state. If the actual UAT Sign-off occurs on Nov 21, the project manager will report a 2-day negative schedule variance against this baseline.
The Package Deal
The sponsor isn't just approving a list of dates. By signing the baseline, they are implicitly approving the logical dependencies (Network Diagram) and effort calculations (Estimates) that generated those dates.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Schedule Baseline Template & Example. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Schedule Baseline Template & Example as a decision instrument rather than an administrative form. The subject terms—schedule, baseline, template, example, worked—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Schedule Baseline Template & Example?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about schedule would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.