Statusing the CPM Schedule
A baseline is a snapshot; statusing keeps it alive. It's the periodic discipline of recording what actually happened as of a cutoff and letting the schedule recompute the forecast — the heartbeat of project control. Built on AACE 90R-17.
What statusing (updating) is
A baseline is a plan frozen at a moment in time. The instant work starts, reality diverges from it. Statusing is how the schedule stops being a stale plan and becomes a live forecast: each cycle you tell it what actually happened, and it tells you where the project is now headed.
The data date — past vs. future
Every update is built around the data date (also called the status or "as-of" date): the cutoff that splits the schedule into history and forecast.
| Side of the data date | What it holds |
|---|---|
| Left (the past) | Actuals — actual start/finish dates, actual progress. Fixed history. |
| Right (the future) | Forecast — remaining work, recalculated by the CPM from the data date forward. |
What you record each cycle
For every activity touched in the period, statusing captures the actuals that let the CPM recompute:
- Actual start / actual finish — the real dates work began and ended. Once recorded, these are fixed history.
- Progress / % complete — how far in-progress activities have got — measured by quantity installed where possible, not gut feel.
- Remaining duration — the honest estimate of time left on in-progress work — the single most important forecast input. Don't just let it count down automatically; reassess it.
- Changes since last update — new activities, logic or duration changes (with reasons), and any delays modelled as fragnets (Lesson 2).
A disciplined update cycle
Good statusing is a consistent, repeatable routine on a fixed cadence:
Ten things to remember
- Statusing turns a frozen baseline into a live forecast — the heartbeat of project control.
- You compare baseline vs current every period — the variance is the control signal.
- The data date splits past from future — actuals left, forecast right.
- No remaining work to the left of the data date — a hallmark of a clean update.
- Record actual start/finish, progress, and remaining duration for touched activities.
- Remaining duration is the forecast — reassess it honestly, don't just auto-count-down.
- Measure % complete by quantity where possible, not gut feel.
- Status on a fixed cadence — consistency makes trends and variance meaningful.
- Recalculate, then review — the update isn't done when the dates change; you must interpret them (Lesson 16).
- Preserve every update — the series is the contemporaneous record for any future claim.
Glossary
- Actual start / finish
- The real dates work began/ended — fixed history once recorded.
- Baseline
- The frozen original plan compared against each update.
- Current schedule
- The updated schedule reflecting reality plus forecast.
- Data date
- The "as-of" cutoff splitting actuals (past) from forecast (future).
- Percent complete
- How far an in-progress activity has progressed.
- Remaining duration
- The estimated time left on in-progress work — the key forecast input.
- Statusing / update
- Recording actual progress as of a cutoff and recalculating the schedule.
- Update series
- The preserved set of schedules at each data date — the project's time record.