Study guide
5.2 Progress Measurement and Data Date Mechanics
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.2 Progress Measurement and Data Date Mechanics
Key Takeaways Explain This Topic AI
The Data Date (Time Now / Status Date / As-of Date) establishes the strict temporal boundary dividing recorded historical facts from forward CPM forecast calculations.
No actual dates, actual costs, or progress percentages may exist to the right of (after) the Data Date; similarly, no uncompleted work or remaining duration may remain to the left of (prior to) the Data Date.
Physical Percent Complete provides the only truly objective measure of earned value, whereas Duration Percent Complete reflects elapsed calendar time and Units Percent Complete reflects resource expenditure.
Remaining Duration must be estimated independently by project controls personnel based on remaining quantities and anticipated production rates, rather than auto-calculated using software default formulas.
Cutoff date synchronization between field progress surveys, timesheet payroll systems, and CPM schedule recalculation cycles is mandatory to prevent distorted earned value metrics.
Last updated: October 2026
5.2 Progress Measurement and Data Date Mechanics
AACE Professional Context: Updating a CPM schedule is fundamentally an exercise in temporal accounting. The Data Date —synonymously termed Time Now , Status Date , or As-of Date —is the fulcrum of schedule progression. It separates immutable historical execution from dynamic forward-looking forecasts. On the PSP examination, candidates must demonstrate an uncompromising understanding of Data Date mechanics, the critical operational distinctions among percent complete types, the mathematics of remaining duration estimation, and the rigorous protocols required to status in-progress activities without corrupting network mathematics.
The Data Date: Temporal Anchor of CPM Scheduling
The Data Date (DD) defines the exact point in time up to which actual project performance is recorded and from which future work is scheduled. In the CPM forward pass algorithm, the Data Date acts as the earliest possible start date for any unstarted activity or any remaining portion of an in-progress activity. HISTORICAL ACTUALS FORWARD CPM FORECAST
- (Past: Recorded Reality) (Future: Predictive Logic)
- ───────────────────────────────────────────┬───────────────────────────────────────────►
- Actual Start (AS) │ • Early Start (ES) & Early Finish (EF)
- Actual Finish (AF) │ • Remaining Duration (RD)
- Actual Labor Hours & Costs ($ACWP$) │ • Total Float (TF) & Free Float (FF)
- Physical Quantities Installed ($BCWP$) │ • Dynamic Critical Path
- ▲
- DATA DATE
- (Time Now)
- The Cardinal Rules of the Data Date
The Inviolability of the Temporal Divide:
To the left of the Data Date ( < D D < DD < DD ): Only completed historical performance may reside. Actual Start dates, Actual Finish dates, actual costs, and completed physical quantities must have occurred on or before the Data Date.
To the right of the Data Date ( > D D > DD > DD ): Only future scheduled dates may reside. No uncompleted task work, remaining duration, or unearned budget may be placed in the past.
Zero Incomplete Work in the Past: If an activity started two weeks prior to the Data Date and has an estimated Remaining Duration of 5 days, those 5 days must be scheduled to occur strictly on or after the Data Date . Leaving remaining duration to the left of the Data Date is an egregious scheduling defect known as an invalid date or lagging task .
Zero Actual Dates in the Future: Recording an Actual Start or Actual Finish date that is later than the current Data Date represents an impossibility that invalidates the mathematical credibility of the update.
Cutoff Date Conventions and System Synchronization
In enterprise project controls, multiple data streams converge during each reporting cycle. Misalignment between cutoff dates corrupts Earned Value calculations:
Field Progress Cutoff Date: The date physical quantities (cubic yards of concrete, linear feet of pipe) are surveyed and signed off by quality inspectors.
Accounting / Financial Cutoff Date: The date labor timesheets and subcontractor invoices close in the enterprise resource planning (ERP) system.
Schedule Data Date: The official date entered into the CPM scheduling engine to trigger the forward and backward pass calculations.
Cutoff control: Define and reconcile the field-progress, accounting, and schedule cutoffs. If they differ, accruals and reported quantities must identify the timing difference so cost and earned progress are compared on a consistent basis.
Progress Measurement Methods: EVMT Evaluation
A central competency tested on the PSP exam is selecting and applying the appropriate Earned Value Measurement Technique (EVMT) . The choice of percent complete method determines whether progress reporting reflects reality or dangerous wishful thinking.
Measurement Method Mathematical Basis Primary Application Exam Traps & Vulnerabilities
Physical Percent Complete Quantity Installed to Date Total Forecast Quantity \frac{\text{Quantity Installed to Date}}{\text{Total Forecast Quantity}} Total Forecast Quantity Quantity Installed to Date Discrete physical deliverables (piping, cable, concrete, steel) Most objective EVMT. Does not auto-adjust Remaining Duration; requires independent re-estimation.
Duration Percent Complete Actual Duration Actual Duration + Remaining Duration \frac{\text{Actual Duration}}{\text{Actual Duration} + \text{Remaining Duration}} Actual Duration + Remaining Duration Actual Duration Level of Effort (LOE) or non-deliverable support activities Major Trap: Equates elapsed time with work accomplishment. If a 10-day task spends 5 days idle, Duration % Complete reports 50% even if 0% of work is installed!
Units Percent Complete Actual Units (Hours) At-Completion Forecast Units \frac{\text{Actual Units (Hours)}}{\text{At-Completion Forecast Units}} At-Completion Forecast Units Actual Units (Hours) Engineering drawings, software modules, direct craft hours Measures resource burn, not physical completion. If a crew burns 80% of budgeted hours doing 20% of work, Units % Complete inflates progress.
Incremental Milestones Pre-assigned weighted percentages earned upon passing formal quality hold points Complex work packages (e.g., spool fabrication: fit-up 20%, weld 50%, NDT 20%, hydro 10%) Highly objective; eliminates subjective interim percent guesses. Requires well-defined technical stage-gates.
Fixed Formula (0/100 or 50/50) 0% until complete (0/100); or 50% at start, remaining 50% at completion (50/50) Short-duration activities spanning one or two reporting cycles Simple and conservative. Inappropriate for long-duration or capital-intensive work packages.
Level of Effort (LOE) E V = P V EV = PV E V = P V by definition; percent complete equals elapsed time ratio Management, safety oversight, security, project controls Produces zero schedule variance ( S V = 0 SV=0 S V = 0 ). It is generally unsuitable for discrete deliverable work because elapsed time is not objective physical accomplishment.
Actual Dates: Protocols and Field Validation
Recording validated actual dates creates an auditable project-control record whose contractual significance depends on the governing documents. In construction litigation and forensic claims, actual dates are scrutinized against site superintendent daily logs, security gate badge-in records, and concrete delivery tickets.
Actual Start (AS) Criteria
Record an Actual Start when work that satisfies the activity’s defined start criterion has begun, supported by contemporaneous evidence. The criterion may be physical installation, design work, procurement work, or another modeled scope—not merely an unrelated administrative event.
Valid Actual Start: Mobilizing an excavator and breaking ground for ACT-1020: Foundation Excavation .
Invalid Actual Start: Delivering an excavation permit or staging safety cones in the parking lot when no physical digging occurred. Staging materials does not justify setting an Actual Start unless material receipt is explicitly modeled as a discrete procurement milestone.
Actual Finish (AF) Criteria
An Actual Finish date may be set only when 100% of the activity deliverable has been physically executed, inspected, and verified against technical acceptance criteria.
Setting an Actual Finish automatically forces Remaining Duration to 0 and Percent Complete to 100% .
An activity cannot possess an Actual Finish date without an Actual Start date.
An activity cannot finish on a date earlier than its Actual Start date.
Remaining Duration (RD) Recalculation vs. Original Duration (OD)
One of the most dangerous errors in CPM schedule updating is relying on software default formulas to calculate Remaining Duration.
The Software Auto-Calculation Fallacy
Many commercial scheduling engines provide an automatic calculation setting that links Remaining Duration directly to Percent Complete:
Remaining Duration (Auto) = Original Duration × ( 1 − Percent Complete ) \text{Remaining Duration (Auto)} = \text{Original Duration} \times (1 - \text{Percent Complete}) Remaining Duration (Auto) = Original Duration × ( 1 − Percent Complete )
Consider why this formula creates catastrophic reporting failures:
Suppose ACT-2050: Install High-Pressure Steam Piping has an Original Duration ( O D OD O D ) of 20 work days.
At the monthly update, 15 work days have elapsed ( A D = 15 AD = 15 A D = 15 ).
A physical field survey reveals that due to severe fit-up misalignments, only 25% of the piping has been installed ( P h y s i c a l % = 25 % Physical \% = 25\% P h ys i c a l % = 25% ).
If the planner allows the software to auto-calculate remaining duration based on duration percent complete or original duration: RD auto = 20 × ( 1 − 0.25 ) = 15 days \text{RD}_{\text{auto}} = 20 \times (1 - 0.25) = 15 \text{ days} RD auto = 20 × ( 1 − 0.25 ) = 15 days
The total at-completion duration would appear to be 15 + 15 = 30 days 15 + 15 = 30 \text{ days} 15 + 15 = 30 days .
The Field Reality: The crew required 15 days to install 25% of the scope (a production rate of 1.67% per day). To install the remaining 75% at that proven production rate will require: Realistic RD = 75 % 1.67 % / day = 45 work days \text{Realistic RD} = \frac{75\%}{1.67\% / \text{day}} = 45 \text{ work days} Realistic RD = 1.67%/ day 75% = 45 work days
The true at-completion duration is 15 + 45 = 60 work days 15 + 45 = 60 \text{ work days} 15 + 45 = 60 work days , not 30 days! Auto-calculating Remaining Duration conceals a massive 30-day critical path delay.
Forward-looking remaining-duration estimate
Do not let a percent-complete formula mechanically determine Remaining Duration when current scope, productivity, access, method, or resources say otherwise. Re-estimate the remaining work from current evidence, using the original duration as a comparison rather than an automatic answer:
Forecast Remaining Duration = Remaining Physical Quantity Anticipated Daily Production Rate \text{Forecast Remaining Duration} = \frac{\text{Remaining Physical Quantity}}{\text{Anticipated Daily Production Rate}} Forecast Remaining Duration = Anticipated Daily Production Rate Remaining Physical Quantity
At-Completion Duration = Actual Duration + Forecast Remaining Duration \text{At-Completion Duration} = \text{Actual Duration} + \text{Forecast Remaining Duration} At-Completion Duration = Actual Duration + Forecast Remaining Duration
Rules for Statusing In-Progress Activities
When updating an in-progress activity during a schedule cycle, planners must execute a standardized 6-step statusing protocol: SIX-STEP ACTIVITY STATUSING PROTOCOL
- ┌────────────────────────────────────────────────────────────────────────┐
- │ Step 1: Validate Actual Start date against contemporaneous site records.│
- │ Step 2: Measure physical quantities installed during the period. │
- │ Step 3: Compute Physical Percent Complete from verified quantities. │
- │ Step 4: Re-estimate Remaining Duration based on forward productivity. │
- │ Step 5: Verify Remaining Duration starts strictly on/after Data Date. │
- │ Step 6: Recalculate Estimate to Complete (ETC) hours and costs. │
- └────────────────────────────────────────────────────────────────────────┘
- Common Statusing Defects to Avoid
The Stalled In-Progress Task: An activity has an Actual Start, has been statused at 50% complete for four consecutive months, but the planner leaves the Remaining Duration at 5 days without moving it. As the Data Date advances, the uncompleted work is pushed into the future, consuming float every month without explanation.
The 99% Complete Syndrome: An activity reaches 90% or 95% complete rapidly, but lingers for months because punch-list items, testing, or documentation remain incomplete. If the remaining scope is minor, close the activity and create a discrete tie-in/closeout activity, or re-estimate RD realistically.
Premature Actual Finish: Setting an Actual Finish on an activity before formal inspection sign-off to show milestone achievement on paper, while field crews continue working on site.
Worked Example: Structural Steel Erection Progress Audit
An industrial warehouse project has an approved baseline activity: ACT-3100: Erect Structural Steel Frame .
- Original Duration (OD): 30 work days
- Baseline Dates: Start Day 20, Finish Day 50
- Scope: 1,200 structural steel tons (Budgeted production rate = 40 tons/day)
Reporting Cycle at Data Date = Day 40 (20 work days elapsed):
Contemporaneous Verification: Actual Start was confirmed on Day 22 (2 days late due to crane mobilization).
Elapsed Actual Duration (AD): Day 22 to Day 40 = 18 work days worked.
Field Survey: 450 tons of steel have been completely bolted and plumbed.
Project Controls Calculation:
Physical Percent Complete: Physical % = 450 tons 1 , 200 tons = 37.5 % \text{Physical } \% = \frac{450 \text{ tons}}{1,200 \text{ tons}} = 37.5\% Physical % = 1 , 200 tons 450 tons = 37.5%
Duration Percent Complete (Software Default Trap): Duration % = 18 elapsed days 30 OD = 60.0 % \text{Duration } \% = \frac{18 \text{ elapsed days}}{30 \text{ OD}} = 60.0\% Duration % = 30 OD 18 elapsed days = 60.0% Notice: Relying on Duration % Complete would over-state progress by 22.5 % 22.5\% 22.5% !
Demonstrated Production Rate: Actual Productivity = 450 tons 18 days = 25 tons/day (vs. planned 40 tons/day) \text{Actual Productivity} = \frac{450 \text{ tons}}{18 \text{ days}} = 25 \text{ tons/day (vs. planned 40 tons/day)} Actual Productivity = 18 days 450 tons = 25 tons/day (vs. planned 40 tons/day)
Independent Remaining Duration (RD) Estimation:
Remaining Quantity = 1 , 200 − 450 = 750 tons 1,200 - 450 = 750 \text{ tons} 1 , 200 − 450 = 750 tons .
With an additional crane mobilized next week, the team projects a forward rate of 30 tons/day. Forecast RD = 750 tons 30 tons/day = 25 work days \text{Forecast RD} = \frac{750 \text{ tons}}{30 \text{ tons/day}} = 25 \text{ work days} Forecast RD = 30 tons/day 750 tons = 25 work days
At-Completion Duration and Milestone Variance:
Total At-Completion Duration = 18 (AD) + 25 (RD) = 43 work days 18 \text{ (AD)} + 25 \text{ (RD)} = 43 \text{ work days} 18 (AD) + 25 (RD) = 43 work days (an overrun of 13 work days beyond the 30-day baseline).
Forecast Finish Date = Data Date (Day 40) + 25 work days = Day 65 \text{Data Date (Day 40)} + 25 \text{ work days} = \text{Day 65} Data Date (Day 40) + 25 work days = Day 65 .
Schedule Slippage = Day 65 forecast vs Day 50 baseline = 15 work days delay to the structural critical path .