Critical Path Report
The part of the route to finish with no P6 float left, and what a delay to it moves.
Not assignedEvidence detailsChecking
Critical Path Report content
Inspect saved schedule uncertainty
The longest path from declared logic, beside the total float this tool computed and the total float P6 reported. Where those disagree is a review signal, not a defect: P6 applies constraints and calendars this pass does not.
Load a review to read the critical path.
How this reading is bounded
The activities within two weeks of critical that are not on the longest path: the ones that could join it next. Float is read in working days of each activity's own calendar, and each ring names the few activities every path in it has to pass through.
Path 1 is the critical path. Path 2 is what takes over when it is recovered, or what goes critical first if anything slips. Each activity sits on exactly one path, traced back through the relationships that actually drive it.
Insert a delay into the logic and run the whole network again. See what it pushes later downstream, the float it takes from the work upstream, and what becomes critical because of it.
Pick an activity, or use Delay on any row above.
Declare the event as a fragnet: new activities with their working days, tied into this version's logic. The version is scheduled from its data date without the fragnet and with it, every activity on its own calendar, and only if it first reproduces P6's own dates. A bounded simulation: it reads what moves, never whose delay it was.
Declare an event to run the analysis on this version.
Name the delays to take out of this version's as-built: an activity, how many working days, and what happened. The as-built is rebuilt from the recorded dates and must reproduce them exactly first; then each delay comes out alone and all together. A bounded simulation: it reads how far the completion comes back, never whose delay it was.
Name a delay to collapse this version's as-built.
The first open activity on the critical path is held for longer and longer, and the whole network is run again each time: when the finish starts to move, and when it moves further than recovery can pull back at the declared crash share. A counterfactual on this schedule's own logic, not a forecast.
Load a review to read its stress tests.
Saved schedule uncertainty
Configure or run a simulation in What-If
How does the target's remaining network time vary under declared duration assumptions?
Working hours only—not calendar finish dates, P6 verification or a completion guarantee. Every trial recalculates the whole eligible network, so the driving path can change.
Choose an authorized review.
Practice history gaps and re-declaration — synthetic, resettable demo
Review legacy subjects before declaring them again. A new declaration seals today's attestation; unavailable older content stays a history gap.
Reading authorized projects…
Review status and evidence steps
Steps of the decision on this page.
