ClashWise
How ClashWise works
From Navisworks checks to the next model revision.
Follow a clash through Navisworks, the matrix, model review and the next revision. See where ClashWise supports you and your team.
Where are you starting?
Choose the work you already have. You can still explore the earlier steps.
ClashWise plug-in + web app
Optional preparation for this starting point
Prepare the checks
Start with the classes in your federation. Build or reuse a matrix, review its rules, then preview the search sets and tests in Navisworks.
Give the team a repeatable checking scope.
Wise can draft the matrix from your selected classes. You review the rules before using them.
What this includes
Map class and discipline properties from the source models. Use Wise to generate a matrix, create one manually or reuse a project matrix.
Review the test type, tolerance and rule defaults for each pair. The Navisworks preview shows proposed changes and protects conflicting user edits.
Coordination Setup requires an active or trial Pro or Business organisation subscription. Company-library standards are available on Business.
ClashWise plug-in in Navisworks
Optional preparation for this starting point
Run, organise and publish
Run the checks in Navisworks. Keep your existing titles or review locally generated ones, apply your chosen grouping and publish the results with model context.
Give reviewers results they can understand and locate.
What this includes
Run & Publish carries your selected tests through the stages you choose. You can also publish or update an existing clash set directly.
Local title generation works offline after setup and model download. Publishing requires a connection.
Reuse context models across clash sets. Prepared IFC models can provide properties and spatial information; a geometry export alone does not add IFC rooms.
ClashWise web app
Optional preparation for this starting point
Find what needs attention
Use the matrix to spot a busy discipline pair, then see its exact clashes in the linked grid. Open #042 to find the two elements and their place in the building.
Get from the overall pattern to the issue you need to review.
Ask Wise to analyse a scope or explain a clash using the available project data.
What this includes
The sample contains three clashes: #042, #057 and #061. A selected pair narrows the linked rows; blue shading represents clash count.
Use Plan, levels and prepared room information to locate the issue. Review this space explicitly selects the room scope.
Isolate the two clash elements, turn on ghosted context and inspect available IFC properties without editing the model.
ClashWise web app
Optional preparation for this starting point
Review alone or together
Work through the clashes with guided review, or bring the team into a coordination session. Keep the model, the discussion and the decision together.
Give each decision enough context to act on it.
Wise can help capture decisions and draft a summary from the saved session record.
On your own
Use guided review to work through the selected clashes at your own pace.
With the team
Follow the presenter or review in parallel, then save the shared decision.
What this includes
Guided review lets you move through a defined scope. Viewing, skipping and marking a clash reviewed are separate actions.
In a session, follow the presenter or review independently in split lanes. Participants return to the shared review with their findings.
Status, priority, contact and due-date edits are recorded while a session is active. Save decisions and action items explicitly; minutes use that record.
ClashWise web app + plug-in
Optional preparation for this starting point
Assign and hand over
Give the issue an owner, a due date and a recorded action. Share the context the designer needs, and sync supported workflow fields back to Navisworks.
Make it clear who is doing what next.
What this includes
Use permission-controlled shares or export the relevant scope through BCF 2.1, Excel and CSV. Session reports include recorded changes, decisions and saved actions.
Sync mapped status and assignee fields to Navisworks. Priority write-back is supported in Navisworks 2026 and 2027; web title edits are not synced back.
MCP lets authorised assistants work with permitted ClashWise records and operations. Access still follows the account permissions.
Design team + Navisworks + ClashWise
Optional preparation for this starting point
Check the next revision
The designer changes the model in their authoring tool. Refresh the federation, rerun the Navisworks checks and publish the updated results before reviewing the outcome.
See whether the model change addressed the clash.
What did the next check show?
The clash is addressed: retain the outcomeOpen or new clashes: return to reviewWhat this includes
In this illustration, the revised duct clears the beam at #042. The outcome follows the updated geometry and check, not a status change alone.
Clashes that remain open, and newly found clashes, return to review. An acceptance without a model change needs its own recorded decision.
ClashWise web app + plug-in
Optional preparation for this starting point
Retain and reuse
Keep the outcome, supporting evidence and outstanding actions with the project. Reuse reviewed matrices, presets and models when the next coordination cycle starts.
Carry useful work into the next review.
What this includes
History, comments, decisions and reports explain what happened. Outstanding actions remain work to follow up.
Reuse a project matrix, grouping and search presets, or a model from the library. Company standards provide a starting point on Business.
Try it with your own Navisworks results.
Choose a familiar project and bring its next review into ClashWise.