Revit Tip: Revit to Navisworks Export Checklist

A clean, coordinated Revit model exports to Navisworks faster and provides more reliable clash and quantity results. Use this concise checklist before generating NWC files.

Create a dedicated coordination view

• Make a 3D view named “_COORD_Navis”. Lock it with a View Template to control categories, detail level, and graphic overrides.
• Turn off non-coordination categories (entourage, planting, CAD symbols, room/space tags, temporary elements).
• Set Detail Level to Medium for architectural/structural and Fine for MEP where geometry precision matters.
• Use Scope Boxes or Section Boxes to limit the export to the coordination area and reduce file size.

Stabilize coordinates

• Set and validate Shared Coordinates across all models. Use “Publish/Acquire” and confirm with a known benchmark point.
• In the NWC export options, choose Coordinates = Shared to ensure alignment in Navisworks.
• Verify orientation by appending a quick NWC to Navisworks and checking against grid/level references.

Control links and scope

• Link other Revit models (do not import). Keep link visibility managed by the coordination view.
• Export linked files as separate NWC files to allow discipline-by-discipline control in Navisworks.
• For CAD links: clean layers, purge, and set them to “Link” with limited visibility, or replace with native Revit geometry where possible.

Prepare model health

• Resolve high-impact warnings (constraints, room-bounding conflicts, duplicated instances).
• Purge unused types, materials, and imported line patterns to shrink the export footprint.
• Audit and compact the model regularly, especially before major coordination milestones.

Set exporter options (NWC)

• Export Scope: Current View Only (use the dedicated view) for predictable results.
• Properties: Enable element and type properties, rooms/areas/spaces, and linked file properties for robust Search Sets.
• Parts and Assemblies: Export Parts as separate geometry if fabrication-level coordination is required.
• Phasing: Match the coordination phase (e.g., “Show New Only” or “Show Complete”) to your clash test intent.
• Units: Confirm project units; verify in Navisworks (Options > Model > Units) after appending.

Make properties “Navis-friendly”

• Standardize parameter names (e.g., System, Level, Zone, Floor, Fire Rating) so they’re easy to filter in Navisworks.
• Use Shared Parameters for fields you need in Search/Selection Sets and Quantification.
• Populate Room/Space data for MEP coordination (Space Number/Name, Department, Airflow targets).

Export organization and naming

• Use a consistent file naming convention: Project_Discipline_Zone_Level_YYYYMMDD.nwc.
• Export by logical packages (Core, Shell, Interiors, ME, EL, FP) so teams can append only what they need.

Quick QA after export

• Append the NWC(s) in Navisworks and check: coordinates, levels, grid alignment, and units.
• Open Properties and confirm critical fields appear as expected for Search Sets and Clash Rules.
• Spot-check element tessellation and visibility; adjust detail level if files are too heavy or too coarse.

Need Revit or Navisworks licensing, renewals, or workflow advice? Explore NOVEDGE, or browse Revit and Navisworks solutions for your team.

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