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.

    Footings started two days late, and the foreman says five days of work remain. Shifting the bar by hand hides it: the walls and the milestone don't move. Statusing it properly (actual start, remaining duration from the status date, logic left on) pushes the walls and backfill out, and the milestone shows five days late.

    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

    40% done7 days remaining
    Baseline startActual startStatus dateForecast finish
    Before the status date: actuals onlyAfter it: forecasts only
    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.
    What to record for each activity at every update: actual start (and actual finish when done), how much work remains in working days, and the forecast finish that follows from the remaining duration and the logic. Actual dates sit before the status date; forecasts sit after it.

    How to update the schedule, step by step

    1. 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.

    2. Record actual starts and finishes

      From daily reports and the look-ahead. Use the real dates, even when they're embarrassing.

    3. 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.

    4. 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.

    5. Recalculate

      Let the scheduling tool push successors from the status date. No actual dates after it; no forecast dates before it.

    6. 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

    Common updating habits and what they hide
    HabitWhat it hidesDo this instead
    Dragging a late bar to the rightSuccessors and milestones don't moveEnter the actual start and remaining duration; let logic move the rest
    Typing a finish date by handThe forecast stops following the logicChange the remaining duration, not the date
    Adding a hard date constraintNegative float and the true finishUse logic; keep constraints for genuine contract dates
    Remaining = duration × (1 − %)Slow crews and reworkAsk for remaining working days
    Updating the baselineAll varianceKeep the baseline; re-baseline only by approval
    Skipping a monthGradual slipsUpdate 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.

    01020JanFebMarAprMayJunsurprise
    • Statused properly
    • Bars shifted by hand
    • Working days late (vertical)
    Illustrative milestone trend: how many working days late the completion forecast was at each monthly update. Statused properly, the slip shows from February and grows steadily, so there is time to act. With bars shifted by hand, the report says “on time” until the delays can't be hidden any more.

    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.

    Sources

    1. Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G)(opens in a new tab). U.S. Government Accountability Office, 2015.
    2. 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.