Skip to main content
April 2, 2026Trevor Cornell/7 min read

Organizing Clash Reports in Navisworks: Grouping and Filtering Strategies

Master clash organization for efficient BIM coordination

Video Series Context

This tutorial builds upon previous lessons using the BIM361 complete model from Lesson 6, focusing specifically on clash organization techniques to create manageable and readable reports.

This lesson is a preview from our Revit MEP Certification Course Online (includes software & exam). Enroll in this course for detailed lessons, live instructor support, and project-based training.

Welcome back to the Navisworks video series. In this installment, we're launching a focused series on clash organization—a critical skill for any BIM professional managing complex coordination workflows. We'll be working with the BIM360 complete model located in the Lesson 6 folder. As you'll recall from our previous session, running clash detection batches on this model yielded significantly high clash counts—a common scenario in real-world projects that demands systematic organization.

The primary objective of clash organization extends beyond simple detection: it's about transforming overwhelming clash data into actionable intelligence. By strategically reducing visible clashes and creating streamlined, comprehensible reports, we enable project teams to prioritize resolution efforts effectively. Among the various organizational tools at our disposal, clash grouping stands as the most powerful for creating logical clusters of related issues. This video will focus primarily on mastering this essential technique, starting with our structural versus plumbing clash batch.

Begin by selecting the Structural versus Plumbing batch, then navigate to the Results tab to configure your visibility settings. Ensure your display matches the optimal configuration: Item 1 and Item 2 activated, with "Highlight All Clashes," "Dim Other," and "Transparent Dimming" all enabled. These settings provide the clearest visual context for clash analysis. Clash grouping serves multiple strategic purposes in professional workflows: it consolidates similar conflicts for efficient reporting, reduces visual clutter in complex models, and enables simultaneous viewing of multiple related clashes without overwhelming the display.

Understanding the behavior of the "Highlight All Clashes" function is crucial for effective clash management. When activated, this feature displays every clash within the selected batch simultaneously—useful for overall assessment but potentially overwhelming in dense conflict zones. Deactivating this option reveals only your currently selected clash, providing focused examination capabilities. An important limitation to note: when multiple clashes are selected, only the most recently chosen clash remains visible, regardless of your selection order. This behavior often surprises new users who expect all highlighted clashes to display simultaneously.

To overcome this limitation and view multiple specific clashes simultaneously, leverage the grouping functionality. Select your desired clashes using standard multi-selection techniques, then right-click and choose "Go to Group." This action creates a new group container that displays all enclosed clashes when selected. The newly formed group now functions as a single entity, allowing you to activate "Hide Other" for clearer visualization of grouped conflicts while eliminating model noise. This approach proves invaluable when conducting detailed analysis of related clash clusters.

Group management remains flexible throughout your workflow. Individual clashes can be removed from groups through drag-and-drop operations, or entire groups can be dissolved using the "Explode Group" command accessed via right-click. Once exploded, constituent clashes return to the root level of your clash batch, reverting to their original ungrouped state. This flexibility allows for iterative organization as your understanding of clash relationships evolves during the coordination process.

However, be aware of interaction limitations between visibility controls. When "Hide Other" and "Highlight All Clashes" are simultaneously activated, "Hide Other" takes precedence, overriding the global highlight function and displaying only your selected clash. This behavior, while logical from a software perspective, can initially confuse users expecting both functions to work in tandem.


A sophisticated workaround involves creating comprehensive groups to maintain visibility control without relying on "Highlight All Clashes." Select your entire clash set using Shift-click range selection, right-click, and create a group. This technique enables selective visibility of all grouped clashes even with "Highlight All Clashes" disabled, providing superior control over model element selection. This approach proves particularly valuable when working in "Dim Other" mode, where foreground model elements often obstruct access to target objects requiring selection.

Establishing a systematic naming convention enhances long-term project organization. Create an initial group for unprocessed clashes, naming it with an underscore prefix such as "_unsorted." This naming strategy ensures consistent positioning when sorting groups alphabetically, maintaining the unsorted group at either the top or bottom of your list regardless of ascending or descending sort order. This practice prevents confusion between your master unsorted group and newly created organizational groups, maintaining clarity in complex coordination scenarios.

Now let's examine practical clash resolution strategies using our structural versus plumbing model. Upon initial review, you'll notice numerous slab-related clashes—a common occurrence in multi-trade coordination. However, many of these represent acceptable conditions rather than actual conflicts requiring resolution. Vertical pipes penetrating slabs without pre-cut openings often fall into this category, particularly when the coordination effort required across multiple trades outweighs the minor nature of the conflict. Professional judgment plays a crucial role in determining which clashes warrant active resolution versus administrative acceptance.

To efficiently filter these acceptable clashes, utilize Navisworks' powerful selection and filtering capabilities. Access the Selection tool from either the View panel or the Home tab's Select and Search section. Systematically select each problematic slab using Ctrl+click for multi-selection. Once your target elements are identified, activate the Selection Filters—the key to refined clash analysis.

Selection Filters operate in two distinct modes, each serving specific analytical needs. "Exclusive" filtering displays clashes where both selected Item 1 and Item 2 elements are involved, requiring selection of components from both clash categories. "Inclusive" filtering shows clashes involving any selected element from either category, making it ideal for slab analysis since you're typically not selecting the penetrating pipes. Choose "Inclusive" for this slab-focused workflow to capture all relevant conflicts.

Upon filter activation, you won't immediately see changes in your clash batch display—filtered results appear only when you expand the containing group. The filtered clashes appear highlighted in gray, representing all slab-related conflicts based on your selection criteria. Note that fewer total clashes display with the filter active, as non-slab-related conflicts are temporarily hidden. This reduction demonstrates the filter's effectiveness in isolating specific clash categories for targeted analysis.


Transform your filtered results into organized groups using the established selection and grouping workflow. Select the first filtered clash, scroll to the final entry, Shift-click for range selection, then right-click and choose "Group." Assign a descriptive name like "okay_1" to prepare for potential additional "okay" categories. These grouped clashes will later receive appropriate status designations during the status management phase of coordination.

After creating your organized group, disable the filter to restore full clash visibility. You'll now observe a clear organizational structure: your "okay_1" group contains all slab-related clashes, while the "_unsorted" group houses remaining unprocessed conflicts. Notice that the displayed clash count reflects the number of groups rather than individual clashes—this represents your working organizational count, not the final resolution tally.

Continue the organization process by identifying patterns among remaining clashes. Look for recurring conditions such as steel beam conflicts that share similar characteristics across different building levels. These repetitive clashes often indicate systematic design issues where a single coordinated solution can resolve multiple conflicts simultaneously. For instance, four similar steel beam clashes might be grouped together, as adjusting pipe elevation could potentially resolve the entire cluster. Additionally, isolated similar conditions can form separate groups, as they may require distinct resolution approaches despite sharing geometric characteristics.

Implement this pattern-based grouping using the same selection and filtering methodology. Use the Selection tool to identify related structural elements, activate "Inclusive" filtering, select all affected clashes, and create appropriately named groups such as "group_1" for the first cluster. Remember to deactivate filters between operations to ensure clear visibility when selecting your "_unsorted" group for subsequent analysis. Continue this process for additional clash patterns, creating "group_2" and beyond as needed.

Be prepared for occasional filter-related prompts from Navisworks. When selecting groups while filters remain active, the software may detect no matching clashes within that group and offer to remove the filter automatically. Accepting this prompt simply resets the filter to "none" and allows normal operation to continue—this is standard behavior and requires no concern.

As we conclude this section of our clash organization workflow, take a moment to save your progress. Store your file in the Lesson 4 directory to maintain proper version control and project organization. You may choose to keep the file open for immediate continuation or close and reopen it for the next video segment. In Part Two, we'll advance to status management, resolution strategies, and report generation—essential skills for completing the professional clash coordination workflow. This systematic approach to clash organization forms the foundation for efficient project coordination and successful BIM implementation across complex multi-trade projects.


Key Takeaways

1Clash grouping reduces the number of visible clashes and creates manageable, easy-to-read reports for project stakeholders
2Use '_unsorted' as a master group name with underscore prefix to maintain organization and ensure proper alphabetical sorting
3Inclusive filters work best for element-based selection, while Exclusive filters require both clash items to be selected
4Acceptable clashes like vertical pipes through slabs should be grouped separately and marked appropriately to focus on critical issues
5The 'Hide Other' option overrides 'Highlight All Clashes', but groups provide an effective alternative for selective clash display
6Similar clash conditions across different floors or areas should be grouped together since resolving one often provides the solution for others
7The dynamic clash count shows groups rather than individual clashes during organization, serving as a working count rather than final tally
8Regular saving during the organization process is essential, especially when working with complex models and multiple clash batches

RELATED ARTICLES