Skip to main content
April 2, 2026/8 min read

Performing Electrical and HVAC Model Clash Detection in Revit

Master BIM coordination through automated clash detection workflows

Why Clash Detection Matters

Identifying spatial conflicts between building systems before construction prevents costly field changes and project delays. This proactive approach saves time, money, and ensures coordinated installation.

Key Building Systems for Clash Detection

Electrical Systems

Lighting fixtures, power equipment, switches, and receptacles that require precise spatial coordination with other building components.

HVAC Systems

Air terminals, supply and return systems that often compete for ceiling space with electrical and other MEP systems.

Structural Elements

Beams, columns, and other structural components that create fixed constraints for MEP system routing.

Setting Up Effective Clash Detection

1

Navigate to Collaborate Tab

Access the Interference Check tool from Revit's Collaborate tab to begin the clash detection process.

2

Select Specific Categories

Choose focused categories like Lighting Fixtures from current project to compare against linked model categories like Air Terminals.

3

Run Targeted Analysis

Execute interference check between selected categories to generate manageable, actionable clash reports.

Best Practice: Start Small

Fewer categories in clash detection create more manageable reports. Begin with specific comparisons like lighting fixtures to air terminals rather than checking all categories simultaneously.

Clash Resolution Strategies

FeatureSelf-ResolveCoordinate with Team
Minor OverlapsAdjust your model elementsDocument for awareness
Significant ConflictsLimited optionsEngage other disciplines
Modeling ErrorsQuick local fixesShare corrections needed
Design IssuesCannot resolve aloneFormal coordination required
Recommended: Reserve team coordination for significant conflicts that cannot be resolved through minor adjustments.

Clash Detection Workflow Checklist

0/5
Show Button Limitations

The Show button in clash detection can be unreliable. If it doesn't work, rerun the interference check. Manual selection of individual clashes often provides more consistent results.

HTML Report Export Benefits and Limitations

Pros
Creates permanent documentation of clash status
Enables before-and-after comparison tracking
Provides unique Revit IDs for precise element identification
Facilitates communication with other discipline teams
Cons
Limited descriptive information about clash nature
Requires knowledge of Revit ID system for effective use
Basic formatting may not convey clash severity
Manual interpretation needed for prioritization

Using Revit IDs for Clash Communication

1

Copy ID from Report

Extract the numeric Revit ID code from the HTML clash report for the specific conflicting element.

2

Navigate to Select by ID

Go to Manage tab, find Inquiry section, and select the Select by ID tool for precise element location.

3

Paste and Locate

Paste the copied ID and use Show button to automatically zoom to the conflicting element in the model.

Clash Detection Limitations

Automated clash detection may miss obvious conflicts due to element positioning or shared edges. Always perform visual verification alongside automated reports to ensure comprehensive conflict identification.

Complete Clash Detection Process

Start

Initial Setup

Configure interference check with specific categories and linked models

Step 1

Generate Before Report

Export baseline HTML report showing all detected clashes

Step 2

Resolve Conflicts

Address clashes through element adjustment and team coordination

Final

Export After Report

Document resolved clashes and remaining coordination items

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.

With our comprehensive electrical model now complete in Revit, we have built a detailed digital environment populated with lighting fixtures, power equipment, switches, and receptacles. This rich dataset becomes invaluable when we need to identify potential conflicts between building systems—a critical quality control step that can save thousands of dollars in construction rework. The real power emerges when we compare our electrical model against other disciplines, particularly HVAC systems where spatial conflicts are most common.

Let's examine this process through a practical example by analyzing how electrical and HVAC components interact in our model. We'll start by navigating to the project browser to access our lighting plan.

Navigate to the ceiling plans section in your project browser and locate the L2 lighting plan. Double-click to open this view, which displays our complete lighting layout for the second level.

Focus your attention on classroom 5004 by zooming into the upper portion of the plan. Here you'll observe our carefully modeled lighting fixtures alongside air terminals from the linked HVAC model. Notice how the HVAC elements—including one return air terminal and two supply terminals—appear as reference objects from the linked model, allowing us to see the complete picture of ceiling-mounted systems.

While these elements appear well-coordinated at first glance, apparent clearances in plan view can be deceiving. Let's intentionally create a conflict to demonstrate the clash detection process. Select one of the lighting fixtures and drag it until it overlaps with an air terminal, creating an obvious spatial conflict.

This deliberate overlap represents exactly the kind of coordination failure that costs projects time and money during construction. When two building systems attempt to occupy the same physical space, field crews must halt work, coordinate with multiple trades, and often redesign solutions on-site—a scenario that's both expensive and time-consuming. Revit's built-in interference detection tools help us identify and resolve these conflicts during the design phase when changes are still cost-effective.

The interference check will identify our intentionally created clash along with any other conflicts that may exist in the model. Keep in mind that your results will differ from this example since each model contains unique element placements and potential conflict points.

To execute the interference check, navigate to the Collaborate tab and select the Interference Check tool. This launches Revit's coordination analysis engine.

A key strategy for effective clash detection involves starting with focused, targeted comparisons rather than broad, comprehensive checks. While it's tempting to analyze all categories simultaneously, this approach typically generates overwhelming reports filled with insignificant conflicts that obscure genuine coordination issues. Instead, begin with specific category pairs that are most likely to conflict.

In the interference check dialog, start by selecting categories from your current project. Choose "Lighting Fixtures" from the available options—be careful not to select "Lighting Devices," which refers to switches and controls that rarely generate meaningful clashes due to their small size and wall-mounted locations.

For comparison, select the linked HVAC model from the dropdown menu and check the "Air Terminals" category. This focused approach examines ceiling-mounted electrical fixtures against HVAC terminals—the most common source of coordination conflicts in modern building projects. Click "OK" to generate the interference report.

Before exploring the results, note the interface options available. The "Show" button can highlight conflicts in the model view, though this feature has historically been unreliable in Revit and may require multiple attempts to function properly.


Instead of relying on the Show button, focus on the "Export" function, which creates a permanent record of all detected conflicts. This HTML report becomes a valuable coordination document that can be shared with other team members and serves as a tracking mechanism for conflict resolution progress.

Click "Export" to save your interference report. Use a systematic naming convention such as "BIM323_Interference_Report_[YourName]_Before" to clearly identify this as the initial analysis before any corrections. This naming strategy becomes essential when managing multiple coordination cycles throughout a project.

The exported HTML file provides a structured list of all detected conflicts with unique identification numbers for each clash. While the format appears basic, this report contains critical information for coordination workflows.

The report shows the total number of conflicts detected between your selected categories. This baseline establishes the scope of coordination work required and provides a benchmark for measuring resolution progress.

Return to Revit to begin resolving the identified conflicts. While the Show button remains problematic, you can manually select individual interferences from the list to highlight them in the model view. Selected conflicts appear in orange, making them easily identifiable against the standard model graphics.

When analyzing conflicts, distinguish between genuine coordination issues and minor modeling inconsistencies. Some conflicts result from imprecise modeling practices where elements barely overlap—these typically require simple adjustments to one component or the other. However, significant overlaps often indicate fundamental coordination problems that require communication with other disciplines.

For minor conflicts where elements slightly overlap, adjust your electrical components to maintain proper clearances. Remember that you should only modify elements within your discipline—never alter linked model components, as these changes won't propagate back to the source model and may create confusion in the coordination process.

After resolving a conflict by moving a fixture, click the "Refresh" button in the interference check dialog to update the analysis. Successfully resolved conflicts will disappear from the list and the affected elements will return to their normal display colors.

Continue systematically through each identified conflict, making decisions about which issues you can resolve independently versus those requiring coordination with other disciplines. Significant overlaps or conflicts involving critical system components typically warrant communication with the relevant engineering teams.

For better visualization during conflict resolution, enable "Thin Lines" from the view control bar. This display option reduces line weights throughout the model, making overlapping elements easier to distinguish and improving your ability to identify precise conflict locations.

Document your decision-making process as you work through each conflict. Some clashes represent genuine coordination issues that require engineering input, while others may result from modeling precision or represent acceptable tolerances in construction practice.


It's important to understand that Revit's clash detection isn't infallible. The system occasionally misses obvious conflicts or flags acceptable conditions as problems. Geometric complexity, element positioning relative to different work planes, and modeling approaches can all influence detection accuracy.

To verify potential missed conflicts, consider creating section views through suspected problem areas. These views reveal vertical relationships that may not be apparent in plan view and can expose conflicts that the automated system overlooked.

For example, if a lighting fixture appears to conflict with an air terminal in plan view but doesn't register as a clash, a section view might reveal that the elements exist at different elevations—perhaps with the light fixture properly positioned below the ceiling plane while the air terminal occupies the ceiling cavity above.

This three-dimensional complexity highlights why manual verification supplements automated clash detection rather than replacing professional judgment in coordination workflows.

Once you've addressed all feasible conflicts, generate an updated interference report using the same export process. Name this file with an "_After" suffix to distinguish it from your initial analysis.

The "after" report demonstrates your coordination progress and identifies remaining conflicts that require interdisciplinary communication. This documentation becomes particularly valuable during design team meetings and coordination sessions.

While the HTML reports may appear simplistic, they contain sophisticated identification codes that streamline coordination workflows. Each clash includes unique Revit element IDs that allow team members to quickly locate specific problematic components within complex models.

To locate elements by ID in Revit, navigate to the Manage tab and select "Select by ID" from the Inquiry panel. Copy the element ID from your clash report and paste it into this dialog. Revit will automatically locate and highlight the specified element, even in models containing thousands of components.

This ID-based workflow enables efficient communication with other disciplines. Rather than trying to describe conflict locations verbally or through screenshots, you can simply reference specific element IDs in coordination communications. The receiving team member can instantly locate the problematic component in their model using the same Select by ID process.

The combination of systematic clash detection, focused resolution efforts, and clear documentation creates a robust coordination workflow that significantly reduces construction conflicts while maintaining design intent across all building systems.

You've now completed a comprehensive clash detection and resolution cycle that demonstrates industry-standard BIM coordination practices. This process forms the foundation for professional-quality model coordination and sets the stage for producing coordinated construction documentation. With your electrical model properly coordinated against other building systems, you're ready to finalize your drawing set with confidence in the accuracy and constructability of your design.


Key Takeaways

1Focus clash detection on specific category comparisons rather than comprehensive checks to create manageable, actionable reports
2Use Thin Lines view to improve visibility when identifying and resolving spatial conflicts between building systems
3Resolve minor modeling discrepancies locally while flagging significant conflicts for interdisciplinary coordination
4Export before-and-after HTML reports to document clash resolution progress and communicate with team members
5Leverage Revit ID codes from clash reports to enable precise element identification across different discipline models
6Understand that automated clash detection has limitations and may miss obvious conflicts requiring manual verification
7Only modify elements owned by your discipline; coordinate with other teams for changes to their linked model elements
8Use the refresh function after making changes to verify clash resolution and update interference counts in real-time

RELATED ARTICLES