Five questions to ask before accepting the weekly schedule update
Review weekly schedule changes with five practical questions about actual progress, remaining work, logic, float and decisions.
The finish date has not moved. That is usually the first thing everyone wants to hear.
It should not be the last thing anyone checks.
A construction schedule update can hold the same completion date while the work behind it becomes less credible. Remaining durations shrink. Logic changes. A delivery commitment gets replaced with an assumption. None of those changes necessarily makes the update wrong, but someone needs to explain them.
Use these five questions in the weekly review. They are a practical discussion structure, not a substitute for a full schedule analysis.
#What actually happened before the data date?
Start with facts that can be checked. Which activities started? What finished? Who confirmed it? Does “complete” include the inspection, test or handoff the next trade needs?
An illustrative case: rough-in is reported complete, but the inspection is still outstanding. If inspection is a separate activity with the correct dependency, the schedule may represent this perfectly well. If the next trade is already shown working in that area, the team needs to understand the actual field condition.
Ask for the project record behind a disputed status. A short clarification today is cheaper than rebuilding three weeks of progress history later. Do not revise historical actuals merely to make the current update look tidy; document corrections and the basis for them.
#How much work remains, and what does the estimate assume?
“Eighty percent complete” is a weak answer to “when will it finish?” The remaining work may be the awkward part: restricted access, commissioning, corrections, or a sequence that depends on someone else.
Ask the trade to describe the remaining quantity, crew availability, achievable production and unresolved constraints. When a remaining duration falls sharply, distinguish a real plan change from a spreadsheet adjustment.
The point is not to demand certainty from the field. It is to make the uncertainty visible enough to manage.
#What changed in the logic?
Compare new relationships, deleted predecessors, constraints and calendars. Some changes reflect good planning. Others remove the very dependency that explains the risk.
The GAO schedule guide1 includes updating the schedule using actual progress and maintaining a baseline among its best practices. For a weekly GC meeting, a simple change register helps preserve the reasoning behind each meaningful revision.
Record the change, the person who proposed it, the evidence and the expected effect. Keep the baseline intact so the team can distinguish the approved plan from the current forecast.
#Where did the float go?
A stable finish date can conceal declining flexibility. Review the paths approaching criticality, not only the activities currently printed in red. Ask which delivery, inspection or trade handoff now has less room than last week.
Do not add float losses across unrelated paths and call the total a project delay. Use the schedule relationships to understand how the paths interact. Where the model does not represent a real dependency, fix the model through the project's agreed process.
#Which decision would change next week's forecast?
End with decisions, not a tour of every bar on the screen. Name the issue, the owner, the required-by date and the evidence needed to close it.
A good outcome might be: “Confirm the enclosure release by Thursday; if it slips, reassess interior work-area availability.” That is more useful than an unexplained amber status.
Keep a short record of which decisions were made and whether the expected effect occurred. Over several updates, that record will show where the team's forecasts are reliable and where assumptions repeatedly fail.
#Make the review repeatable
Run the five questions in the same order every week, with the same people in the room: the scheduler, the superintendent or field lead for the area, and the project manager who owns the commitments to the owner. A consistent order makes it easier to notice what changed, because the team is comparing like with like instead of reacting to whichever bar looks worst on the day.
Keep the exceptions short. If a package has the same evidence, the same dependency and the same date as last week, it does not need airtime. Spend the meeting on the activities where the record changed or where the explanation for a date is thin. A reviewer who cannot say where a duration, relationship or status came from has found the next question to ask.
Finally, write the questions down as a checklist that travels with the schedule file. When a project manager or scheduler changes mid-project, the checklist and the decision record let the next person see how the team reasoned about the dates, not just what the dates are now. For a broader look at reviewing schedule and project records against their sources, see how SP4N approaches project evidence.