Revit Tip: Streamlined Clash Coordination Workflow for Revit, Navisworks, and ACC

Clash Detective (Navisworks Manage) and Model Coordination (BIM 360/Autodesk Construction Cloud) are the fastest way to find and resolve design conflicts before they hit the field. Here’s a focused workflow that keeps issues actionable, accountable, and fast to fix.

Prepare Revit models for reliable clash results:

• Align models with Shared Coordinates and verify Project Base Point/Survey Point; publish coordinates to links before export.
• Clean the model: purge unused, remove unused CAD, resolve warnings that duplicate geometry or create tiny slivers.
• Structure visibility by discipline worksets and turn off non-coordination categories (entourage, furniture in early passes, heavy detail levels).
• Export to NWC with the Navisworks exporter: Coordinates = Shared; Convert element properties = All; Include linked files = As separate; Export Rooms/Spaces and MEP systems.
• Name NWCs consistently (Project_Discipline_Level_Date.nwc) to keep sets and tests stable across updates.

Use BIM 360/ACC Model Coordination for fast, automated checks:

• Organize models by discipline folders; let Model Coordination auto-aggregate “coordination spaces.”
• Create model “Sets” that mirror real review scopes (e.g., STR vs. MEP, Mech vs. Arch Core, Level-by-level packages).
• Review clashes in the browser: filter by Category/System, hide non-critical models, isolate problem types (e.g., ducts vs. structure).
• Create Issues directly from clashes; assign, add due dates, and track status. Consume them in Revit with the Revit Issues Add-in for closed-loop resolution.
• Use issues dashboards to monitor trendlines before coordination meetings.

Leverage Navisworks Manage Clash Detective for deep control:

• Build Search Sets (property-based) rather than Selection Sets; this keeps tests dynamic when models update.
• Template core tests: Hard vs. Clearance checks, discipline-to-discipline, and system-to-system (e.g., Sprinkler vs. Ceilings at 25 mm clearance).
• Set tolerances thoughtfully. Small clearances for finishes; larger for constructability clearances around equipment and access zones.
• Apply Rules to suppress noise (same file self-intersections, duplicates, tiny penetrations below tolerance, insulation-only overlaps).
• Run batch tests, then group results logically (by element in Selection A, by Level, or proximity) and create saved viewpoints with redlines.
• Use status flow (New, Active, Reviewed, Approved) and comments to keep meeting notes inside the model.
• Sync Navisworks issues with BIM 360/ACC Issues so field and design teams see a single source of truth.
• Use SwitchBack to jump to the element in Revit for fast fixes; verify with element IDs when needed.

Governance and performance tips:

• Standardize naming for tests, sets, and viewpoints. Save Clash Detective templates for reuse across projects.
• Re-run coordination on a set cadence (e.g., nightly or pre-meeting) and track clash count trends, not just snapshots.
• Keep NWDs lean; refresh NWCs frequently and archive milestone NWDs for traceability.

Need help standing up a bulletproof coordination workflow, licenses for Navisworks Manage, or ACC setup? Connect with NOVEDGE for procurement, onboarding, and expert training. Your coordination stack (Revit + Navisworks + ACC) is only as strong as its standards—let NOVEDGE help you lock them in.

You can find all the Revit products on the NOVEDGE web site at this page.