Esc

↑↓ move↵ openIndex · Pagefind
Project management

Progress Override

Definition

A progress setting that releases the logic into an out-of-sequence activity, so its remaining work continues from the data date.

Topic: Scheduling

Updated

Progress override is a progress mode for activities that started before their predecessors finished. It releases the relationships into the started activity, so its remaining work is scheduled from the data date without waiting for the unfinished predecessor. The relationship stays in the schedule; the calculation just ignores it for that activity.

Compare retained logic, which keeps the remaining work waiting for the predecessor.

How it works

Progress override only changes the answer when there is out-of-sequence progress: an activity with an actual start while one of its predecessors is still open. For that activity the engine:

  1. Keeps the actual start.
  2. Schedules the remaining duration to begin at the data date, regardless of the open predecessor.
  3. Schedules the activity’s own successors from the resulting forecast finish, using their relationships as normal.

The released relationship isn’t deleted. It still applies to activities that haven’t started, and it will apply again if the file is recalculated under retained logic. The setting lives in the project’s scheduling options in Primavera P6 and applies to every out-of-sequence activity in the project at once.

Releasing the link also deserves a look from the other side. Check the open predecessor: if the released relationship was what tied it to the finish, its float can grow and it can drop off the critical path even though the work still has to be done. How each tool handles this differs, so compare the predecessor’s float under both settings.

Worked example

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

Progress override Retained logic
Remaining drywall starts Data date After framing, day 4
Drywall forecast finish Day 6 Day 10
Framing as a driver of drywall Released Kept

The override forecast is four working days earlier. Whether that’s credible depends on the site. If the drywall crew has enough framed and inspected rooms to keep working for six days, the override date is realistic. If they’ll run out of rooms on day 2 and wait for framing, the override date is optimistic by about the gap, and the real forecast is closer to retained logic.

A reviewer can test this quickly: recalculate the update under both settings and compare the forecast finish. A large difference means the forecast depends heavily on out-of-sequence assumptions, which belongs in the narrative.

  • Retained logic keeps the relationship for remaining work. It is the P6 default and usually the more conservative forecast.
  • Actual dates is a third P6 option, used less often in construction. Check its behaviour against your own P6 version before relying on it.
  • Fixing the logic means changing or splitting relationships so they describe the sequence being built. Unlike either setting, it changes the network itself, so it needs a recorded reason.

Why it matters

Progress override usually gives an earlier forecast than retained logic, and it can hide a real dependency. If the drywall really can’t finish until the framing is done, override reports a finish the field won’t hit. Use it when the out-of-sequence start truly broke the dependency, and record why. In delay analysis, a schedule that switched to override mid-project can show apparent recovery that came from the setting rather than from the field, so analysts check the setting in every update they rely on, including those used for a time impact analysis.

What to check

  • The setting in every update you compare, read from the file rather than assumed.
  • The list of out-of-sequence activities and whether each one’s remaining work can really proceed without its predecessor.
  • The forecast finish under both settings. If the gap is large, say so in the narrative.
  • Open predecessors’ float before and after the override.
  • A recorded reason for using override, especially if the project’s specification asks for retained logic.

Common mistakes

  • Switching modes between updates without noting it in the narrative.
  • Leaving override on for a whole schedule to make out-of-sequence starts look harmless.
  • Fixing logic by changing the mode instead of correcting the relationship.
  • Not checking open predecessors that gained float once their link was released.
  • Inheriting override from a template nobody reviewed.

See how P6 settings affect the forecast for the wider set of scheduling options to check.

How os.construction handles it

The scheduling engine honours the progress mode stored in the schedule definition and imported from P6. It records the mode on each result and lists the relationships it suppressed.

FAQ

What does progress override do in P6?

Progress override is a scheduling option for activities that started before their predecessors finished. It ignores the incoming relationship for that in-progress activity, so its remaining duration is scheduled from the data date instead of waiting for the predecessor. The relationship stays in the file; the calculation just doesn't apply it to that activity.

Is progress override or retained logic the P6 default?

Retained logic is the default in Primavera P6. Progress override has to be selected in the project's scheduling options, which is why it's worth checking the setting on any schedule built from a template or received from someone else.

When should I use progress override?

When an out-of-sequence start shows that the dependency no longer holds for the rest of the activity, for example because the crew can work in areas the predecessor has already released. Even then, splitting the activity by area or correcting the relationship is usually clearer than relying on the setting.

Why does progress override make the schedule look better?

It removes a constraint on remaining work. Out-of-sequence activities no longer wait for open predecessors, so their forecast finishes, and anything they drive, can move earlier. If the dependency is real, that earlier date is one the field won't meet.

Does progress override delete relationships?

No. The relationship remains in the schedule and applies again to any activity that hasn't started. The override only affects how remaining work is scheduled for activities that have already progressed out of sequence.

Sources

Open file