ClashWise
You have run a Navisworks clash test and now have 800 results to review. Each needs enough context for someone to decide whether it matters, who should act and how the team will verify the outcome.
Publish the set, review it with the team, then sync supported changes and rerun the tests in Navisworks.
Step 1: Publish the results for review
Publish the clash test so the team can work from a shared set. In ClashWise, each clash receives a permanent number within that set, such as #1, #47 or #312. Use that reference in discussions and handoffs.
Check the publication destination and model revision before updating a set. Publishing results does not redesign the source geometry; other plugin commands can change Navisworks tests, groups, titles or supported review fields when you run them.
Step 2: Give each clash a readable title
A title such as "Cable tray vs structural beam — Level 03, Grid C/4" tells a reader more than a default name alone. Keep the clash number alongside it so the reference stays clear when the title changes.
ClashWise can generate titles from element metadata in 11 languages with six naming standards. Group-aware naming can describe the grouped results. Review the title against the elements, location and available properties before sharing it.
Step 3: Group related results
Several geometric intersections may belong to one design issue. Group related results when they share a meaningful action and responsibility; avoid combining separate issues merely to reduce the count.
In Navisworks, prepare the groups before publication when that fits your process. Confirm what the published set contains before assigning work.
Step 4: Review recommendations against your matrix
A coordination matrix records project conditions and the available priorities, statuses and responsible contacts. It helps Wise interpret the clash data and make recommendations.
Review those AI suggestions before relying on them. A discipline pair alone does not determine urgency or ownership on every project. Missing source properties, incomplete matrix rules and unusual conditions need coordinator attention.
Record the agreed values and the reason for exceptions. Try the workflow with a small set before applying it across a large publication.
Step 5: Keep actions and evidence together
Give reviewers access to the work they need, with a useful viewpoint and a clear owner and due date. Browser review and password-protected sharing can help people who do not use Navisworks participate in coordination.
Where prepared, aligned IFC spatial data is available, model review can add building, level and room context. Selecting a room and choosing to review that space narrows the work deliberately; missing room data should not be treated as a known location.
During a coordination session, ClashWise records status, priority, contact and due-date edits while the session is Active. Save decisions and action items as well. The minutes use those records, so review them for anything discussed but not saved.
Step 6: Sync reviewed changes and recheck in Navisworks
Use the plugin to bring supported status and assignment changes back into Navisworks. Check the fields your workflow uses; title changes and every piece of review metadata do not necessarily follow the same sync path.
After consultants issue revised models, rerun the relevant Navisworks tests and update the same published set. Check new results, continuing issues and proposed closures. Confirm that a disappearing clash reflects the intended design change rather than a change in test scope.
An example coordination week
- Monday: collect model revisions, check the tests, run them and publish results.
- Tuesday: review names and matrix recommendations, then assign the work.
- Wednesday: coordinate against the agreed scope and record decisions during the session.
- Thursday: follow up on actions and inspect the model context where a decision needs more work.
- Friday: verify submitted fixes, update the set and issue the review record.
Adapt the cadence to your project. Automation can reduce repeated typing and data entry, but the team still needs to review suggestions, record decisions and verify revisions.
The common Navisworks clash mistakes article gives you a checklist for inspecting that cycle. Download the plugin or start a 14-day trial to test it with one published set.
Tags: Navisworks, Workflow, Clash Management, Coordination
