How does Retained Logic, Progress Override and Actual Dates in Scheduling Options work?

Primavera P6 provides three key options in the Scheduling Options dialog that control how the software handles Out-of-Sequence Progress:

• Retained Logic
• Progress Override
• Actual Dates

Understanding these options is essential for accurate schedule calculations. Let’s explore how each works with an example.

What is Out-of-Sequence Progress?

Out-of-sequence progress occurs when an activity starts or finishes before its predecessor is complete, violating the planned logic.

Example:

• Activity A2 should start after A1 finishes.
• In reality, A2 starts and finishes before A1 begins.

How does Primavera P6 deal with this situation?

It depends on which scheduling option was chosen.

Scheduling Options Explained

1. Retained Logic

• Primavera retains the original logic.
• Even if A2 finishes early, A3 cannot start until A1 is complete.
• This enforces the original dependency chain.

2. Progress Override

• Primavera overrides the original logic.
• A3 is scheduled immediately after A2 finishes, ignoring A1’s dependency.
• A1 is no longer considered a predecessor for A3.

3. Actual Dates

• Primavera uses actual dates to drive the schedule.
• A3 starts as soon as A2 is complete, even if A2’s actual finish is after the data date.
• Logic is overridden by actual progress.

Key Differences

Option	Behavior
Retained Logic	Keeps original logic; successor waits for all predecessors.
Progress Override	Ignores logic; successor starts after out-of-sequence activity.
Actual Dates	Uses actual dates; overrides logic based on real progress.

Best Practice

• Use Retained Logic for strict dependency control (such as: when analyzing delays or performing forensic schedule analysis)
• Use Progress Override when real-world progress should drive the schedule.
• Use Actual Dates for generating reports for stakeholders that need to show what actually happened, regardless of the original logic.