A construction schedule update review is the cheapest control an owner has and the one most often skipped, because the document is long, the software is unfamiliar, and the completion date at the bottom has not moved. The date is the last thing to move, which is exactly why reading only the date is useless.
Why the completion date tells you nothing until it is too late
A construction schedule is a network of activities linked by logic, and the completion date is an output of that network rather than an input to it.
Between the network deteriorating and the date moving there is a buffer, and the buffer is float. Activities that are not on the critical path can slip by weeks without the date changing at all, and activities on the critical path consume total float before they consume the date.
So a project can lose most of its resilience over four months while every monthly report says the completion date is unchanged, and every statement in those reports is accurate.
When the date finally moves it moves in one step, usually by a large amount, and by then the remedies are expensive ones. Adding crews, working shifts, resequencing, or accepting the delay and paying for it.
The purpose of a monthly review is not to find out whether the project is late. It is to find out whether the project is becoming fragile, which is a question the date cannot answer and float can.
This is the same argument as reading the date before signature, set out in whether the completion date is real, applied every month instead of once.
The five checks in a construction schedule update review
One. Total float on the critical path, this month against last. One number, taken from the same place each time. A path that had 24 days of float in March and 6 in June is deteriorating, whatever the date says.
Two. Has the critical path changed. A critical path that runs through the envelope in one update and through the elevators in the next is telling you that a second path has caught up. Two near critical paths is a materially different risk from one.
Three. Activities added, deleted or relogicked. Schedules are revised, not only updated. An activity duration shortened from 40 days to 25 with no change in scope is a forecast being adjusted to hold a date, and it is visible only by comparison.
Four. Progress against plan on the critical path only. Overall percentage complete averages across hundreds of activities and hides the ten that matter. Read the ones on the path.
Five. Procurement and long lead dates. The dates behind the dates. An activity cannot start earlier than its material arrives, and those dates live in a separate log that is often not reconciled with the schedule at all, as in the date behind the date.
What relogicking looks like and why it matters
The single most informative comparison in a schedule update review is between this month network and last month network, and it is the one almost nobody makes.
Schedules absorb pressure by changing their own logic. An activity that was finish to start becomes start to start with a lag. Two activities that were sequential become parallel. A duration is compressed. None of these are wrong in themselves and all of them are legitimate planning responses.
What they have in common is that each one recovers time on paper without anybody doing anything differently on site. The date holds because the model changed, not because the work did.
The question to put is simple and it is not adversarial. This activity was 40 days and is now 25. What changed to make that possible. There are good answers: an additional crew has been committed, a different method has been adopted, scope has moved to another package. There are also no answers, and the absence of one is the finding.
Accumulated over six months, unexamined relogicking produces a schedule that is internally consistent, holds the contractual date, and cannot be built.
A worked example
Illustrative figures. Not taken from any client project and not a quotation.
A 340 unit residential building with a contractual completion in month 26.
Months 6 through 14 all report the completion date as unchanged. Percentage complete tracks within two points of plan throughout.
The five checks over the same period show something else. Total float on the critical path falls from 31 days to 2. The critical path moves from the structure to the facade in month nine and to the elevators in month twelve, meaning three paths are now within days of each other. Eleven interior activities have had durations reduced by an average of 34 percent with no scope change and no committed resource change. The curtain wall release date has slipped twice in the procurement log and has not been reflected in the schedule at all.
In month fifteen the date moves by 98 days in a single update.
Nothing happened in month fifteen. Everything happened between months six and fourteen, in a document that was issued monthly and read by nobody on the owner side beyond the date at the bottom.
Doing it without scheduling software
An owner does not need to run the software to do this review, but does need the file rather than a printed summary.
Ask for the native file monthly, and ask for three standard reports alongside it: the longest path, the activities with negative or low float, and a comparison report against the previous update. All three are single clicks for whoever maintains the schedule, and none of them requires new analysis.
Put that requirement in the contract as part of the reporting exhibit rather than requesting it in month nine, for the reasons set out in the monthly report an owner should demand.
Then the monthly reading is five numbers, one comparison and one list of questions. It takes about an hour, it does not require expertise in the software, and it produces questions that are answerable rather than accusations that are not.
Where the owner side has no capacity for that hour, it is worth being honest that the schedule is therefore not being controlled by anybody outside the contractor, and deciding whether that is acceptable.
One further habit is worth building. Keep every update as its own file rather than replacing the previous one. A schedule folder with fourteen monthly files is a complete record of how the plan evolved, and it is the single most useful document an owner can hold if a delay argument arrives in month twenty.
An overwritten schedule folder leaves the owner arguing about a network nobody can reconstruct, against a contractor who kept every version.
The questions that come out of the five checks are worth putting in writing rather than raising in a meeting. A short monthly note listing what moved and asking three specific questions creates a dated record, gives the contractor a chance to explain before anything hardens, and takes fifteen minutes.
Most of the time the answers are good ones. The value is in the months when they are not, and in the fact that both parties then know the schedule is being read.
The cost of the habit is disk space. The cost of not having it is the whole factual basis of a position.
What we do
We set the baseline before signature and specify what the monthly update has to contain to be readable. After signature we run the five checks each month against that baseline and report what moved, what changed in the logic, and which questions are worth putting this month. The pre signature reading is the schedule and procurement risk review. Where a claim is already on the table, dispute and claims support works from the same records under the direction of your counsel.
Questions people ask
What if the contractor will not release the native file?
Ask at signature, where it is an ordinary requirement and costs nothing to agree. A refusal later is itself informative. In the meantime the three standard reports carry most of the value, and a printed longest path report with float values answers four of the five checks on its own.
Is negative float always a problem?
It means the schedule is forecasting a date later than the contract requires on that path, so it is always worth a question. It is not always alarming, because it sometimes reflects a constraint that has been imposed for planning purposes. What matters is whether the number is growing month to month.
How far back should the comparison go?
Month to month finds the changes, but a comparison to the baseline accepted at signature finds the drift. Both are worth running. The monthly comparison catches relogicking as it happens and the baseline comparison shows how far the plan has moved from the one the price was built on.
This is general information about construction contracts and is not legal advice.