How to Use Primavera P6 Baselines
A baseline preserves an approved schedule state. A comparison in P6 is useful only when everyone knows which version represents the original commitment, how changes are approved and which forecast is current.
Define exactly what was approved
Capture a baseline after scope, milestones, calendars and major dependencies have been reviewed. Record the approval date, boundaries and unresolved assumptions. Without that context, a later variance may look like poor execution when the deliverables have actually changed. Name the version so project leads and clients can refer to the same schedule state during a review.
Explain variance before assigning action
Compare intermediate milestones and the activities behind movement, not just the final finish date. Distinguish a late start from increased remaining duration, revised logic or added scope. Bars show that dates moved; status records and the change log explain why. This distinction helps the team choose between recovery work, formal approval of a change and a better forecast estimate.
Keep change history readable
When a new deliverable is agreed, record the request, decision and schedule effect separately from routine progress updates. A newly approved baseline may be appropriate while the original remains available for historical comparison. Define the rule in the project’s control process. On European programmes with several contracting parties, a shared version register helps prevent different teams reporting against different commitments.
Use comparisons to frame decisions
Present a small set of material changes with the original date, current forecast, cause, owner and next action. A long list of every shifted activity can obscure the interfaces that matter. Check that the selected baseline covers the same project scope as the report. A precise looking comparison against an outdated or differently bounded version can still lead to the wrong conclusion.
Frequently asked questions
Should a baseline be replaced after every update?
No. Update the live schedule routinely; establish a new baseline only for an agreed reason with documented approval.
How should a scope change appear in baseline reporting?
Record the change and its schedule effect separately, then follow the project’s approval process to decide whether a new reference is needed.
Need help with your project schedule? Explore our project planning services.