BIM Clash Detection: How to Catch Conflicts Before They Cost You on the Jobsite

Every contractor has a story about the time a plumber and an electrician showed up to the same ceiling space and realized their runs were designed to occupy the same 12 inches. The plumber blames the electrician. The electrician blames the engineer. The GC burns a day of schedule and $5,000 in labor figuring out who moves what.

This is the problem that BIM clash detection solves. And if you are not using it on your commercial projects, you are leaving money on the table and gambling with your schedule every single day.

This guide explains what BIM clash detection is, how it works in practice, what software and processes you need, and how to set up an effective clash detection workflow on your projects.

The Real Cost of Field Conflicts

Before diving into the technical side, let’s talk about why this matters in dollars.

A study by the Construction Industry Institute found that rework costs between 5 and 12 percent of total project costs on average. On a $10 million project, that is $500,000 to $1.2 million. And the majority of rework traces back to coordination failures: systems designed to occupy the same space, clearance requirements that were not accounted for, or sequencing conflicts between trades.

Field resolution of a clash typically costs 5 to 10 times more than resolving it in the model. Here is why:

• Labor costs: A crew standing around waiting for a resolution burns money every minute
• Material waste: Prefabricated ductwork, piping, or conduit that does not fit gets scrapped or reworked
• Schedule impact: One conflict can cascade through the schedule, delaying other trades and pushing back milestones
• Change orders: Rerouting systems often requires design changes, engineer review, and additional materials

Catching these conflicts in a digital model before anyone picks up a wrench changes the math entirely. A BIM coordinator spending 4 hours resolving a clash on screen prevents a field crew from spending 2 days and $8,000 resolving it with pipe cutters and new hangers.

What Is BIM Clash Detection?

BIM (Building Information Modeling) clash detection is the process of combining 3D models from multiple design disciplines and checking them for physical conflicts using specialized software.

Here is how it works at a high level:

1. Each trade (structural, mechanical, electrical, plumbing, fire protection) creates a 3D model of their scope
2. These models are combined into a single federated model
3. Software runs automated interference checks between selected systems
4. The software flags every location where two objects occupy the same space or violate clearance rules
5. Teams review the clashes, assign responsibility, and resolve them by modifying the models
6. The process repeats until conflicts are reduced to an acceptable level

The key insight is that resolving conflicts in a model is cheap. Moving lines on a screen takes minutes. Moving installed ductwork takes days.

Types of Clashes

Not all clashes are created equal. Understanding the three main types helps you prioritize resolution efforts.

Hard Clashes

A hard clash occurs when two physical objects occupy the same space. A pipe passing through a beam. A duct running through a column. An electrical panel mounted where a window is specified. These are the most straightforward to identify and the most critical to resolve.

Soft Clashes (Clearance Conflicts)

A soft clash occurs when two objects are too close together, even if they do not physically overlap. Examples include:

• A valve that has no access space for maintenance
• Ductwork installed too close to a sprinkler head, violating code clearances
• Electrical panels without required working clearance per NEC 110.26
• Insulated pipes too close to other services, leaving no room for insulation

Soft clashes require defining clearance zones around objects, which adds complexity to the clash detection setup but catches problems that hard clash detection misses.

Workflow (4D) Clashes

These are scheduling conflicts rather than spatial ones. Two trades need access to the same area during the same time period. A concrete pour is scheduled in a space where the mechanical contractor has not finished their rough-in. Drywall is going up before the fire protection inspection.

Workflow clashes require integrating the 3D model with the project schedule (creating a 4D model). This is more advanced than spatial clash detection but incredibly valuable on complex projects with tight timelines.

The Clash Detection Process Step by Step

Here is what an effective clash detection workflow looks like on a real project:

Step 1: Establish the BIM Execution Plan

Before anyone starts modeling, the team needs to agree on standards. The BIM Execution Plan (BEP or BXP) defines:

• Which trades will produce models and at what level of detail
• File formats and naming conventions
• Model origin point and coordinate system (critical for alignment)
• Clash detection schedule and meeting cadence
• Roles and responsibilities (who runs clashes, who resolves them, who approves)

Do not skip this step. Without a BEP, you end up with models that do not align, inconsistent levels of detail, and confusion about who owns what. Invest a day in preconstruction to save weeks in the field.

Step 2: Collect and Federate Models

Each discipline produces their model in their native software (Revit for architects and engineers, Fabrication CADmep for mechanical, AutoCAD MEP for electrical, etc.) and exports it in a common format, typically NWC (Navisworks Cache) or IFC (Industry Foundation Classes).

The BIM coordinator imports all models into the clash detection software, aligning them to the agreed-upon origin point. This combined model is called the federated model. It should represent every system in the building at the current state of design.

Step 3: Configure and Run Clash Tests

The BIM coordinator sets up clash tests between relevant system pairs:

• Structure vs. Mechanical
• Structure vs. Electrical
• Structure vs. Plumbing
• Mechanical vs. Electrical
• Mechanical vs. Plumbing
• Mechanical vs. Fire Protection
• Electrical vs. Plumbing
• Electrical vs. Fire Protection
• And so on for every relevant combination

Each test can be configured with tolerances (ignore clashes smaller than half an inch, for example) and clearance zones (require 6 inches around sprinkler heads, 36 inches in front of electrical panels, etc.).

The first run will produce a lot of results. On a 100,000 square foot commercial building, it is normal to see 2,000 to 5,000 clashes in the first round. Do not panic. Many of these will be duplicates, minor issues, or false positives.

Step 4: Review, Group, and Assign

This is where the BIM coordinator earns their paycheck. They review the raw clash results and:

• Group related clashes so a single conflict that generates 20 individual clash points gets treated as one issue
• Filter out noise like clashes between a pipe and its own insulation, or between a duct and the hangers that support it
• Assign responsibility to the trade that needs to move their system (based on coordination priority rules)
• Set severity levels to focus attention on critical conflicts first

The cleaned-up clash report gets distributed to all trades before the coordination meeting.

Step 5: Coordination Meetings

Regular coordination meetings (usually weekly or biweekly during the MEP coordination phase) bring all trades together to review and resolve clashes. The BIM coordinator displays the federated model on a large screen and walks through each clash group.

The goal is to reach agreement on who moves what. Decisions get documented, models get updated, and the next round of clash detection verifies that resolutions worked and did not create new conflicts.

Effective coordination meetings require:

• A skilled facilitator who understands all the systems and can mediate disagreements
• Decision-makers in the room from each trade, not just CAD operators
• Clear documentation of every decision, including sketches and model markups
• Accountability for model updates between meetings

Step 6: Iterate Until Clean

The process repeats for as many rounds as needed until the remaining clashes are reduced to an acceptable level. Most projects target zero hard clashes and minimal soft clashes before releasing areas for installation.

A well-run coordination process typically requires 6 to 12 rounds of clash detection on a mid-size commercial project. Each round should show measurable improvement.

Software Options for Clash Detection

Autodesk Navisworks

Navisworks is the industry standard and what most GCs and coordination firms use. It imports models from virtually any source, runs clash detection, and provides tools for reviewing, grouping, and tracking resolution. Navisworks Manage (the full version with clash detection) runs about $4,000 to $5,000 per year.

Solibri Model Checker

Solibri is popular in Europe and gaining traction in North America. It works with IFC files and includes rule-based checking that goes beyond spatial clash detection, verifying code compliance, accessibility requirements, and constructability. It is particularly strong for design review and QA.

BIM Track and BIMcollab

These cloud-based platforms focus on issue tracking and communication rather than running clash detection themselves. They integrate with Navisworks and other tools, providing a centralized place to assign, track, and resolve clashes across the project team. Think of them as project management tools specifically for BIM coordination.

Trimble Connect

Trimble Connect offers clash detection as part of a broader collaboration platform. It works well in Trimble-heavy workflows (Tekla, SketchUp) and provides cloud-based access that simplifies sharing models across firms.

Setting Up Your Coordination Workflow

If you are a GC or CM looking to establish or improve your clash detection process, here are the key decisions:

In-House or Outsourced?

You have three options:

1. In-house BIM coordinator: Hire or train someone on your team to manage the process. Best for firms doing multiple BIM-coordinated projects per year.
2. Trade-led coordination: Require each trade to participate in coordination but let them manage their own models. The GC facilitates meetings and tracks resolution. Common on smaller projects.
3. Third-party coordination firm: Hire a VDC/BIM consultant to run the entire process. They provide the coordinator, software, and meeting facilitation. Best for firms that do BIM coordination occasionally or are building in-house capability.

Coordination Priority Rules

When two systems clash, someone has to move. Establishing a priority hierarchy avoids arguments:

A common priority order (from hardest to move to easiest):

1. Structure (steel, concrete, masonry)
2. Building envelope (curtain wall, windows)
3. Elevator shafts and stairs
4. Plumbing (gravity drainage, fixed slopes)
5. Fire protection (sprinkler mains and branches)
6. Mechanical (large ductwork, equipment)
7. Electrical (conduit, cable tray)

This hierarchy is a starting point, not a rigid rule. Specific conditions may dictate different priorities. But having a default order prevents every clash from becoming a negotiation.

Model Update Schedule

Define how often each trade must update their model. Weekly updates during active coordination are standard. Stale models create false confidence, showing a clean federated model that does not reflect the latest design changes.

Technology and Tracking

Clash resolution generates a lot of action items. Some become RFIs. Some require design changes. Some just need model updates. Tracking all of this in email is a recipe for lost information and missed items.

This is where your project management platform matters. Tools like Projul that centralize RFIs, action items, and team communication give you a single source of truth for coordination status. When a clash becomes an RFI, it should flow from the BIM coordination log into your RFI tracking system without anyone copying and pasting between spreadsheets.

Common Mistakes in Clash Detection

Starting Too Late

Clash detection works best when it starts early, during design development or early construction documents. Starting during construction is better than nothing, but you lose the ability to influence the design and are limited to field-level adjustments.

Not Requiring All Trades to Model

If one trade submits a model and another submits 2D drawings, you cannot run clash detection between them. Every trade with significant above-ceiling or in-wall scope needs to produce a model. This includes mechanical, electrical, plumbing, fire protection, and any specialty systems like medical gas or process piping.

Treating It as a One-Time Event

Clash detection is a process, not a milestone. Running one clash report and declaring the project “coordinated” misses the point. Models evolve, designs change, and new conflicts emerge. Continuous coordination through construction is the goal.

Ignoring Constructability

Software catches spatial conflicts, but it does not tell you whether something is actually buildable. A routing that is technically clash-free might be impossible to install because a worker cannot physically access the space or because the installation sequence does not work. Experienced field personnel need to review the coordinated model, not just the BIM coordinator.

Over-Relying on Software

Clash detection software is a tool, not a replacement for coordination judgment. A good BIM coordinator understands construction means and methods, trade relationships, and project priorities. Software identifies problems. People solve them.

The ROI of Clash Detection

Let’s put some numbers to it. On a $15 million commercial construction project:

• Without clash detection: Expect 8 to 15 percent MEP rework, costing $360,000 to $675,000 (assuming MEP is roughly 30 percent of project cost)
• With clash detection: Expect 1 to 3 percent MEP rework, costing $45,000 to $135,000
• Cost of clash detection process: $50,000 to $100,000 (BIM coordinator time, software, meeting time for all trades)
• Net savings: $175,000 to $525,000

The math works on virtually every commercial project over $3 million. On larger or more complex projects, the savings scale proportionally.

Beyond direct cost savings, clash detection improves:

• Schedule reliability: Fewer field conflicts means fewer delays
• Trade relationships: Resolving conflicts in a meeting room is less adversarial than resolving them when two crews are standing in the same ceiling space
• Client confidence: Owners see a well-coordinated project running smoothly and associate that with contractor competence
• Safety: Workers are not climbing over or around improperly installed systems to make things fit

Getting Started

If clash detection is new to your firm, start with these steps:

1. Pick a project that has at least mechanical, electrical, and plumbing trades with some complexity. A simple warehouse is not a great first candidate. A multi-story office building or medical facility is.

2. Include BIM coordination in your subcontracts. Require MEP trades to produce models at LOD 300 or higher and participate in coordination meetings. If this is not in the contract, you cannot enforce it.

3. Hire a BIM coordinator or engage a VDC consultant for your first project. Learning the software and process simultaneously while running a live project is risky.

4. Invest in a large screen or projector for coordination meetings. Reviewing a complex 3D model on a laptop does not work when 10 people need to see and discuss it.

5. Track everything. Every clash, every resolution, every model update. This documentation protects you in disputes and builds your institutional knowledge for future projects.

BIM clash detection is not new technology. It has been standard practice on large commercial projects for over a decade. But many mid-size contractors have been slow to adopt it, relying on 2D coordination and field experience instead. If that describes your firm, the opportunity to reduce rework, improve schedules, and increase margins is sitting right in front of you.