A schedule update moves the data date forward and records what actually happened in the update period since the last one: actual starts and finishes, remaining durations, and any logic or duration changes. Most contracts require a monthly update with a narrative. Once the owner accepts it, it becomes the update of record.
In UK practice, and under NEC contracts, the equivalent submission is usually called a revised programme.
How it works
- Copy the last accepted update. Work on a new version so the update of record stays intact.
- Set the new data date. Everything before it is history; everything after it is forecast.
- Record progress as of the data date. Actual starts and finishes, remaining durations or percent complete for work in progress. Progress comes from the field: daily logs, superintendent walk-downs, installed quantities.
- Add approved and pending changes. Change work is usually added as a small group of new activities (a fragnet) tied into the existing logic.
- Make and log revisions. Any change to logic, durations, calendars or constraints is recorded with a reason, separately from progress.
- Recalculate and check. Look for actual dates after the data date, unstatused work before it, out-of-sequence progress, open ends and new constraints.
- Write the narrative. Explain the critical path, the change in forecast finish and float, what drove it and what is being done about it.
- Submit, review, accept. The owner’s scheduler reviews and comments. Once accepted, the update is archived as the update of record.
Worked example
Illustrative (sample data): the June update moves the data date from 1 June to 1 July on a mid-rise building.
| Item | May update (accepted) | June update |
|---|---|---|
| Data date | 1 June | 1 July |
| Forecast substantial completion | 14 March | 20 March |
| Change from previous update | 6 days later | |
| Critical path runs through | Level 4 deck pour | Level 5 steel erection |
| Total float on critical path | 0 | -6 days |
During June, steel for levels 5 and 6 arrived eight working days late, and level 5 erection started late as a result. The scheduler records the actual start, keeps the remaining duration, and adds no logic changes. Recalculation shows steel erection is now driving the finish.
The narrative names the late delivery as the cause, notes that the supplier’s revised dates are in a submitted letter, and proposes a recovery: a second erection crew for levels 6 and 7, which would recover four of the six days if approved. The owner’s scheduler compares the update with May, asks why one MEP rough-in activity shows progress with no actual start date, gets a corrected file, and accepts the update.
Update vs related schedule submissions
| Submission | What changes | Typical approval |
|---|---|---|
| Update | Progress, plus small justified changes | Reviewed and accepted each period |
| Revision | Logic, durations or sequence | Often needs separate approval |
| Recovery schedule | A plan to regain lost time | Usually requested by the owner |
| Re-baseline | Replaces the baseline | Rare; usually after major changes |
| Look-ahead | Short-term field plan from the update | Internal |
Why it matters
Accepted updates are the fixed points of delay analysis. A windows analysis measures delay between consecutive updates of record. Updates that were never reviewed, or that changed after acceptance, weaken any later claim or defence.
They also matter for money. Many contracts tie the pay application to a submitted or accepted update, and a time impact analysis for a change is usually inserted into the most recent accepted update.
Common mistakes
- Changing logic quietly to hide a slip, then reporting it as progress.
- Status dates that don’t match the data date: actuals in the future or forecasts in the past.
- Updating durations from memory instead of field records.
- A narrative that lists activities but never says what drove the finish date.
- Submitting late, so the review lags behind the work and problems pile up.
- Editing an accepted update instead of making the fix in the next one.
How os.construction handles it
The Updates page runs each period as one record: open at a new data date, eight update checks, a six-section narrative, multi-step review, and an immutable update of record that feeds the forensic series. See The update cycle.
FAQ
What is a schedule update in construction?
A schedule update records actual progress on the project schedule as of a new data date: what started, what finished, how much work remains, and any changes to logic or scope. The schedule is recalculated from the new data date to forecast the remaining work and the finish date, and the result is submitted with a narrative.
How often should a construction schedule be updated?
The contract decides. Monthly updates tied to the pay application cycle are the most common requirement, and some contracts ask for more frequent updates on fast or complex work. Internally, many teams update the look-ahead weekly and the full schedule monthly.
What is the difference between a schedule update and a schedule revision?
An update records progress and keeps the plan's logic and durations unless a change is justified. A revision changes the plan itself: new sequencing, revised durations or restructured work. Many contracts treat revisions as needing separate approval, and the narrative should say which changes are progress and which are revisions.
What is an update of record?
It is an update the owner or its scheduler has reviewed and accepted. Accepted updates become the reference points for measuring progress and analysing delay, so they should be archived exactly as accepted and not changed afterwards.
What should a schedule update narrative include?
Typically the data date, the current critical path, the forecast finish compared with the previous update and the baseline, the activities that drove any change, logic or duration changes made and why, added change activities, problems and proposed recovery. Contracts often list the required contents.