Scheduling

How to update a construction schedule every week

Pick a fixed data date, collect actual starts, finishes, and remaining durations from the field, update any logic that changed, recalculate, review the critical path against the baseline, then roll the look-ahead and send a one-page summary.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

To update a construction schedule every week, set the same data date each week (for example, end of day Friday), collect actual start and finish dates and the remaining duration for every activity in progress, add or fix logic where the field changed the plan, recalculate, and compare the new forecast finish and critical path to the baseline. Then roll the three-week look-ahead from the updated schedule and send a short summary of what moved and why. Done weekly, it is a short routine. Done every few months, it becomes a reconstruction project.

Contracts often require less. U.S. Army Corps of Engineers guidance, for example, calls for statusing the schedule at least monthly. Weekly updates make the monthly submission a formality, keep the field on real dates, and catch slips while they are still days, not weeks.

What a schedule update includes

  • Data date: the cutoff. Everything before it is actual; everything after it is forecast.
  • Actual start and finish dates for activities that started or finished since the last update.
  • Remaining duration for each activity in progress, based on what is left, not on percent of time used.
  • Logic changes where the field changed sequence, plus new activities for changes, delays, or added scope.
  • Recalculated forecast of the finish date and milestones.
  • Narrative: a short note on what moved, why, and what is being done about it.

How to update the schedule in 7 steps

  1. Fix the data date. Pick one cutoff, like Friday at end of day, and keep it every week.
  2. Collect progress from the field. The superintendent marks actual dates and remaining days on a printout or the look-ahead. Check against daily logs and sub reports, not memory.
  3. Enter actuals and remaining durations. For each in-progress activity, ask how many working days are left at the current crew size. Do not just slide the bar forward.
  4. Update logic for reality. If the electrician started the west wing before the east, change the links. Add activities for change orders, owner delays, and RFIs that are holding work. Keep delay events as separate activities so they can be traced later.
  5. Recalculate and check the critical path. Note the new forecast finish, the critical path, and any path with low float. Compare to last week and to the baseline.
  6. Roll the look-ahead. Pull the next three weeks from the updated schedule into the three-week look-ahead for the sub meeting.
  7. Report and save. Save a dated copy of the update. Send a one-page summary to the PM, owner if required, and key subs.

Worked example: a week 18 update

Say a GC is in week 18 of a 40-week school renovation. Last week's update forecast substantial completion on time with 6 working days of float. The superintendent's markup for this week shows the following.

Example: field markup for the week 18 update
ActivityLast week's planThis week's statusEffect
Wing B ductwork rough-inFinish Thursday3 days remaining, crew was short 2 peoplePushes Wing B inspection 3 days
Wing B above-ceiling inspectionNext TuesdayNow following FridayOn critical path
Gym floor sleepersStart MondayStarted Monday, on trackNone
Owner hardware decision (RFI 44)Not on scheduleAdded as activity, answer due in 5 daysHolds door install in Wing A
Wing A door installStart in 2 weeksStart in 3 weeksFloat drops from 9 to 4 days

After recalculating, forecast completion is still on time, but float dropped from 6 to 3 working days because the Wing B duct delay hit the critical path. The PM's summary is three lines: Wing B duct is 3 days late due to short manpower, mechanical sub has committed 2 more fitters Monday; RFI 44 hardware answer is needed in 5 days or Wing A doors become critical; overall float is now 3 days. The owner reads it in a minute. The mechanical sub sees its name next to the delay. The hardware decision is now on the owner's desk with a date.

What to check after you recalculate

The forecast finish date is only the first line. Before you send the update, look at four more things.

  • Did the critical path change? A new chain on the critical path, like the owner hardware decision above, needs an owner and a date right away.
  • Which paths lost float this week? A path that went from 12 days to 4 is the next problem, even if it is not critical yet.
  • Are there open ends or broken links? New activities added this week must have a predecessor and a successor, or the forecast is wrong.
  • Do actual dates match the logs? A finish date entered on Friday that the daily log shows as Tuesday will be found later, usually by the other side in a dispute.

If the forecast finish moved past the contract date, the update is not done until you have written notice of any owner-caused delay and a plan for any delay that is yours. See how to recover a construction schedule.

How to keep the routine to an hour

  • Same day, same time, same person every week.
  • Super marks up the look-ahead daily, so Friday is a transfer, not a memory test.
  • Only update activities that are in progress or due to start in the next update period.
  • Keep delay events, change orders, and owner decisions as their own activities so you never have to rebuild the story.
  • Use the weekly meeting to confirm remaining durations with sub foremen. The Lean Construction Institute's Last Planner approach tracks how many weekly commitments were completed on time, which is a useful check on whether your remaining durations are realistic.

Mistakes to avoid

  1. Changing the data date from week to week, which makes updates impossible to compare.
  2. Moving bars instead of entering actual dates and remaining durations.
  3. Deleting or shortening activities to keep the finish date looking good.
  4. Leaving changes and delays out of the schedule, then trying to add them at claim time.
  5. Updating the office schedule without telling the field and subs.
  6. Not saving each update, so there is no history to show when things moved.

Templates, terms, and tools

Use the construction schedule template with baseline, actual, and remaining duration columns, and the construction meeting minutes template to record sub commitments. Related terms: progress schedule, float, and critical path method. Also see baseline schedule vs current schedule and how to write a construction project status report.

Smart Business Automator can summarize the week's daily logs and flag risks such as short manpower or late deliveries, so the PM starts the weekly update with the field's facts already pulled together. See construction workflow automation.

Frequently asked questions

What is a data date in a construction schedule?

The data date is the cutoff for an update. Work before it is shown as actual, and everything after it is forecast. Keeping the same data date each week makes updates comparable.

Should I update the schedule weekly or monthly?

Follow the contract's minimum, which is often monthly. Updating weekly in the field keeps crews on real dates and makes the monthly submission quick and accurate.

Who updates the construction schedule?

Usually the project manager or a scheduler enters the update, using progress the superintendent collects from the field and sub foremen.

What should a weekly schedule update report say?

Keep it to one page: the forecast finish compared to the baseline, the current float, what moved on the critical path and why, and the actions and owners for each problem.

Sources

  1. U.S. Army Corps of Engineers (via WBDG): Engineering and Construction Bulletin 2008-23, Adverse Weather Policy for Construction Contracts
  2. Lean Construction Institute: Last Planner System
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment