A coordinated design can be technically correct and still leave one critical question unanswered:
Who is responsible for figuring out how it will actually be built?
We see this gap often in HVAC work. Engineering defines the system. Coordination resolves spatial conflicts. The field is expected to execute.
But somewhere between those three functions, implementation planning can become nobody’s clear responsibility.
The Field Reality?
A mechanical design may show the required duct sizes, pipe routing, equipment locations, and system performance. The coordination model may confirm that everything fits. But field execution still depends on another layer of decisions:
-
What gets installed first?
-
Where does installation start?
-
What needs to be demolished or relocated before HVAC can begin?
-
Which systems need to be installed together?
- Where are temporary openings, access paths, lifts, supports, or shutdowns required?
Those decisions are not always engineering decisions. But they cannot be left for the field to discover after fabrication and mobilization either.
The responsibility often sits between traditional scopes. The engineer is responsible for design intent and system performance. The contractor is responsible for means, methods, and execution. The coordination team is responsible for making the systems fit.
Each responsibility makes sense individually.
The problem is the space between them.
A model can be coordinated without anyone fully owning the transition from “this is where it goes” to “this is how we are going to install it.”
That is where sequencing conflicts, access problems, fabrication changes, RFIs, and rework start appearing.
The Practical Control?
Before HVAC coordination is considered complete, establish:
- Who owns the installation sequence for each major area?
- Who verifies that coordinated routing can actually be installed in that sequence?
- Who identifies predecessor work, access requirements, temporary conditions, and shutdowns?
- Who has authority to change the coordinated plan when field execution exposes a buildability problem?
The answer does not have to be the same person on every project. But it does need to be explicit.
The final Key Takeaway is
Engineering owns the design.
The field owns execution.
But implementation planning needs an owner too.
If nobody is responsible for connecting design intent, coordination, sequencing, and field conditions before installation begins, that responsibility does not disappear. It simply gets pushed downstream—to the superintendent, foreman, or crew standing in the field trying to make the coordinated plan work.
On your projects, who owns that gap between a coordinated HVAC design and an executable installation plan?
Share your thoughts, or explore our free HVAC audit to identify potential implementation risks before they escalate into field problems.
FOR FREE -> [FREE Audit]
