June 12, 2026

What developers get wrong about construction schedules

Every project has a schedule. Fewer projects have a real one. The difference isn’t software or formatting — it’s whether the schedule is a working model of how the building actually gets built, or a drawing of a date somebody needed to hear.

We’ve built schedules from the contractor’s side and interrogated them from the owner’s side on more than $3 billion of work. Here’s what separates the two kinds — and how owners, who rarely open the scheduling software themselves, can still tell which one they’ve been handed.

The tells of a decorative schedule

You don’t need scheduling software to spot these; you need an afternoon and a skeptical eye.

No logic links. Bars that float independently, so slipping one doesn’t move the others — which is not how buildings work. Ask to see the schedule with logic displayed. If the answer is evasive, that’s the answer.

Procurement absent. As if switchgear, elevators, curtain wall and air handlers arrive by wishing. A real schedule maps long-lead items from shop drawing to delivery, because on most urban projects the gear — not the concrete — sets the pace.

Zero float anywhere. Meaning every single activity must go perfectly for the date to hold. That’s not confidence; it’s a schedule that has already failed and doesn’t know it yet.

Approval cycles missing. Shop drawings, inspections, permits, your own sign-offs — the quiet two-week loops that consume months in aggregate. Their absence means the schedule models a project with no paperwork, which has never existed.

Weather that never happens. A Canadian schedule with no winter logic was written for a different country.

Where the time actually goes

Owners watch the site, because the site is visible. But projects are usually lost off-site: the equipment released eight weeks late, the shop-drawing cycle that took three rounds instead of one, the permit that sat in a queue, the decision that waited on a meeting that waited on a calendar.

By the time delay is visible in the field — trades demobilizing, floors sitting idle — it’s old news. The damage happened upstream, quietly, weeks earlier. A schedule’s real job is to make upstream slippage visible while it’s still upstream, which is why procurement and approvals belong on it with the same prominence as concrete pours.

The most preventable species of upstream delay is your own: owner decisions are activities too, and they belong on the schedule with dates and owners attached.

What we require from a contractor’s schedule

When we review schedules for owners as part of representation, the checklist is consistent:

• Followable logic — we can trace the critical path and question it
• Procurement mapped — every long-lead package from release to delivery, with float shown
• Owner obligations shown — our client’s decisions, approvals and vendor deliveries, so nobody’s surprises are hiding in ours
• Float visible and honestly owned — including who owns it, which the contract should say
• Honest monthly updates — actuals against plan, not a fresh optimistic redraw that resets history every month

That last one is the big tell over time. A schedule that gets re-baselined every month isn’t a model; it’s a public-relations document with dates on it.

The monthly question that keeps schedules honest

Not “are we on schedule?” — that invites yes, and yes teaches you nothing. Ask instead:

“What’s the driving path to completion right now, and what changed on it since last month?”

A team running a real schedule answers specifically: the path runs through switchgear delivery, it moved nine days because the shop drawings bounced, here’s the recovery plan and here’s what it costs. A team running a decorative one gives you weather and adjectives.

Specific bad news is a healthy project. Vague good news is not.

When the schedule slips anyway

Some slippage is real life. What matters is the response discipline: recovery plans priced before they’re approved (acceleration costs money — decide deliberately whether the date is worth it), relief claims documented against the contract’s notice provisions, and the change log and schedule reconciled monthly so time and money tell one story instead of two. The contract’s schedule provisions decide most of this — which is why they’re worth reading before signing, not after slipping.

Frequently asked questions

What scheduling software should my contractor use?

Whichever they actually maintain. A living schedule in modest software beats an abandoned masterpiece in enterprise software every time. Judge the update discipline, not the licence.

What’s a reasonable schedule contingency?

Like cost contingency, it depends on stage and risk — but a schedule with literally zero float is either padded activity-by-activity (dishonest) or genuinely fragile (worse). Ask where the float lives. Someone should be able to point to it.

Can an owner’s rep really move a schedule?

Not by pushing the site — by clearing the path: decisions on time, submittals turned fast, procurement released deliberately, claims resolved before they fester. Most schedule recovery we’ve delivered came from the owner’s side of the ledger, which is the side nobody was watching. That’s the job.