Baselines & Compare
Govern baseline designations and compare one compatible update.
Evidence detailsChecking
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedBaselines & 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.
Governed registerBaseline historySCD-II
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.
Review status and evidence steps
Steps update from visible page evidence. Blocked and withheld states name the boundary; no completion percentage is inferred.
Discussion questions and talking points
Observed → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.
Unavailable context remains explicitly not supplied.
This talking point preserves the page’s evidence and authority boundary.