Rules instead of repetition
Spreadsheet-based clash matrices have run BIM coordination for fifteen years. ClashWise turns those matrices into a live engine: "Mech vs Struct → owner = mech consultant, priority = high" applies automatically to every new clash, every model update.
Bi-directional Navisworks sync
Status changes in ClashWise push back to Navisworks. Status changes in Navisworks come into ClashWise. One source of truth — no manual reconciliation between the model and the tracker.
Dashboards built for project meetings
Open clashes by discipline, by level, by owner, by age. Trends per project week. Identify the slowest-resolving consultant without opening Navisworks. Share password-protected views with stakeholders who don't have Autodesk seats.
AI Clash Assistant
Chat about any clash set. "What's the oldest unresolved clash on L05?" "Show me everything assigned to MEP consultant A this week." Plain language in, real answers out.
Frequently asked questions
How are clash rules defined?
Through a clash matrix UI. Pick the discipline pair, the conditions (level, zone, element type), and the actions (set priority, assign owner, set status). Save once, applies to all future clashes.
What if a clash doesn't match any rule?
It lands in an "unassigned" bucket for manual triage. You can then either assign it manually or extend the rules to cover the case.
Does the bi-directional sync work over the network?
Yes. The Navisworks plug-in and the web app communicate over standard HTTPS. No on-premise server required.