ClashWise
ClashWise tools for Navisworks
Map the model data, create repeatable search sets and tests, organise and name the results, then publish a worklist the team can coordinate. When decisions are made, bring the supported fields back into Navisworks.
Navisworks Manage 2024, 2025, 2026, 2027 · 14-day trial · No card required
Navisworks runs the geometric clash tests. ClashWise helps prepare, organise, publish and coordinate the results. Design changes stay in the authoring tools.
01
Prepare the model
Start by showing ClashWise where useful identity, location and discipline data lives. Then turn the federation and a reviewed matrix into a repeatable coordination setup.
Identify the properties that represent an element’s name, ID, category, level, type, source and discipline. Reliable mappings improve titles, filters, locations and the coordination setup without changing the source model.
Explore Property Mapping
Download, select and test the local model before a large title run. Once set up, local title generation can run on the CPU without a per-title charge. Publishing, shared coordination and Wise remain cloud-connected.
See local title generation
Scan the model inventory, connect a matrix and review which search sets and clash tests will be new, updated, unchanged, conflicting or obsolete. Coordination Setup requires active or trial Pro or Business organisation access.
Explore the clash matrix02
Build and run the checks
Create reusable property-based selections, turn them into checks and run the tests that are ready. Complex tests remain available in Clash Detective when they cannot be simplified safely.
Combine property conditions, preview matching objects, check overlaps and save useful definitions as presets. Property-only sets stay dynamic; computed and hybrid location results save as static selection sets.
Create or edit supported names, saved-set selections, test types and tolerances. Run or update several tests in sequence, then hand selected results directly into Group Clashes.
03
Make the results usable
Group related results around the properties your project uses, then replace generic names with descriptions that make sense in a meeting, report or worklist.
Order rules for level, grid, system, category or another model property. Preview the hierarchy and reuse saved presets. Grouping organises the results; it does not decide whether a clash matters.
Choose the tests, naming format, language and output field. Generate titles for individual results, groups or both, then edit, reject or regenerate proposals before applying them.
Compare title formats04
Publish with confidence
Use the guided batch when several stages or destinations belong together. Keep the focused publish and context tools for smaller jobs.
Validate readiness, run or reuse tests, apply optional grouping and local titles, then create or update the chosen destinations. You start every run and keep control of scope, options and destinations.
The optional local-title stage uses local inference without cloud fallback. Local naming and cloud publishing check their plan access separately.
Select the finished clash tests, name the destination and publish their results with the supporting viewpoints, model properties and available location context. Use Update Clashes when that destination already exists.
Publish source models to a personal or organisation library, reuse unchanged versions and review replacements before attaching them. Context models support visual understanding; they do not replace the Navisworks federation.
See model and room review05
Coordinate and close the loop
Work through the published set beside the model, carry revised results into the same record and choose which agreed fields return to Navisworks.
Browse and filter the worklist, inspect details, show issues in the model, edit coordination fields and ask Wise for supported actions. Clash Workspace works with published data; Clash Detective still authors and runs native tests.
See Wise in Navisworks
Send the latest Navisworks results to an existing cloud clash set. Existing issues keep their identity where they can be matched, resolved results can be recognised and new results join the same coordination record.
Review the cloud changes, select the clashes and map supported status, priority, contact and comment fields. Sync does not change model geometry or rerun clash tests. Priority sync requires Navisworks 2026 or later.
Send completed Navisworks results to a new ClashWise destination.
Send the latest results to an existing coordination record.
Bring selected coordination fields from ClashWise back into Navisworks.
One ribbon, several ways to work
Not every project needs every tool. Start with local naming and grouping, prepare a complete setup, or use Run and Publish for a regular coordination issue. The focused commands remain available when you need one controlled action.
Starter includes local naming, Sets and Clashes and grouping. Pro and Business add the shared cloud workflow, Coordination Setup, publishing, analysis, Wise and sync.
Compare plans and pricingPractical questions
Start with a familiar federation and a small test scope you can verify.
No. Navisworks Manage 2024, 2025, 2026, 2027 runs the geometric clash tests. ClashWise prepares the checking structure and helps organise, publish and coordinate the results.
No. You start each run in the plug-in, choose its scope and destinations, and review its report. Saved choices reduce repeat setup; resuming after a supported failure also requires your action.
Local AI can generate titles on your computer after setup. Publishing, shared coordination, Wise and sync are cloud-connected workflows. Property Mapping is still required so local naming receives useful element data.
No. Preparation tools create or update Navisworks sets, tests, groups and clash text. Sync applies selected coordination fields to clash records. Geometry changes remain in the authoring tools.
Install the plug-in, map a familiar model and choose the first tool your project needs.