How Coordination That Looked Clean On-Screen Turns Into Rework In The Field
19 August 2026
A federated model can look flawless in a coordination meeting. Every duct, pipe, and beam appears to have its own space, the walkthrough proceeds without anyone raising a hand, and the meeting ends with everyone satisfied that the design is ready to build. Then construction starts, and a duct run turns out to intersect a structural beam that nobody flagged, or a shaft sized during preliminary design proves too small once every system is actually routed through it. The screen said one thing. The field says another.
That gap traces back to what the coordination process was actually verifying, and how thoroughly, rather than any inherent unreliability in the software itself.
Why design inefficiency keeps showing up as a central driver, not a peripheral one
A large-scale analysis mapping cost overrun factors across decades of construction research found design inefficiencies to be one of the most centrally connected factors in the entire network, trailing only planning and scheduling issues and project estimation problems in overall influence. The study’s distinct contribution was showing that design inefficiency rarely operates in isolation. It was closely linked with a lack of communication and with poor coordination and cooperation between parties, factors that frequently co-occurred with design inefficiency across the studies reviewed. When researchers traced why design flaws made it past review and into construction, communication and coordination breakdowns were consistently part of the same pattern, not a separate issue.
Owners and design teams evaluating what genuine BIM coordination requires are, in effect, asking how to close that specific gap between models that have been merged into the same viewer and models that have actually been checked against each other with a shared, disciplined process behind them.
What coordination standards are actually built to catch
The national framework governing how BIM is planned and executed in the United States is explicit about what coordination requires: a defined process for identifying BIM requirements, developing a documented execution plan, and specifying exactly how information will be exchanged between every party working on a project. The standard’s own framing is that structured information management is essential for successfully delivering built assets, not an optional add-on layered over an already-designed project.
That framing matters because it implies coordination is a planning discipline, not a single review step. A federated model that looks clean because every discipline dropped their files into the same viewer without a defined execution plan governing how those models were built, at what level of detail, and against what shared coordinate system, has been merged rather than genuinely coordinated. The distinction sounds semantic until a clash surfaces that nobody caught because two disciplines were modeling to different levels of development or working from outdated shared coordinates, an error that no amount of visual inspection in a coordination meeting reliably catches.
This is part of why the national framework places so much emphasis on defining requirements and execution planning before information exchange even begins, rather than treating coordination as something to be verified only once models are already built. A plan that specifies expected levels of development, shared reference points, and information exchange formats up front gives a clash detection process something meaningful to check models against. Without that groundwork, the same software can run and return a clean report simply because the inputs were never rigorous enough to expose the conflicts that actually exist.
What happens when the design phase misses what it was supposed to catch
A case study analyzing a real school project, originally designed as ten two-story buildings with two ultimately constructed, converted the architectural and construction drawings independently from 2D into 3D models and ran them through clash detection software as a check against what had already been designed and priced. The findings were not subtle. Multiple design flaws surfaced that required correction before construction could proceed, and when the actual costs were compared against the estimated costs for each building, actual spending exceeded the estimate by approximately 25 percent, driven specifically by design errors that had not been caught before pricing and construction began. A closer look at individual line items in the bill of quantities found that specific items ran roughly 10 percent over their estimated values once the clash-related design flaws were factored in.
Case study research on a real school construction project found that total costs exceeded estimated costs by approximately 25 percent per building due to design errors that clash detection later revealed, with individual bill-of-quantity items running roughly 10 percent over their estimated values once those design flaws were accounted for.
That 25 percent gap is the practical translation of a design that looked complete on screen but had not actually been checked against the full set of disciplines and systems it needed to be checked against. Nothing about the drawings looked wrong to the people reviewing them. The clash detection process, run independently and after the fact, is what surfaced the actual state of coordination.
What actually closes the gap between the screen and the field
None of this means clash detection software is unreliable or that BIM coordination doesn’t work. The software only catches what the underlying process feeds it, and a poorly structured execution plan, an inconsistent level of detail across disciplines, or a breakdown in communication between the teams building each model will produce a federated view that looks clean without actually being coordinated. A few practical implications follow:
- A documented execution plan matters more than the software running the check. Clash detection tools can only flag what the models actually contain; if disciplines are modeling to inconsistent levels of detail or against different reference points, a clean-looking clash report can still miss real conflicts.
- Design inefficiency rarely travels alone. Because it is so tightly linked to communication and coordination breakdowns in the research, treating a design flaw as a one-off modeling mistake, rather than as a symptom of how teams were coordinating, tends to leave the underlying cause unaddressed for the next phase.
- A clean coordination meeting is not the same as a verified model. The school project case study shows that clash detection run independently, after design was already priced, found flaws the design review process had missed entirely, meaning the visual walkthrough alone was not sufficient verification.
- The cost of catching a clash late compounds quickly. A 25 percent cost overrun tied specifically to design errors illustrates how much cheaper it is to catch a coordination failure before pricing and construction than to discover it once trades are already in the field.
- Shared coordinates and levels of development deserve as much scrutiny as the clash report itself. Two models can appear perfectly aligned in a viewer while actually referencing different baselines, a mismatch that only becomes obvious once fabrication or installation begins in the field.
The gap between a coordinated-looking model and a genuinely coordinated design is rarely visible in the room where the model is reviewed. It shows up later, when a crew in the field runs into a conflict nobody flagged, at a point in the schedule where the fix costs far more than it would have during design. Treating coordination as a documented, disciplined process rather than a single successful-looking meeting is what keeps that gap from opening in the first place.
Comments on this guide to How Coordination That Looked Clean On-Screen Turns Into Rework In The Field article are welcome
Architecture Design
Contemporary Building Designs – recent architectural selection from e-architect below:
Property Design
Contemporary Property Designs – recent architectural selection from e-architect below:
Comments / photos for the How Coordination That Looked Clean On-Screen Turns Into Rework In The Field information page welcome.
