BIM clash detection catches conflicts between trades before they reach the field. It is not, however, a guarantee against every coordination problem.
This guide covers exactly what clash detection catches and where it falls short. It also covers how to get the most out of it.
A quick answer: BIM clash detection catches hard clashes, which are physical overlaps, and soft clashes, which are clearance violations. It misses issues outside the modeled scope, like sequencing.
What BIM Clash Detection Actually Catches
Clash detection federates models from multiple trades into one software environment. It then scans for geometric conflicts automatically.
- Hard clashes: direct physical overlaps between two elements
- Soft clashes: clearance and access violations without direct overlap
- Workflow clashes: scheduling or sequence conflicts, in advanced setups
Hard Clashes vs. Soft Clashes
Hard clashes are easy to spot visually. A duct and a structural beam occupying the same space is an obvious example.
Soft clashes are easier to miss. Equipment that technically fits but cannot be serviced once installed is a common soft clash.
How Navisworks Runs a Clash Detection Pass
Navisworks federates MEP, architectural, and structural models together. It runs automated clash tests between selected model groups.
- 1Federate MEP, architectural, and structural models
- 2Select model groups to test against each other
- 3Run the automated clash scan
- 4Review and prioritize clashes by location and severity
- 5Resolve clashes with the responsible trade and re-run the scan
Clash Detection and Level of Development
Clash results depend heavily on the model's level of development, or LOD. A low-LOD model will miss clashes a higher-LOD model would catch.
- LOD 300: sized and located for design coordination, basic clash results
- LOD 350: adds connection detail needed for reliable clash detection
- LOD 400: fabrication-level detail, most accurate clash results
Running clash detection on an LOD 300 model is still useful. It just will not catch every connection-level conflict an LOD 350 model would.
What BIM Clash Detection Misses
Clash detection only catches what is actually modeled. Elements left out of the model cannot be flagged as a conflict.
- Unmarked or undocumented existing field conditions
- Construction sequencing and access logistics
- Scope modeled at too low a level of development to show real detail
- Human error during installation that deviates from the coordinated model
This is why experienced review still matters. Software finds the conflicts, but people decide how to resolve them.
Who Should Attend a Clash Detection Review
Clash detection works best as a collaborative process, not a one-person task. Each trade's representative should review clashes affecting their scope.
- Mechanical, electrical, plumbing, and fire protection trade representatives
- The general contractor's project engineer or superintendent
- The design team, for clashes involving architectural or structural elements
Without the right people in the room, clash reports pile up unresolved. Resolution requires someone with authority to approve a routing change on the spot. Unresolved clashes simply carry forward to the next review cycle.
A clear meeting agenda helps keep clash review efficient. Prioritizing clashes by severity prevents minor issues from eating time needed for major ones.
Document every resolution decision in writing. A verbal agreement in a meeting is easy to forget by the next coordination cycle. A shared log keeps everyone aligned between meetings.
Why Clash Detection Still Reduces RFIs
Most field RFIs on MEP-heavy projects trace back to an unresolved trade conflict. Catching that conflict in the model removes the RFI before it is written.
Clash detection depends on an accurate model to begin with. See our Revit MEP modeling service for how models are built to support coordination.
How Often to Run Clash Detection
Clash detection works best as a recurring process, not a one-time check. Running it weekly or biweekly during coordination catches new conflicts as models update.
A single clash pass near the end of design often arrives too late to fix cheaply. Earlier and more frequent passes catch issues while changes are still simple.
Clash Detection on Renovation Projects
Renovation projects complicate clash detection. Existing conditions often are not fully modeled, which limits how much the software can catch.
Field scanning technology, like 3D laser scanning, can close this gap. It captures existing conditions into a model that clash detection can then test against. This extra step adds cost but prevents far costlier field surprises.
- Existing conditions may need field scanning before reliable clash detection is possible
- New MEP routing gets tested against both new design and captured existing conditions
- Renovation clash detection typically takes longer to set up than new construction
Getting the Most Out of Clash Detection
Our BIM coordination and clash detection service tracks every clash through to resolution, not just identification. See our full design and drafting services.
Frequently Asked Questions
What is the difference between a hard clash and a soft clash?
A hard clash is a direct physical overlap between two elements. A soft clash is a clearance or access violation without actual overlap.
Can BIM clash detection catch every coordination issue?
No. It only catches what is modeled. Sequencing issues and undocumented field conditions fall outside its scope.
What software is used for BIM clash detection?
Navisworks is the most common tool, federating MEP, architectural, and structural models to run automated clash scans. Other platforms offer similar federation capability.
Does clash detection replace coordination meetings?
No. Clash reports inform coordination meetings, but resolving conflicts still requires discussion between trades.
Need a coordinated model and clash detection pass? Request an estimate and get results in 24-48 hours.
Topics
