Retained Logic and Progress Override are two of the three Primavera P6 options that decide how an out-of-sequence activity is scheduled. Under Retained Logic, the remaining work of an activity that started before its predecessor finished keeps waiting for that unfinished predecessor. Under Progress Override, P6 ignores that relationship and the remaining work proceeds from the data date. The third option is Actual Dates.
The choice changes the forecast finish, the float and which path is critical. For a construction programme, and for any programme that may be used in a claim, Retained Logic is the usual default, and the option used must be stated in a delay analysis.
Where are the scheduling options in Primavera P6?
In P6 Professional, open Tools, Schedule, Options, then the General tab. The setting is labelled "When scheduling progressed activities use", with three choices: Retained Logic, Progress Override and Actual Dates. It is a project-level setting saved with the project, so it travels with the XER and applies every time the project is scheduled.
It only matters for out-of-sequence activities: progressed activities whose actual dates contradict a predecessor relationship, typically a Finish-to-Start successor that has started while its predecessor is still incomplete. For activities progressed in sequence, Retained Logic and Progress Override give the same dates. How to find and clean up those activities is covered in out-of-sequence progress in P6.
What is the difference between retained logic and progress override?
- Retained Logic: the relationship is kept. The out-of-sequence activity's remaining duration cannot be scheduled until its unfinished predecessor finishes (for a Finish-to-Start tie). If the predecessor runs late, the successor's remaining work is pushed out with it.
- Progress Override: the relationship is ignored for the progressed successor. Its remaining duration is scheduled from the data date regardless of the predecessor's status. The predecessor's remaining work no longer drives that successor, so the predecessor can show float it does not really have.
- Actual Dates: progressed activities are scheduled from their actual dates rather than the logic. It is intended for schedules where actual dates may fall after the data date. On a correctly statused programme, where no actual date is later than the data date, it is rarely needed, and if a schedule uses it the reviewer should find out why.
How does each option handle a worked example?
Activity A (6 working days) is the Finish-to-Start predecessor of Activity B (5 working days). At the data date, A has 3 days done and 3 remaining. B has already started out of sequence, with 1 day done and 4 remaining.
Retained Logic
B's 4 remaining days cannot start until A's 3 remaining days are finished. B is forecast to finish 7 working days after the data date. A stays on B's driving path, and if A slips, B slips with it.
Progress Override
B's 4 remaining days start at the data date, so B is forecast to finish 4 working days after the data date, 3 days earlier than under Retained Logic. A's remaining work no longer controls B, so a delay to A does not show up on B or on anything after B.
How does the option change the forecast and critical path?
| Aspect | Retained Logic | Progress Override |
|---|---|---|
| Remaining duration of the out-of-sequence successor | Starts after the unfinished predecessor finishes | Starts from the data date |
| Forecast finish | Later, more conservative | Earlier, may mask delay |
| Critical path | Follows the network logic | Can show a path that does not reflect the remaining dependencies |
| Float on the predecessor | Calculated through the successor | Can be inflated, because the predecessor no longer drives the successor |
Retained Logic gives the more realistic forecast when the original logic is still valid. Progress Override can be justified when the team has genuinely resequenced the work and the remaining dependency no longer exists, but in that case the better fix is to correct the relationships so the logic says what is really happening.
Which scheduling option should you use for a construction schedule?
Use Retained Logic as the default for baseline and monthly updates. It keeps the effect of unfinished predecessors visible, which is what owners, reviewers and delay analysts expect to see. Treat out-of-sequence activities as a logic problem to fix at each update, not as something the scheduling option should hide.
Why does the setting matter in a claim or delay analysis?
The option decides whether an unfinished predecessor still drives its out-of-sequence successor, so it decides which path is critical and how much float each path has. The same update calculated under Retained Logic and under Progress Override can show different critical paths and different forecast finishes. A delay that is critical under one option may sit on a path with float under the other.
- State the setting. A delay analysis report should say which option each update was scheduled with. Without it, another expert cannot reproduce the critical path or the delay.
- Keep it consistent. In a windows or other update-based analysis, a change of option between updates can create or remove apparent delay that has nothing to do with events on site. If a change was made, identify it and show its effect separately.
- Do not change it silently. Rescheduling contemporaneous updates under a different option from the one the project used changes the evidence. If the analyst believes a different option is more appropriate, the reasons and the effect should be set out.
- Watch for masked delay. Progress Override can make the programme look as though it is recovering when the predecessor delay is still there, which weakens a claim built on it and invites challenge.
Checking the scheduling option and the out-of-sequence activities in each update is a standard step in our forensic planning work.
What are the best practices?
- Default to Retained Logic for the baseline and all monthly updates.
- Record the scheduling option in the update narrative, and document any use of Progress Override or Actual Dates with the reason.
- Find out-of-sequence activities at each update (the schedule log lists them when "Log to file" is ticked) and correct the logic rather than relying on the option.
- Run a schedule quality check, including the DCMA 14-point assessment, after each update. Out-of-sequence progress is not one of the 14 points, but it affects the logic, negative float and critical path test results.
- If you want to see the effect of Progress Override, model it in a copy of the project as a what-if rather than changing the primary schedule.
Retained Logic keeps the CPM network honest about what is still waiting for what, which is why it underpins credible forecasting and delay analysis. Progress Override is a shortcut that can lead to the wrong critical path. Know which one your programme uses, keep it consistent and say so.
