Four tests, in this order: the long lead items, the owner decisions, the float, and the sequence at enclosure. Learning how to review a construction schedule is mostly learning that the completion date is an output, and the inputs are where the answer lives.
How to review a construction schedule without being a scheduler
A construction schedule is a model. It takes activities, durations and dependencies, and produces a date. Arguing with the date is pointless. The date is arithmetic. The inputs are where judgment belongs, and the inputs are readable by anybody willing to open four documents at once.
You are not checking whether the logic is technically correct. A scheduler can do that and will find things. You are checking whether the assumptions behind the activities match what is actually true on your project today.
Those are different questions, and the second one is the one that decides whether the date holds.
Tests one and two: procurement, and your own decisions
The long lead items
Every job has equipment with a lead time measured in months. Switchgear, generators, elevators, air handling units, curtain wall, chillers. Each has an order date implied by the schedule, and that date is usually earlier than anybody expects.
Take the five longest lead items. For each one, find the date the schedule assumes it arrives, subtract the quoted lead time, and you have the date it must be ordered. Then ask whether it has been ordered.
An item that must be ordered in week six, on a job currently in week eleven, has already moved the completion date. The schedule may not show it yet, because a schedule shows what was planned until somebody updates it.
This test takes an afternoon and finds more than any other single check.
Do it with the procurement log open beside the schedule. The log holds the quoted lead times and the actual purchase order dates. The schedule holds the assumed delivery. Where those two disagree by more than a couple of weeks, the completion date has already moved and nobody has said so yet.
The owner decisions on the critical path
Schedules contain activities the owner performs. Finish selections, equipment approvals, sign-off on mock-ups, permit responses. They are frequently shown with short durations and no float, because the person building the schedule had no reason to assume the owner would be slow.
Find every activity assigned to the owner. Check the duration allowed and whether that duration is realistic for your approval process. A two week allowance for a decision that needs a board vote is not a schedule, it is a wish.
Then check whether those decisions sit on the critical path. If they do, the completion date depends on your internal speed, and any slip is attributable to you rather than to the contractor.
That attribution matters more than it looks. A delay caused by the owner usually converts into a time extension and sometimes into a cost claim for extended general conditions. A delay caused by the contractor usually does not. The schedule is where that liability is quietly assigned, months before anybody is late.
Test three: where the float sits, and test four: enclosure
Float is the slack between when an activity could finish and when it must. Total float on the critical path is zero by definition. What matters is how much sits elsewhere, and whether the contract says who may use it.
A schedule with generous float distributed across many paths is resilient. One with float concentrated in a single non-critical chain is a schedule with one buffer and many ways to lose it.
Enclosure is the fourth test because it is where most jobs actually slip, and because it is the point at which schedule risk and scope gaps between trade packages stop being separate problems. Everything interior depends on the building being weathertight. Find the enclosure date, then check what has to happen before it: structure complete, curtain wall delivered, roof installed. Those three have to line up, and they depend on the long lead answers from test one. The schedule and procurement risk review runs all four tests against the documents rather than against the narrative.
What a schedule will not tell you
Three things sit outside the model and none of them appear as an activity.
Whether the durations were estimated or negotiated. A duration can be what the trade said it needs, or what the completion date required working backwards. Both produce a valid looking bar. Only one of them is a plan. The tell is a sequence of suspiciously round durations on trades that rarely behave roundly.
Whether the trades have seen it. A schedule produced by the general contractor and never circulated to the people who have to execute it is a proposal, not a commitment. Ask when each major trade last reviewed their own durations, and whether any of them objected.
What happens when it slips. The remedy sits in the contract, not the schedule. Liquidated damages, a recovery obligation, a right to accelerate, or nothing at all. A date with no remedy behind it is a forecast, and forecasts move.
These three are questions for people rather than documents, which is why they are usually the last ones asked and the first ones that would have helped.
A worked example
Illustrative figures. Not taken from any client project and not a quotation.
A schedule shows substantial completion in twenty two months. The switchgear has a quoted lead time of thirty eight weeks and the schedule needs it energized in month fifteen.
Thirty eight weeks before month fifteen is month six. The project is in month eight and the order has not been placed, because the electrical package is still being bought out.
That is a minimum two month slip to energization, and energization gates commissioning, which gates substantial completion. The published date has already moved and the schedule has not been updated to say so.
Meanwhile four owner decisions sit on the critical path with ten working days allowed for each. The owner approval process runs through a monthly committee. Ten working days is achievable only if every decision lands in the right week of the month.
Neither finding requires scheduling software. Both require somebody to open the procurement log and the schedule at the same time.
What to ask for before you sign
- The procurement log, with quoted lead times and actual order dates for every long lead item.
- A list of every schedule activity assigned to the owner, with the duration allowed.
- The float report, showing where slack sits and how much.
- A written statement of who may consume float, and under what conditions.
- The enclosure sequence, and what each step depends on.
- The milestones you want written into the contract, with the remedy attached to each.
Ask for these before signature. Afterwards they are still useful, but the moment to fix what they reveal has passed. Schedule and procurement covers the rest of this ground.
What we do
We read the schedule against the procurement log and the contract, and write down where the date depends on something that has not happened yet. Every finding names the activity, the document and the number of weeks at stake. It is a commercial reading rather than a scheduling exercise, which is why it takes days rather than weeks.
Questions people ask
Do I need a scheduling consultant to check a completion date?
For a forensic delay analysis, yes. For the question of whether the date is achievable before you sign, no. Four readings find most of it: long lead order dates, owner decisions on the critical path, where the float sits, and the enclosure sequence. All four use documents you already have.
What is a reasonable amount of float on a construction schedule?
There is no standard figure, and a number quoted without seeing the job is not worth much. What matters more is where float sits and who may use it. A schedule with slack spread across several paths behaves very differently from one carrying the same total in a single chain.
Who owns float on a construction project?
It depends entirely on the contract, and many contracts do not say. Where the agreement is silent, float in practice belongs to whoever consumes it first, which is usually not the owner. This is worth settling in writing before signature rather than arguing about it in month fourteen.
This is general information about construction contracts and is not legal advice.