Key Takeaways
- BIM clash detection identifies hard clashes (physical overlaps), soft clashes (clearance violations), and 4D clashes (scheduling conflicts) within a coordinated model.
- The process follows a seven-step workflow: model preparation → federation → clash rule configuration → clash testing → analysis → resolution → final verification.
- Autodesk Navisworks remains the industry standard for clash testing; Revit, Solibri, and BIMcollab serve complementary coordination roles.
- Resolving a clash in the design phase typically costs 5–10 times less than fixing the same conflict on site (Construction Industry Institute).
- Every discipline - architecture, structure, MEP- carries specific clash responsibilities; the process only works when all models meet agreed LOD thresholds before federation.
What Is BIM Clash Detection?
What Does Clash Detection Mean in BIM?
Clash detection in BIM is an automated computational process that examines three-dimensional spatial relationships between building elements within a federated model to identify physical interferences, clearance violations, and scheduling conflicts.
Unlike manual 2D overlay checks, where a coordinator visually compares printed drawings hoping to catch every conflict, BIM clash detection runs geometric algorithms across every element simultaneously - and produces a timestamped, assignable report.
The term "clash" covers more than two elements physically occupying the same space. A hard clash is the obvious one: a structural beam intersects an MEP duct. But a soft clash - where a duct runs 30 mm from a beam, technically not touching but violating minimum maintenance access clearance - is equally disruptive on site. Miss it in the model, and a maintenance engineer will find it the hard way years later.
Why Is Clash Detection Important in Construction?
Rework is expensive. According to the Construction Industry Institute, rework accounts for between 5 and 12 percent of total project costs on average - on a $10 million project, that is $500,000 to $1.2 million. The majority traces back to coordination failures: systems designed to occupy the same space, clearance requirements that were never checked, or trade sequencing that was never modelled.
Resolving a clash in the digital model costs a fraction of what field resolution demands. Labor is standing still, prefabricated components may be scrapped, and one unresolved conflict can cascade through the programme, delaying every downstream trade. BIM clash detection addresses this before materials are ordered or workers step on site.
Projects using BIM-enabled coordination have reported up to 42% fewer change orders and coordination savings in the range of 24% on infrastructure work, according to reporting from Autodesk and Arkance. Those figures are not guaranteed on every project, but the direction is consistent.
Traditional methods are not obsolete everywhere a small single-trade renovation may not justify a full BIM workflow. But on any multi-discipline project above modest scale, manual overlay checks carry unacceptable risk.
How Does BIM Clash Detection Work?
BIM clash detection follows a structured coordination cycle. Each stage must be completed correctly; shortcuts at the federation stage, for instance, will contaminate every downstream clash test.
Collecting Architectural, Structural & MEP Models
Each discipline prepares its own authoring model in the agreed software platform typically Autodesk Revit for architecture and structure, with MEP modelled in Revit MEP or specialist tools. Before any model is submitted for coordination, it must reach the agreed Level of Development. A structural model submitted at LOD 200 when coordination requires LOD 350 will produce false clash-free results, because the elements are not geometrically resolved.
This is where many projects go wrong. LOD 300 confirms that an element is coordinated in terms of quantity, size, shape, and location. LOD 350 adds the interfaces and connections between systems which is the threshold needed for reliable clash detection between disciplines. If your structural engineer has modelled connections at LOD 300 and your MEP contractor has modelled at LOD 350, the test results will be unreliable.
Creating a Federated BIM Model
The federated model is an aggregated file combining all discipline models into a single coordination environment without merging or altering the native source files. Navisworks is the most common platform for this. Each discipline model is imported as a separate layer, preserving ownership, and the coordination coordinator manages the combined file.
The federated model is not a design tool. No one edits it. It is a read-only environment for clash testing and review, and any changes made to resolve clashes happen in the authoring tools.
Setting Up Clash Detection Rules
Before running a single test, the team must agree on what to test for and what to ignore. A clash between two objects in the same discipline is usually not meaningful; you want to test architecture against structure, MEP against structure, MEP against MEP systems across disciplines. Running every element against every other element produces tens of thousands of results, most of which are noise.
Clash rules also define tolerance thresholds. For hard clashes, the threshold is typically zero tolerance any intersection is reported. For soft clashes, the team must define what clearance distances matter for which systems: HVAC maintenance access, fire damper clearance, electrical conduit separation from heat sources.
Running Clash Tests
With rules set and models federated, the software runs the tests. Navisworks Manage, Solibri, or BIMcollab executes the geometry comparison and generates a results list: each clash assigned an ID, a location, the elements involved, and a severity classification.
Reviewing and Classifying Clashes
Not every flagged clash requires immediate resolution. The coordination team reviews results and classifies each clash:
- Active - a real conflict requiring resolution
- Approved - known condition, accepted by the team (e.g., a design tolerance)
- Resolved - fixed in the authoring model, awaiting verification
- Duplicate - same conflict flagged by multiple test rules
Prioritisation matters. A structural beam intersecting a main supply air duct on Level 5 blocks progress for multiple trades. A minor conduit clearance issue in a maintenance room can wait. Treating all clashes as equal urgency is one of the most common coordination failures.
Assigning and Resolving BIM Issues
Each active clash is assigned to the responsible discipline and tracked through a BIM Issue tracker - BIMcollab, Autodesk Construction Cloud (ACC), or a shared BCF file. The assignee modifies their authoring model to resolve the conflict and updates the status in the tracker. The resolution is not confirmed until the next coordination cycle verifies it in the federated model.
Rechecking the Coordinated Model
Once resolutions are implemented across authoring models, updated files are imported into the federated model and the relevant clash tests are re-run. A resolved clash that reappears in the next cycle - and this happens more often than teams expect - indicates the fix was incomplete or introduced a secondary conflict. Multiple coordination cycles are normal on complex projects.
Types of Clashes in BIM
Hard Clashes
A hard clash occurs when two or more building elements physically occupy the same three-dimensional space. A beam passing through a duct, a column intersecting a pipe run, a slab penetration that was not coordinated with structural reinforcement- these are hard clashes. They are the easiest to detect and the most visually obvious in a clash report.
Soft Clashes and Clearance Issues
Soft clashes do not involve physical overlap. Instead, an element violates a defined clearance or buffer zone around another element. A duct running within 50 mm of a beam may be geometrically clear, but maintenance access requirements mean the installation cannot function correctly.
Electrical cable trays have minimum separation requirements from heat-generating pipework. Soft clash thresholds must be defined by the discipline responsible for each clearance zone, not assumed by the coordination team.
Workflow and 4D Clashes
A 4D clash is a scheduling conflict: two elements or activities that cannot be in the same location at the same time during the construction sequence. These are not geometric conflicts - they are temporal ones.
A concrete pour scheduled before formwork is struck, or a duct installation sequenced before ceiling framing is complete, generates a 4D clash when the construction programme is linked to the 3D model. Not all projects run full 4D coordination, but on phased or fast-track projects, 4D clash detection is a genuine risk management tool.
Examples of Architectural, Structural & MEP Clashes
Common real-world clash scenarios include:
- HVAC duct vs. structural beam - the most frequently reported hard clash on commercial projects; occurs when MEP routing is not checked against the structural grid
- Sprinkler pipework vs. ceiling void - a soft clash where the finished ceiling level leaves insufficient clearance for both the sprinkler grid and light fittings
- Electrical conduit vs. plumbing stack - two services routed along the same vertical riser without separation
- Slab penetration vs. rebar layout - an MEP sleeve location that conflicts with structural reinforcement, often discovered only during rebar fixing on site
- Curtain wall system vs. floor slab edge - an architectural element that encroaches on the structural perimeter when tolerances are not modelled
BIM Clash Detection Process
Model Preparation
All discipline teams produce authoring models to the agreed LOD and coordinate system. File naming, grid references, and shared coordinates must be consistent before federation. A model with incorrect coordinate origin will register hundreds of false clashes when combined with other disciplines.
Model Federation
The BIM coordinator aggregates discipline models into the federated environment. File formats are converted as needed - Revit models export to NWC for Navisworks, IFC for Solibri. The coordinator checks for coordinate consistency before running any tests.
Clash Test Configuration
The coordination team defines test sets: which disciplines to test against which, what clearance tolerances apply to each system, and which elements to exclude from testing. Test configuration should be documented and version-controlled alongside the federated model.
Clash Identification
Tests run. The software returns a results set sorted by clash count, severity, and location. The coordination team exports the report into the agreed issue-tracking platform.
Clash Analysis and Prioritization
The team reviews every result, removes duplicates and approved conditions, and prioritises the remaining active clashes by severity and construction sequence impact. The highest-priority clashes are assigned first.
Coordination and Resolution
Responsible disciplines receive their assigned clashes with clear location data, screenshots, and a resolution deadline. Changes are made in authoring tools. Resolution is documented in the issue tracker, not by email.
Final Verification and Reporting
Updated models are re-federated. A re-run of all test sets confirms that resolutions have not introduced new clashes. The final coordination report - listing all identified clashes, their classification, assigned discipline, and resolution status - is issued to the project team. This report forms part of the project's BIM deliverables and supports the health-and-safety file.
BIM Clash Detection Software
Autodesk Navisworks
Navisworks Manage is the de facto standard for clash detection on most commercial and infrastructure projects. Its Clash Detective module allows multi-discipline federation, configurable test sets, and report export in multiple formats. It handles very large model sets without the performance issues that affect authoring tools. The NWC format, compatible with Revit, AutoCAD MEP, and most third-party platforms, makes it the most interoperable option in practice.
Autodesk Revit
Revit's built-in Interference Check tool is suitable for single-discipline or two-discipline clash checks within the Revit environment. It lacks the advanced configuration and reporting capabilities of Navisworks, but for quick checks during design development - before a formal coordination round - it serves a useful function. Many projects use Revit for in-discipline quality checks and Navisworks for the federated coordination cycle.
Solibri
Solibri Model Checker takes a rule-based approach that goes beyond geometry. It can check for model quality, regulatory compliance, and design rule violations alongside spatial clash detection. It is widely used in the Nordic market and on ISO 19650-compliant projects that require model quality assurance as a documented deliverable. Its reporting and issue-management interface is arguably more intuitive than Navisworks for non-specialist reviewers.
Other BIM Coordination Tools
BIMcollab integrates with Navisworks, Revit, and Solibri as an issue-tracking and BCF management platform rather than a clash detection engine. Trimble Connect and Autodesk Construction Cloud (ACC) serve similar coordination and review functions, particularly on projects requiring cloud-based access for distributed teams. The right toolset depends on the project's CDE (Common Data Environment) requirements and the client's BIM Execution Plan.
Benefits of BIM Clash Detection
Reducing Construction Rework
Rework is not just a cost line it is a schedule, a relationship, and a safety risk. When a duct has to be rerouted because it intersects a beam that was always in the drawing but never checked, everyone loses: the MEP subcontractor absorbs the cost, the programme slips, and the coordination team explains to the client why something was missed. BIM clash detection removes the conditions under which most of that rework originates.
Identifying Design Conflicts Before Construction
The earlier a conflict is found, the cheaper it is to fix. A conflict caught during design development costs a model edit and a meeting. The same conflict found during installation requires material removal, rescheduling, potential structural intervention, and a change order. The mathematics are not complicated.
Improving Multidisciplinary Coordination
Clash detection enforces a discipline that informal coordination often fails to maintain. When every discipline knows their model will be federated and tested, the quality of model authoring improves. Trades stop relying on others to catch their conflicts. The federated model becomes a shared reference, not a territory dispute.
Reducing Project Delays
Scheduling conflicts 4D clashes are particularly damaging on fast-track projects. A structural piling rig cannot operate in a zone where another contractor is working. A curtain wall installation cannot proceed before the floor slab is poured to the correct level. Identifying these conflicts in programme planning, before they become on-site standoffs, directly reduces programme risk.
Improving Construction Documentation
A coordinated model produces coordinated drawings. Shop drawings, spool drawings, and fabrication details derived from a clash-free federated model are far less likely to carry hidden errors. The downstream quality improvement in construction documentation is a direct consequence of upstream coordination discipline.
Supporting Better Project Planning
For owners and project managers, a coordinated BIM model provides a reliable foundation for cost estimation, procurement sequencing, and handover documentation. The confidence that what is in the model represents what will be built - without hidden conflicts - changes how pre-construction planning is conducted.