AI Clash Detection in Navisworks with Claude
Clash detection is one of the most valuable — and most tedious — jobs in BIM coordination. Running tests is quick; making sense of hundreds or thousands of results is not. AI clash detection puts Claude in the loop: it runs the ClashDetective tests in Navisworks, reads the results back, and helps you triage, group and report them in plain language. This guide covers the workflow and the real prompts behind it.
What "AI clash detection" means today
Navisworks already has a first-class clash engine — ClashDetective — that finds hard clashes, clearance clashes and duplicates between selections. What it doesn't do on its own is reason about the output: prioritise, group the repeats, tell you which clashes are real coordination problems versus modelling noise, and write it up.
That's where AI helps. HuskyBIM for Navisworks connects Claude Desktop to Navisworks Manage through the Model Context Protocol (MCP), exposing the clash tools (and 82 operations in total) to the AI. Navisworks still does the geometric clash test; Claude drives it and does the interpreting. The clash results are objective; the triage is where the assistant earns its keep.
The clash workflow, with prompts
A typical coordination pass looks like this.
Create a new clash test between the structural and mechanical disciplines, run it, and show me a summary of the results.Run the MEP vs structure clash test and summarise the top 10 by severity, telling me which building level each falls on.Look at the clash results and tell me which clashes look like the same duct crossing the same beam repeatedly, versus genuinely separate problems.Show all active clashes in the "Structure vs MEP" test and mark the ones between insulation and architectural finishes as reviewed.Isolate the elements involved in the worst clash, override their colour, save the view as a viewpoint, then export the clash report as HTML.Behind these prompts the connector is listing and creating ClashDetective tests, running them, reading summaries and paginated results, updating each result's status (New, Active, Reviewed, Approved, Resolved), and exporting the report — while also using viewpoint, selection and appearance tools to show you exactly where a clash sits.
Where AI adds the most value
- Triage at speed. A raw clash report of 1,900 items is unmanageable. Claude can summarise it by test, by level and by status so you focus on the coordination issues that matter.
- Grouping the noise. A single misaligned duct can throw dozens of clashes. Ask Claude to spot the repeats so you resolve the root cause once instead of clicking through each hit.
- Consistent status updates. Describe a category of false positive and have it marked reviewed or approved in bulk, keeping your clash matrix clean between coordination rounds.
- Faster reporting. Export the HTML report and have Claude draft the coordination summary that goes with it.
Honest limits
- Navisworks does the geometry. Claude does not invent a new clash algorithm — it runs ClashDetective and interprets the results. The clash accuracy is Navisworks' own.
- Navisworks Manage must be open with your federated model loaded, on Windows. Freedom and Simulate editions don't include ClashDetective and aren't supported.
- Running large tests is heavy. A big clash run takes real time and CPU — that's Navisworks, not the connector. Expect the same wait you'd get running it by hand.
- Verify before you act. Review status changes before you save, especially bulk updates. The AI's grouping is a helpful first pass, not a substitute for a coordinator's judgement.
Try AI clash detection — free
Create a free HuskyBIM account, install the Navisworks connector, open your federated model, and coordinate clashes in plain language.
Frequently asked questions
Does the AI actually run the clash test, or just explain how?
It runs it. HuskyBIM for Navisworks can list, create and run ClashDetective tests, read summaries and paginated results, update result status, and export the clash report as HTML — all against your open Navisworks model. The clash geometry engine is Navisworks itself; Claude drives it and helps you interpret the output.
Can it prioritise or group clashes for me?
Claude can read the full results and help you triage — summarise by test, count by status, surface the items that recur, and draft a coordination note. Navisworks assigns each clash a status (New, Active, Reviewed, Approved, Resolved) which the connector can read and update, so you can mark false positives resolved in bulk by describing them.
What Navisworks version do I need?
Navisworks Manage 2026 or 2027 — the Manage edition, because Freedom and Simulate do not include ClashDetective. HuskyBIM ships a build for each version.
Can it export a clash report?
Yes. It can export the ClashDetective report as HTML, and separately export element properties or a model summary to CSV, so you can hand off results or drop them into a coordination log.