Your First Coordination Cycle

This article walks you through one complete ClashWise coordination cycle — from clash results in Navisworks, to an AI-triaged worklist on the web, and back into your model. It's the loop you'll repeat throughout the project.

The cycle in one line: detect in Navisworks → publish → build the matrix → run AI analysis → review and triage on the web → (optionally) run a coordination session → sync decisions back to Navisworks.

You'll need the plugin installed and a Clash Management plan or the free trial (every new account starts with one). The web app shows this same journey as a "Getting started" guide on your dashboard and as a progress pill on each clash set — it tracks which step you're on.

Step 1 — Run clash detection in Navisworks

ClashWise does not detect clashes — Navisworks does. Open your federated model in Navisworks Manage and run your clash tests in Clash Detective as usual. Once tests have results, ClashWise takes over the management side.

Optional but recommended before publishing:

Enhance (ribbon ClashWiseAI → Clashes panel) gives every clash a descriptive, AI-generated title — far easier to work with than "Clash847".
Group Clashes (same panel) groups related clashes by rules such as level, grid, or proximity. Grouped sets are dramatically easier to review, and the publish flow will nudge you about it.

Step 2 — Publish the clash test to ClashWise

On the ClashWiseAI ribbon, go to the Clash Management panel and click Publish (Alt+9).
Select the clash test(s) to upload and confirm. Keep 3D capture enabled if you want to review these clashes in the browser 3D viewer later — a set published without 3D capture can't be viewed in 3D.
Publishing runs in phases with progress; when it finishes, your clashes exist on the web as a clash set.

Open https://clashwise.ai/my/clash-sets — your new set appears in the sidebar. (You'll also get a "Clash Set Created" email if operational emails are enabled.) Publishing from the plugin is the only way clash sets are created — the web app can't create clashes.

Step 3 — Create the clash matrix

The matrix is your project's rulebook: every pairing of element classes (Walls × Pipes, Ducts × Beams, …) gets a default priority, status, tolerance, and responsible contact. ClashWise builds it from the model elements in your published clashes.

On the clash set page, click "Generate matrix".
The three-step wizard asks you to pick which captured properties identify each element's class and discipline, select the classes to include, and name the matrix.
Generation runs in the background; you'll see the new matrix under Clash matrices when it's ready, already assigned to your set.

Step 4 — Review and refine the matrix

Open the matrix and check the generated rules: adjust default priorities and statuses, and assign responsible contacts to rules (you can bulk-apply and import contacts from Excel). Fix it once here and it applies across thousands of clashes — now and on every future analysis.

Step 5 — Run the analysis

Back on the clash set, click "Run analysis". AI applies your matrix across the whole set: every clash is matched to a rule and stamped with a recommended priority, status, and responsible contact — turning a flat list of clashes into a triaged worklist. Progress shows live; you'll get an email when it completes.

Step 6 — Review and triage on the web

Now work the list:

The clash grid shows every clash with its permanent number (clash #N), thumbnail, and the AI recommendations. Edit recommended status, priority, contact, due date, and tags inline. (Clash titles are read-only on the web — renaming is a plugin feature.)
Search and filter with plain-language AI filters or the manual condition builder; save filters as views; group the grid by any field.
Click "3D" to review clashes in the composed 3D viewer, or open "Insights" for the live dashboard once analysis is complete.

Step 7 (optional) — Run a coordination session

Click "Coordination" on the clash set to schedule or start a live clash-review session. While a session is active, every status, priority, contact, and due-date change is recorded automatically, and when you end it, AI generates the meeting minutes — ready to copy or download as a PDF. See the Coordination Sessions section.

Step 8 — Sync back to Navisworks

Close the loop by pushing the agreed outcomes back into the model:

In Navisworks, open the same model and click Sync on the Clash Management panel.
Choose what to write back: status, priority (Navisworks 2026 and later), assigned-to (Navisworks 2025 and later), comments, and groups created on the web.
Clashes are matched automatically, and the whole sync is a single undo step — press Ctrl+Z once in Navisworks to revert it entirely.

What happens next

As the design evolves, re-run your clash tests in Navisworks and use Update (Alt+0) on the ribbon to refresh the published set — clash numbers and your web-side work are preserved, and the set's progress guide will advise a re-analysis when new clashes arrive ("This set changed since the last analysis"). That's the cycle: update, analyze, review, sync, repeat.

Tips

Group clashes in the plugin before publishing — reviews, 3D scenes, and shares all work better with focused groups.
Keep one matrix per project and refine it as you go; every analysis benefits.
Lead with clash numbers (#N) when discussing clashes with your team — they're the permanent identity of each clash within a set and appear in links, the grid, the 3D viewer, and reports.