July 15, 2026

The quiet cost of slow decisions

Ask an owner what delayed their project and you’ll hear about the contractor, the weather, the permits. Ask the site team, quietly, and you’ll often hear something more awkward: they were waiting on an answer.

Owner decisions are activities. They sit on the critical path exactly like concrete and steel — and unlike concrete and steel, they’re entirely within your control. On the projects we’ve delivered and rescued, decision speed is the single most underrated variable in schedule performance, and the cheapest one to fix.

Why decisions stall

Almost never because someone is lazy. Decisions stall for structural reasons:

They arrive unframed. A forwarded email chain with no options, no costs and no deadline isn’t a decision request — it’s homework. The person receiving it does the rational thing: sets it aside until it’s clearer, which is never.

Nobody saw them coming. The decision-maker is hearing about the issue for the first time on the day it’s urgent. Without a forward view of what’s coming, every decision is an ambush, and ambushed people defer.

The approval path doesn’t match the project’s pace. A committee that meets monthly governing a project that moves daily has a built-in four-week lag on everything it touches. Nobody decided that; the org chart did.

Deferral feels safe. Saying “let me think about it” feels prudent. On a live project it isn’t neutral — it has a meter running, invisible to the person deferring and vivid to the crew resequencing around the silence.

What a stalled decision actually costs

The costs are real, compounding, and mostly invisible at the moment of deferral:

• Productivity. A crew resequenced around a missing answer works out of order and out of rhythm. You pay for that inefficiency in the next progress claim, unlabelled.
• Expired pricing. Supplier quotes have shelf lives. The answer that took six weeks gets repriced into the market that exists six weeks later.
• Rework. The answer that arrives after adjacent work is in place turns into demolition plus construction. The most expensive way to build anything is twice.
• Claims. Owner-caused delay is the contractor’s cleanest claim, and the contract’s schedule provisions decide how expensive it gets.
• Culture. A pattern of slow answers teaches the contractor’s team that your dates are soft. That lesson quietly infects every other date on the job, including theirs.

The decision log: boring and transformative

Every project we run gets a decision log, managed with the same seriousness as the change log. The mechanics are simple:

Every open decision gets an entry — what’s being decided, who owns it, and a required-by date pulled from the construction schedule, not from politeness. Each entry arrives framed: the question, the options, the cost and schedule impact of each, and a recommendation. Framing is the owner’s rep’s job — decision-makers decide fast when the homework is done. The log gets a forward look at every meeting: here’s what’s coming at you in the next six weeks, so nothing arrives cold. And late decisions get named, without drama, with their consequences attached — because the meter should be visible to the person holding the pen.

The companion discipline is limiting who holds pens. Projects governed by consensus decide at the speed of their most hesitant participant. One empowered decision-maker per category — with clear escalation for the genuinely big calls — is worth weeks per year of schedule.

What it looks like when it works

Owners are consistently surprised by how much smoother a project feels when the answers keep pace with the work. Meetings shorten, because they’re forward-looking instead of forensic. The contractor’s claims file thins, because the cleanest claim category is empty. The schedule’s driving path runs through construction instead of correspondence.

Nothing about the building changed. The decisions just stopped being the slowest trade on site.

Frequently asked questions

How fast should project decisions be?

As fast as the schedule requires — which is knowable. Each decision’s required-by date comes from working backward from the activity it releases, including procurement and shop-drawing time. Some decisions genuinely need a week; almost none need a month.

What if we truly need more time on a major decision?

Then buy the time deliberately: understand what the delay costs, decide it’s worth it, and tell the contractor a real date. A managed delay is a decision. An open-ended one is a claim in progress.

Can’t the contractor just work around missing answers?

They will — that’s the problem. Workarounds mean resequencing, and resequencing means inefficiency you’ll pay for without ever seeing it itemized. The cheap version is the answer, on time.

If your project’s meetings have started sounding like a list of things waiting on someone — that’s fixable in a month, and the schedule will show it.