How to update a construction progress schedule without hiding delays
Dragging late bars to the right makes the schedule look fine this month and terrible in three. Here is how to status a schedule so it tells the truth early, while there's still time to recover.
Updated 14 November 2026 · 7 min read
- Excavation
- Footings
- Foundation walls
- Backfill
- Foundations done
Milestone forecast: on time. But walls can't start until footings finish, so this date is wrong.
Quick answer
To update a construction progress schedule: pick a status date; record actual start and finish dates for work that started or finished; for work in progress, enter the remaining duration in working days (ask the foreman, don't derive it from a percentage); leave the logic on so successors move with the work; then recalculate and compare the forecast with the baseline. Don't drag bars or type dates by hand: that hides delays until they can't be recovered.
Key takeaways
- Everything before the status date is an actual; everything after it is a forecast.
- Remaining duration drives the forecast. Percent complete is for reporting, not forecasting.
- Let the logic move successors; manually typed dates and hard constraints mask slips.
- Report the variance against the baseline every update, with a short narrative of why.
Why shifting bars hides delays
When an activity runs late, it's tempting to slide its bar to the right and move on. If the successors don't move with it, the schedule now shows overlapping work that can't happen, and the milestone still looks on time. The real delay comes out months later, all at once, when there's no float left to absorb it.
The U.S. Government Accountability Office's schedule best practices call for updating with actual progress and logic, so that the forecast follows from what happened. The figure above shows the difference on four foundation activities.
What to record for each activity
- Status date
- The cut-off the update describes. Everything before it is fact, everything after it is forecast.
- Actual start and finish
- The dates it really started and finished, not the planned ones.
- Remaining duration
- Working days of work left, estimated by the foreman, not worked out from the percentage.
- Forecast
- Calculated by the logic from the remaining durations. Never typed in by hand.
How to update the schedule, step by step
Set the status date
Usually the last day of the period you're reporting. Collect progress as of that date, not as of the day you open the file.
Record actual starts and finishes
From daily reports and the look-ahead. Use the real dates, even when they're embarrassing.
Ask for remaining durations
For each activity in progress, ask the foreman how many working days of work are left. Don't calculate it from percent complete: 80% done can still mean a week of work.
Check logic and out-of-sequence work
If work started before its predecessor finished, fix the logic to match what really happened, rather than leaving an impossible sequence.
Recalculate
Let the scheduling tool push successors from the status date. No actual dates after it; no forecast dates before it.
Compare with the baseline and explain
Report milestone and critical path movement with a short narrative: what slipped, why, and what recovery is planned.
Habits that hide delays
| Habit | What it hides | Do this instead |
|---|---|---|
| Dragging a late bar to the right | Successors and milestones don't move | Enter the actual start and remaining duration; let logic move the rest |
| Typing a finish date by hand | The forecast stops following the logic | Change the remaining duration, not the date |
| Adding a hard date constraint | Negative float and the true finish | Use logic; keep constraints for genuine contract dates |
| Remaining = duration × (1 − %) | Slow crews and rework | Ask for remaining working days |
| Updating the baseline | All variance | Keep the baseline; re-baseline only by approval |
| Skipping a month | Gradual slips | Update on a fixed cycle, every period |
Watch the trend, not just this month
Plot the forecast completion at every update. A steady slip is a warning you can act on; a flat line followed by a jump means delays were being hidden.
- Statused properly
- Bars shifted by hand
- Working days late (vertical)
Feed it from the look-ahead
The best source of actual dates and remaining durations is the weekly look-ahead: it records what each trade actually finished, and why anything slipped. A 2012 study found that weekly plans not linked to the master schedule could report high completion while the project still slipped, so the information has to flow both ways.
- In 3WLA each task carries progress, status and a delay reason, updated by foremen from site, including on their phones.
- Every issued look-ahead is a frozen copy, so you can see exactly what was planned and when for the monthly update.
- On the Business plan, AI compares the look-ahead with your master schedule PDF and lists activities that have moved, are early or are missing.
Common questions
What is a status date (data date)?
The date the update describes. Progress before it is recorded as actuals; everything after it is forecast by the schedule logic.
How often should a construction schedule be updated?
Usually monthly for the progress schedule, or as the contract requires, and weekly for the look-ahead. Keep the cycle fixed so trends are comparable.
Should I use percent complete or remaining duration?
Record both, but forecast from remaining duration. Percent complete shows how much is done; remaining duration tells you when it will finish.
Is it ever right to change the baseline?
Only through a documented, approved re-baseline when the plan no longer represents the work, such as after major approved changes. Keep the original for reference.
Get honest progress from the field every week
3WLA records progress, status and delay reasons on every look-ahead task, from the office or a phone, and keeps a frozen copy of each issue. That's the input a truthful monthly update needs. Free for one project, with unlimited people.
Keep reading
- GuideBaseline vs progress vs look-ahead schedulesHow the baseline, the progress schedule and the 3-week look-ahead answer different questions: purpose, detail, ownership and update frequency compared.
- GuideWhat is a 3-week look-ahead schedule?What a 3-week look-ahead schedule is, who prepares it, what goes in it and how it connects to the master schedule, with an annotated example.
- GuideHow to create a 3-week look-ahead scheduleStep by step: turn master schedule activities into a 3-week look-ahead, fill in each column, check readiness, get commitments and update it weekly.
Sources
- Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G)(opens in a new tab). U.S. Government Accountability Office, 2015.
- Rethinking Lookahead Planning to Optimize Construction Workflow (Hamzeh, Ballard and Tommelein), Lean Construction Journal, pp. 15–34(opens in a new tab). Lean Construction Institute, 2012.
