BIM Coordination Without Navisworks: A $0/Month Stack That Actually Works in 2026

Navisworks Manage is the de facto standard for federated-model coordination, and for big GCs and well-funded MEP firms it is worth the money. For a small mechanical, electrical, or plumbing shop that wants to start running its own coordination – instead of waiting for the GC’s BIM lead to send out a clash report once a week – the licensing cost is a real obstacle. A Navisworks Manage seat is in the $4,000 to $5,000 range per year, and you need at least two if you want a coordinator and an estimator looking at the same federated model.

You do not actually need it. There is a free, open-source stack that handles 80 to 90% of what most subs use Navisworks for, and it has gotten genuinely good in the last 18 months. Here is the workflow I use with smaller MEP clients who want to bring coordination in-house without a five-figure software bill.

This post is part of Meyers Construction Group’s BIM/VDC consulting practice. If you would rather have someone set this stack up and run the first three coordination cycles for you, that is one of the things we do – see the Clash Audit service.

The stack

• Authoring: Whatever you already use – Revit, Tekla, AutoCAD MEP, ArchiCAD. The trick is the export format, not the authoring tool.
• Federation and clash detection: BlenderBIM, the IFC-native add-on for Blender. Free.
• Issue tracking: BCF (BIM Collaboration Format) files passed back and forth, or a free tier of BIMcollab if you want a hosted issue tracker.
• Viewer for the field / for non-modelers: BIMvision (free Windows IFC viewer) or BlenderBIM itself.

That is the entire stack. Total recurring cost: $0. Total install time on a fresh laptop: about 30 minutes.

Step 1: Get clean IFCs out of every trade

This is the step that makes or breaks the whole workflow. The free tools are only as good as the IFCs going in. The minimum required quality:

• Correct IFC type assignments. Pipes are IfcPipeSegment, ducts are IfcDuctSegment, conduits are IfcCableCarrierSegment, electrical equipment is IfcElectricApplianceType with the right PredefinedType. If your Revit families are categorised wrong, the IFC export inherits the wrong types and the clash report becomes garbage.
• Discipline-separated IFCs. One IFC per discipline (mechanical, electrical, plumbing, fire protection, structure). Do not export a single combined IFC – you lose the ability to filter clashes by trade pair.
• Coordinate system aligned. Use IFC4 (not IFC2x3) and set the project base point and survey point correctly in Revit before export. The single most common reason BlenderBIM clash detection produces a thousand false positives is mismatched coordinate systems.
• Levels and grids exported. You want to be able to filter clashes by floor.

In Revit: File -> Export -> IFC -> Modify Setup -> use IFC4 Reference View MVD, by Revit family classification. Save the setup so you do not have to redo it every export.

Step 2: Federate in BlenderBIM

Open Blender, enable BlenderBIM (it is a regular Blender add-on), and load each discipline IFC into the same scene as a separate IFC project. BlenderBIM keeps each IFC as its own native model under the hood, so you can hide / isolate by discipline, and changes to one IFC do not corrupt the others.

The BlenderBIM Properties panel under “IFC Project” gives you a tree view of every element in the federated model. You can filter by discipline, by IfcType, by storey, and by predefined type.

Step 3: Run clash detection

BlenderBIM’s clash detection lives under Scene Properties -> BlenderBIM Clash Detection. The interface is more spartan than Navisworks but the functionality is comparable for the common cases:

• Hard clashes (geometric intersection). Pick two IFC sets (e.g. mechanical vs electrical), set a tolerance (typically 1 mm to filter rounding artifacts), run.
• Clearance clashes. Same UI, set a positive tolerance to flag elements within X mm of each other (useful for keeping clearance around access panels and electrical equipment).
• Filter by trade pair. Mechanical-vs-structural, electrical-vs-plumbing, etc. This is the workflow that produces actionable reports – “all clashes” is too noisy to use.

The output is a list of clashes, each with the two clashing elements identified by IFC GlobalID, the clash location, and an optional thumbnail. Export to BCF for distribution.

Step 4: Run a coordination meeting that actually closes issues

This is the part that has nothing to do with software and that most coordinators get wrong. A clash report with 800 entries is not a deliverable – it is a list of homework that nobody will do. The coordination meeting needs to:

1. Group clashes by location and by responsible-party-pair before the meeting. 800 raw clashes typically reduce to 30 to 60 real “issues” once you cluster (a single misrouted main can produce 40 individual clashes).
2. Assign every issue to one person by name, not by trade. “MEP to coordinate” is not an assignment; “John from M-1 to revise duct routing in corridor C2 between grids E and F” is.
3. Set a due date for the next federation so issues have a hard close-out deadline. Two weeks is the maximum.
4. Re-federate and re-run clash detection at the deadline. The metric that matters is “number of issues closed”, not “number of issues identified”. Clash counts that go up over time mean coordination is failing.

If you use BIMcollab’s free tier, every issue gets a stable URL and an assigned owner with auto-reminders. If you stick with BCF files, do the assignment in a shared spreadsheet and review at every meeting. Either way, the discipline of “every issue has an owner and a due date” is what separates a useful coordination process from a clash-report theatre.

Where the free stack falls short

To be fair, here are the things this stack does not do as well as Navisworks Manage. Worth knowing before you commit:

• Time-liner / 4D scheduling. Navisworks’s TimeLiner is genuinely useful for sequence visualisation, and BlenderBIM’s 4D support is functional but more manual. If 4D is part of your deliverable, this matters.
• Quantity takeoff against the federated model. Navisworks’s QTO is integrated; BlenderBIM has IFC quantity reading but it is more cumbersome.
• Performance on huge models. A 2 GB+ federated model will load in Navisworks faster than in BlenderBIM. For most MEP coordination work (single-building healthcare, K-12, mid-rise) this does not bite. For large industrial, it does.
• The “everyone else uses Navisworks” problem. If your GC sends you NWC files, you cannot read them natively. Get the GC to send IFC alongside (every modern GC will if you ask), or accept that you will have a one-way dependency on whoever has the Navisworks seat.

Summary

For a small MEP shop that wants to bring coordination in-house, the IFC + BlenderBIM + BCF stack is a real option in 2026. The software is free, the workflow is industry-standard, and the only investment is the time to get clean IFCs flowing out of every authoring tool and to discipline the coordination meeting itself. If you are paying $5k+ per year for a Navisworks Manage seat that gets used twice a week, this is worth a try.

If you want help setting it up, or if you want a one-time clash audit on a project you are already running, that is what the MCG Clash Audit service exists for. Fixed-fee, two-week turnaround, deliverable is a clean federated IFC and a prioritised issue list with named owners.