Clash grouping for Navisworks
Collapse thousands of clash hits into reviewable assemblies.
Productivity Toolbox groups clashes by element, system, zone, or any custom property. A Friday of sorting becomes a coordination meeting you can run.
Before and after
A coordination Friday, rewritten.
Same federated model, same clash tests. The difference is what happens after the clash run finishes.
Before
- Raw clash output
- ~2,000 hits
- Duplicates after model updates
- ~40% noise
- Manual grouping effort
- 4 to 6 hours per run
- Result shared with trades
- by Monday, if lucky
With Productivity Toolbox
- Grouped by element or system
- ~200 assemblies
- Duplicates collapsed automatically
- noise eliminated
- Grouping time
- under a minute
- Result shared with trades
- the same afternoon
How it works
Three steps, one pass.
Clash grouping inside Productivity Toolbox reads from the standard Clash Detective. Your tests and tolerances do not change.
- 01
Point at a property
Level, system, zone, custom text property, Revit family, or any property the coordination logic depends on.
- 02
Run the grouping
Productivity Toolbox walks every clash and groups by that property. The operation is reversible. Your original clash results are untouched.
- 03
Rename and export
Auto-rename groups by status, test name, custom prefix, or tolerance. Export to image, HTML, or Excel.
Return on investment
$59 per month pays for itself the first Friday.
- Coordinator hourly rate
- $35 to $50
- Hours per week recovered
- 5 to 10
- Monthly value recovered per coordinator
- $750 to $2,150
- Monthly subscription
- $59
Based on typical coordinator salaries in the US, UK, and Australia.
Questions
What coordinators ask before they trial.
Does this change how I configure clash tests in Navisworks?
What happens to grouped results when the federated model updates?
Does it support Navisworks 2026?
How is it licensed?
Try it on your next coordination run.
30 days, unrestricted. Installs from the Autodesk App Store in one click.