Notes · 01

The Coordination Window

There is a window in most capital projects that the project's advisors are not watching — and it closes before anyone names it.

It opens before construction starts. It closes well before most owners realize it was ever there. Inside it sits the difference between the building you contracted for and the building you eventually take possession of.

Your architect protects design intent. Your GC protects budget. Your CM protects schedule. None of them protect this window by design. Each is structured to protect a different thing, and the coordination window falls between all of them.

What the window actually is

Coordination decisions made before installation are roughly a dollar decision. The same decisions made during installation cost ten to a hundred times that — through rework, trade conflicts, schedule impact, and the change orders that follow.

The dollar-to-hundred-dollar cost asymmetry is well understood in construction. What's less understood is that the window during which you can act on it has a duration, and there is no notice when it ends.

You aren't buying BIM. You aren't buying coordination software or modeling services. You're buying the right to change design before it's built — and that right has an expiration that doesn't announce itself.

Why no one is watching it

Each of the project's advisors is protecting something real. The architect is protecting the integrity of the design. The GC is protecting the budget. The CM is protecting the schedule. These are legitimate protections.

But none of them are structured to protect the coordination window, because the coordination window isn't a single discipline's problem. It lives at the boundary between design and installation — between what was specified and what can actually be built in the sequence and geometry the trades will encounter in the field. No single advisor owns that boundary by default.

The result is that coordination decisions migrate into the field, where they're resolved by whoever discovers them first, under time pressure, without the dimensioned evidence the engineering teams would need to respond with confidence. The window doesn't reopen.

What protected looks like

Projects where the coordination window is governed don't talk about software. They talk about predictable schedule variance, RFI counts that decrease as construction advances rather than rise, and change orders measured in single digits over a project's life. The teams make installation decisions before steel is in the air. The building they receive is the building they specified.

The difference between those projects and the ones that don't land that way is not the quality of the advisors, the technology stack, or the size of the VDC budget. It's structural: whether the coordination window has a governance layer watching it — someone with the authority to force a decision, the evidence to force it on, and the timing to force it before installation forecloses the options.

The diagnostic question

Before your next preconstruction meeting, ask your GC or CM:

“Who owns the coordination schedule, and what happens to the project if they miss it?”

If your GC or CM cannot answer that in one sentence, your window is already closing. A confident answer means coordination is governed. The absence of one is the signal.