Every construction project reaches moments where work does not unfold in the precise sequence shown in the approved CPM baseline. A crew accelerates ahead of its predecessor on a government building project, a subcontractor starts mechanical rough-in before the rough framing milestone is achieved, or a site manager moves forward with a utility installation because material arrived early. These situations are a routine feature of real-world project delivery, and how a Primavera P6 Professional schedule responds to them has direct consequences for project controls accuracy, payment certification, delay analysis, and owner trust.
Primavera P6 Professional, the industry-standard CPM scheduling software developed by Oracle and used on federal, state, and private construction projects nationwide, provides three distinct settings for handling activities that have progressed out of their planned sequence. These settings are Retained Logic, Progress Override, and Actual Dates. They are accessed through the Schedule Options dialog (F9 > Options) and apply each time a schedule is recalculated. Understanding the precise behavioral difference between these three settings is one of the most consequential decisions a CPM scheduling consultant makes during the progress update cycle.
The distinction matters for several interconnected reasons. Agency clients such as the U.S. Army Corps of Engineers (USACE), NAVFAC, the Department of Transportation (DOT), and the Department of Veterans Affairs (VA) typically mandate specific schedule update practices within their project specifications. Selecting the wrong progress setting can cause a schedule to misrepresent the critical path, generate artificial float, or produce a projected completion date that is neither defensible nor realistic. In adversarial claim environments, the chosen setting becomes part of the evidentiary record for time impact analysis.
This article explains each of the three settings in depth, examines the practical consequences of each through a consistent four-activity scenario, discusses the conditions under which each setting is appropriate, and explains how Leopard Project Controls applies this knowledge when delivering compliant Primavera P6 scheduling services to contractors and project owners across the United States. Whether you are a general contractor preparing a monthly schedule update for a federal agency, an owner reviewing a contractor’s submittal, or a scheduling professional seeking to sharpen your command of Primavera P6, the principles covered here are fundamental to sound project controls practice.
What is out-of-sequence progress?
After the CPM baseline schedule is approved, the project team begins tracking work progress. Correct schedule progress updates and reporting are essential to monitor project performance status and to support the KPI reporting that management and leadership rely on for decision-making.
The Oracle Online P6 Professional Help defines out-of-sequence progress as work completed for an activity before it is scheduled to occur. In a conventional Finish-to-Start relationship, an activity that starts before its predecessor completes shows out-of-sequence progress. This happens because some successor activities are not truly fully dependent on their predecessor activities, and weak relationships exist between them. Out-of-sequence work generally falls into four categories: early start of an activity, early finish of an activity, a combination of early start and early finish, and rearrangement of repetitive work.
The question Primavera P6 must answer when out-of-sequence progress exists is how to schedule the remaining work on affected activities and their successors. The answer depends entirely on which of the three progress settings is active at the time the schedule is recalculated.
The example project: four activities in sequence
A consistent four-activity example is used throughout this article to illustrate each setting. Activity A, Activity B, Activity C, and Activity D are all connected by Finish-to-Start relationships in the following order: A drives B, B drives C, and C drives D. Activity A started and completed as planned. Activity C, however, started out-of-sequence at 25% completion before Activity B has begun. This is the condition that each of the three settings must interpret.
To access the scheduling options in Primavera P6 Professional, navigate to Tools > Schedule (or press F9 on the keyboard) and select Options. The Schedule Options dialog presents the three settings for scheduling progressed activities.
Primavera P6 Schedule Options dialog F9 > Options, showing the three scheduling progress settings: Retained Logic, Progress Override, and Actual Dates
Retained Logic
Retained Logic is the default setting in Primavera P6 Professional and is the option most commonly required by project specifications for government and institutional construction projects. When this setting is active, Primavera P6 respects the network logic established in the approved baseline schedule, even when an activity has started or partially progressed out of sequence.
In practical terms, the remaining duration of the out-of-sequence activity is not scheduled until all of its predecessors are complete. In the example scenario, with Activity C at 25% completion out-of-sequence, Primavera P6 schedules the remaining work of Activity C to begin after Activity B finishes. Activity B is placed immediately after the data date, and Activity D follows Activity B’s completion.
The result is a schedule that presents the most conservative and defensible picture of the project’s remaining work. The out-of-sequence start of Activity C is recorded as actual progress, but the remaining portion waits for its predecessor to be satisfied. This approach prevents the schedule from implying that work can continue on a parallel track when the established logic says otherwise.
Retained Logic applied to Activity C at 25% complete out-of-sequence. Remaining work of Activity C is scheduled after Activity B completes. Activity B appears immediately after the data date as critical.
In the case where Activity C has been fully completed out-of-sequence, Primavera P6 accepts the out-of-sequence completion and schedules Activity B immediately after the data date, with Activity D following Activity B’s completion, retaining logic to the extent possible.
Retained Logic applied to Activity C fully completed out-of-sequence. Activity B is scheduled immediately after the data date, and Activity D follows Activity B’s completion.
Retained Logic is the preferred option for several reasons. It preserves the integrity of the network logic that was reviewed and approved by the owner or agency. It produces a schedule least susceptible to manipulation, since a contractor cannot compress the project completion date simply by entering optimistic out-of-sequence progress. It is also the setting that USACE, NAVFAC, DOT, and VA scheduling specifications explicitly require or strongly imply.
When out-of-sequence activities appear under Retained Logic, the schedule log flags them. The preferred corrective action, if the client permits, is to revise the logic to reflect the actual execution sequence. For instance, if Activity C is genuinely no longer dependent on Activity B finishing first, the relationship can be modified to reflect the as-built construction approach, with appropriate documentation and owner notification.
Progress Override
The Progress Override option instructs Primavera P6 to ignore the network logic between an out-of-sequence activity and its predecessor. The software allows the remaining work of the out-of-sequence activity to continue from the data date regardless of whether its predecessor has been completed.
In the four-activity scenario, if Activity C is 25% complete out-of-sequence, Progress Override schedules the remaining work of Activity C to proceed in parallel with Activity B immediately after the data date. Primavera P6 ignores the logic that Activity B must finish before Activity D can begin.
Progress Override applied to Activity C at 25% complete out-of-sequence. Activity C continues after the data date in parallel with Activity B. Activity D also follows immediately after the data date.
In the case where Activity C has been fully completed out-of-sequence, Primavera P6 accepts that completion and schedules both Activity B and Activity D immediately after the data date, ignoring the predecessor logic entirely.
Progress Override applied to Activity C fully completed out-of-sequence. Activity B and Activity D are both scheduled immediately after the data date with no predecessor constraint observed.
The practical consequence is a shorter projected completion date relative to Retained Logic. This may appear favorable from a contractor’s perspective, but it comes at the cost of schedule credibility. The setting can produce unrealistically positive float values and suggest that work can proceed on multiple fronts simultaneously when resource availability or physical constraints may not permit it.
For this reason, Progress Override is generally not recommended and is often prohibited by agency scheduling specifications. Owners and scheduling reviewers should specifically verify whether Progress Override has been used when reviewing contractor schedule submittals, particularly when the projected completion date shows unexpected improvement between update cycles.
There is one narrow circumstance where Progress Override may be technically defensible: when an activity has genuinely started out of sequence under conditions formally acknowledged by the owner, and both parties have agreed that the predecessor relationship is no longer valid. Even in that case, the better practice is to revise the network logic rather than apply Progress Override globally.
Actual Dates
The Actual Dates option is a hybrid that combines elements of the other two settings, with behavior that depends on whether the out-of-sequence activity is still in progress or has already been completed. For activities that are partially complete and still in progress out of sequence, Actual Dates behaves like Retained Logic: the remaining work is held until the predecessor is complete. For activities that have been fully completed out of sequence, Actual Dates behaves like Progress Override, accepting the out-of-sequence completion and scheduling downstream activities from the data date.
In the scenario where Activity C is 25% complete out-of-sequence, the result matches Retained Logic. The remaining work of Activity C is held until Activity B completes.
Actual Dates applied to Activity C at 25% complete out-of-sequence. Result mirrors Retained Logic: remaining work of Activity C is scheduled after Activity B completes.
In the case where Activity C has been fully completed out-of-sequence, Actual Dates mirrors Progress Override: Activity B and Activity D are both scheduled immediately after the data date, ignoring the predecessor logic.
Actual Dates applied to Activity C fully completed out-of-sequence. Result mirrors Progress Override: Activity B and Activity D are scheduled immediately after the data date.
Actual Dates also introduces a useful diagnostic feature: it calculates forward and backward passes using actual dates as constraints, which can generate negative total float on the predecessor activity. This negative float is a warning signal that the network logic has been violated and that corrective action may be needed. In practice, Actual Dates is used less frequently than Retained Logic. Its hybrid behavior adds interpretive complexity, and the negative float it generates can create confusion if not properly explained in the schedule narrative.
Handling out-of-sequence activities in practice
When out-of-sequence activities are discovered during a schedule update, the response should follow a structured process. First, copy the prior period schedule and rename it for the current period. Store period performance data before applying new progress. Insert the progress information reported from the site as of the data date, including actual starts, actual finishes, remaining durations, percent complete values, and actual resource units.
After recalculating the schedule, review the schedule log file. Search specifically for out-of-sequence activities and look for other errors including activities with actual dates greater than the data date, unreasonable critical path activities, constraint violations, calendar errors, and open-ended activities. USACE and NAVFAC specifications typically require that open ends be limited to the project start milestone and the project completion milestone.
When out-of-sequence activities are identified, reassess whether the original predecessor relationship is still valid for the remaining scope. If it should remain in force, document the out-of-sequence progress and recalculate under Retained Logic, allowing remaining work to be scheduled after the predecessor completes. If the relationship is genuinely no longer applicable, revise the logic with proper documentation and owner or agency notification as required by the contract. After each update, study the longest path and near-critical paths to confirm that the projected completion date is supported by the schedule logic.
How Leopard Project Controls addresses these challenges
At Leopard Project Controls, managing out-of-sequence progress and applying the correct scheduling settings are core elements of the CPM scheduling consulting services the firm provides to general contractors and project owners across federal, state, and private construction sectors throughout the United States.
Leopard Project Controls is a registered construction scheduling firm based in Saint Augustine, Florida, holding a Florida Certified General Contractor license. The firm is a certified Disadvantaged Business Enterprise (DBE) and Minority Business Enterprise (MBE), with credentials in the SWaM Program administered by Virginia’s Department of Small Business and Supplier Diversity. Every Primavera P6 schedule Leopard develops uses Retained Logic as the default setting, consistent with agency expectations and industry best practice. Monthly progress updates include a review of the schedule log, identification and resolution of out-of-sequence activities, and a narrative report explaining any logic revisions made during the update cycle.
Leopard Project Controls also provides forensic schedule analysis and time impact analysis (TIA) services for contractors pursuing delay claims or defending against owner-initiated time assessments. A consistent, well-documented use of Retained Logic across all updates strengthens the contractor’s position by demonstrating that the schedule was maintained with integrity throughout the project lifecycle. For contractors whose schedules have been rejected by NAVFAC, USACE, or DOT due to non-compliant scheduling settings or missing logic, Leopard provides correction services with guaranteed turnaround and unlimited revisions until accepted.
For contractors managing schedule recovery after project slippage, identifying where out-of-sequence progress has occurred, where predecessor logic may be masking float, and where the critical path has shifted are all part of the recovery analysis. Leopard Project Controls develops realistic catch-up strategies grounded in the actual network logic, giving contractors a credible roadmap for regaining schedule control and protecting their timeline, budget, and cash flow.
Conclusion:
The choice between Retained Logic, Progress Override, and Actual Dates in Primavera P6 Professional is not a minor technical preference. It is a decision with meaningful consequences for how a project’s critical path is calculated, how the projected completion date is reported to owners and agencies, and how the schedule performs under review or in a claims context.
Retained Logic is the foundation of sound CPM scheduling practice. By preserving the network logic established in the approved baseline, it ensures that the schedule remains an accurate representation of the work remaining and the sequence in which it must be completed. It prevents the artificial compression of the project timeline that Progress Override introduces, and it aligns with the requirements of virtually every major agency scheduling specification in the United States construction market, including those from USACE, NAVFAC, DOT, and VA.
Progress Override has a narrow technical use case, but its risks outweigh its benefits in most situations. Schedulers and owners encountering it during schedule reviews should treat its use as a flag warranting closer examination of the critical path and float values. The same scrutiny applies when projected completion dates improve unexpectedly between update cycles without a clear explanation in the narrative.
Progress Override has a narrow technical use case, but its risks outweigh its benefits in most situations. Schedulers and owners encountering it during schedule reviews should treat its use as a flag warranting closer examination of the critical path and float values. The same scrutiny applies when projected completion dates improve unexpectedly between update cycles without a clear explanation in the narrative.
Equally important is the process surrounding these settings. Detecting out-of-sequence activities through the schedule log, evaluating whether predecessor logic should be retained or revised, documenting those decisions, and communicating them clearly to the project team and owner are what separate a compliant, defensible CPM schedule from one that merely reports numbers. These disciplines compound over the life of a project and matter most precisely when a project is under stress from delays, disputes, or acceleration demands.
For general contractors managing complex construction projects under agency contracts, partnering with an experienced CPM scheduling consultant is one of the most effective ways to ensure that these decisions are made correctly and consistently. Leopard Project Controls brings that expertise to every engagement, from initial baseline development through monthly progress updates, schedule recovery, and time impact analysis support. Contact Leopard Project Controls at consultleopard.com for a no-obligation consultation.
Frequently asked questions
What is the most commonly required scheduling progress setting for federal construction projects?
Retained Logic is the setting most commonly required or implied by agency scheduling specifications, including those from USACE, NAVFAC, DOT, and VA. These specifications typically require contractors to maintain network logic integrity during progress updates and to revise the schedule if significant out-of-sequence progress is identified. Retained Logic directly supports these requirements by preventing predecessor relationships from being ignored when an out-of-sequence activity is in progress.
Can Progress Override ever be appropriate on a construction project?
Progress Override may be defensible in narrow situations where an activity has started out-of-sequence under conditions formally acknowledged by the owner and where both parties have agreed the predecessor relationship is no longer valid for the remaining scope. Even in those cases, the more professionally sound approach is to revise the network logic to reflect the actual sequence rather than applying a global setting that ignores all violated predecessor relationships. Agency reviewers should confirm whether Progress Override is in use before accepting any schedule update.
How does the Actual Dates setting differ from Retained Logic when an activity is partially complete out of sequence?
When an activity is partially complete and still in progress out of sequence, Actual Dates behaves identically to Retained Logic: the remaining work is held until the predecessor is complete. The difference appears only when an activity has been fully completed out of sequence, at which point Actual Dates behaves like Progress Override and ignores the predecessor relationship for downstream activities. Actual Dates also introduces negative float on the predecessor activity as a warning signal, which can be useful diagnostically but requires careful explanation in the schedule narrative.
What should a scheduler do when the schedule log identifies out-of-sequence activities during a monthly update?
The first step is to evaluate whether the predecessor relationship that was violated is still valid given current field conditions. If it should remain in force, document the out-of-sequence progress and recalculate under Retained Logic, allowing remaining work to be scheduled after the predecessor completes. If the relationship is genuinely no longer applicable, revise the logic with proper documentation and owner or agency notification as required by the contract. The schedule narrative should clearly explain what occurred and how it was addressed.
How does Leopard Project Controls help contractors with out-of-sequence issues in their Primavera P6 schedules?
Leopard Project Controls provides CPM scheduling consulting services that include reviewing the schedule log after each update cycle, identifying and evaluating out-of-sequence activities, recommending logic revisions based on field conditions, and preparing schedule narratives that explain all changes to owners and agencies. For contractors subject to USACE, NAVFAC, DOT, or VA oversight, Leopard ensures that scheduling progress settings are applied consistently with contract requirements. For contractors dealing with delay claims or seeking time extensions, Leopard provides forensic schedule analysis and time impact analysis that relies on a properly maintained, Retained Logic-based schedule throughout the project record.
