Study guide
5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic
AACE Planning and Scheduling Professional PSP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Introduction & AACE PSP Exam Structure
0.1 Current AACE PSP Exam, Eligibility, and Certification Facts 0.2 Planning and Scheduling Professional Roles and Competencies 0.3 Cost Engineering and Scheduling Terminology per RP 10S-90
2 Chapter 1: Scope Definition & Planning Fundamentals
1.1 Work Breakdown Structure (WBS) Architecture & RP 33R-15 1.2 Organization & Resource Breakdown Structures (OBS, RBS, RAM) 1.3 Project Planning and Activity-Logic Development 1.4 Contract Requirements and Delivery Constraints 1.5 Stakeholder Identification, Needs, and Plan Review 1.6 Constructability Methods and Value Engineering 1.7 Resource Identification and Project Variables 1.8 Scope, Goals, Project Plan, and Phase Definition 1.9 Cost Breakdown Structure and Cost Estimate Development 1.10 Phase Relationships, Baseline Plan, Forecasts, and Risk/Recovery Planning
3 Chapter 2: Critical Path Method Mechanics & Network Logic
2.1 Activity Definition and Logic Relationships 2.2 Activity Durations, Productivity, and Work Calendars 2.3 Forward and Backward Pass Mathematical Mechanics 2.4 Float Calculations and Critical-Path Identification
4 Chapter 3: Advanced Network Techniques & Schedule Constraints
3.1 Schedule Constraints and Their Impact on Dates and Float 3.2 Advanced Logic Modeling: Ladders and Fragnets 3.3 Schedule Levels of Detail and Schedule Basis Documentation 3.4 Schedule Scope and Schedule Specification 3.5 Breakdown-Structure Relationships and the Cost Estimate Model 3.6 Stakeholder Feedback and Types of Schedules 3.7 Activities, Milestones, Schedule Quality, and Basis Documentation
5 Chapter 4: Resource Management & Leveling
4.1 Resource Planning, Allocation, and Histograms 4.2 Resource Leveling vs. Resource Smoothing 4.3 Cumulative Resource S-Curves & Productivity Tracking
6 Chapter 5: Baseline Management & Schedule Updating
5.1 Baseline Establishment, Forecasts, and Controlled Revision 5.2 Progress Measurement and Data Date Mechanics 5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic 5.4 Schedule Update Review and Quality Verification per RP 53R-06 5.5 Cost/Resource Management, Schedule Change, and Feedback 5.6 Acceleration and Recovery Scheduling per RP 54R-07 5.7 Control Schedules, Variance Analysis, Forecasts, and Management Summaries
7 Chapter 6: Schedule Risk Analysis & Monte Carlo Simulation
6.1 Schedule Risk Principles, Risk Drivers, and Three-Point Estimates 6.2 Monte Carlo Simulation, Criticality, Correlation, and Merge Effects 6.3 Risk Outputs, Confidence Dates, Sensitivity, and Contingency
8 Chapter 7: Earned Value & Earned Schedule Management
7.1 Earned Value Foundations: PV, EV, AC, and Variances 7.2 Traditional EV Performance Indices & Late-Project Quirks 7.3 Earned Schedule (ES) Theory, SV(t), and SPI(t) 7.4 Independent Schedule Forecasting & IEAC(t)
9 Chapter 8: Forensic Schedule Analysis & Delay Claims
8.1 Delay Classification, Criticality, and Contract Questions 8.2 RP 29R-03 Taxonomy, Data Validation, and Method Selection 8.3 TIA, Windowed Analysis, and Subtractive Models 8.4 Concurrency, Pacing, and Float: Technical Analysis Before Entitlement
10 Chapter 9: Executive Communication & Practical Scenario Applications
9.1 Official PSP Memo Writing Framework 9.2 Structured Technical Problem-Solving for PSP Scenarios 9.3 Current Exam Strategy and Core Calculation Review
5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic
Key Takeaways Explain This Topic AI
Out-of-sequence (OOS) progress occurs when work begins or completes on a successor activity before its logical predecessor has finished (for Finish-to-Start ties) or reached the required offset.
Retained Logic (RL) calculation mode respects the original network dependency, requiring the remaining duration of an out-of-sequence successor to wait until its predecessor finishes before resuming.
Progress Override (PO) calculation mode overrides the network dependency, permitting the remaining duration of an out-of-sequence successor to execute immediately from the Data Date.
Progress Override may disregard an unfinished dependency for remaining work, while Retained Logic may preserve a dependency that field execution has changed; either result must be tested against current means and sequence.
Neither Retained Logic nor Progress Override substitutes for investigating the cause, validating remaining dependencies, documenting settings, and revising logic through the project's change process when appropriate.
Last updated: October 2026
5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic
AACE Professional Context: In a textbook CPM network, construction proceeds in strict chronological order according to baseline logic. In field execution, however, contractors frequently adapt: work commences out of order due to material availability, selective access, or subcontractor expediting. When a successor activity begins before its predecessor finishes, the network encounters Out-of-Sequence (OOS) Progress . How the scheduling engine resolves this conflict—via Retained Logic (RL) or Progress Override (PO) —fundamentally impacts early dates, total float, critical path alignment, and delay claim liabilities. Mastery of these calculation algorithms is a cornerstone of the AACE PSP examination.
Definition and Causes of Out-of-Sequence Work
An activity is executing out of sequence when it records progress (an Actual Start date or physical percent complete) prior to the satisfaction of its predecessor logic relationships. NORMAL SEQUENCE (Finish-to-Start)
- [Activity A: Foundations] ──(FS)──► [Activity B: Backfill]
- (Activity A finishes ──► Then Activity B starts)
- OUT-OF-SEQUENCE PROGRESS
- [Activity A: Foundations] ──(FS)──► [Activity B: Backfill]
- ▲ │
- │ ACTUAL START │
- └──────── (Starts early!) ─────────┘
- (Activity B starts while Activity A is still in progress!)
- Primary Root Causes of Out-of-Sequence Work
Field Workarounds and Expediting: Site superintendents seize operational opportunities. For example, backfilling around completed pier footings before all foundation walls in the area are poured.
Defective Baseline Logic (Preferential Logic): The original baseline incorporated discretionary or soft logic (e.g., an arbitrary Finish-to-Start tie between independent work areas) rather than true physical dependencies.
Scope Packaging and Granularity Issues: An activity represents too large a scope. If ACT-100: Install Underground Piping covers 5,000 feet, the electrical contractor may begin ACT-200: Install Duct Bank in Trench Zone 1 while pipe testing continues in Trench Zone 3.
Data Entry Errors: The site clerk erroneously records an Actual Start date on Activity B instead of Activity A.
The Two Primary CPM Calculation Modes
When calculating the forward pass for an updated schedule containing out-of-sequence progress, scheduling software (such as Primavera P6) requires the user to select a calculation mode: Retained Logic , Progress Override , or Actual Dates .
1. Retained Logic (RL)
Under Retained Logic , the software respects the original network relationship , regardless of the progress achieved to date. Although the successor activity has started and accumulated actual duration prior to the Data Date, its Remaining Duration cannot resume until its predecessor finishes .
Early Start of Successor Remaining Duration (RL) = max ( Data Date , Early Finish of Predecessor ) \text{Early Start of Successor Remaining Duration (RL)} = \max(\text{Data Date}, \text{Early Finish of Predecessor}) Early Start of Successor Remaining Duration (RL) = max ( Data Date , Early Finish of Predecessor )
Physical Interpretation: The software assumes that whatever portion of the successor work remains is strictly dependent upon the incomplete predecessor work.
Network Impact: If the predecessor is delayed, the remaining portion of the successor is pushed out into the future, creating a "split activity" or extended duration.
Float Impact: Preserves logical dependencies, resulting in lower (and often realistic or negative) total float.
2. Progress Override (PO)
Under Progress Override , the software overrides the network relationship . The algorithm assumes that because work on the successor has already begun, the predecessor logic has been broken, invalidated, or bypassed in the field. The Remaining Duration of the successor is permitted to proceed immediately from the Data Date , completely unconstrained by the predecessor's early finish date.
Early Start of Successor Remaining Duration (PO) = Data Date \text{Early Start of Successor Remaining Duration (PO)} = \text{Data Date} Early Start of Successor Remaining Duration (PO) = Data Date
Physical Interpretation: The software assumes the unfinished predecessor work no longer restrains the remaining successor scope.
Network Impact: The successor finishes much earlier than under Retained Logic, often finishing before its own predecessor finishes!
Float Impact: Artificially increases total float on the successor path, frequently masking real project delays.
3. Actual Dates Option
Some scheduling software offers an Actual Dates calculation option. Under this setting, backward pass calculations evaluate float based on actual dates where recorded. However, forward pass calculations for remaining durations typically adhere to Retained Logic rules. While theoretically pure, Actual Dates mode can generate erratic negative float on historical activities, making Retained Logic the preferred professional industry standard.
Comprehensive Comparison: Retained Logic vs. Progress Override
Feature Retained Logic (RL) Progress Override (PO)
Predecessor Logic Respected; remaining duration waits for predecessor EF Overridden; remaining duration ignores predecessor EF
Successor Remaining Start max ( Data Date , Predecessor EF ) \max(\text{Data Date}, \text{Predecessor EF}) max ( Data Date , Predecessor EF ) Strictly at the Data Date
Split Activities Can generate split activities waiting for predecessor Continuous remaining duration from Data Date
Schedule Forecast Defers remaining successor work until the unsatisfied predecessor permits it Allows remaining successor work to proceed without waiting for that predecessor
Total Float Impact Can produce later dates or lower float Can produce earlier dates or higher float; the effect depends on the network
Path effect Preserves the unsatisfied relationship for remaining work Treats the relationship as overridden for the out-of-sequence calculation
Physical interpretation Appropriate when the predecessor still governs remaining work Appropriate only when field execution has genuinely bypassed that dependency or the model is otherwise corrected
Use Select and document according to actual remaining logic, software behavior, and governing requirements Select and document according to actual remaining logic, software behavior, and governing requirements
Mathematical Worked Example: The Concrete Basin vs. Hydrostatic Test
To see the dramatic divergence in mathematical outcomes, examine a two-activity network on an industrial wastewater facility.
Baseline Conditions:
Activity A (Predecessor): Pour Concrete Basin Walls ( O D = 10 days OD = 10 \text{ days} O D = 10 days )
Activity B (Successor): Install Hydrostatic Test Seals & Fill Basin ( O D = 6 days OD = 6 \text{ days} O D = 6 days )
Network Relationship: Activity A → FS \xrightarrow{\text{FS}} FS Activity B (Basin walls must be poured before test seals and filling occur)
Month 1 Update Status (Data Date = Day 6):
Activity A Status: Actual Start = Day 1. Worked 6 days ( A D = 6 AD = 6 A D = 6 ). Due to honeycombing and repair work, the remaining duration is evaluated at 8 days ( R D = 8 RD = 8 R D = 8 ). Early Finish of Activity A = Data Date (6) + 8 = Day 14 \text{Early Finish of Activity A} = \text{Data Date (6)} + 8 = \text{Day 14} Early Finish of Activity A = Data Date (6) + 8 = Day 14
Activity B Status (Out of Sequence!): The piping crew jumped ahead and pre-installed test bulkheads on an adjacent pipe spool on Day 4. Actual Start = Day 4. Worked 2 days ( A D = 2 AD = 2 A D = 2 ). Remaining Duration = 4 days ( R D = 4 RD = 4 R D = 4 ). DAY: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
- Activity A: [=== Actual ===] [======== Remaining Duration =======]
- ▲ ▲
- DD (Day 6) EF = Day 14
Forward Pass Calculation Under Both Modes:
1. Retained Logic (RL) Calculation:
The Remaining Duration of Activity B ( R D = 4 RD = 4 R D = 4 ) cannot start until Activity A finishes.
ES of Activity B Remaining = max ( Data Date 6 , EF of Activity A 14 ) = Day 14 \text{ES of Activity B Remaining} = \max(\text{Data Date 6}, \text{EF of Activity A 14}) = \text{Day 14} ES of Activity B Remaining = max ( Data Date 6 , EF of Activity A 14 ) = Day 14 .
Early Finish of Activity B = 14 + 4 = Day 18 \text{Early Finish of Activity B} = 14 + 4 = \mathbf{\text{Day 18}} Early Finish of Activity B = 14 + 4 = Day 18 .
Result: Activity B is split: worked Days 4–6, paused Days 6–14 while waiting for concrete repairs on Activity A, and completes on Day 18. This accurately reflects that the basin cannot be filled with water until the concrete walls are finished!
2. Progress Override (PO) Calculation:
The Remaining Duration of Activity B ( R D = 4 RD = 4 R D = 4 ) starts immediately at the Data Date.
ES of Activity B Remaining = Data Date = Day 6 \text{ES of Activity B Remaining} = \text{Data Date} = \text{Day 6} ES of Activity B Remaining = Data Date = Day 6 .
Early Finish of Activity B = 6 + 4 = Day 10 \text{Early Finish of Activity B} = 6 + 4 = \mathbf{\text{Day 10}} Early Finish of Activity B = 6 + 4 = Day 10 .
Result: Activity B finishes on Day 10 , while Activity A is still pouring concrete until Day 14 ! Progress Override produces a physically absurd schedule: the basin is hydro-tested and filled with water 4 days before the walls are poured!
AACE Best Practice: Resolving Out-of-Sequence Logic
Core AACE Principle: Neither Retained Logic nor Progress Override is a substitute for proper engineering schedule maintenance. When out-of-sequence progress occurs, investigate the field condition and decide whether the remaining dependency still applies, the logic should be revised, or a calculation option is appropriate under the governing requirements. OUT-OF-SEQUENCE RESOLUTION PROTOCOL
- ┌────────────────────────────────────────────────────────────────────────┐
- │ 1. Run the software schedule update log to identify all OOS tasks. │
- │ 2. Investigate site reality with superintendents and project engineers. │
- │ 3. Determine if the relationship was discretionary or a true restraint.│
- │ 4. If work is truly concurrent: replace FS with SS/FF or break scope. │
- │ 5. If true restraint exists: retain logic and enforce the dependency. │
- │ 6. Document all logic modifications in the Schedule Narrative Report. │
- └────────────────────────────────────────────────────────────────────────┘
- Standard Logic Solutions for OOS Activities
Convert to Start-to-Start (SS) / Finish-to-Finish (FF) Ladder Logic: If the successor genuinely did not need the predecessor to finish, replace the Finish-to-Start (FS) tie with a Start-to-Start (SS) tie with appropriate lag, plus a Finish-to-Finish (FF) tie to ensure the predecessor still governs completion.
Activity Scope Decomposition (Fragmenting): Decompose the activity into geographic or phase steps. For example, divide ACT-A: Concrete Walls into Area 1 Walls and Area 2 Walls , and link Area 1 Walls → FS \xrightarrow{\text{FS}} FS Area 1 Backfill .
Delete Inapplicable Preferential Logic: If an FS relationship represented merely a contractor preference that has been abandoned, delete the tie and link the successor to its true physical predecessor.
Forensic Delay & Claims Implications (AACE RP 29R-03)
In forensic schedule delay analysis, out-of-sequence progress is a primary battleground:
"Gaming" the Critical Path: An unscrupulous contractor facing owner liquidated damages might switch calculation settings from Retained Logic to Progress Override between monthly updates. This instantly eliminates negative float and delays without adding craft labor or re-sequencing in the field.
Forensic reproducibility: Record calculation options and changes across schedule versions. If retained-logic or progress-override settings changed without explanation, test the material effect and disclose it; do not assume that reversing every change produces one uniquely true path.