Out-of-sequence progress in Primavera P6 is progress recorded on a successor activity before the logic says it could have happened: the successor has an actual start (or actual finish) while a predecessor that should have come first is still incomplete. If Activity B is tied to Activity A by a Finish-to-Start relationship and B has started while A is still open, B is out of sequence.
P6 does not refuse the progress. It records it and then schedules the remaining work according to the project's scheduling option for progressed activities: Retained Logic, Progress Override or Actual Dates. Whichever option is set, out-of-sequence activities left uncorrected distort float, the critical path and the forecast, so they should be found and resolved at every update.
What is out-of-sequence progress in P6?
An activity is out of sequence when its actual dates contradict one of its predecessor relationships. The common case is a Finish-to-Start successor that has started before its predecessor has finished. The same applies to a Start-to-Start successor that started before its predecessor started, or a Finish-to-Finish successor that finished before its predecessor finished.
How P6 then schedules the successor's remaining duration depends on the option set in the Schedule Options dialog (General tab, "When scheduling progressed activities use"):
- Retained Logic: the successor's remaining work waits for the unfinished predecessor, so it is scheduled after the predecessor finishes.
- Progress Override: the relationship is ignored for the progressed successor, so its remaining work proceeds from the data date.
- Actual Dates: the third option, which schedules progressed activities from their actual dates. It is rarely used on construction programmes.
The differences, and why the choice matters in a claim, are covered in retained logic vs progress override.
Why does out-of-sequence progress happen?
- The field did not follow the plan. Crews start early because a resource, a weather window or a workface became available, or because management pushed for it.
- The logic is wrong. Missing or inappropriate relationships (an over-strict Finish-to-Start where the work really overlaps, or a missing Start-to-Start with lag) force a sequence nobody intended to follow.
- Resources moved early. A crew leaves a predecessor with remaining work in it and starts on the successor.
- Statusing errors. Actual dates are typed incorrectly, or progress is applied to the wrong activity.
How does out-of-sequence progress distort the schedule?
- Unreliable float. Out-of-sequence logic can inflate or deflate total float and hide the true critical path. Under Progress Override, the unfinished predecessor no longer drives the progressed successor, so its remaining work can show float it does not really have.
- Misleading earned value. Progress is earned on work the plan did not expect yet, which can overstate performance against the planned sequence.
- Distorted forecast. Under Retained Logic, the successor's remaining work is pushed out behind the predecessor, which may show a delay that the field does not expect. Under Progress Override, the schedule can look compressed and hide a future clash between the two activities.
- Weaker schedule quality results. Out-of-sequence progress is not one of the DCMA 14 points, but it affects the logic, negative float and critical path test results, and reviewers and many owner specifications report the count at each update.
How do you fix out-of-sequence progress in P6?
Step 1: Identify the out-of-sequence activities
In the Schedule dialog, tick "Log to file" and schedule the project. The schedule log lists the out-of-sequence activities. You can also filter or sort for activities with an actual start where a Finish-to-Start predecessor has no actual finish, or check the relationships of each in-progress activity in the Relationships tab or the Activity Network view. A schedule-checking tool or a standard P6 report gives the same list.
Step 2: Find the root cause
For each activity, ask three questions: is the logic right, did the site really work out of sequence, or is it a data entry error? If the logic is wrong, fix the relationships. If it is a data entry error, correct the actual dates against the site records (daily reports, progress records). If the site genuinely worked out of sequence, update the logic to reflect how the work was actually done.
Do not change genuine actual dates to make the logic look clean. Actual dates are a record of what happened, and altering them undermines the schedule as evidence.
Step 3: Correct the logic
- Change a Finish-to-Start relationship to Start-to-Start with a lag, or add a Finish-to-Finish, where the activities really overlap.
- Where the successor has started but genuinely still needs the predecessor's output to finish, tie the predecessor to the successor's finish (Finish-to-Finish) rather than its start.
- Remove relationships that no longer reflect the work, and make sure the predecessor still has a valid successor so it does not become an open end.
- Remove constraints that force a sequence the field is not following.
Step 4: Reschedule and check again
Reschedule the project (F9) and review the schedule log for remaining out-of-sequence activities. Repeat until the count is as close to zero as the facts allow.
Step 5: Document and communicate
Record in the update narrative which activities were out of sequence, why, and what logic was changed. Where out-of-sequence work comes from a constructive change or acceleration, say so. This record matters if the programme is later used in a delay analysis.
How do you prevent out-of-sequence progress?
- Build realistic logic. Use Start-to-Start and Finish-to-Finish relationships where work overlaps, and avoid over-constraining the network.
- Train the people who status the programme. Progress updates should record the sequence actually followed on site.
- Review every update. Run a schedule quality check, including the DCMA 14-point assessment and an out-of-sequence count, each month. An independent reviewer (Project Assure) does this as part of a schedule review under our project controls and EVM service.
- Set the scheduling option deliberately. Retained Logic is the usual choice for construction programmes because it keeps the effect of unfinished predecessors visible. Whatever you choose, state it and keep it the same from update to update.
Out-of-sequence progress is common and manageable. Find it at every update, fix the cause rather than the symptom, and record what changed, and the programme stays reliable for forecasting, earned value and any later delay analysis.
