Out-of-Sequence Progress in Primavera P6: What It Means and How to Fix It

Project Assure · Schedule analysis

What Is Out-of-Sequence Progress?

Out-of-sequence (OOS) progress occurs when a successor activity is started or completed before its predecessor(s) are finished, according to the defined logic. In Primavera P6, this is flagged when actual dates violate the network logic. For example, if Activity B has a Finish-to-Start relationship with Activity A, but B starts before A finishes, P6 records OOS progress.

P6 handles OOS progress in two ways depending on the Progress Calculation setting: Retained Logic or Progress Override. Under Retained Logic, the remaining duration of the successor is scheduled after the predecessor finishes. Under Progress Override, the successor can proceed independently. Both methods can distort the schedule if not managed.

Why Does Out-of-Sequence Progress Happen?

Common causes include:

Field execution vs. plan: Crews may start work early due to resource availability, weather windows, or management pressure, ignoring the planned sequence.
Incorrect logic: Missing or inappropriate relationships (e.g., unnecessary FS constraints or missing SS lags) force unrealistic sequences.
Resource constraints: A resource finishes early on a predecessor and moves to a successor, even if the predecessor has remaining work.
Status errors: Actual dates are entered incorrectly, or progress is applied to the wrong activity.

How Out-of-Sequence Progress Distorts the Schedule

OOS progress can significantly mislead schedule analysis and forecasting:

False float values: OOS can artificially inflate or deflate total float, hiding true critical paths.
Misleading EVM metrics: Earned value may be claimed for work that logically shouldn't have started, overstating performance.
Inaccurate remaining duration: Under Retained Logic, remaining duration may be pushed out, creating a false delay. Under Progress Override, the schedule may appear compressed, hiding future conflicts.
DCMA 14-point check failures: The DCMA 14-point assessment includes a check for OOS progress (typically >5% of activities with OOS is a warning). Many government contracts require clean schedules.

If you need to quickly check your XER for OOS progress and other DCMA metrics, you can use Project Assure, a free browser-based tool that parses your XER locally—no upload needed.

How to Clean Up Out-of-Sequence Progress

Step 1: Identify OOS Activities

In P6, run a Schedule Check report or use the Tools > Schedule > Schedule Log to see warnings. Alternatively, filter for activities where Actual Start is earlier than the Early Start of the predecessor (or actual finish of predecessor). You can also use the Activity Network view to visually spot broken logic.

Step 2: Analyze the Root Cause

For each OOS activity, ask: Is the logic correct? Did the field actually work out of sequence? Or is it a data entry error? If the logic is wrong, fix the relationships. If the field worked out of sequence, you have two options:

Accept and update: If the work was truly done out of sequence, you can retain the actual dates and adjust logic to reflect the as-built sequence. This may involve adding new relationships or removing outdated ones.
Re-sequence: If you want to enforce the original plan, you may need to break the actual dates and re-enter them correctly—but this must be done carefully to avoid falsifying history.

Step 3: Correct the Logic

Common fixes:

Change FS relationships to SS with a lag if activities can overlap.
Remove unnecessary constraints that force a sequence not followed in the field.
Add resource calendars or activity codes to reflect true dependencies.

Step 4: Recalculate the Schedule

After making changes, perform a full schedule calculation (Tools > Schedule > Schedule). Review the Schedule Log for remaining OOS warnings. Repeat until OOS activities are minimal (ideally zero).

Step 5: Document and Communicate

If OOS progress is unavoidable (e.g., due to constructive changes or acceleration), document the reasons in a narrative. This is critical for forensic delay analysis later.

Best Practices to Prevent Out-of-Sequence Progress

Use proper logic: Avoid over-constraining schedules. Use SS and FF relationships where appropriate.
Train field staff: Ensure progress updates are accurate and reflect actual sequence.
Regular schedule reviews: Run DCMA 14-point checks monthly. Project Assure can help you quickly identify OOS and other metrics.
Set Progress Calculation to Retained Logic for most projects, as it’s more conservative and transparent.

Conclusion

Out-of-sequence progress is a common but manageable issue in Primavera P6. By understanding its causes and impacts, and by following a systematic cleanup process, you can maintain a reliable schedule that supports accurate forecasting, earned value management, and delay analysis. Regular use of schedule health checks will catch OOS early, saving time and avoiding disputes.

Run these checks free, in your browser

Free, browser-based Primavera P6 XER schedule analyser — DCMA 14-point, GAO & NASA checks, EVM/S-curve, and forensic baseline-vs-update comparison. Nothing is uploaded; your XER is parsed locally in the browser. 3 free analyses, no card required.

Analyse your XER →

Frequently asked questions

What is out-of-sequence progress in Primavera P6?

Out-of-sequence progress occurs when a successor activity starts or finishes before its predecessor(s) are complete, violating the defined network logic. P6 flags this when actual dates conflict with relationships.

How does out-of-sequence progress affect schedule accuracy?

It can distort float values, mislead EVM metrics, and create inaccurate remaining durations. Under Retained Logic, it may push out the schedule; under Progress Override, it can hide future conflicts.

What is the DCMA 14-point check for out-of-sequence progress?

The DCMA 14-point assessment includes a check for activities with out-of-sequence progress. A warning is typically triggered if more than 5% of activities have OOS progress.

Should I use Retained Logic or Progress Override for out-of-sequence progress?

Retained Logic is generally recommended for most projects because it is more conservative and transparent. Progress Override can mask delays and is often discouraged by owners and auditors.

How can I quickly check for out-of-sequence progress in my XER?

You can use a free browser-based tool like Project Assure (scheduleanalyser.projectassure.xyz) to parse your XER locally and instantly see OOS activities along with other DCMA metrics.