Project Portfolio & Resource Management
Schedule baselines and variance history
An authorized project Manager reviews a summary and explicitly sets a schedule baseline. Undated tasks are reported as gaps; dates are never invented. Current schedule edits do not alter saved baseline snapshots.
Steps to follow
- 1
Baselines retain task identity, hierarchy, dates, duration, dependencies, milestones and the working calendar used. Grid and Timeline compare baseline and current dates using working-day variance, marking delays, earlier dates, unchanged dates and unavailable comparisons.
- 2
Added tasks are marked; removed tasks retain comparison history. Rebaselining requires a reason and explicit confirmation, retains earlier versions, and identifies the current reference baseline. Select an earlier baseline for comparison.
- 3
Setting a baseline approves neither execution nor resource allocations and does not change official project health. Whole-schedule deletion preserves baselines, task history and audit history.