5.4 Schedule Update Review and Quality Verification per RP 53R-06

5.4 Schedule Update Review and Quality Verification per RP 53R-06

AACE RP 53R-06 addresses schedule update review as applied in engineering, procurement, and construction. An update review asks whether status is supported, revisions are explained, the network remains technically usable, and the forecast communicates current conditions. The governing contract or schedule specification determines submittal and acceptance requirements.

Separate status from revision

Status information includes actual starts and finishes, installed quantities, physical progress, remaining duration, and actual resource or cost data. Model revisions include added or deleted activities, changed logic, calendars, constraints, coding, and future durations. The two can occur in one update, but reviewers should identify them separately. Otherwise, an unexplained logic change can be mistaken for the effect of progress.

Review sequence

1. Confirm the correct file, data date, calendars, and calculation settings.
2. Reconcile material actual dates and progress with contemporaneous records.
3. Check that remaining work is scheduled on or after the data date under the selected calculation rules.
4. Compare the update with the prior accepted or submitted version.
5. Review added and deleted activities, logic changes, constraint changes, duration changes, calendar changes, and coding changes.
6. Trace the current and near-critical paths to each important milestone.
7. Compare baseline, prior forecast, and current forecast dates and explain movement.
8. Test remaining resource, procurement, access, approval, and productivity assumptions.
9. Review risks, changes, out-of-sequence work, and recovery actions.
10. Document findings, responses, accepted exceptions, and unresolved decisions.

Metrics are screens

Open ends, leads, lags, hard constraints, high float, negative float, long durations, invalid dates, missed tasks, and other metrics can direct attention to potential problems. The DCMA 14-point assessment is a separate framework often used in government contracting; its definitions and thresholds are not automatically AACE requirements or universal PSP rules. Use any required threshold exactly as its source and project specification define it.

For example, a zero-lead target may be a contract requirement and a useful clarity rule. A detected negative lag should then be reviewed and resolved or documented. The finding does not prove deception or legal liability. Likewise, an open endpoint may be an accidental omission, an external interface, or an intentionally bounded subnetwork. Determine effect and disposition.

The Critical Path Length Index is commonly calculated as:

$CPLI = \frac{\text{Critical Path Length} + \text{Total Float}}{\text{Critical Path Length}}$

If path length is 250 working days and float is negative 25 days, CPLI is 225 ÷ 250 = 0.90. That quantifies the gap to the constrained target under the stated model. A threshold may trigger escalation, but the index alone does not prove that a particular recovery plan is feasible or determine contractual responsibility.

Delta and narrative review

The reviewer should be able to explain why each key date changed. A schedule comparison can reveal a deleted tie, new constraint, duration reduction, calendar change, or newly added scope. Ask for the execution basis and authorization rather than assuming every change is improper. Field resequencing may make a logic change necessary; undocumented change still weakens auditability.

A useful update narrative states progress achieved, milestone variance and trend, current driving paths, material model revisions, change status, risks and opportunities, resource or procurement concerns, recovery actions, and decisions required. It should reconcile with the native schedule.

Acceptance and records

Schedule review is a technical and administrative process governed by the project documents. Record whether a finding is corrected, accepted as an exception, deferred, or disputed. Preserve the submitted file, review comments, responses, and final disposition. Avoid claiming that technical acceptance automatically waives rights or establishes entitlement; those consequences depend on contract and law.

The objective is a truthful, reproducible forecast that decision-makers can use—not a perfect score on an isolated diagnostic dashboard.

Applied review: sample from source to report

Select several reported actual starts, finishes, quantities, and remaining durations and trace them to daily reports, inspection records, procurement logs, or responsible-party confirmation. Then select each key forecast milestone and trace backward to the current driving work. This two-way sampling tests both status evidence and network explanation.

For every material delta, record whether it is progress, correction, execution resequencing, approved change, risk response, or unexplained revision. Quantify its milestone effect where practical. A concise exception log with owner, response, disposition, and due date turns quality review into an actionable control process rather than a one-time score.