Shocks, Issues & Risks
Read what happened around the schedule, and what may still.
Evidence detailsChecking
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedShocks, Issues & Risks content
A risk has not happened and carries probability times impact. An issue has, and carries a severity. A shock came from outside the project. Nothing here infers a cause.
Observed records carry a source and are evidence. Modelled records are plausible reconstruction and are not. They are never added together.
Probability times impact, largest first. Exposure is a weighting, not a prediction: a 40% risk does not mean four tenths of a delay.
Choose a project.
Front-days are working days lost on the affected front. A front holding float can lose days without the project moving, so this is a workload figure and never a schedule variance.
Choose a project.
A shock is dated and hits named fronts. That an issue followed one is a sequence, not a cause.
Choose a project.
The share of issues a risk had already been logged for. It is not a grade: some things cannot be foreseen, and a register that predicted everything was written afterwards.
Choose a project.
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.