Publishing Clash Sets

What publishing does

Publishing sends selected clash test results from Navisworks Clash Detective to clashwise.ai as a new clash set. Along with the clash data itself, the plugin uploads per-clash viewpoint images, per-clash 3D captures, level and grid location context, optional ghosted 3D context models, and an index of element properties — everything the web app needs for analysis, triage, the 3D viewer, and reporting.

Before you start

Run your clash tests in Navisworks Clash Detective so they contain results.
Sign in to ClashWise in Navisworks (the ClashWiseAI ribbon tab).
You need a Clash Management subscription — the Pro or Business plan, or an active trial.
You need the Full Suite plugin edition. If you installed the Starter edition, the plugin shows a Plugin Not Found message and directs you to download the full version from https://clashwise.ai/download.
Save your Navisworks file first — the file name is used to build the default clash set name.
Tip: group your clashes before publishing (ribbon Clashes → Group Clashes). Grouped sets are far easier to triage on the web, and ClashWise will prompt you if a large selection is mostly ungrouped.

Where to find it

Ribbon tab ClashWiseAI → panel Clash Management → Publish (keyboard: Alt+9).

How to publish a clash set

Step 1: Select the clash tests

The Publish Clash Results as Clashset window opens.

The grid lists every clash test in your document, with columns Clash Test, Type of Test, Total Issues, and Information. Use the Search clash tests box to filter.
Tick the clash tests you want to include. You can select several — they all become part of one clash set.
(Optional) Open the Project tab to share the new set with a project. The dropdown under "Share this clash set with a project" defaults to None (private) — visible only to you. Pick a project, or click + New project to create one on the spot. Refresh reloads the project list.
Click Select to continue (or Cancel to abort). If nothing is ticked, the plugin reminds you: "Please select at least one clash test."

Step 2: The grouping prompt (if it appears)

If your selection contains 100 or more clashes and more than 30% of them are not in any group, the Group before publishing dialog appears. It shows how many clashes are ungrouped and explains why grouping helps: you can triage status, priority, and owner for a whole group at once, hand a single group to the responsible team, and open groups reliably in the 3D viewer.

Open grouping tool (recommended) — opens the Group Clashes window. When you finish grouping, publishing continues automatically if enough clashes are now grouped.
Continue without grouping — publishes as-is.
Cancel — aborts the publish.

Step 3: Choose context models

The Publish context models window lists each appended model in your document. Ticked models are published as ghosted 3D context around your clashes in the web viewer (geometry is simplified to fit a web-friendly size).

Publish selected — uploads the ticked models as context.
Skip (keep as is) — keeps whatever context is already published for this set.

You can change this selection on any future publish or update. Context upload is best-effort — if it fails, the clash set itself still publishes successfully.

Step 4: Watch the progress

The Creating Clash Set window shows an 8-step checklist ticking off as the publish runs:

Select context models
Collect clash data — "Processing clashes: {x}/{y}"
Upload clashes to the cloud — very large sets continue processing server-side: "Clash Set creation is running in the background. You will receive an email notification upon completion."
Publish levels and grids — may report "No grid data found in model" if your model has no grids
Publish context models
Capture and upload viewpoints — the per-clash images and 3D captures
Upload element properties — powers advanced property filtering on the web
Finalize clash set

You can click Cancel mid-run; the button becomes Close when the operation finishes.

Step 5: Open your new set

On success you'll see "Clash Set created successfully!" with an Open in web button that takes you straight to the new set at clashwise.ai.

What happens next

The set appears on the web under Clash Sets, with every clash given its permanent number (#1, #2, …), viewpoint images, the 3D viewer, and searchable properties.
ClashWise starts processing the set automatically (viewpoint images, locations, and searchable properties). AI analysis is a separate step you run on the web: assign a clash matrix to the set and click Run analysis to get recommended priorities, statuses, and responsible contacts — see the Clash Matrix section for how to create and assign a matrix.
Level and grid locations are computed shortly after publishing finishes — if the Location column looks empty at first, refresh after a couple of minutes.
If you shared the set with a project, project members can see and work on it immediately.

Options and settings

Viewpoint and 3D capture are on by default. They are what make per-clash images and the multi-clash 3D viewer work on the web. If capture was disabled, step 6 shows "Skipped — disabled in settings", and the set won't offer 3D viewing until it is re-published with capture on.
Default set name — "{model file name} Clash Set - {date and time}". You can rename the set later on the web.
Project sharing — defaults to None (private). You can also move a set into a project later from the web.

Tips

Give clash tests meaningful names in Navisworks before publishing — they carry through to the web.
Publish only the tests you need. You can publish different tests to different sets (for example, one set per discipline pair or per building area) and keep other tests local.
Group first. The grouping prompt exists because ungrouped 1,000-clash sets are painful to work with anywhere.
For very large publishes, let the background processing finish — you'll get an email when the set is ready.

Troubleshooting

Common messages ("Failed to start Clash Set creation…", "No valid clashes found to process.", long-running publishes) are covered in "Troubleshooting Publish and Sync".