Log, prioritize, and resolve BIM coordination clashes across disciplines — following the Navisworks and BIM 360 clash management workflow used on real construction projects.
Clash detection is the automated process of identifying spatial conflicts between building model elements from different disciplines — for example, a structural beam passing through a duct, or an electrical conduit running through a plumbing pipe. Clashes are detected by running interference checks between federated models in Navisworks Manage or Autodesk BIM 360 before construction begins, when corrections cost a fraction of field rework.
Hard clashes: elements physically overlap (most critical — must resolve). Soft clashes: elements are within a defined clearance distance (e.g., a pipe within 50mm of a beam — may indicate maintenance access or fire rating concern). Duplicate clashes: identical elements from linked models. This tracker color-codes by severity and discipline so teams can triage and assign efficiently.
Standard BIM coordination cycle: (1) All discipline BIM authors publish updated models to the Common Data Environment (CDE). (2) BIM coordinator federates models in Navisworks and runs clash detection. (3) Clash report distributed with auto-assigned IDs (CLH-001…). (4) Discipline leads triage clashes — accept, reject, or assign for resolution. (5) Resolved clashes are closed and documented. (6) Cycle repeats weekly during active design.
N: create new clash entry. F: filter clashes by status or discipline. Esc: close modals. The tracker supports clash log export, coordination meeting minutes, and resolution documentation — all the records needed for BIM audit and project handover.
Autodesk Navisworks Manage is the industry-standard tool for clash detection — it accepts NWC/NWD files exported from Revit, AutoCAD, Civil 3D, and most MEP software. Autodesk BIM 360 Coordinate (now part of Autodesk Construction Cloud) offers cloud-based clash detection with model version tracking. Other tools include Trimble Connect, Solibri Model Checker (rule-based checking beyond simple geometry clashes), and Bentley ProjectWise. This tracker works alongside any of these platforms as the project clash log.
A new model federation run on a medium commercial project typically generates 500–5,000 raw clashes. After filtering out duplicates, architectural-to-architectural clashes (typically acceptable), and known accepted clashes, a typical working set is 50–300 active clashes per coordination cycle. Projects with complex MEP in low-ceiling spaces (hospitals, data centers, below-grade parking) routinely have 500+ active clashes at peak coordination. The goal is to reduce unresolved hard clashes to zero before construction documents are issued.
Responsibility depends on the clash type and project BEP. Typical rules: Structural penetrations through slabs/beams — structural and MEP discipline leads resolve jointly. MEP-to-MEP conflicts — MEP coordinator resolves with discipline leads following coordination priority hierarchy (gravity > pressurized > electrical). Architectural-to-MEP — architect adjusts ceiling heights or partition layouts if MEP requires more space. The BIM coordinator facilitates but does not own resolution. All resolution decisions must be documented in the clash log with the responsible party and resolution date.
When MEP disciplines conflict with each other, a priority hierarchy determines who moves: (1) Gravity systems — sanitary drainage and storm drain cannot change slope, so they take priority. (2) Large-bore pressurized — chilled water, heating water, and fire suppression mains are difficult to reroute. (3) Medium-bore pressurized — condenser water, domestic water. (4) Rectangular ductwork — ductwork is the most flexible in the vertical dimension. (5) Round ductwork — easier to offset than rectangular. (6) Electrical cable trays — most flexible, can be layered. (7) Conduits — easiest to reroute.
Clash resolution documentation for project handover should include: the original clash report export (PDF or HTML from Navisworks/BIM 360), the coordination log with resolution notes and responsible parties, markup screenshots showing the before/after coordination, RFI numbers if field conditions required design changes, and the final as-coordinated model federation. The BIM Execution Plan should specify the format and retention requirements. For public projects with FM handover requirements (COBie), resolved clashes affecting installed-asset data must be reflected in the final as-built model.