If you’ve ever sat in a “coordination meeting” that felt productive, but the site still raised RFIs, rework, and “this wasn’t in the model” complaints, your workflow needs structure, not more screenshots.
This guide breaks down a Revit-to-Navisworks coordination workflow you can run weekly (or even twice a week) with clear inputs, outputs, and quality gates—so coordination actually improves site execution, speeds up approvals, and supports downstream deliverables like shop drawing packages.
Who this workflow is for: Revit to Navisworks coordination
- BIM Managers & Coordinators running multi-discipline federation and clash reviews
- MEPF contractors/detailers preparing routing, penetrations, and shop drawings
- Architects/structural teams who want fewer late-stage changes
- Project teams using ACC/BIM 360 for issue tracking
What “good coordination” produces
At the end of each coordination cycle, you should have:
- Updated discipline models (RVT) with fixes applied
- A federated Navisworks file (NWF) + a shareable snapshot (NWD)
- Clean clash tests with priorities, owners, and closure status
- A trackable issue log (ACC/BIM 360, BCF, or structured spreadsheet)
- Coordination views / saved viewpoints that teams can review quickly
This is exactly where strong BIM coordination services and 3d clash services stop being “reports” and start becoming a project control system.
Step-by-step: Revit → Navisworks Coordination Workflow
Step 1: Set the coordination rules before you touch. Navisworks
Most clash chaos happens because teams skip the basics.
Lock these 6 rules early
- One coordinate strategy (shared coordinates vs. internal)
- One naming convention (models, views, exports, tests)
- One exchange frequency (weekly, twice weekly, milestone-based)
- One clash priority system (Critical / Major / Minor)
- One issue ownership rule (every clash must have an owner + due date)
- One sign-off gate before shop drawings/spooling / IFC release
Step 2: Prepare each Revit model for export (the “clean model” checklist)
A. Coordinate + levels + grids must be consistent
If your models don’t align in Navisworks, you’ll waste days “fixing clashes” that are actually coordinate errors. Autodesk specifically flags the Shared Coordinates setup as a common cause of wrong placement in Navisworks exports.
B. Create a dedicated Navisworks export 3D view
In each discipline model (Arch/Struct/MEP), create a view like:
In that view:
- Hide clutter (rooms, tags, 2D annotations, CAD junk)
- Use proper visibility/graphics for only the scope you coordinate
- Apply section boxes for zones if your project is huge (better performance)
C. Model health matters (or Navisworks becomes slow and messy)
Before exporting:
- Purge/clean obvious garbage
- Reduce linked duplicates
- Don’t export placeholder geometry unless it affects routing
This aligns with QA/QC best practice: clean input = fewer false positives and fewer “noise clashes.”
Step 3: Export Revit → NWC the right way (avoid the #1 failure: wrong location)
When you should export NWC
Export one NWC per discipline model (and per building/zone if needed). That gives you stable, lightweight federation and clean version control.
Autodesk’s guidance for alignment is straightforward: when you use shared coordinates, export NWC with coordinates set to shared, and keep it consistent across all models.
Export tips that save real time
- Export from your coordination 3D view (not random views)
- Keep export naming consistent:
- Store exports in a controlled folder structure (by week/package)
“Export to NWC missing?”
That usually means the exporter/add-in isn’t installed for your Revit version. Autodesk provides the Navisworks exporter utility and also references the Publish to NWC add-on for batch exports.
Step 4: Build the federated model in Navisworks (NWF first, NWD for sharing)
Use NWF as your live coordination file
- Create an NWF (project file)
- Append each discipline NWC
- Save the NWF so you can refresh/replace weekly
Autodesk’s Navisworks learning content explicitly covers append and merge as the standard way to build a combined model.
Publish NWD for distribution
If your stakeholders don’t have Navisworks Manage, publish an NWD snapshot for review and sign-off cycles. (It’s a practical way to share viewpoints without giving everyone “live federation” access.)
Step 5: Create selection sets (this is where coordination becomes fast)
Before clash tests, create:
- Search Sets (by system, level, zone, discipline)
- Selection Sets (critical corridors, risers, plant rooms)
- A standard set library you reuse weekly
Step 6: Run clash detection the right way (rulesets + tolerances + priorities)
Clash Detective requires Navisworks Manage, if clash detection is missing, you’re not in the right Navisworks version.
Autodesk describes Clash Detective as the tool used to identify cross-discipline interferences early.
A. Don’t run “everything vs everything.”
Start with high-impact tests:
- Structure vs MEP (biggest rework risk)
- Architecture vs MEP (ceilings, shafts, openings)
- MEP vs MEP (riser + corridor first)
B. Use tolerances like a professional (not a guess)
If you set tolerances wrong, you’ll get:
- 5,000 false clashes nobody closes, or
- “clash-free” models that still fail on site
A practical tolerance approach depends on the system and stage (concept vs IFC vs spooling).
C. Classify clashes by type (so teams fix the right thing)
- Hard clashes: physical intersection
- Soft clashes: clearance/access issues
- Constructability clashes: installation reality issues
Early clash detection reduces rework, supports schedules, and improves trade coordination, especially for MEPF-heavy projects.
Step 7: Turn clashes into trackable issues (not screenshots)
Option 1: ACC / BIM 360 issue workflow
If your issues still live in Excel + WhatsApp + email threads, you don’t have traceability. ACC/BIM 360 centralises issues and links them to model views, locations, and owners.
Option 2: Navisworks ↔ ACC integration
Autodesk provides workflows and add-ins to connect Navisworks coordination with Autodesk Construction Cloud issues, so teams can create/assign issues and track closure.
Option 3: BCF (vendor-neutral issue handoff)
If your project involves mixed tools, BCF keeps issue communication portable and structured across platforms.
Step 8: Push issues back to Revit
A coordination loop is useless if fixes stay in Navisworks forever. If you use issue workflows, Autodesk documents steps for loading issues into Revit via the Issues add-in, so designers can resolve and resync.
- Clash found in Navisworks
- Issue created (with owner + due date)
- Fix applied in Revit
- Re-export NWC
- Refresh Navisworks federation
- Re-test and close
Step 9: Add sign-off gates before shop drawings (this is where projects win)
If you release shop drawings without a gate, you’re basically sending risk to fabrication and site.
- Model readiness gate (before clash tests)
- Routing freeze gate (zone-wise)
- IFC / construction issue gate
- Shop drawing / spooling readiness gate
This is where shop drawing production becomes predictable instead of revision-heavy.
Common failures (and how to fix them fast)
This is usually a coordinate mismatch (Shared vs Internal, wrong publish point, inconsistent exports). Autodesk documents Shared Coordinates setup as a key fix path when Revit exports land incorrectly in Navisworks.
“We have too many clashes; nobody can close them.”
- Reduce scope
- Filter junk
- Prioritise risk zones first
“Clashes keep coming back after closure.”
You’re missing change control:
- Freeze routing when needed
- Control model versions
- Don’t allow random uploads without package logic (
Practical templates you can copy-paste into your coordination SOP
Revit pre-export checklist (per discipline)
- Coordinates verified (Shared/Internal chosen and consistent)
- Correct export 3D view active (NW_Export_Coord)
- Links checked (no duplicates / correct versions)
- Scope verified (right phase, right worksets)
- Export folder + naming followed
Navisworks weekly checklist
- NWF updated with latest NWCs
- Sets updated (zones/levels/systems)
- Clash tests reused (same naming and structure)
- Tests run + grouped + prioritised
- Issues assigned + due dates set
- NWD published for review
Where your service keywords fit naturally (without stuffing
If you’re publishing this blog on BMSI, these keywords align perfectly with the topic and intent:
- bim modeling service → Revit model readiness, export hygiene, QA/QC gates
- BIM Coordination services → federation, clash strategy, issue ownership
- 3d clash services → clash rulesets, tolerances, reporting, closure tracking
- shop drawing → coordination gates before releasing fabrication documentation
- 3d architectural rendering → optional add-on for stakeholder design review (separate from coordination deliverables)
Final CTA (BMSI-aligned)
If you want this exact workflow implemented on your projects with disciplined exports, clean federations, actionable clash reports, and issue closure tracking, this is where structured BIM Coordination services, reliable 3D clash services, and shop-drawing-ready BIM modeling service delivery make the difference.