Schedule Overview
Inspect one accepted schedule before making comparison claims.
Evidence detailsChecking
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedSchedule Overview content
Inventory, hierarchy, dates, duration, and total float come from the selected immutable review. No trend or finish forecast is inferred.
Review, project, snapshot, Data Date, received time, and parser evidence stay together.
Choose a schedule.
The file carries no trade column. Pick a grouping it already contains — a code prefix, a WBS node, a calendar, or an assigned resource — and this reports what that caught, what it left out, and where your work hands off.
Your window, your float, the tightest run inside your package, and the project milestones downstream of you. Your tightest run is reported separately from the project critical path — they are usually different chains.
An XER carries no cure times, no lead times and no hoist counts, so nothing in the file can contradict it until you say them. Declare what you hold and this reports the durations, starts and site claims the schedule asks for that your evidence cannot support. Declaring nothing tests nothing — it is not a clean bill.
Counts and bounded date/float distributions describe structure, not quality or causation.
Schedule shape loads after a release is selected.
Selected metadata rows only; raw XER/XML bodies and server paths are never returned.
No schedule selected.
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.