Clash Management in BIM is the structured process of reviewing, classifying, assigning, tracking, resolving, verifying, and closing coordination conflicts identified within a BIM model.
It begins after clashes are detected and continues until each relevant clash has been reviewed and either resolved, approved, or otherwise closed according to the project’s coordination requirements. Effective Clash Management helps BIM teams control large numbers of coordination issues instead of treating every detected clash as an isolated problem.
Clash Management: Quick Definition
| Item | Description |
|---|---|
| Term | Clash Management |
| Category | BIM Coordination |
| Meaning | The process of organizing, reviewing, assigning, tracking, resolving, and closing BIM clashes |
| Begins After | Clash Detection |
| Includes | Review, classification, prioritization, assignment, resolution, verification |
| Common Clash Types | Hard Clash, Soft Clash, MEP vs MEP Clash, MEP vs Structure Clash |
| Typical Users | BIM Coordinators, BIM Managers, MEP Engineers, Designers, Contractors |
| Common Outputs | Clash Reports, assigned issues, clash statuses, coordinated models |
| Final Goal | Verified and coordinated model with relevant clashes appropriately closed |
What Does Clash Management Mean?
Clash Management is broader than simply finding clashes.
BIM clash-detection tools can identify hundreds or thousands of potential conflicts, but those results still need to be reviewed before useful coordination decisions can be made.
A Clash Management process helps teams determine:
- whether a detected clash is genuine
- how important the clash is
- which discipline is responsible
- how the clash should be resolved
- whether the issue has been corrected
- whether the revised model introduces new conflicts
- whether the clash can be officially closed
The purpose of Clash Management is therefore to turn raw clash-detection results into an organized and traceable coordination workflow.
Why Is Clash Management Important?
Large BIM projects can generate significant numbers of clash results.
Without a structured Clash Management process, teams may face duplicate issues, unclear responsibilities, unresolved conflicts, repeated coordination discussions, or clashes being marked complete without proper verification.
Effective Clash Management helps project teams maintain a clear record of:
- what the problem is
- where it occurs
- who owns the issue
- what action is required
- what changes were made
- whether the solution has been verified
This makes coordination more systematic and easier to manage across multiple disciplines and model revisions.
Clash Detection vs Clash Management
Clash Detection and Clash Management are related but represent different stages of BIM coordination.
| Clash Detection | Clash Management |
|---|---|
| Identifies potential conflicts | Controls what happens after conflicts are identified |
| Focuses on finding clashes | Focuses on reviewing and progressing clashes |
| Produces clash results | Organizes, assigns and tracks clash results |
| May identify physical or clearance conflicts | Determines responsibility, status and resolution |
| Occurs earlier in the workflow | Continues until clashes are verified and closed |
A simple distinction is:
Clash Detection finds the problem.
Clash Management controls the problem through its lifecycle.
Clash Management vs Clash Resolution
Clash Management should also be distinguished from BIM Clash Resolution.
Clash Resolution is the process of modifying the affected model elements so that an identified conflict is appropriately addressed.
Clash Management includes the wider process surrounding that resolution.
For example:
Clash Management
→ identify the clash
→ review it
→ classify it
→ prioritize it
→ assign responsibility
→ resolve it
→ verify it
→ close it
Clash Resolution
→ specifically focuses on changing the model or coordinating the design solution.
So Clash Resolution is an important stage within the broader Clash Management workflow.
Main Stages of Clash Management
A typical Clash Management workflow can be represented as:
Clash Detection → Review → Classification → Prioritization → Assignment → Resolution → Rechecking → Verification → Closure
Each stage serves a different coordination purpose.
Clash Identification
Clash Management begins with clashes identified through a BIM Clash Detection process.
Teams may run clash tests between different disciplines or model categories, such as:
Mechanical vs Structural
Plumbing vs Electrical
Ducts vs Pipes
MEP vs Structural Framing
The clash-detection process creates an initial set of potential conflicts.
However, these results should not automatically be treated as confirmed coordination problems.
They first need to be reviewed.
Clash Review and Classification
After clashes are identified, BIM coordinators review the results to understand the type and significance of each issue.
Clashes may be classified according to factors such as:
- clash type
- discipline
- severity
- location
- system
- responsible team
- construction impact
- resolution status
Common clash classifications include:
Hard Clash — direct physical intersection between elements.
Soft Clash — insufficient required clearance between elements.
MEP vs MEP Clash — conflict between two building-services systems.
MEP vs Structure Clash — conflict between an MEP service and a structural element.
Proper classification helps teams manage similar conflicts together rather than treating every clash independently.
Clash Grouping and Prioritization
Clash-detection software may report multiple clash results that originate from the same underlying coordination problem.
For example, a large duct crossing several structural members may generate multiple individual clashes even though the root cause is one routing issue.
During Clash Management, related clashes may therefore be grouped together.
Clashes may also be prioritized based on:
- severity
- construction sequence
- system importance
- design impact
- site accessibility
- likelihood of creating further conflicts
Higher-priority clashes can then be addressed before less critical coordination issues.
Clash Assignment
Once a clash has been reviewed, it should be assigned to the appropriate person, discipline, or project team.
For example:
A duct vs beam clash may require coordination between the mechanical and structural teams.
A pipe vs cable tray clash may involve plumbing and electrical coordination.
A BIM coordinator may identify and manage the clash, while the responsible modeller or engineer makes the required design change.
Clear assignment helps prevent coordination issues from remaining unresolved because responsibility is unclear.
Clash Resolution
After assignment, the responsible team reviews the issue and determines how the clash should be corrected.
Possible resolution methods may include:
- moving an element
- changing elevation
- adding an offset
- introducing a bend
- rerouting a service
- modifying service spacing
- redesigning part of the system
- coordinating an approved opening or penetration where appropriate
The selected solution should consider engineering requirements, system connectivity, clearances, access, constructability, and surrounding model geometry.
Clash Tracking and Status Management
Clash Management requires teams to track the progress of each issue.
Different organizations may use different terminology, but common clash statuses can include:
New
The clash has been identified but not yet reviewed.
Reviewed
The clash has been checked and confirmed as relevant.
Assigned
Responsibility has been given to a person or discipline.
In Progress
The responsible team is working on the issue.
Resolved
A model change has been made to address the clash.
Ready for Verification
The team believes the clash has been resolved and is awaiting confirmation.
Closed
The resolution has been verified and no further action is required.
Approved / Accepted
The condition has been reviewed and intentionally accepted according to project requirements.
The exact status names can vary by project, software, and BIM execution plan.
Clash Verification and Closure
A clash should not necessarily be closed simply because an element has been moved.
The revised model should be checked to confirm that:
- the original conflict has been removed
- system connectivity remains correct
- required clearances are maintained
- no unacceptable new clashes were introduced
- the revised arrangement remains constructible
- relevant engineering requirements are satisfied
This verification stage is important because one model change can sometimes solve one clash while creating another.
Only after verification should the clash be considered complete.
What Is a Clash Report?
A Clash Report is a structured record of clashes identified during BIM coordination.
A clash report may include information such as:
- clash ID
- clash location
- involved model elements
- disciplines
- clash type
- screenshots
- assigned person or team
- comments
- status
- date identified
- resolution notes
Clash reports help teams communicate coordination issues and monitor their progress throughout the Clash Management process.
Common Clash Statuses
Clash statuses provide a simple way to understand where each coordination issue sits within the workflow.
A project may use statuses such as:
Open → Reviewed → Assigned → In Progress → Resolved → Verified → Closed
Some projects may also use statuses such as:
Duplicate
Approved
Not an Issue
Deferred
Accepted Condition
The status terminology should ideally be defined in the project’s BIM coordination procedures or BIM Execution Plan so that all disciplines interpret the statuses consistently.
Who Is Responsible for Clash Management?
Clash Management is usually a multidisciplinary responsibility.
The BIM Coordinator or BIM Manager often oversees the overall process by running clash tests, organizing clash results, assigning issues, and monitoring closure.
Individual engineering disciplines are generally responsible for reviewing and modifying their own model elements.
Depending on the project, responsibility may involve:
BIM Coordinator — manages clash identification, review, tracking, and coordination.
MEP Engineer or Modeller — reviews and resolves conflicts involving MEP systems.
Structural Engineer — reviews structural constraints and proposed changes involving structural elements.
Architect — reviews clashes involving architectural layouts and requirements.
Contractor or VDC Team — coordinates constructability and installation requirements.
The specific responsibilities should be defined within the project’s BIM Execution Plan or coordination procedure.
Clash Management in MEP Coordination
Clash Management is especially important in MEP Coordination because several systems frequently compete for limited space.
Mechanical, electrical, plumbing, fire-protection, architectural, and structural elements may all occupy common service zones.
Typical areas where clash management becomes important include:
- ceiling voids
- plant rooms
- service corridors
- risers
- shafts
- equipment rooms
- congested structural zones
A structured process helps BIM teams manage these conflicts in an organized manner rather than repeatedly reviewing the same issues during coordination meetings.
Can Clash Management Be Automated?
Parts of the Clash Management process can be automated or assisted by software.
Automation may help with:
- detecting clashes
- grouping similar clashes
- filtering results
- generating reports
- assigning issues
- updating statuses
- tracking changes
- identifying resolved clashes
- supporting automatic or semi-automatic clash resolution
However, engineering judgement may still be required for:
- determining design priority
- evaluating complex constraints
- approving structural changes
- assessing constructability
- accepting intentional conflicts
- deciding between multiple valid solutions
The most effective workflow therefore combines automated processing with appropriate human review.
How VAVETEK AI Relates to Clash Management
VAVETEK AI develops BIM technologies that support different stages of the clash-management workflow.
KlashBIM supports BIM clash detection and reporting, helping teams identify and organize coordination conflicts.
BAMROC supports automatic resolution of eligible clash scenarios using resolution strategies such as movement and bending.
HUBAROC supports engineer-controlled, semi-automatic resolution where human judgement is required to determine the preferred solution.
VERY EASY BIM supports broader MEP coordination workflows.
The overall process can be understood as:
Detect → Review → Manage → Resolve → Verify
Different tools may support different stages of this workflow, while engineers and BIM coordinators remain responsible for reviewing and validating project-specific decisions.
Frequently Asked Questions
What is Clash Management in BIM?
Clash Management is the structured process of reviewing, organizing, assigning, tracking, resolving, verifying, and closing coordination conflicts identified within BIM models.
What is the difference between Clash Detection and Clash Management?
Clash Detection identifies potential conflicts between model elements. Clash Management handles what happens after those conflicts are found, including review, assignment, tracking, resolution, and closure.
What is the difference between Clash Management and Clash Resolution?
Clash Resolution focuses on correcting an individual conflict by modifying the model. Clash Management is the broader process that controls the entire lifecycle of a clash from detection to closure.
What are the main stages of Clash Management?
The process typically includes detection, review, classification, prioritization, assignment, resolution, rechecking, verification, and closure.
Who manages BIM clashes?
BIM coordinators or BIM managers commonly oversee clash management, while individual disciplines review and resolve clashes involving their own model elements.
What is a Clash Report used for?
A Clash Report records coordination issues and may include clash IDs, model elements, screenshots, assignments, comments, statuses, and resolution information.
How are BIM clashes prioritized?
Clashes may be prioritized according to severity, construction impact, system importance, location, design constraints, or coordination sequence.
When should a clash be closed?
A clash should generally be closed after the proposed solution has been implemented and verified to confirm that the original conflict has been appropriately addressed.
Can Clash Management be automated?
Some stages can be automated, including detection, grouping, reporting, tracking, and supported clash-resolution workflows. Complex engineering decisions may still require human review.
Why is Clash Management important for MEP Coordination?
MEP projects can generate large numbers of conflicts across multiple systems. Clash Management helps teams organize these issues, assign responsibility, track progress, and verify resolutions before construction.