Most owners receive a schedule update every month, look at the completion date, and file it. That is understandable — a construction schedule can run to thousands of activities and is not designed to be read by a non-scheduler.
But the completion date is the least informative number in the document. It is the output of assumptions, and the assumptions are where the risk lives. An owner does not need to become a scheduler to interrogate them usefully.
Start With What Changed
The most valuable analysis is comparative. Do not read this month's schedule in isolation; compare it to last month's.
Specifically: which activities took longer than planned, what changed in the sequence, and what was added or removed. A contractor who reports the same completion date every month while quietly re-sequencing the work underneath is absorbing delay by compressing future activities — usually the ones at the end, which are commissioning, closeout, and training.
A completion date that never moves across many updates, on a project that has clearly experienced disruption, is not evidence of good performance. It is a prompt to ask how it is being held.
Find the Critical Path and Test Whether It Is Believable
The critical path is the chain of activities that determines the finish date. Every schedule has one, and an owner should be able to see it and follow the logic.
Two questions are worth asking every time:
Does the critical path make sense? If it runs through activities that are not intuitively the hardest part of the project — while known problem areas sit off the critical path with generous durations — the schedule may be modeling a project other than the one being built.
Has it moved? A critical path that jumps between unrelated chains month to month usually indicates a schedule that is being manipulated rather than maintained.
Understand Who Owns Float
Float is the slack between when an activity can start and when it must. It is a genuine asset, and disputes over who owns it are common.
The relevant question for an owner is whether the contract addresses it. Some contracts state that float is a shared project resource, some that it belongs to whoever uses it first. Where nothing is stated, a contractor may consume all available float and then claim that any subsequent owner-caused delay is compensable — even though the schedule started with weeks of slack.
Watch also for negative float, which means activities are already behind the logic required to finish on time. Negative float appearing in an update is a signal that should generate a conversation, not a filing.
Check Your Own Obligations
Schedules contain owner obligations: decisions, approvals, submittals, owner-furnished equipment, access dates, and consultant deliverables.
These are frequently the activities with the least realistic durations, because the contractor built them optimistically. An owner should extract their own obligations from every update and confirm they are achievable — a three-day approval duration for a decision that requires a board vote is a delay that has already been scheduled.
This is also the most common source of owner-caused delay, and it is entirely preventable. An owner who tracks their own dates is an owner who does not fund the resulting claim.
Watch the End of the Schedule
Commissioning, testing, punch list, training, and closeout sit at the end of the schedule, which is where accumulated delay gets absorbed.
Compare the duration allotted to these activities across successive updates. If a project that once allowed eight weeks for commissioning now allows three, the schedule has not solved a problem — it has relocated it to the phase that determines whether the building actually works on day one. Commissioning compression is one of the most reliable predictors of a difficult first year.
Signals Worth Escalating
- Activity durations that are suspiciously uniform, suggesting placeholder rather than planned durations
- Very long activities that hide progress inside them
- Missing logic links, letting activities float free of their real dependencies
- Progress reported as percent complete with no corresponding physical verification
- Frequent changes to the baseline itself rather than to the current schedule
None of these prove bad faith. All of them mean the schedule is currently less reliable than it appears, which is the thing an owner most needs to know.
What to Require in the Contract
Much of this is easier if it was required at award: a baseline schedule submitted and accepted before major work begins, monthly updates in native file format rather than as a printed image, a narrative explaining changes, and a defined process for requesting time extensions.
Requiring the native file matters more than it sounds. A PDF cannot be interrogated; a schedule file can. Owners who cannot analyze the schedule are dependent on the summary they are given, which is precisely the dependency owner-side representation exists to remove.
