Free tool
Fix out-of-sequence and find what is wrong in a P6 programme
Drop a Primavera P6 XER file. In seconds you see the activities causing trouble - out-of-sequence progress, what pulls the float negative, what drives the finish, open ends, dates in the future - each with the fix. For out-of-sequence progress it tells you how to manage it, suggests a fix for every link, and - when you accept - gives you an XER with the out-of-sequence removed. The file is read in your browser and never leaves your computer.
Drop your XER file hereor click to choose a file 路 .xer exported from Primavera P6
馃敀 Processed locally in your browser. Nothing is uploaded.
Project
Want this checked on every update, automatically?
Chronaxis checks each update against the last one, flags float erosion and logic changes early, and turns the programme into your monthly report or EOT claim.
Try Chronaxis free for 14 daysWhat the checks mean
- Out of sequence: an activity was progressed before its predecessor allowed it. Under retained logic P6 keeps its remaining work waiting for the predecessor, which can push the critical path and the finish for no real reason. The out-of-sequence manager explains each link, suggests the fix (start-to-start plus finish-to-finish where the work overlapped, remove the link where the predecessor never started) and, when you accept, gives you an XER with no out-of-sequence left.
- Negative float always comes from a date the logic cannot meet: a constraint or the project's Must Finish By date. The tool lists those dates.
- Driving activities are the ones that move completion. That is where to look first when the finish slips.
- Open ends and long lags hide float and waiting time; Engineers reject programmes that rely on them.
Related: DCMA 14-point check 路 compare two updates 路 critical path viewer 路 make an XER smaller