Syncing Analyzed Clashes

What syncing does

Sync closes the coordination loop. After your team — and AI analysis against your clash matrix — has set priorities, statuses, responsible contacts, comments, and groups on the web, Sync writes those results back onto the matching clashes inside Navisworks Clash Detective. The model file itself then carries the coordination decisions.

What gets written into Navisworks

ClashWise data	Where it lands in Clash Detective	Availability
Recommended status	The clash's Status field	All supported Navisworks versions (2024–2027)
Recommended priority	The clash's Priority field	Navisworks 2026 and later only — older versions have no priority field the plugin can write to
Responsible contact	The clash's Assigned To field	Navisworks 2025 and later only
Sync comment	A new comment on each synced clash	All supported versions
Web-created clash groups	Native clash groups in Clash Detective	All supported versions

Sync does not rename clash results, create saved viewpoints, add or remove clashes, change clash test settings, or modify model geometry.

Before you start

Sign in inside Navisworks; you need a Clash Management subscription (Pro or Business plan, or an active trial) and the Full Suite plugin edition.
Open the same Navisworks document you published from. Clashes are matched by their identifier (GUID) — a different document, reloaded models, or freshly re-run clash tests may not match, and unmatched clashes are skipped.
Analysis does not have to be complete to sync — manual edits made on the web are syncable on their own.

Where to find it

Ribbon tab ClashWiseAI → panel Clash Management → Sync.

How to sync a clash set

Step 1: Pick the clash set

The Sync Clashes window opens, headed "Select a clash set to update Navisworks clashes". It lists all clash sets you can access, with the same details and Project filter as the Update window. Select your set and click Select Clash Set.

Step 2: Review the Clash Set Summary

The Clash Set Summary window is your pre-flight check — a dashboard of what's about to be synced plus the sync configuration. At the top you'll find the set name, a View this clash set in the browser link, and a refresh button.

Choose the scope — "Clashes to Sync":

Analyzed clashes only (default) — clashes that went through matrix analysis
All clashes (including manually edited) — also includes clashes whose fields were edited by hand on the web

Filter by Tags (shown only when the set has tags): tick specific tags to restrict the sync to just those clashes, with Select all and Clear shortcuts.

Review the information panels: Clash Set Information (analysis status, completion date, total analyzed clashes), Analysis Statistics (clashes with vs. without matched rules), Priority Distribution and Status Distribution (in your matrix's configured colors), Top Contact Companies, and Top Matched Rules. If something looks wrong here, fix it on the web before syncing. You can also Print... this summary.

Step 3: Configure the Sync Settings

Under "Select what to synchronize to Navisworks:" — all options are on by default:

Sync Recommended Priority — a mapping panel, "Map ClashWiseAI priorities to Navisworks clash priorities:", lets you map each of your ClashWise priorities to Navisworks High, Medium, or Low. Takes effect on Navisworks 2026 and later only; on older versions the checkbox is visible but nothing is written.
Sync Recommended Status — map each ClashWise status to Navisworks New, Active, Reviewed, Approved, or Resolved via "Map ClashWiseAI statuses to Navisworks clash statuses:".
Sync Recommended Contact — writes to the clash's Assigned To field (Navisworks 2025 and later only). Choose which piece of contact information to write: Contact Name (default), Contact Email, or Company.
Add Sync Comment — writes the text in the Comment text: box as a new comment on every synced clash. Default: "Clash priority and responsible contact updated by ClashWiseAI". Edit it to anything you like.

Step 4: Choose which groups to create (if offered)

When the web has group changes waiting, a panel — "Clash groups to create in Navisworks" — lists them, all ticked. Each web group becomes one native Navisworks group per clash test it spans. Groups deleted on the web appear as "{name} — remove from model". Untick everything to skip group sync entirely. An optional checkbox, Include the clash test name in each group's name (off by default), prefixes group names for clarity.

Step 5: Run the sync

Click Sync to Navisworks. Progress shows "Syncing analyzed clashes to Navisworks..." with "Processing {x} of {y} clashes...", and briefly "Applying clash groups…" if groups are included. On completion: "Sync completed successfully!" with the tally "Updated: {X} clashes | Skipped: {Y} clashes".

Step 6: Verify in Clash Detective

Open Clash Detective, select a synced clash, and check its Status, Priority (2026+), Assigned To (2025+), and Comments. Web groups appear as native groups within their clash tests.

Undoing a sync

The entire sync is applied as a single Navisworks operation — press Ctrl+Z once to revert everything the sync changed. This is your safety net if the result isn't what you expected.

Skipped clashes and GUID matching

Matching is by clash GUID. A clash is counted as Skipped when no clash in the open document carries the same GUID — typically because models were reloaded, clash detection was re-run so results were regenerated, or you're in a different document than the one that published. There is no partial matching by title or position.

Practical rule: sync before major model changes. Once GUIDs change, those web-side decisions can no longer land on the model's clashes.

Tips

Keep the web as the source of truth. If you sync again later, the cloud data overwrites any manual edits made in Navisworks since the last sync — make adjustments on the web, then sync.
Only sync the fields you need — untick the rest to keep the model tidy and the sync fast.
Use the tag filter to sync one package of work at a time (for example, only clashes tagged for one trade).
Anyone with access to the set can sync it, but coordinate within the team: the last sync wins.