Revit Tip: Standardized Revit Export for Reliable Navisworks Clash Detection

Export from Revit to Navisworks in a controlled, repeatable way to get reliable clash results and faster coordination cycles.

• Prepare a dedicated 3D view for export
  • Create a view named “NW_Coordination” and lock it with a View Template (graphics, filters, detail level, categories). This keeps every export consistent.
  • Set Detail Level to Coarse/Medium to reduce tessellation. Fine is rarely necessary for clash detection.
  • Hide non-coordination categories (entourage, planting, furniture, room tags, etc.).
  • Use a Section Box to limit the scope to active areas or levels; smaller NWCs mean quicker clashes.
• Align coordinates across teams
  • Use Shared Coordinates and verify Project Base Point, Survey Point, and Internal Origin before exporting.
  • Test alignment by overlaying grids/major structure from multiple disciplines in a temporary NWF.
• Export settings that matter (File > Export > Navisworks NWC)
  • Coordinates: Shared (ensures all disciplines land correctly).
  • Convert element properties: On (preserves Category, Type, Workset, Parameters).
  • Export element IDs: On (enables precise round-tripping via Select by ID in Revit).
  • Rooms/Areas: Export properties if needed; export volumes only if necessary (adds weight).
  • Convert linked files: Off if each team exports its own NWC; On only when producing a single combined export.
• Property strategy for smarter clashes
  • Standardize parameter names (e.g., System, Discipline, Status) so they appear as usable property sets in Navisworks.
  • Push shared parameters and key data into Types/Instances before export; they become powerful Search Set criteria.
• Break out and name NWCs predictably
  • Export one NWC per discipline and area/level when practical (e.g., PRJ_A-MOD_L02_2026-01-01.nwc).
  • Keep naming stable so an NWF can refresh without re-binding sets and tests.
• Navisworks setup for productive clash detection
  • Build a federated NWF that references all discipline NWCs.
  • Create rule-based Search Sets (e.g., Category = Ducts; Workset contains “Structure”; Parameter “Status” ≠ Existing) for reusable Clash Tests.
  • Test logical pairs: Structure vs MEP, MEP vs MEP, Architecture vs Structure. Exclude existing/demo as needed.
  • Filter out small hardware and fasteners unless required; it cuts noise significantly.
• Performance and QA tips
  • Resolve high-priority Revit warnings and purge unused content before exporting.
  • Keep exports on a cadence (e.g., daily/weekly) and document versions; consistency beats one-off “hero” exports.
  • Validate a sample clash run after any template/view change to ensure properties and coordinates are intact.

Need Autodesk Revit or Navisworks licensing, renewals, or advice? Connect with NOVEDGE for expert guidance and competitive options: novedge.com. Their team can help you streamline Revit–Navisworks coordination workflows and tool selection.

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