Introduction to Clash Detection in Revit

Clash detection has become an essential pillar of modern Building Information Modeling (BIM) workflows, particularly within the architecture, engineering, and construction (AEC) industry. It refers to the automated process of identifying intersections, conflicts, or interference between different building systems within a 3D model. When executed correctly before construction begins, this process prevents costly rework, reduces material waste, and minimizes project delays. Autodesk Revit remains one of the most widely used BIM authoring tools, and when combined with Autodesk Navisworks Manage, it provides a robust pipeline for comprehensive clash detection. This article explores the complete methodology for performing clash detection in Revit, from model preparation and export to resolution strategies, with actionable best practices for project teams of all sizes.

In a typical building project, disciplines such as structural engineering, mechanical, electrical, and plumbing (MEP), architectural design, and fire protection services all contribute separate models. Without careful coordination, these systems often overlap in tight ceiling spaces, shaft corridors, or structural grids. Clash detection allows stakeholders to compare these models and quickly pinpoint problematic areas. The result is smoother construction sequencing, better site safety, and improved collaboration across teams. As building complexity increases, mastering clash detection in Revit is no longer optional—it is a standard requirement for delivering high-quality projects on time and within budget.

Understanding Clash Detection and Its Role in BIM Coordination

To use clash detection effectively, it helps to first understand the types of clashes that can occur. Most clashes fall into three categories: hard clashes, soft clashes, and workflow or 4D clashes. A hard clash occurs when two or more physical objects occupy the same space. For example, a structural beam intersecting with a duct or a pipe running directly through a steel column. A soft clash occurs when an element does not intersect geometrically but violates a tolerance clearance requirement. For instance, a pipe that is too close to a cable tray or a duct that passes inside a fire-rated wall's clearance zone. Workflow clashes involve conflicts in construction sequencing or site logistics, such as scheduling a concrete pour before the reinforcement model is finalized.

Clash detection in Revit is typically performed using Navisworks Manage, which is the industry standard for model aggregation and clash analysis. While Revit does include basic interference check tools within its own interface, Navisworks offers far more advanced capabilities: customizable clash tests, batch reporting, tolerances, grouping, and issue tracking integration. Revit's native interference check works well for quick checks within a single model or between two linked models, but for multidisciplinary coordination across large projects, the Navisworks workflow is far superior. For a deeper understanding of the BIM coordination process, refer to Autodesk's BIM coordination overview.

Preparing Models for Clash Detection in Revit

The quality of your clash detection results is directly proportional to the quality of your input models. Investing time in proper model preparation eliminates false positives and ensures that the output is actionable. Here is a detailed breakdown of the preparation steps.

Ensure Consistent File Formats and Units

All discipline models should be created in Revit with consistent project units, coordinates, and orientation. Use the Shared Coordinates system to ensure that each linked model aligns correctly in the master file. If models are created using different coordinate origins or survey points, clashes will appear in the wrong locations or be completely missed. Before exporting to Navisworks, verify that the Project Base Point and Survey Point are correctly defined in each model.

Clean Up Model Elements

Remove any unnecessary geometry or oversized scope boxes, phasing, or worksets that are no longer relevant. Ensure that all MEP systems are properly connected and that ducts, pipes, cable trays, and conduits follow correct routing paths. Delete temporary elements, imported CAD files that are no longer needed, and any extraneous detail that could clutter the clash analysis. A clean model reduces the time spent filtering results and improves overall performance when running clash tests.

Define Level of Development (LOD)

Clash detection is most effective when models meet a minimum Level of Development (LOD) of LOD 300, where elements have accurate geometry, sizes, and positions. If a model is still in early design stages (LOD 200 or less), clash results may be misleading because elements may later change in size or location. Establish a BIM Execution Plan (BEP) that clearly defines LOD goals for clash detection milestones.

Create a Master Model Assembly

Create a central Revit project that links all discipline models together. This master model serves as the single source of truth for coordination. Do not use the master model for design work; its sole purpose is aggregation and linking to Navisworks. Alternatively, export each discipline model directly as a separate NWC or NWD file and append them in Navisworks. The advantage of using a Revit master model is that any changes in the linked models are automatically reflected when the master model is exported.

Exporting Revit Models to Navisworks

Once your models are prepared, the next step is to export them into a format Navisworks can read. Revit supports direct export to Navisworks file formats through the NWC Export Utility or the Export to Navisworks add-in.

Using the Navisworks NWC Export Utility

The Navisworks NWC Exporter is a plugin that installs with both Navisworks Manage and Navisworks Simulate. It adds an Export to Navisworks button to the Revit ribbon. When clicked, it opens the export settings dialog, where you can control parameters such as conversion units, element IDs, and room geometry. Select the appropriate conversion settings for your region (e.g., millimeters, inches). The resulting NWC file is a lightweight, cache-friendly representation of your Revit model. NWC files cannot be opened directly in Navisworks for editing; they must be appended or merged into an NWD or NWF project.

Exporting as NWD or NWF

Alternatively, you can export your Revit model directly as an NWD (Navisworks Document) file, which embeds all geometry and model data, including viewpoint and review markups. The NWD format is useful for distribution to stakeholders who need to view the model but not modify it. An NWF (Navisworks File Set) is a container that links to the original source files (NWC, DWG, etc.) and stores only the coordination and clash results. Using NWF is the recommended approach for live coordination because it maintains links to the original files. When a source Revit model is updated, refreshing the NWF in Navisworks pulls in the latest geometry without requiring a full re-export.

For step-by-step instructions on the export workflow, refer to Autodesk's export guide for Revit to Navisworks.

Running Clash Tests in Navisworks Manage

After your models are loaded into Navisworks, the real work begins. The Clash Detective tool is the central hub for defining, running, and reviewing clash tests. Here is a detailed walkthrough of the workflow from start to finish.

Selecting the Models and Selections

In Navisworks, each discipline model appears as a separate item in the Selection Tree. You can run a clash test between two entire models (e.g., architectural vs. structural) or between specific groups within a model (e.g., all columns vs. all ductwork). Use the Selection Sets feature to pre-define groups of elements for targeted clash analysis. This is particularly useful when you want to ignore certain types of elements such as terrain, furniture, or temporary structures from the analysis.

Defining Clash Tests and Tolerance Settings

Click on the Clash Detective button in the Home tab to open the dialog. Create a new clash test by clicking the green plus icon. Name the test descriptively, for example, "Structural Columns vs. HVAC Ducts." In the Rules tab, define which selection sets or model files are involved. You can set a Tolerance value, which is the allowable gap between elements. A tolerance of 0 means any geometry overlap registers as a clash. For soft clearance checks, set a positive tolerance (e.g., 50 mm) to catch elements that are too close. The Type field lets you choose between hard, clearance, or duplicate clash detection. Use Clearance for soft clash checks and Hard for geometric intersections.

Running the Test and Filtering Results

Click the Run Clash Test button. Navisworks processes the geometry and produces a list of clashes grouped by location. The results panel shows each clash with a thumbnail, distance, and group assignment. Use the Filter option to ignore clashes that are within a specific tolerance range or that involve elements from both models. For large projects, it is common to have thousands of clashes. Do not try to review every single one in sequence. Instead, group clashes by location, element type, or severity using the Grouping options in the Clash Detective Results tab. This allows you to focus on the most critical conflicts first.

Reviewing and Commenting on Clashes

For each clash, Navisworks provides a 3D viewport that highlights the conflicting elements. Use the Viewpoint tools to orbit, pan, and zoom to better understand the nature of the conflict. You can set the Status of each clash to Active, Reviewed, Resolved, or Approved. Add comments or assign responsibility to team members. This creates an audit trail that is essential for tracking coordination progress. The Reports tab in the Clash Detective dialog allows you to export the results in HTML, XML, or CSV format. Reports should be shared with all project stakeholders during coordination meetings.

Resolving Clashes and Updating Revit Models

Identifying clashes is only half the battle; the real value comes from resolving them in a collaborative manner. Here is a structured approach to resolving clashes efficiently.

Prioritize Clashes Based on Criticality

Not all clashes are equal. Structural clashes with MEP systems are often more expensive to fix after construction drawings are issued. Electrical and plumbing conflicts in ceiling spaces may be easier to accommodate with slight routing changes. Develop a prioritization matrix that scores clashes by discipline, location, impact on schedule, and cost implications. Typically, high-priority clashes involve structural elements or major MEP mains. Medium-priority clashes involve secondary runs like branch ducts or electrical conduits. Low-priority clashes may involve temporary elements, duplicates, or design items that are still in development.

Coordinate Through a Central Issue Tracker

Use a cloud-based issue resolution tool such as Autodesk BIM Collaborate, Trimble Connect, or even a shared spreadsheet to assign clashes to specific designers. Each clash should have a description, a screenshot or viewpoint link, a responsible party, and a due date. In weekly coordination meetings, review the open clashes, discuss design changes, and mark issues as resolved when the model is updated. This systematic approach prevents clashes from slipping through the cracks and ensures accountability.

Update Models and Re-run Clash Detection

Once the design team makes a change (e.g., a structural engineer moves a column or an MEP engineer re-routes a duct), they must update their source Revit model. For projects using workshared models, this means syncing changes to the central model. For linked models, the master model must be re-exported and the NWF file refreshed in Navisworks. Best practice is to re-run clash tests after every major design milestone or at least bi-weekly during the design development phase. Continuous clash detection reduces the likelihood of surprises later in the construction phase.

Best Practices for an Effective Clash Detection Workflow

To maximize the value of clash detection, adopt the following comprehensive best practices that go beyond the basic steps.

Establish a Clear BIM Execution Plan

Before the project starts, document in your BIM Execution Plan (BEP) exactly how clash detection will be performed. Define the level of development (LOD) expectations, the naming conventions for models and elements, the frequency of clash runs, and the process for communicating results. Also, specify who is responsible for running the clash tests, reviewing results, and coordinating fixes. This upfront planning saves enormous time during the project.

Use Consistent Naming Conventions

Element naming may seem trivial, but when you have thousands of clashes, filtering by element name becomes critical. Ensure that all disciplines use a consistent naming standard for systems, equipment, and components. For instance, ductwork should be named to indicate its system type (supply, return, exhaust), size, and level. Confusing or generic element names make it difficult to quickly identify which system is clashing and which team needs to act.

Perform Clash Detection at Multiple Stages

Do not wait until the design is 100% complete. Run preliminary clash tests early in the concept or schematic phase to identify major conflicts that could affect space planning or structural grids. As the design progresses through design development and construction documents, run more detailed and frequent clash tests. This phased approach catches issues early when they are cheaper to fix, and it builds coordination into the design process rather than treating it as a final quality check.

For a comprehensive guide on BIM best practices including clash detection workflows, review NBS's best practice guidance for BIM clash detection.

Define Clear Tolerance and Clearance Standards

Work with the project team to establish acceptable clearance values for different systems. For example, pipes and ducts often require a minimum clearance of 2 inches (50 mm) from structural elements. Cable trays and fire sprinkler systems may have different clearance requirements. Document these in the BEP and apply them consistently in the Clash Detective tolerance settings. This prevents overreporting of non-issues and focuses attention on real conflicts.

Train Team Members on the Workflow

Even the best tools are useless if the team does not know how to use them. Provide training sessions on the export process, the Clash Detective interface, and the reporting tools. Consider designating one coordination lead who acts as the single point of contact for clash detection results. This person should be proficient in both Revit and Navisworks and be able to interpret clash reports, debrief the team, and follow up on issue resolution.

Advanced Techniques for Large Projects

On large-scale projects involving dozens of models and thousands of clashes, basic techniques may not be sufficient. Consider these advanced approaches to maintain efficiency and accuracy.

Use Batch Clash Testing

Navisworks allows you to run multiple clash tests in a batch. You can define a test for structural vs. MEP, architectural vs. structural, and MEP vs. MEP, and then execute them all with one click. This is far more efficient than running each test one by one. Create a batch run file using the Batch button in the Clash Detective dialog, and schedule it to run overnight for large datasets.

Leverage Rules-Based Clash Detection

For recurring clash detection workflows, you can create rules that automatically group clashes by category, severity, or element type. This reduces manual sorting and helps you focus on the most critical issues first. You can also apply rules to ignore certain element types that are known sources of false positives, such as planters, furniture, or temporary bracing.

Integrate Clash Detection with 4D Scheduling

For advanced construction planning, you can link clash detection results to your project schedule using Navisworks Timeliner. This allows you to identify not only spatial conflicts but also sequencing conflicts—such as a piece of equipment being installed before the structural slab is poured. While this requires additional setup, it provides a powerful layer of insight for construction managers and consultants. Learn more about this integration from Autodesk University resources on 4D BIM and clash detection.

Common Pitfalls and How to Avoid Them

Even experienced teams fall into common traps that reduce the effectiveness of clash detection. Here are the pitfalls to watch for and strategies to avoid them.

Overwhelming Number of False Positives

If your clash results are full of false positives—clashes that are not actual problems—team members will start ignoring the reports. This often happens when models are not properly cleaned, tolerance values are set too tight, or duplicated geometry exists. To combat this, invest time in model preparation, set realistic tolerances, and use filters to exclude irrelevant elements. Also, run a Duplicate Clash test to identify instances where the same geometry appears in multiple models.

Ignoring Clash Reports

A common problem is running clash detection and then not resolving the issues. This occurs when clash reports are too long or when there is no clear accountability for each clash. Implement a strict policy that no design milestone is considered complete until clash reports have been reviewed and all high-priority clashes are either resolved or noted as accepted with documented approval from the project manager or owner. Use the status feature in Clash Detective to track progress and hold stakeholders accountable.

Relying Solely on Revit's Native Interference Check

While Revit's built-in interference check is useful for quick ad-hoc checks, it lacks the advanced grouping, tolerance, and reporting features of Navisworks. Do not rely on it as your primary clash detection tool for multidisciplinary coordination. Always export to Navisworks for comprehensive analysis, especially on projects with three or more disciplines.

Not Updating Models Before Re-running Tests

If you re-run clash tests without ensuring that all discipline models have been updated, you will waste time reviewing the same clashes over and over. Establish a protocol that before each clash run, each discipline team confirms their model is current and has been synced to the central file. Automate this check by using timestamps or version control in your NWF file set.

Conclusion

Clash detection in Revit, when properly executed, transforms the coordination process from a reactive, error-prone activity into a proactive, data-driven practice that saves time, money, and frustration on construction projects. By preparing models methodically, exporting to Navisworks Manage, running targeted clash tests, and resolving issues through a collaborative process, project teams can eliminate the majority of field conflicts before a single shovel hits the ground. The key principles—consistent naming, regular checks, thorough reporting, and clear accountability—are universal and can be applied to any project size or complexity.

Adopting these techniques not only improves the quality of construction documents but also strengthens teamwork and trust among disciplines. When all stakeholders can see the conflicts clearly in the same model environment, coordinated solutions emerge faster and with fewer compromises. Building information modeling is at its most powerful when these coordination workflows are embedded into daily project operations. Start implementing these clash detection practices today, and you will see measurable improvements in project outcomes from design through to delivery.