If you draft MEP in Australia, you already know the conversation: should clash detection live inside Revit, or should you push everything into Navisworks? The honest answer is that both tools earn their seat, and the teams who deliver cleanly coordinated commercial projects almost always run a hybrid workflow. This guide breaks down where each tool actually wins, how BCF keeps them talking, and what we recommend by project scale on Australian commercial jobs.
How each tool detects clashes
Before arguing which is “better,” it helps to understand that Revit and Navisworks aren’t really doing the same job. One checks geometry inside the authoring environment; the other checks a federated model where every discipline has already been linked together.
Revit Interference Check (in-model)
Revit’s built-in Interference Check runs against elements inside the active model or against linked Revit models. It’s fast to launch, it flags geometry the designer can jump straight to, and because it lives in the authoring tool, fixes happen in seconds. For a mechanical drafter double-checking their own ductwork against structural, Interference Check is brilliant.
The catch is scale. Interference Check returns a flat list — there’s no rules engine, no clash grouping, no tolerance settings, no saved viewpoints, no assignee, and no audit trail between runs. On a large commercial project with five disciplines and thousands of clashes, the list becomes unusable within a single federation cycle.
Navisworks Clash Detective (federation-level)
Navisworks Manage is purpose-built for federation. You append Revit (RVT), IFC, DWG, NWC and civil formats into a single NWF, then run Clash Detective with rules like “ignore same-layer clashes,” “tolerance 25 mm,” “group by grid,” or “test only mechanical vs structural.” Every clash becomes a trackable item with status (New, Active, Reviewed, Approved, Resolved), an assignee, a saved viewpoint and a comment thread.
That persistence is the difference. A Navisworks clash report tells your coordinator which issues are actually new since last Friday, which have been closed, and which are stuck waiting on a consultant. It’s the only practical way to manage clash counts above a few hundred — which is every serious commercial project.
Where Revit wins
Revit’s edge is speed, context and the fact that the drafter fixing the clash is already inside the model where the fix needs to happen.
- Self-checking during authoring. A hydraulic drafter routing a sanitary stack can run Interference Check against the architectural link before saving, catching the obvious hits before they ever reach the coordinator.
- In-discipline clashes. Mechanical-vs-mechanical (duct vs pipe in the same model) is usually best caught in Revit because the fix is one MEP discipline’s responsibility anyway.
- Small projects. On a fit-out or a single-storey retail build, Navisworks overhead isn’t worth it — a weekly Revit Interference Check pass plus a visual walk-through does the job.
- Parametric awareness. Revit understands systems, spaces and parameters, so you can filter clashes by system classification in ways Navisworks can’t replicate natively.
Where Navisworks wins
Navisworks wins the moment you have more than two disciplines, more than one consultant, or more than a few hundred clashes to triage.
- Cross-discipline federation. Civil, structural, architectural, mechanical, electrical, hydraulic, fire — all in one NWF. Revit can link some of these, but IFC-only consultants and Civil 3D data land far more cleanly in Navisworks.
- Rules-based clash testing. Tolerance, selection sets, grouping, and “ignore self-intersections” rules let you filter ten thousand raw geometry hits down to a few hundred real coordination items.
- Clash status tracking. Every issue carries status, viewpoint, assignment, date stamps and history. That’s what turns a raw list into a weekly clash report your builder will actually read.
- Performance on big files. Navisworks will happily federate a 2 GB model that would crash Revit. For high-rise and large commercial, this alone is the deciding factor.
- Walk-throughs and reviews. The review tools, sectioning, redlines and saved viewpoints are built for coordination meetings with clients who don’t have Revit open.
The hybrid workflow most Australian MEP teams actually use
In practice, the “versus” question is a false choice. On almost every commercial project we deliver, both tools run side by side with clear responsibilities:
- Drafters self-check in Revit before issuing a weekly model. Interference Check catches the obvious within-discipline and discipline-vs-structure hits.
- Coordinator federates in Navisworks by appending every discipline (RVT, IFC, DWG) into a master NWF. Selection sets map to disciplines; search sets map to levels.
- Clash Detective runs rule-based tests — typically Mech vs Struct, Mech vs Arch, Hyd vs Struct, Elec vs Struct, plus the MEP-vs-MEP combinations — at the tolerance agreed in the BIM execution plan.
- Grouped, assigned and status-tracked clashes are exported to a report or BCF file and issued with the weekly federated model.
- Drafters resolve clashes back in Revit, re-export, and the cycle repeats. This federation cadence is described in more detail in our MEP BIM clash detection guide for Australia.
The rhythm normally tightens as the model progresses from LOD 300 to LOD 400 — weekly early, twice-weekly during shop-drawing development, and daily in the last fortnight before a critical milestone. For background on those stages, see our LOD 100 to LOD 500 guide.
BCF issue tracking between the two tools
The open bridge between Revit and Navisworks is BCF (BIM Collaboration Format). BCF 2.1 and 3.0 let a coordinator export a clash from Navisworks — complete with viewpoint, camera, element IDs and comment — and import it directly into Revit, where the drafter jumps to the exact location to fix it. When the fix is done, the status updates in BCF and rolls back into Navisworks on the next federation.
Plug-ins like BIMcollab, Revizto and the native BCF Manager in Navisworks make this handshake practical. On Australian projects with offshore consultants or multiple contractors, BCF is usually the only realistic way to keep an auditable issue log without forcing everyone onto the same platform.
Recommendation by project scale
There is no single right answer, but after hundreds of commercial coordination cycles we use these rules of thumb:
- Under ~500 m² fit-out or single-trade drafting: Revit Interference Check only. Navisworks is overkill.
- 500 m² – 3,000 m² commercial, two to three disciplines: Revit for self-check + Navisworks federation weekly. Light clash-grouping rules.
- Mid-rise commercial, four or more disciplines, multiple consultants: Mandatory Navisworks federation, full rule set, BCF tracked, weekly reports.
- High-rise, health, data centre, rail: Navisworks is the source of truth for coordination. Revit is purely an authoring tool. Expect daily federation in the last month of shop drafting.
That’s the honest answer for Australian MEP teams: it’s not Navisworks or Revit — it’s Navisworks and Revit, each doing what it’s best at. If you’d like help setting up that workflow on your next commercial project, talk to us about our MEP BIM drafting services and we’ll tailor the federation cadence to your project scale.