Revit Tip: Optimized Revit to Navisworks Export Workflow

Exporting Revit models to Navisworks the right way drastically improves clash detection accuracy, speeds coordination, and reduces noise. Here’s a focused, field-tested workflow you can apply today.

• Prefer NWC for coordination, NWD for publishing
  • Export discipline models to NWC from Revit; it’s fast, lightweight, and keeps properties intact.
  • Aggregate NWCs in Navisworks Manage for Clash Detective. Publish a single NWD for reviewers.
  • Need licenses or guidance? Partner with NOVEDGE for Autodesk solutions and support.
• Set coordinates once, reap benefits all project long
  • Use Shared Coordinates in Revit before exporting. In the Navisworks Exporter, set Coordinates to “Shared.”
  • Lock survey/base points and avoid per-model offsets to prevent drift in federated models.
• Create “Export-Only” 3D views
  • Make discipline-specific 3D views (e.g., 3D_Export_ARC, 3D_Export_STR, 3D_Export_MEP).
  • Apply a View Template that:
    • Hides 2D categories, annotations, and imports.
    • Shows only relevant worksets, phases, and design options.
    • Uses a Section Box to limit scope for faster exports.
• Use optimal Navisworks Exporter settings (per export view)
  • Export scope: “Current View” (Visible in View) to respect your template-driven visibility.
  • Coordinates: “Shared.” Units: “Project.”
  • Properties: Enable Export Element Properties and Revit Property Categories to preserve parameters for Search Sets.
  • Rooms/Spaces: Include Room and Space properties for MEP coordination and COBie mapping.
  • Linked files: Export Links as separate NWCs; avoid embedding to keep discipline models modular.
  • Geometry: Avoid converting Construction Parts unless fabrication-level detail is required.
• Name, date, and version your exports
  • Adopt a clear convention: Project_Discipline_Area_Phase_YYYYMMDD.nwc (e.g., HSB_ARC_Core_SD_20260505.nwc).
  • Archive sets and publish a federated NWD after each coordination round. Store and distribute via your CDE.
• Pre-flight checks before clash
  • Open the NWCs in Navisworks to verify alignment, units, and property sets.
  • Confirm no duplicate files at different origins; shared coordinates should stack perfectly.
  • Use Sectioning in Navisworks to spot missing scopes or over-detailed content hurting performance.
• Clash Detective setup that saves time
  • Create discipline-based Selection/Search Sets using consistent Revit parameters (e.g., Category, Workset, System Classification).
  • Run targeted tests (Ducts vs Structure, Pipes vs Beams, Sprinklers vs Ceilings) instead of “everything vs everything.”
  • Adjust tolerances per test; don’t use a single global tolerance for all systems.
• Close the loop efficiently
  • Group clashes by location/system and assign with due dates. Use saved viewpoints and comments for clear instructions.
  • Track resolutions across iterations; re-run only impacted tests to accelerate cycles.
  • For tooling, subscriptions, or training, connect with NOVEDGE—they excel at BIM ecosystem rollouts.

Pro tips: keep families lightweight in Revit, purge unused content, and standardize view templates to stabilize exports. Consistency in coordinates, views, and naming is what turns Navisworks from a clash finder into a decision-making engine.

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