Esc

↑↓ move↵ openIndex · Pagefind
Project management

Retained Logic

Definition

A progress setting where an out-of-sequence activity's remaining work still waits for its unfinished predecessors.

Topic: Scheduling

Updated

Retained logic and progress override on the same progressTwo versions of the same update. In both, framing has 4 working days left after the data date and drywall has an early actual start before it. Under retained logic, drywall's remaining 6 days wait for framing to finish and end on day 10. Under progress override, drywall's remaining 6 days start at the data date and end on day 6.Data dateRETAINED LOGICFraming, 4 days leftDrywall, 6 days leftFinishes day 10PROGRESS OVERRIDEFraming, 4 days leftDrywall, 6 days leftDay 6
Illustrative: the same out-of-sequence progress forecast two ways. Retained logic holds drywall's remaining work until framing finishes; progress override starts it at the data date.

Retained logic is a scheduling setting for activities that started out of sequence, before their predecessors finished. Under retained logic, the activity’s remaining work can’t continue until the unfinished predecessor completes. The relationship is kept for the remaining work even though the start already broke it. It is Primavera P6’s default.

The alternative is progress override. It releases the incoming relationship, so the remaining work continues from the data date.

How it works

The setting only matters when out-of-sequence progress exists. For an activity that has no actual start, or whose predecessors are all complete, retained logic and progress override give the same answer.

When an activity has an actual start but a finish-to-start predecessor is still open, the scheduling engine has to decide what to do with the remaining duration. Under retained logic it:

  1. Leaves the actual start where it is. History isn’t rewritten.
  2. Holds the remaining duration until the open predecessor finishes, plus any lag.
  3. Schedules successors from the new forecast finish as usual.

The effect is a split: some work done early, a pause, then the rest after the predecessor. Real crews rarely stop like that, but the forecast reflects the dependency the schedule still claims exists.

In P6 the choice sits in the project’s scheduling options, alongside progress override and a third option, actual dates. The setting applies to the whole project, not activity by activity, so the same rule governs every out-of-sequence activity in the update.

Worked example

Illustrative: framing on Level 2 has 4 working days remaining at the data date. Drywall hang (10 days) is linked finish-to-start from framing, but the crew started early in finished rooms and has 6 days remaining.

Setting Remaining drywall starts Drywall finishes
Retained logic After framing finishes (day 4) 4 + 6 = 10 working days after the data date
Progress override At the data date 6 working days after the data date

The same progress, the same file, and two forecast finishes four days apart. If drywall sits on the critical path, the project finish moves by up to the same four days depending on the setting.

Which one is right depends on the field. If the remaining rooms can’t be hung until framing passes inspection, retained logic matches reality. If the crew has open rooms to work through and framing only gates the last few, neither forecast is quite right: the better fix is to split drywall by area so the logic matches the sequence.

Retained logic vs progress override

Retained logic Progress override
Remaining work Waits for open predecessors Runs from the data date
Forecast Usually later, more conservative Usually earlier
Risk Can overstate delay if the dependency is gone Can hide a dependency that still exists
P6 default Yes No

Why it matters

The two settings can move the critical path, float and the forecast finish. A reviewer comparing two updates needs to know which setting each used before reading any slip as performance. A changed setting between updates can look like a month of delay or recovery when nothing changed on site. That is why many schedule specifications and reviewers expect retained logic, or at least expect the setting to be stated and held constant.

What to check

  • Confirm the scheduling option in each update file, and that it matches the previous update and any specification requirement.
  • List the out-of-sequence activities and look at their split forecasts. Ask the field whether the pause the schedule shows will really happen.
  • Recalculate a copy under progress override. The difference in forecast finish shows how much the forecast depends on out-of-sequence work.
  • Where the dependency has clearly changed, revise or split the logic and record why, instead of leaving retained logic to carry an outdated relationship.

Common mistakes

  • Not knowing which setting the file uses. It is easy to inherit progress override from a template.
  • Switching settings between updates without saying so in the narrative.
  • Leaving out-of-sequence activities unaddressed month after month, so the forecast depends on split work nobody plans to do.
  • Treating the setting as a fix for bad logic. If the dependency is wrong, correct the relationship.
  • Comparing durations across updates without accounting for the pause retained logic inserts.

For how scheduling options change the forecast, see P6 settings and their effect and the schedule audit checklist.

How os.construction handles it

The scheduling engine supports retained logic (the default), progress override and actual dates, reads the mode from P6 project settings on import, and lists suppressed relationships in the calculation result.

FAQ

What is retained logic in P6?

Retained logic is one of the scheduling options Primavera P6 offers for activities that have progressed out of sequence. When an activity has started but a predecessor hasn't finished, P6 schedules the activity's remaining work to continue only after that predecessor completes, as the relationship says. It is P6's default setting.

What is the difference between retained logic and progress override?

Both apply only to activities that started before their predecessors finished. Retained logic keeps the relationship for the remaining work, so it waits for the predecessor. Progress override ignores the relationship for that activity, so its remaining work runs from the data date. Retained logic usually gives the later, more conservative forecast.

Which is better, retained logic or progress override?

Neither is right for every case. Retained logic suits work where the dependency is still real, such as finishing drywall that can't close until framing and inspections are done. Progress override suits work where the early start genuinely removed the dependency. Many reviewers prefer retained logic as the default and fixing the logic where it is wrong.

Does retained logic affect the critical path?

It can. Because remaining work waits for the open predecessor, the predecessor and the out-of-sequence activity can become part of the driving chain to the finish. Switching to progress override can drop them from the critical path and move the forecast completion date earlier.

Should I fix out-of-sequence activities or just rely on retained logic?

Review them each update. Retained logic produces a defensible forecast for the remaining work, but repeated out-of-sequence progress usually means the logic or the activity breakdown no longer matches how the job is being built. Revise relationships where the plan has truly changed and explain the change in the narrative.

Sources

Open file