How to Use Navisworks for Clash Detection: A BIM Master Guide

MacLeamy Curve benchmark — relative cost to fix the same clash at each project phase

TL;DR — Key Takeaways

What Is Clash Detection in BIM?

Navisworks Manage 2024 — Clash Detective running Test 01: MEP vs Structure on a fully federated model. Clash1 shows a hard clash at −38 mm between an HVAC Duct and a Structural Beam. Total: 295 clashes across 5 clash groups in one coordination cycle.

The Problem Clash Detection Solves

Every building above a certain scale is a three-dimensional coordination problem. Structural beams, HVAC ducts, drainage pipes, electrical cable trays, fire sprinkler systems, and architectural walls all compete for the same physical space — specifically the ceiling plenum, the shaft zones, and the structural floor openings. In 2D CAD workflows, these conflicts are discovered on site when a contractor tries to install an element and finds another trade has already occupied the space. At that point, the fix requires physical demolition, rework, procurement delays, and contract disputes. On a typical Indian commercial project above ₹50 crore, unresolved coordination conflicts generate 5–12% in rework costs as a percentage of total project budget.

Clash detection in BIM is the process of identifying those physical and logical conflicts in a federated digital model before construction begins. By federating all discipline models in Autodesk Navisworks Manage and running automated interference tests, a BIM coordinator can identify thousands of conflicts in minutes — conflicts that would otherwise surface as expensive site-level RFIs weeks or months into the construction programme.

Figure 1: Cost to fix a clash by project phase — MacLeamy Curve benchmark for AEC projects. Clash detection during design phase costs 1×; the same fix post-completion costs 100×.

Clash Detection vs Coordination: Understanding the Difference

Clash detection and coordination are related but distinct activities. Detection is the automated process: Navisworks runs an interference test and reports which elements physically conflict. Coordination is the human process: the BIM coordinator reviews those results, assigns responsibility, facilitates resolution meetings, and tracks the status of every issue through to closure. Detection finds the problem. Coordination resolves it. Both require Navisworks Manage and a structured workflow.

For Indian AEC projects, the MEP coordination workflow is where most coordination effort concentrates — HVAC, plumbing, fire fighting, and electrical systems running through a constrained ceiling plenum alongside structural elements. This is the highest-density conflict zone on any commercial floor plate and the primary focus of every clash detection cycle.

Navisworks Manage vs Simulate: Why You Need Manage for Clash Detection

The Critical Distinction

Autodesk markets Navisworks in two primary versions: Simulate and Manage. The distinction is not cosmetic — it determines what you can and cannot do as a BIM coordinator. Navisworks Simulate handles model aggregation, 3D navigation, markup, sectioning, and 4D construction simulation via the TimeLiner module. These are review-level capabilities. What Simulate does not include is the Clash Detective module — the tool that runs automated interference tests between discipline models. Without Clash Detective, you cannot run clash detection in any automated or professional sense.

Figure 2: Clash Detective is exclusive to Navisworks Manage and is the defining requirement for BIM Coordinator roles.

Licensing Guidance for Indian Firms

For Indian BIM teams, Navisworks Manage is available via Autodesk subscription on a monthly or annual basis. Most Tier-1 Indian AEC firms — L&T Construction, Tata Projects, Shapoorji Pallonji, and the major PMCs — carry Navisworks Manage licences as part of their Autodesk AEC Collection subscription. For independent BIM coordinators and smaller consultancies, the standalone Navisworks Manage subscription is the minimum viable version for any professional coordination role. Simulate-only licences are appropriate for project managers and clients who need to review models but are not running coordination workflows.

Types of Clashes: Hard, Soft, and Workflow/4D

Understanding What You Are Looking For

Not all clashes are equal. Navisworks Clash Detective can detect three distinct categories of conflict, each with a different severity profile, detection method, and resolution approach. Before configuring any clash test, a BIM coordinator must understand what they are trying to find — because the tolerance settings, clash type selection, and review process differ significantly across these categories.

Figure 3: Clash type comparison — risk severity, frequency in Indian AEC projects, and resolution complexity scored out of 10.

Step-by-Step Clash Detection Workflow in Navisworks

The Navisworks clash detection workflow runs in four sequential phases. Attempting to skip any phase — particularly Phase 2 (selection sets) — results in either missed clashes or an unmanageable volume of false positives. The discipline of following this structure is what separates professional BIM coordination from ad hoc model checking.

The complete Navisworks clash detection workflow — from discipline modeling in Revit through model federation, clash detection, coordination review meeting, issue assignment, resolution in Revit, and final approval. This 7-step cycle repeats until all critical clashes reach zero.

Figure 4: Navisworks clash detection workflow — from model federation to zero-clash verification. The loop between resolve and verify repeats until all critical clashes are closed.

Phase 1: Preparing the Federated Model (NWC vs NWD)

The federated model is the foundation of the entire clash detection process. Every discipline model must be exported in NWC (Navisworks Cache) format from Revit using the Navisworks exporter plugin (included with Revit). NWC files are the correct format for active coordination because they maintain a live link to the source Revit file — when the Revit model is updated and the NWC is re-exported, Navisworks automatically reloads the updated geometry without requiring the test configuration to be rebuilt.

NWD (Navisworks Document) is a compressed, self-contained snapshot of the federated model. NWD is appropriate for distributing a static model to a client, for archiving coordination milestones, or for sending a federated model to a party who does not need to update it. Do not use NWD as the working format in an active coordination workflow — when discipline models update, you cannot refresh an NWD file without rebuilding the entire federation.

Phase 2: Setting Up Rules and Selection Sets

Selection sets are the mechanism that allows Navisworks to run targeted clash tests between specific disciplines rather than running every element against every other element. Without selection sets, a clash test on a large project returns tens of thousands of results — the majority of which are irrelevant expected contacts. Creating discipline-based selection sets before configuring any tests is not optional procedure — it is the difference between a usable coordination output and an unusable noise dump.

In the Sets palette (View > Sets), create a saved selection for each major discipline: Architecture, Structure, MEP-M (mechanical/HVAC/firefighting), MEP-E (electrical, cable tray, conduit), and MEP-P (plumbing, drainage). On complex Indian projects with separate consultant models for each MEP sub-discipline, creating six to eight selection sets is standard practice.

Configure clash rules in the Rules tab to suppress known expected contacts: elements of the same file clashing with each other (intra-discipline false positives), duplicate geometry at model links, and element types expected to overlap by design (structural reinforcement within concrete).

Phase 3: Configuring the Clash Detective Tool

Open Clash Detective from the Home tab in Navisworks Manage. Click Add Test to create a new test, then configure the following parameters for each discipline pair in your test matrix:

Phase 4: Running Tests and Assigning Responsibility

With all tests configured, click Run All to execute the full clash test matrix simultaneously. On a typical 300,000 sq ft Indian commercial project in the first coordination cycle, expect 800–3,000 hard clashes before resolution begins — this is normal and does not indicate poor BIM quality. It indicates that the model has been properly set up to find real conflicts that would otherwise become site-level problems.

Autodesk Navisworks Manage 2024 — BIM Coordinator view during a live MEP vs Structure coordination session. Clash Detective panel lists Test 01 clashes with statuses New, Active, Reviewed, and Approved. The orange circle marks a hard clash between a rectangular duct and a structural column at −23 mm.

For each identified clash, Navisworks displays the two conflicting elements highlighted in the 3D view. Review each clash to confirm it is a genuine coordination issue (not a false positive), then assign it to the responsible discipline using the Comments panel. Export the full results as a BCF file for Revit round-tripping or as an HTML report for distribution to consultants who do not have Navisworks licences.

Top Causes of Clashes in Indian AEC Projects

Figure 5: Top causes of clashes in Indian AEC projects — survey data from BIM coordinators on commercial projects above ₹50 crore (2025–26).

Level 02 South Zone — MEP installation in progress on an Indian commercial project after successful Navisworks clash detection. HVAC ducts, fire protection piping (red), chilled water pipes (green), and cable trays installed in the ceiling plenum with zero rework.

MEP vs Structure: The Ceiling Plenum Problem

The single largest source of clashes on Indian commercial projects is the competition for ceiling plenum space between MEP systems and structural elements. On a typical Indian commercial office floor plate, the plenum depth is 600–900 mm. Within that zone, the structural team needs to accommodate beams (typically 300–600 mm deep), and the MEP team needs to route primary HVAC ducts (150–600 mm section), chilled water piping with 50 mm insulation clearance, cable trays for power and ELV systems, fire sprinkler branch piping, and condensate drain pipes from cassette FCUs. Indian floor-to-floor heights on commercial Grade A office buildings typically range from 3.6 m to 4.2 m — less margin than equivalent buildings in the UAE or UK, which makes coordination tighter and clash rates higher per square metre.

Late Model Uploads and Coordination Lag

The second most common cause of clashes is not a technical problem — it is a process failure. Teams working in disciplinary silos upload their models late in the coordination cycle, often after other disciplines have already made routing decisions based on earlier model states. An HVAC engineer who designed duct routes based on a structural model from four weeks ago will conflict with updated beam positions they were never shown. The solution is a BEP-mandated upload schedule: all discipline models to the CDE at the same agreed frequency (typically weekly), with a hard deadline before each coordination meeting.

LOD Non-Compliance

Clash tests run against LOD 200 models — approximate geometry without real connections, insulation, or fitting dimensions — produce meaningless results. An LOD 200 duct may show no clash with a structural beam because its approximate dimensions do not reflect the actual installed duct including flanges, hangers, and insulation. The same duct at LOD 300 or above — with exact dimensions, insulation thickness as a parameter, and real fittings — will show the clash. For coordination-quality clash detection, all discipline models must be at LOD 300 or above. This is a contractual requirement on ISO 19650-referenced Indian government projects and should be specified in the BEP from the outset.

Poor Naming Conventions

Unstructured file naming in a multi-disciplinary federated model makes it impossible to identify which discipline a clashing element belongs to, who owns the resolution, and which model version is current. On Indian joint-venture projects involving multiple consultants — common on hospital, airport, and metro rail projects — the naming problem compounds across offices, software versions, and geographic locations. ISO 19650 naming conventions (Project-Originator-Volume-Level-Type-Role-Classification) provide a structured framework that Navisworks can use to automatically identify discipline ownership from the file name.

Configuring Clash Tests in Clash Detective

The Discipline-Pair Priority Matrix

Figure 6: Clash test discipline-pair priority matrix — recommended execution order for Indian high-rise and commercial projects.

Test Configuration Parameters

For each discipline pair in your matrix, the Clash Detective configuration window requires the following parameters to be set correctly before the test produces useful results:

1. Selection A and Selection B: Use named selection sets — never use default All or Last Selection. Named sets ensure the test is repeatable when models update.
2. Clash type: Hard for MEP vs Structure and Architecture vs Structure. Clearance for MEP vs MEP (to enforce insulation separation distances). Duplicates as a standalone test for quality checking the federated model itself.
3. Tolerance: For hard clash tests, set 0.001 m to suppress geometry rounding. For clearance tests, set the project-specific clearance value per the tolerance table — 100 mm for cable tray vs HVAC duct, 150 mm for sprinkler vs structure (NFPA 13), 50 mm for general MEP vs MEP.
4. Rules tab — suppress: Same file (prevents intra-discipline false positives), Same layer (prevents geometry within the same component), and Approved (suppresses clashes already signed off in previous cycles).
5. Grouping: Configure grouping by Grid Location or Level to organise large result sets into spatially manageable blocks. On Indian projects with 20+ floors and hundreds of active clashes, ungrouped results are unworkable in a coordination meeting context.

Running and Reviewing Clash Test Results

Interpreting the Results Panel

After clicking Run All, the Results panel populates with every detected conflict, organised by test. Understanding the status values is essential for managing the resolution workflow:

The Clash Resolution Workflow

The resolution loop follows a structured sequence that must be completed for every critical and major clash before site mobilisation is approved: Identify (Navisworks detects conflict) → Assign (BCF issue raised, responsible discipline notified) → Resolve (discipline lead modifies element in Revit, re-exports NWC) → Re-run (Navisworks reloads NWC, re-runs test) → Confirm (status updated to Resolved in Clash Detective). This loop typically runs four to eight times on a large Indian commercial project before zero critical clashes are achieved.

Reporting: BCF, HTML, and XML

Navisworks Clash Detective supports three export formats. BCF (BIM Collaboration Format) is the standard for professional Revit round-tripping — BCF files carry 3D viewpoint data, element GUIDs, status, comments, and assigned responsibility. When a BCF file is imported into Revit or Autodesk Construction Cloud (ACC), the responsible modeler can navigate directly to the conflicting element in one click without manual searching. HTML is appropriate for distributing readable clash reports to consultants who do not have Navisworks licences. XML is used for programmatic processing and integration with BIM management platforms. For standard Indian BIM workflows, BCF for Revit coordination and HTML for distribution covers the majority of use cases.

Clash Detection Best Practices for AEC Projects

• Run clash detection on a BEP-mandated schedule, not ad hoc. Define the coordination meeting frequency in the BIM Execution Plan — typically weekly for active construction coordination — and tie the clash detection run to the same cadence. Ad hoc clash detection discovers problems too late to feed into the coordination meeting agenda.
• Always run MEP vs Structure first. The ceiling plenum conflict between HVAC ducts and structural beams is the highest-frequency, highest-risk clash type on Indian commercial projects. Resolving these first prevents cascade conflicts where an HVAC reroute creates a new conflict with an electrical cable tray.
• Set tolerances per applicable codes, not by gut feel. Soft clash tolerances must reference NBC 2016 maintenance access requirements, NFPA 13 sprinkler clearance rules, and SMACNA duct installation standards. Document all tolerance values in the BEP so they are contractually binding and auditable.
• Use clash grouping to make large result sets manageable. On a 300,000 sq ft project, ungrouped clash results can run to 2,000–3,000 items. Grouping by Grid Location or Level breaks these into 30–50 item blocks that a discipline lead can review and action within a coordination meeting timeframe.
• Keep NWC files as the working format for active coordination. Update NWC exports from Revit on the BEP-defined schedule. A stale NWC is worse than no model — it produces clash results that do not reflect the current design state, undermining trust in the entire coordination process.
• Document every Approved clash with an engineering justification. Approved clashes that are accepted by design intent must carry a comment in Navisworks explaining why. This creates the audit trail required for ISO 19650 compliance and protects the BIM coordinator if the decision is later questioned.

Conclusion: Making Clash Detection a Competitive Advantage

The skills gap that matters most in Indian BIM hiring in 2026 is not Revit modeling — it is the ability to run a professional clash detection workflow from start to finish. Thousands of Indian AEC professionals can place MEP elements in a Revit model. A much smaller number can federate a multi-discipline model, configure a clash test matrix in Navisworks Manage, interpret the results, generate a BCF report, facilitate a coordination meeting, and track every conflict to resolution before site mobilisation. That capability is what converts a Revit-trained professional into a BIM Coordinator role — and a BIM Coordinator into someone who adds measurable financial value to every project they work on.

The economics of this skill are unambiguous. A coordination cycle that costs ₹8–12 lakhs in BIM time prevents ₹2–3 crore in site rework on a mid-scale Indian commercial project. The BIM coordinator who runs that cycle is not a cost — they are a risk reduction mechanism with a 20:1 return on investment. As Indian infrastructure continues to scale — metro rail Phase 3, Smart Cities, AMRUT 2.0, hospital construction under Ayushman Bharat — the demand for professionals who can genuinely execute this workflow will only grow.

👉 Click here to get complete details about the MEP BIM Design Course

Frequently Asked Questions