Free tool
Critical path viewer for P6 (XER)
Drop a Primavera P6 XER file and see the critical and near-critical activities on one clear bar chart: how many there are, where the float sits and whether the critical path is believable. The file is read in your browser and never leaves your computer.
Project
Need to know what moved the critical path?
Chronaxis compares every update window by window, shows which events drove the delay and writes the analysis for your claim or review.
Join the founders listReading a critical path
The critical path is the longest chain of logically linked activities to completion: any delay to it delays the finish. In P6 it shows as activities with total float of zero or less, or as the longest path when that option is used. A reliable programme usually has one continuous critical path from the data date to completion, with a sensible share of activities on it.
- Very few critical activities (or a broken chain) often means constraints or missing logic are hiding the real path.
- Too many critical activities (often above 30%) usually points to constraints, a compressed programme or a finish date that is already in trouble.
- Negative float means the programme already forecasts a finish later than a constraint or the contract date.
- Near-critical work is where the next delay will come from: watch everything within ten working days of float.