Updating Clash Sets

What updating does

Update pushes new and changed clash results from Navisworks into an existing clash set on the web, instead of creating a new one. The set keeps its clash numbers, share links, analysis results, and clash matrix connections — so your team's work carries forward across coordination rounds.

Use Update when:

The model has evolved and you've re-run your clash tests
You want to add new clash tests to a set that's already published
You want the web data refreshed to match the current state of the model

Before you start

The same requirements as publishing: sign in inside Navisworks, a Clash Management subscription (Pro or Business plan, or an active trial), the Full Suite plugin edition, and an open document with clash results. Update from the same Navisworks document you originally published from — clashes are matched by their identifier (GUID), so a different document won't match.

Where to find it

Ribbon tab ClashWiseAI → panel Clash Management → Update (keyboard: Alt+0).

How to update a clash set

Step 1: Pick the clash set

The Select Clash Set to Update window opens, headed "Select the clash set to add new or update clashes".

Each row shows the set's name, its clash count, a clickable clash-test count (click it to list the test names — handy for confirming you have the right set), when it was last updated, and how many users it's shared with.
Use the Project: filter to narrow the list (All projects, No project (private), or a specific project).
A set that is still processing shows a spinner and can't be picked yet — "Clash Set is still processing, check back later".
The link View and manage all available clash sets → opens your clash sets on the web.
Click Refresh to reload the list.

Step 2: Choose your update options

Once a set is selected, two options appear:

Include new Clash Tests — tick this to fold additional clash tests into the set. A panel lists the tests in your document that are not already part of the set, with a search box and Select All. If every test is already included you'll see: "All ClashTests in the current document are already included in the selected ClashSet."

Clash groups — this choice decides what happens when the grouping in your Navisworks model differs from grouping done on the web:

Keep groups created on the web (recommended) — the default. If a clash is grouped differently on the web and in Navisworks, the web grouping wins. Navisworks grouping still applies to clashes that were never regrouped on the web. Choose this when your team organizes clashes on the web — their work is preserved.
Overwrite web groups with Navisworks groups — the grouping in your Navisworks model replaces any grouping done on the web, including groups created or changed there. Choose this only when the model is your single source of truth for grouping — web-side grouping work will be lost.

Your choice is remembered for next time. Click Select Clash Set to continue.

Step 3: The grouping prompt (new tests only)

If the tests you are adding contain 100 or more clashes with more than 30% ungrouped, the Group before updating dialog appears — the same prompt as at publish, with Open grouping tool, Continue without grouping, and Cancel. A plain refresh of existing tests never triggers it.

Step 4: Confirm context models

The Publish context models picker appears with the models already published as context pre-ticked. Adjust the selection, or Skip (keep as is).

Step 5: Watch the progress

The Updating Clash Set: {name} window shows the same 8-step checklist as publishing, with a few differences:

The server step shows "Updating Clash Set on server... (Timeout: 15 minutes)" with a live countdown.
Levels and grids are re-uploaded, and the element-property index is refreshed for the whole set.
Viewpoint images are captured only for newly added tests — existing clashes keep their images ("Skipped — no newly added tests" otherwise).
Unless you chose Overwrite web groups with Navisworks groups, groups created on the web are synchronized back into the plugin's knowledge of the set at the end.

Step 6: Done

On success: "Clash Set '{name}' update successfully sent! An email will be sent when processing completes." You'll get an Open in web button — and if the set feeds one or more clash matrices, a Sync matrix in web button that deep-links to the set page so you can bring the matrix up to date with the new clashes.

What changes and what's preserved

Preserved across updates:

Clash numbers — existing clashes keep their permanent #N identity; new clashes get the next numbers
Share links, project sharing, and insight dashboards
Analysis results, manual edits, comments, tags, and due dates on existing clashes
Clash matrix assignment

Refreshed:

Clash data for the tests in the set (matched by clash GUID)
Levels, grids, and the element-property index
Context models, if you changed the selection

After adding many new clashes, re-run analysis on the web so the new arrivals get recommendations too — the web app marks analysis as stale when the underlying set has changed.

Tips

Update regularly during active coordination — after each model coordination cycle — rather than publishing a fresh set each time. History, numbers, and shares stay intact.
If a matrix is assigned, use the Sync matrix in web button after updating so new element classes are reflected in your matrix.
Sync your decisions back to Navisworks (see "Syncing Analyzed Clashes") before major model changes — re-running clash detection can change clash GUIDs, and changed GUIDs no longer match.

Troubleshooting

Timeouts ("Operation timed out. The update may still be processing on the server…"), "No valid clashes found to process.", and login prompts are covered in "Troubleshooting Publish and Sync".