A schedule baseline is the accepted reference plan for a project, saved so that every later update can be compared against it. It preserves the scope, activities, logic, durations, milestones, calendars and assumptions as they stood when the plan was approved. Recording its version and acceptance status tells reviewers exactly which comparison they are making.
A current update answers “where are we now?” A baseline answers “what was the reference plan?” Updating progress does not, by itself, establish a new baseline.
How it works
- Build and review the plan. The contractor develops the schedule from the work breakdown structure, with logic, durations and calendars that reflect the contract. Many contracts require submission within a set number of days after award or notice to proceed.
- Get it accepted. The owner or its scheduler reviews and accepts it, sometimes after several rounds of comments. The accepted version, with its narrative, becomes the baseline.
- Freeze a copy. Scheduling tools keep baseline dates alongside current dates. Primavera P6 can store several baselines per project and compare against a chosen one; Microsoft Project stores a baseline plus up to ten numbered baselines.
- Update against it. Each period, the current schedule is statused to a new data date. Baseline dates stay fixed, so variances show how the forecast has moved.
- Revise only with approval. When an approved change or time extension makes the old plan unrepresentative, a revised baseline is approved and saved as a new version. The earlier baseline stays available.
What a baseline should preserve
- Activity IDs, names, durations and relationships, including lags
- Calendars, holidays and work-week definitions
- Contract milestones and any constraints
- Scheduling settings, such as how out-of-sequence progress is handled and how float is calculated
- Resource and cost loading, if the schedule carries them
- The narrative: assumptions, exclusions, critical path description and basis for key durations
If any of these change between the baseline and an update, a date comparison can mislead. A finish that moved because a calendar was edited is a different story from one that moved because work ran late.
Worked example
Illustrative, on a five-day work week with no holidays in these windows:
| Milestone | Baseline | September update forecast | Variance |
|---|---|---|---|
| Structure topped out | Jul 24 | Jul 31 | +5 working days |
| Enclosure complete | Sep 18 | Oct 2 | +10 working days |
| Substantial completion | Jan 15 | Jan 22 | +5 working days |
Enclosure has slipped ten working days, but substantial completion has moved only five. Tracing the logic shows the enclosure path had about five working days of float to the interior finishes that drive completion, so half of its slip was absorbed.
The variance tells the team where to look, not who is responsible. The next step is to trace which activities changed, check the field records and daily logs behind the actual dates, and confirm that calendars and settings match the baseline. Whether any party is entitled to time is a separate contractual question that needs the contract, notices and evidence.
Kinds of baselines
| Term | What it means |
|---|---|
| Original baseline | The first accepted plan. Kept permanently for the record. |
| Revised or current baseline | An approved re-baseline after a change or extension. |
| Previous update | Last period’s schedule, used for period-to-period comparison. It is not a baseline. |
| Performance measurement baseline | In earned value management, the combined scope, schedule and cost baseline that earned value and indices such as SPI(t) are measured against. |
Distinguish which of these a report compares against. “Two weeks late” against the original baseline and “on time” against last month’s update can both be true.
Why it matters
The baseline is the yardstick for performance, monthly reporting and delay analysis. Without a preserved, accepted baseline, a time impact analysis or delay claim has no agreed starting point, and every party argues from its own version of the plan. The GAO’s Schedule Assessment Guide treats maintaining a baseline schedule as one of its scheduling best practices for that reason.
Common mistakes
- Overwriting the baseline with current dates, which erases the history it exists to keep.
- Re-baselining to hide variance rather than to reflect an approved change.
- Comparing schedules with different calendars or settings as if the dates were directly comparable.
- Treating the previous update as the baseline.
- Accepting a baseline with weak logic, such as open ends or heavy constraints, which makes later variance hard to interpret. The critical path and float entries explain why.
- Losing the narrative, so nobody can later say what assumptions the durations rested on.
Use the baseline submission guide, then the monthly narrative guide. Find the review tools in the Schedule Forensics hub.
FAQ
What is a baseline schedule in construction?
A baseline schedule is the accepted reference plan for a project: its scope, activities, logic, durations, calendars and milestone dates as they stood when the plan was approved. Later schedule updates are compared against it to show how the forecast has moved and which work changed.
What is the difference between a baseline and a schedule update?
The baseline is a frozen reference. An update is the current schedule, statused to a data date with actual progress and a fresh forecast of remaining work. Updating progress doesn't change the baseline; comparing the two shows the variance.
How do you calculate baseline variance?
For a finish date, variance is the current forecast finish minus the baseline finish, usually measured in working days on the activity's calendar. A positive number on most tools means the forecast is later than the baseline. Check whether your software reports variance as baseline minus forecast instead, because the sign convention differs.
When should you re-baseline a schedule?
When the reference plan no longer represents the agreed scope or time, for example after an approved change that adds work or a granted time extension. A re-baseline should be approved, documented with its reason and date, and saved as a new version, with the earlier baseline kept for the record. Re-baselining just to remove unfavorable variance destroys the history it exists to keep.
What is a baseline called in the UK?
UK practice usually says baseline programme or as-planned programme, because schedules are called programmes. Under NEC contracts, the current approved programme is the Accepted Programme, which is revised as the work proceeds, so it plays a different role from a frozen baseline.