Design coordination is the process of aligning the work of different design disciplines, architecture, structural, civil, mechanical, electrical, and plumbing, during the design phase itself, before the documents ever go out for construction. It’s the design-phase counterpart to BIM coordination, which happens closer to and during construction, though the line between the two has blurred as more projects run coordinated BIM models from schematic design onward rather than waiting until construction documents.
Traditionally, design coordination happened through a combination of periodic drawing exchanges and design team meetings, where each discipline’s lead reviewed the others’ progress drawings for obvious conflicts. That process still exists on plenty of projects, but it’s slower and more prone to missed conflicts than model-based coordination, mainly because reviewing static 2D drawings for spatial conflicts asks a person to mentally overlay information that software can overlay automatically and far more reliably.
The stakes of design coordination compound as a project moves forward. A structural grid decision made early affects mechanical routing options, which affects ceiling heights, which affects the architectural interior elevations, which affects finish selections, and unwinding a bad early decision after downstream disciplines have built on top of it gets progressively more disruptive the later it’s caught, in a way that mirrors how design changes generally get more expensive the further along a project gets.
Design coordination and constructability review overlap but aren’t identical. Design coordination asks whether the disciplines agree with each other. Constructability review asks whether what they agree on can actually be built. A design can be perfectly internally coordinated, with every discipline’s drawings consistent with every other, and still be difficult or impossible to construct as drawn, which is exactly why both checks matter and neither substitutes for the other.
Timing the handoff between design coordination and construction-phase coordination is a judgment call in itself. Some teams run a hard cutover, treating design coordination as finished once construction documents are issued and construction-phase coordination as an entirely separate process. Others run the two as a continuous activity, with the same coordination model and process carried forward from schematic design through construction without an artificial break, an approach that tends to catch more issues, since it doesn’t create an arbitrary boundary where accumulated coordination knowledge might otherwise get lost in the handoff.
A recurring failure mode worth naming: design coordination that happens in isolated bilateral conversations, architect talks to structural, structural talks to mechanical, without anyone ever getting all three in the same room simultaneously. Issues that only become visible when information from three or more disciplines overlaps can slip through entirely under that kind of pairwise coordination pattern, even when each conversation went well.
