Baselines & Compare
Govern baseline designations and compare one compatible update.
Not assignedEvidence detailsChecking
Baselines & Compare content
An XER role or XML hint may be a candidate, but it never silently becomes the client-approved baseline.
The project and update come from the workspace header above.
Loading the current client-approved baseline…
Waiting for project context…
The current client-approved baseline is used by default. A visible temporary override never changes the register.
Set the client-approved baseline in the comparison setup above. The selected update will appear here.
Actual dates, else P6’s forecast, against the baseline’s own dates, in working days on each activity’s calendar. It shows what moved, not why or whose.
Compare the baseline with an update to see each activity against the plan.
Governed registerBaseline historyHistory kept
Prior and current designations remain readable; changing the approved baseline closes the prior knowledge interval.
Loading baseline history…
How much float your package held at the baseline, how much it holds in this update, and which observed changes account for the difference. The hours that are not accounted for are stated, not absorbed.
Choose authorized project releases in order. Compare each with the first anchor, or browse adjacent updates. This does not change the approved baseline.
Choose a project to read its full release inventory.
Review status and evidence steps
Steps of the decision on this page.
