BIM Clash Detection: How to Prevent Costly Construction Errors
A $100M construction project can save $10 million by resolving clashes in the model before breaking ground — but only if the process is done right. Clash detection is the most widely used VDC workflow and the most misunderstood. Learn how experienced teams triage, assign, and close out clashes before they become field problems.
Clash detection, the process of finding geometric conflicts between different building systems in a federated BIM model, is often the first VDC workflow a project adopts. It is also the most frequently done wrong.
What Is a Clash?
In Navisworks or Revizto, a "clash" is any intersection or unacceptable proximity between two objects in the model. A structural beam running through a duct is a hard clash. A conduit running into the insulation of a pipe by 1/4" is a soft clash.
Not all clashes are created equal. A first-run detection on a $50M project might generate 1,000+ clashes. Most are duplicates, irrelevant, or already coordinated. The VDC coordinator's job is to triage that list down to the 50–100 that actually require decisions.
The 5-Step Clash Review Process
- 1Federation All discipline models (structural, mechanical, electrical, plumbing, fire protection) are linked into a single federated model in Navisworks.
- 2Clash Tests Discipline pairs are tested against each other. Running all disciplines against all others creates noise be selective. Focus on structural vs. MEP first, then MEP vs. MEP.
- 3Grouping and Triage Clashes are grouped by location, trade, or issue type. Duplicates are merged. Irrelevant clashes (pipes clashing with walls) are filtered out.
- 4Assignment Each clash group is assigned to the responsible trade with a clear question: who owns this, and who moves?
- 5Resolution and Re-test Trades update their models, new models are loaded, the clash test reruns. The goal is not zero clashes it is zero unresolved clashes.
"A clash report is a communication tool, not an outcome. The outcome is a coordinated, buildable model."
Common Clash Detection Mistakes
Generating clashes without a triage protocol. Dumping 1,200 clashes into issues and assigning it to subcontractors does not result in coordination. It results in ignored issues and the same clashes showing up in every meeting for three months.
Testing too early. Running clash detection on design-development models (LOD 200) is mostly noise. Wait until models are at LOD 300+ before running coordination-level tests. Starting too early burns the team's attention on issues that will be resolved in the next design revision anyway.
Other common failures:
- No status tracking (new / in progress / resolved / not an issue) without it, the same clashes get re-discussed in every meeting
- No assigned owner every clash needs a trade responsible for resolution
- Treating clash count as a success metric a lower clash count means better modeling, not better coordination
LOD Requirements for Coordination
The models must be at the right level before clash detection produces meaningful results:
- LOD 200: Good for early spatial planning. Too approximate for coordination.
- LOD 300: The minimum for coordination-level clash detection. All major systems with accurate size, elevation, and routing.
- LOD 350: Includes hangers, supports, and sleeves. Required for prefabrication coordination.
Include LOD requirements by phase in your BIM Execution Plan. If a subcontractor submits an LOD 200 model for a LOD 300 coordination review, send it back. Coordinating approximate geometry wastes everyone's time.
The EZ-VDC Approach
Our clash management workflow is built around the principle that every coordination meeting moves issues forward not just identifies them. We use EZ Clash Manager, our own Navisworks plug-in, to streamline clash assignment, status tracking, and coordination report generation, cutting meeting prep time significantly and keeping all stakeholders aligned.
On our projects, we run weekly coordination cycles: model deadline Monday, clash detection Tuesday, meeting Thursday, updated models by Friday. That cadence keeps every trade accountable and prevents coordination from falling behind the construction schedule.
The ROI of BIM Clash Detection: What the Data Shows
Clash detection is not just a quality tool — it is one of the highest-ROI investments in construction preconstruction.
A widely cited case study published by the Design-Build Institute of America (DBIA) found that a $200,000 investment in BIM coordination translated into over $2.5 million in cost and time savings on a single project — a 10:1 return. On a $100 million project, case study data has documented savings of $10 million by resolving approximately 500 serious conflicts during the design stage rather than in the field.
A 2020 cost-benefit analysis published in *Construction Management and Economics* confirmed a positive net present value (NPV) and benefit-cost ratio (BCR) greater than 1 across the studied projects, with ROI estimates across ten projects ranging from 140% to 39,900% depending on project complexity and clash severity.
A clash resolved in Navisworks during preconstruction costs a fraction of the same clash discovered during MEP installation. Field rework on congested runs can cost 10–20× more than the coordination time required to prevent it.
The research is consistent: projects that run structured clash detection programs see rework costs drop from the industry average of 8–10% of contract value to under 5%. On a $50M project, that gap is $1.5–2.5 million.
Frequently Asked Questions About BIM Clash Detection
What is the difference between hard clashes and soft clashes in BIM?
A hard clash is a direct geometric intersection between two elements — a structural beam running through an HVAC duct, or a conduit penetrating a pipe. A soft clash is a clearance violation: two elements that do not intersect but are closer than the required minimum distance for maintenance access, insulation, or fire code compliance. Soft clashes are often more important to catch than hard clashes — a hard clash is obvious on site; a soft clash only becomes a problem after installation when equipment cannot be serviced or code-required clearances are missing.
How many clashes are normal on a construction project?
There is no "normal" number — it depends on project size, model LOD, and how early in design the first detection runs. A first-run test on a $50M project commonly generates 500–1,500 raw clashes. After triage and grouping, the actionable list is typically 50–150 issues that require real coordination decisions. Treating raw clash count as a performance metric is a mistake: a lower count after filtering means better model quality, not less coordination needed.
What software is used for BIM clash detection?
Autodesk Navisworks Manage is the industry-standard platform for federated model aggregation and clash detection. Revizto is increasingly common for cloud-based issue tracking and coordination — it allows real-time clash assignment and status updates across distributed teams. Other tools include Solibri Model Checker (rule-based checking beyond geometry) and Autodesk Construction Cloud (BIM Collaborate Pro) for integrated design-to-construction workflows.
When in the project schedule should clash detection begin?
Clash detection should begin no earlier than LOD 300 — when models include accurate sizes, elevations, and routing for all major systems. Running tests on LOD 200 models produces mostly noise: objects that will be repositioned in the next design iteration. The most productive coordination window is after design development is complete and before construction documents are issued — when there is still design flexibility but enough model detail to run meaningful tests. Starting clash detection after GMP is damage control, not coordination.
Stanford MS · Published Autodesk Marketplace Developer
Stanford-trained civil engineer with over a decade leading VDC on projects from $30M to $1.5B across healthcare, pharma, hospitality, and infrastructure.
Let's talk about your project.
EZ-VDC provides BIM coordination, 4D scheduling, Scan to BIM, and custom automation tools. We respond within 24 hours.
