Rework remains one of the most expensive problems in construction, and a large share of it starts as a clash in the model that nobody fixed in time. Industry estimates put rework at roughly 5 to 10 percent of total project cost (Autodesk), and fixing a problem on site typically costs far more than fixing it during design (PlanRadar).
Most teams have already solved the first half of the problem: finding clashes. The slow part is fixing them. A single coordination run can return hundreds or thousands of conflicts, and each one has to be moved, rerouted or bent by hand in the model. This guide explains how to automate MEP clash resolution in Revit step by step, covering the Move and Bend strategies, clearance settings, connectivity checks and the engineer review that every automated change still needs.Understanding the Impact of Unresolved Clashes
Why MEP Clash Resolution in Revit Is Still So Slow
A clash in a 3D model is more than a red marker on a screen. An overlooked conflict between a duct and a structural beam can trigger work stoppage on site, urgent redesign, new material orders and disputes between trades. The cost of poor information exchange is well documented: a study by the U.S. National Institute of Standards and Technology estimated that inadequate interoperability cost the U.S. capital facilities industry about $15.8 billion per year (NIST GCR 04-867, 2004).
Revit and Navisworks have made clash detection routine. But turning a clash report into constructible fixes is still largely manual. Coordinators open each clash, decide which element should move, check clearances, reconnect fittings and re-run the test. When this work is rushed, clashes are missed, fixed in isolation or create new conflicts downstream. That gap between detection and resolution is where automating MEP clash resolution in Revit saves the most time.
What You Need Before You Start
Before you automate MEP clash resolution in Revit, make sure you have the following in place:
A clash report
Automated resolution works from an existing clash report; it does not detect clashes itself. Detection and documentation are handled by tools such as KLASH BIM, which detects and documents clashes and produces reports.
Your Revit model(s)
Single and multiple Revit files are supported, including cloud models on BIM 360 / Autodesk Construction Cloud.
A clear scope
Decide which areas and systems you want to resolve first, and confirm the clashes are eligible types (MEP vs MEP and MEP vs structure).
A reviewing engineer
Someone accountable must review and approve the changes before the model is issued.BAMROC’s Approach to Clash Resolution
Step-by-Step: How to Automate MEP Clash Resolution in Revit
The steps below follow the workflow used by BAMROC, VAVETEK AI’s tool for automatic MEP clash resolution in Revit. For screenshots and button-level detail, see the BAMROC documentation.
Step 1: Detect clashes and export the clash report
Export an NWC file of your project, set up your clash tests in Navisworks, and use the VAVETEK AI Navisworks plugin to generate the clash report file that the resolver reads. Keep tests focused (for example, ducts vs structure or pipes vs cable trays) so results are easier to review.
Step 2: Set up the project area
Use section boxes to isolate the region you want to resolve, such as one floor or one ceiling zone. Working zone by zone keeps changes manageable and makes review faster.
Step 3: Configure clearances
Set the clearance distance that must be maintained between elements once a clash is resolved, along with any custom maintenance gaps for access and insulation. The resolver uses these values when it calculates new positions, so getting them right here avoids soft clashes later.
Step 4: Group parallel systems
Group elements that should move together, such as parallel cable trays or pipe racks. Grouping keeps runs aligned and preserves design consistency instead of shifting each element independently.
Step 5: Choose a strategy: Move or Bend
When you run the resolver, the clash data is processed on VAVETEK AI’s secure servers and prediction files are returned to your machine. You then choose one of two strategies:
- Move strategy: shifts the clashing element slightly (up, down or sideways) to clear the obstruction while respecting your clearance settings. It works best where there is space to offset a run without affecting connected equipment.
- Bend strategy: adds bends or offsets so the system routes around the obstruction, such as a duct dropping under a beam and returning to its original level. It works best where the run cannot move as a whole.
Step 6: Implement the predictions in Revit
Select the prediction file and the tool applies the adjustments to the Revit model automatically. Each change is logged per Revit file so you can trace exactly what was modified.
Step 7: Run connectivity checks
Moving or bending MEP elements can break connections to fittings, branches or equipment. Open the error log to review every disconnection. Items marked green have already been corrected automatically; items marked red need attention and can usually be reconnected quickly with the autoconnect function. Do not skip this step: a clash-free model that is disconnected is not constructible.
Step 8: Validate with a before-and-after report
Re-run your clash tests on the updated model, then produce a clash resolution report with CRDR BIM, a Navisworks plugin that compares the “before” and “after” models and generates before/after clash resolution reports in HTML or PDF. This gives the team clear evidence of which clashes were resolved and which remain.
Step 9: Engineer review and sign-off
Automation shortens the work, but it does not replace engineering judgment. A responsible engineer should review the changes for slopes, access, maintenance zones, code requirements and coordination with other trades before the model is issued. Any clash the tool could not resolve goes back into the normal coordination process.
Benefits of Automating MEP Clash Resolution in Revit
Automating MEP clash resolution in Revit offers several practical advantages for coordination teams:
- Shorter coordination cycles: eligible clashes are resolved in a batch instead of one at a time.
- Less manual modeling: coordinators spend less time on repetitive moves and more on decisions that need judgment.
- Consistent clearances: the same clearance and maintenance-gap rules are applied across every resolved clash.
- Traceability: logs and before/after reports show what changed, which supports review and handover.
- Fewer surprises on site: resolving more clashes during design reduces the risk of costly site rework.
Current Limitations
Automated MEP clash resolution in Revit is not suitable for every clash. According to the BAMROC documentation, the following are currently out of scope:
- Industrial plants and infrastructure projects
- Buildings with special or free-form geometry
- LOD 400+ fabrication models
- Gravity pipes vs structure (slopes must be maintained)
- Equipment vs MEP clashes
The tool also does not detect clashes; it needs a clash report as input. Clashes outside these limits should be handled manually or with engineer-guided tools.
When to Use Engineer-Guided Resolution Instead
Not every case suits fully automatic MEP clash resolution in Revit. For complex zones, sensitive systems or clashes that fall outside the limits above, a semi-automatic approach can be a better fit. HUBAROC is VAVETEK AI’s engineer-guided MEP coordination software: it is semi-automatic, works on one Revit file at a time, and keeps the engineer in control of each decision. Many teams combine both approaches, automating eligible clashes first and then working through the remainder with engineer guidance.
Conclusion
Clash detection is no longer the bottleneck; resolution is. By setting clearances, grouping parallel runs, choosing the right Move or Bend strategy, checking connectivity and keeping an engineer in the loop, teams can automate MEP clash resolution in Revit for eligible clashes and spend their time where judgment matters most.
Want to see how this workflow fits your project? Read the BAMROC documentation or contact us to discuss your next coordination cycle.
Frequently Asked Questions
1. Can MEP clash resolution in Revit be fully automated?
Eligible clashes, mainly MEP vs MEP and MEP vs structure, can be resolved automatically from a clash report. Every change still needs connectivity checks and review by an engineer, and clashes outside the tool’s limitations need manual or engineer-guided resolution. Automation shortens coordination work; it does not replace the coordination team.
2. What is the difference between the Move and Bend strategies?
The Move strategy shifts a clashing element to a new position that clears the obstruction. The Bend strategy adds bends or offsets so the system routes around it. Move suits runs with free space nearby; Bend suits runs that must stay connected at both ends.
3. Does BAMROC detect clashes?
No. BAMROC resolves clashes from an existing clash report. Clash detection and documentation are handled by KLASH BIM and Navisworks, and the clash report is then used as the input for resolution.
4. Which clashes cannot be resolved automatically?
Industrial and infrastructure projects, special-geometry buildings, LOD 400+ fabrication models, gravity pipes vs structure and equipment vs MEP clashes are currently outside the scope of automatic resolution.
5. How do I check that the model is still connected after resolution?
Review the error log generated for each Revit file. Green items were fixed automatically; red items need attention and can usually be reconnected with the autoconnect function. Then re-run your clash tests and create a before/after report with CRDR BIM.