Schedule Update Review
An update can show a comfortable finish date while quietly hiding shaved durations, manipulated logic, or out-of-sequence work the software "fixed." The update review is the disciplined audit that confirms a statused schedule is honest before you trust it, accept it, or pay against it. Built on AACE 53R-06.
What an update review is
Statusing produces the update; the review verifies it. The two are a pair: a sound control loop is "status, then review, every period." Skipping the review means trusting a forecast you haven't checked — and, on contracts where payment or extensions ride on the schedule, accepting numbers you can't defend.
Why the review matters
An unreviewed update can mislead in three expensive ways. It can be optimistic — remaining durations shaved to hold a date that won't hold. It can be manipulated — logic quietly changed, constraints added, or progress overstated to mask slippage. Or it can simply be wrong — statusing errors that corrupt the forecast. Any of these turns the schedule from a control tool into a comfort blanket, and on a claim it becomes evidence you can't rely on.
What the review checks
- Data date & progress integrity — correct data date; no remaining work to the left of it; actuals match the field; % complete is honest, not inflated.
- Logic & duration changes — were activities, relationships, or durations changed since last update? Each change should be intentional, documented, and explained — not silent.
- Constraints & float — watch for new hard constraints or sudden float changes that mask slippage and distort the critical path.
- Out-of-sequence progress — work reported done before its predecessors — a sign of broken logic or shortcut reporting.
- Forecast reasonableness — does the new completion date make sense given actual performance? A forecast that ignores a clear downward trend is a red flag.
Out-of-sequence progress & retained logic
One issue trips up nearly everyone: out-of-sequence progress — an activity that has progressed even though a logical predecessor hasn't finished. It happens in the real world (crews jump ahead), but it tells the software the logic was violated, and how the tool handles it changes the forecast.
| Setting | How it treats out-of-sequence work |
|---|---|
| Retained logic | Keeps the original logic — remaining work waits for the predecessor anyway (can look pessimistic) |
| Progress override | Ignores the unmet predecessor and lets the activity continue (can look optimistic) |
Ten things to remember
- The update review verifies the statused schedule before anyone trusts or pays against it.
- "Status, then review, every period" — the two halves of a sound control loop.
- The reviewer should be independent of the update's author.
- Updates mislead three ways — optimistic, manipulated, or simply wrong.
- Check progress integrity — correct data date, no work left of it, honest % complete.
- Scrutinize logic/duration changes — each should be intentional and documented.
- Watch new constraints and sudden float changes — common ways slippage is masked.
- Out-of-sequence progress + the retained-logic vs progress-override setting can change the forecast.
- Compare update-to-update — a clean diff means a trustworthy update.
- Confirm the forecast is reasonable — it must respect actual performance, not ignore the trend.
Glossary
- Acceptance
- The owner's approval of a submitted update, often tied to payment.
- Float erosion
- Unexplained loss of float that can mask real slippage.
- Out-of-sequence progress
- Work progressed before its logical predecessor finished.
- Progress override
- A setting that ignores unmet predecessors and lets the activity proceed.
- Retained logic
- A setting that keeps original logic for out-of-sequence work.
- Schedule manipulation
- Undisclosed changes (logic, constraints, durations) that distort the forecast.
- Update review
- A structured check that a statused schedule is accurate, complete, and unmanipulated.
- Update-to-update comparison
- Reviewing what changed between successive updates.