A duct runs straight through a structural beam. A sprinkler line lands where a light fixture needs to go. On paper, each discipline did its job. On site, those conflicts turn into stop-work calls, change orders, and a schedule that keeps slipping.
BIM clash detection catches those conflicts in the model, weeks or months before a crew ever finds them in the field. For project managers and principals watching time, accuracy, and budget, it is one of the clearest ways to keep a project from paying for the same wall twice.
What Is BIM Clash Detection?
BIM clash detection is the process of finding conflicts in 3D building models before construction begins. Instead of waiting for trades to discover that two systems want the same space, the team runs the models against each other digitally and flags every spot where elements collide or crowd.
The work happens inside a federated model. A federated model combines the individual discipline models, architectural, structural, and MEP, into one coordinated environment. Clash detection software then analyzes that combined model and runs automated tests, producing a ledger of flagged intersections for the team to review.
For any of this to hold up, the underlying BIM models have to be built with accurate geometric dimensions and a shared coordinate system. A clash report is only as good as the models feeding it.
The Three Types of Clashes
Not every conflict is the same, and teams sort them into three groups so they can act on the ones that matter most.
Hard Clashes
A hard clash happens when two components physically intersect, like a pipe passing through a beam. These are the most direct conflicts and the easiest to detect, since the geometry plainly overlaps.
Soft Clashes
A soft clash involves insufficient clearance between components, even when they do not touch. A valve crammed against a wall may still fit, but no one can reach it later. Soft clashes can lead to maintenance problems if they go unresolved.
Workflow Clashes
A workflow clash, sometimes called a 4D clash, comes from scheduling conflicts in the construction timeline rather than the geometry. Two trades booked for the same space at the same time is a workflow clash, and left unaddressed it can halt construction activity. This is where 4D BIM matters, because it integrates construction sequencing with clash detection to catch logistical conflicts, not just physical ones.
Clash Severity Levels
A raw clash report can list thousands of hits, and not all of them deserve equal attention. Teams rank each flag by severity so they fix what actually threatens the build first.
- Critical. Conflicts that directly affect construction. These must be resolved before releasing construction packages.
- Major. Real conflicts that cause meaningful rework or cost if they reach the field.
- Minor. Small conflicts with limited impact that still get logged and resolved.
- False positive. Flags that are not genuine conflicts, often elements allowed to overlap by convention.
Prioritizing by potential impact on construction keeps the team focused on the clashes that would stop work, rather than burning hours on flags that do not matter. Performance indicators help measure whether the clash detection process is improving over the life of the project.
The Clash Test Matrix by Discipline
Testing every element against every other element produces noise. Instead, teams define which discipline models get checked against which, then run those pairings deliberately. Structural against MEP catches ducts and pipes hitting beams. MEP against MEP catches ducts, pipes, and conduit fighting for the same ceiling space. Architectural against structural catches walls and framing conflicts.
A clash test matrix lays out those pairings so coordination is systematic and nothing important goes unchecked. It also keeps the review focused, since each test run targets a specific relationship rather than the whole model at once.
Why BIM Clash Detection Matters
The payoff shows up in the three places every principal cares about. Catching conflicts in the model prevents costly rework and delays once crews are on site. Effective clash detection saves time and reduces field rework, which protects both the schedule and the budget.
The benefits reach past the balance sheet:
- It enhances collaboration between the different project teams working in one model.
- It minimizes material waste through more precise planning.
- It streamlines workflows by surfacing conflicts early instead of late.
- It improves job site safety by reducing the unexpected issues crews run into.
Put simply, a conflict solved on a screen costs a fraction of the same conflict solved after the steel is up.
How the BIM Clash Detection Process Works
Clash detection follows a repeatable sequence. The order matters, because skipping steps tends to flood the team with noise instead of answers.
- Integrate the discipline models into one federated model in a shared coordinate system.
- Run automated clash tests to highlight conflicts between elements.
- Review the clash report and prioritize issues by their impact on construction.
- Resolve each clash by modifying the relevant models and documenting the agreed solution.
- Re-run the checks and give final sign-off once the model is clash-free.
Clash detection should not be a single event. It works best as an ongoing process across the project lifecycle, with regular multidisciplinary coordination meetings to resolve what the tests turn up. A BIM Execution Plan sets the standards and workflows so every team runs the checks the same way.
Setting Tolerances
Not every overlap is a real problem. Teams set a tolerance so tiny intersections sitting inside modeling and scan noise do not flag as clashes. Because terrestrial laser scans capture existing conditions to within roughly 2 to 4 millimeters, the tolerance gets set above that noise floor, so the report shows genuine conflicts instead of measurement artifacts.
The setting is a balance. Set it too tight and the report floods with false positives. Set it too loose and real clashes slip through. Dialing in the right threshold early is part of what keeps the first clash run usable.
Controlling False Positives
A report with thousands of hits is useless if most are noise. Keeping the signal clean is a skill, and a few habits do most of the work:
- Group related clashes before review so the team reads one issue, not fifty copies of it.
- Handle unmodelled elements deliberately, since gaps in the model create phantom conflicts.
- Use spatial grouping to batch conflicts by area and review them in context.
- Exclude known conventions, the overlaps that are allowed by design.
One rule holds throughout. Never dismiss a clash silently. Every closed flag should carry a note on why it was closed, so the decision is traceable later.
What LOD Clash Detection Needs
Clash detection only means something when the models carry enough detail to represent real geometry and routing. Coordination-grade checks generally need models developed past generic LOD 200 placeholders, into the LOD 300 to 350 range where elements show accurate dimensions, routing, and clearances.
Run clash detection on under-developed models and the conflicts will not reflect what actually gets built. Matching the LOD to the coordination goal is what makes the clash report trustworthy, and it ties directly back to how the existing-conditions model was built in the first place.
Who Pays for Clash Resolution?
Clash resolution means modifying the relevant models and documenting the agreed solution, and that work takes real hours. Who carries that cost should be settled before coordination starts, not argued over mid-project. A BIM Execution Plan is the place to define the standards, workflows, and responsibilities, so each team knows which fixes it owns and the resolution work moves instead of stalling.
Common Clash Detection Software
Most teams rely on a small set of tools, each with a role:
- Navisworks automates clash detection and generates clear reports across a federated model.
- Revit handles early-stage clash checks during design, before models leave the authoring stage.
- Solibri checks for clashes alongside broader design quality in complex projects.
Automatic clash detection can also run in the cloud for real-time results, so distributed teams see the same conflicts at the same time. The software finds the clashes, but people still decide how to resolve them.
Where Scan to BIM Fits In
Clash detection assumes the model reflects reality. On renovation and retrofit work, that assumption breaks the moment someone trusts an outdated drawing. This is where reality capture earns its place.
A 3D laser scan captures existing conditions to within roughly 2 to 4 millimeters, and point cloud to BIM turns that scan into an accurate as-built model. When the existing-conditions model is built from a point cloud instead of guesswork, clash detection runs against what is really in the building. New ductwork gets checked against the beam that is actually there, not the one the old plans show.
That link between accurate as-built data and dependable coordination is the core of 3DVDT’s BIM coordination and clash detection work.
Best Practices for Reliable Clash Detection
A few habits separate a clean coordination process from a noisy one. Build the discipline models to accurate dimensions and a common coordinate system from the start. Set sensible tolerances and group results before review so the team reads real conflicts. Document every resolution so the fix is traceable. And treat coordination as a standing rhythm, with scheduled meetings, rather than a one-time pass near the deadline.
BIM Clash Detection FAQs
What is the difference between a hard clash and a soft clash?
A hard clash is a physical intersection of two components. A soft clash is a clearance or access problem where components sit too close even though they do not touch.
When should clash detection start?
Early, and often. Running checks in design with a tool like Revit catches conflicts before they reach coordination, and repeating the checks through the project lifecycle keeps new conflicts from slipping through.
What is a federated model?
It is a single coordinated model that combines the separate architectural, structural, and MEP models so clash tests can run across all disciplines at once.
How many clashes are normal on a first run?
A fresh federated model can surface thousands of flags, but many are duplicates or false positives. The number that matters is how many critical clashes remain after grouping, filtering, and prioritizing by impact.
Can clash detection run in the cloud?
Yes. Automatic clash detection can be cloud-based for real-time results, so distributed teams work from the same set of flags.
How does scanning improve clash detection on renovations?
Scanning produces an accurate as-built model of the existing building, so clash detection checks new designs against real conditions instead of outdated drawings.
How 3DVDT Can Help
3DVDT builds the accurate existing-conditions models that make clash detection worth trusting. We capture the site with 3D laser scanning, convert the point cloud into a coordinated BIM model, and run clash detection across the architectural, structural, and MEP models to catch conflicts before they reach the field. Since 2012, we have supported architects, engineers, and contractors across San Francisco, Napa, and the greater Bay Area.
To scope BIM coordination and clash detection for your next project, call us at (415) 543-4202 or request a project quote and tell us what you are building.
