What Is a Hard Clash in BIM?

A Hard Clash is a physical conflict in a Building Information Model (BIM) where two or more model elements occupy the same space. It occurs when the geometry of one building component directly intersects another, such as a pipe passing through a structural beam or a duct crossing a cable tray.

Hard clashes are commonly identified during BIM clash detection and must be reviewed and resolved before construction wherever they represent a genuine design or coordination conflict.

Hard Clash:

Item Description
Term Hard Clash
Category BIM Clash Detection
Meaning A physical intersection between two or more BIM elements
Typical Examples Pipe vs beam, duct vs pipe, cable tray vs structural element
Detected During BIM Clash Detection
Common Disciplines MEP, Structural, Architectural
Next Stage Clash Review and BIM Clash Resolution
Typical Users BIM Coordinators, MEP Engineers, Designers, Contractors

What Does Hard Clash Mean in BIM?

A hard clash occurs when the physical geometry of two model elements intersects.

In simple terms, two building components are trying to occupy the same physical location.

For example, if a plumbing pipe passes directly through a structural beam without an approved opening, both elements cannot be constructed in their current positions.

This creates a hard clash.

Hard clashes are among the most straightforward types of BIM conflicts to identify because they are based on direct geometric interference.

However, determining the correct solution may still require engineering judgment.

Examples of Hard Clashes

Hard clashes can occur between different building disciplines.

Common examples include:

A hard clash does not automatically indicate which element should move.

The coordination team must determine the appropriate resolution based on system requirements, available space, structural restrictions, and constructability.

What Causes Hard Clashes?

Hard clashes commonly occur when different building systems are designed independently and later combined into a coordinated BIM model.

Typical causes include:

Separate Discipline Models

Architectural, structural, mechanical, electrical, plumbing, and fire-protection teams may develop their models independently.

When the models are combined, elements from different disciplines may intersect.

Limited Coordination Space

Areas above ceilings, inside service shafts, plant rooms, corridors, and risers often contain many building services within limited space.

This increases the possibility of physical conflicts.

Design Changes

A change made by one discipline may create a new clash with another system that had already been coordinated.

Incorrect Routing

Services may be routed through structural or architectural elements without sufficient consideration of the surrounding model.

Model Updates

A revised structural, architectural, or MEP model may introduce clashes that did not exist in an earlier coordination version.

How Is a Hard Clash Detected?

Hard clashes are typically identified using BIM clash detection.

Clash-detection software compares the geometry of selected model elements or disciplines and identifies locations where physical intersections occur.

For example, a clash test may compare:

Mechanical ductwork vs Structural model

or:

Plumbing systems vs Electrical containment

The software can then identify instances where elements physically overlap.

A typical clash-detection workflow includes:

  1. Combine or review the relevant discipline models.

  2. Select the systems or model categories to compare.

  3. Define clash-detection settings.

  4. Run the clash test.

  5. Review identified hard clashes.

  6. Classify genuine conflicts and false positives.

  7. Assign clashes for coordination or resolution.

For a broader explanation, see BIM Clash Detection in the VAVETEK AI BIM Glossary and Clash Detection Guide.

Hard Clash Example: Pipe vs Structural Beam

Consider a plumbing pipe routed through a structural beam.

The pipe and beam occupy the same physical space, creating a hard clash.

The clash may be resolved in different ways depending on the project’s engineering requirements.

Possible solutions could include:

The appropriate solution should be determined through coordination between the relevant engineering disciplines.

Simply identifying the intersection does not determine the correct resolution.

Hard Clash vs Soft Clash

A Hard Clash and a Soft Clash represent different types of BIM coordination problems.

Hard Clash Soft Clash
Elements physically intersect Elements may not physically intersect
Based on direct geometric overlap Usually based on required clearance
Example: pipe through a beam Example: equipment lacks maintenance clearance
Usually easy to identify geometrically May require predefined clearance rules
Requires removal of the physical conflict Requires restoration of required clearance

For example:

A pipe physically crossing a beam is a Hard Clash.

A pipe located too close to equipment to allow maintenance access may be a Soft Clash, even though the two objects do not physically intersect.

Related term: Soft Clash →

Hard Clash vs Clearance Clash

A hard clash means two objects actually overlap.

A clearance clash occurs when the objects may remain physically separate but violate a required distance.

For example:

Hard Clash

A duct physically intersects a cable tray.

Clearance Clash

The duct and cable tray do not touch, but the space between them is insufficient for installation, insulation, maintenance, or another required clearance.

Understanding this distinction helps BIM coordinators classify issues more accurately.

MEP vs MEP Hard Clash

An MEP vs MEP hard clash occurs when two building-services elements physically intersect.

Examples include:

These clashes are common in congested service zones where several systems must share limited routing space.

Resolution may require moving, bending, or rerouting one of the affected services.

MEP vs Structure Hard Clash

An MEP vs Structure hard clash occurs when an MEP element physically intersects a structural component.

Examples include:

Because structural elements often have less routing flexibility than MEP services, the building service may need to be adjusted.

However, every resolution should follow the project’s engineering and coordination requirements.

How Are Hard Clashes Resolved?

After a hard clash has been identified, the next stage is BIM Clash Resolution.

Depending on the conflict, the resolution may involve:

The objective is not merely to make the geometric intersection disappear.

The revised solution should also consider:

After the modification, the model should be checked again to confirm that the original clash has been resolved without creating unacceptable new conflicts.

Can Hard Clashes Be Resolved Automatically?

Some hard clashes can be resolved automatically when software can determine the affected elements, available routing space, allowable movements, required clearances, and appropriate resolution strategies.

For example, supported MEP clashes may sometimes be resolved through:

However, not every hard clash is suitable for automatic resolution.

Clashes involving complex geometry, major structural changes, unusual engineering conditions, or project-specific constraints may require human review.

Hard Clashes in BIM Coordination

Hard clash detection is only one stage of the BIM coordination process.

A simplified workflow is:

Model Creation → Model Coordination → Clash Detection → Hard Clash Identification → Clash Review → Clash Resolution → Rechecking → Coordinated Model

This distinction is important because detecting a hard clash does not mean that the coordination issue has been solved.

The clash must still be reviewed and appropriately resolved.

Why Are Hard Clashes Important?

Identifying hard clashes before construction can help project teams:

Hard clashes are therefore one of the fundamental issues addressed during BIM coordination.

How VAVETEK AI Relates to Hard Clash Workflows

VAVETEK AI develops BIM technologies that support different stages of clash coordination.

KlashBIM focuses on BIM clash detection and helps identify coordination conflicts such as hard clashes.

After clashes have been identified, HUBAROC supports engineer-assisted clash-resolution workflows, while BAMROC is designed to automatically resolve supported BIM clash scenarios using resolution strategies such as movement and bending.

These stages can be understood as:

Detect → Review → Resolve → Verify

Frequently Asked Questions:

What is a Hard Clash in BIM?

A Hard Clash is a physical conflict where two or more BIM elements occupy the same space, such as a pipe intersecting a structural beam.

What is an example of a Hard Clash?

A common example is an HVAC duct passing through a structural beam or a pipe physically intersecting a cable tray.

What causes Hard Clashes?

Hard clashes can result from independently developed discipline models, limited coordination space, design changes, incorrect routing, or updated models that introduce new physical conflicts.

How are Hard Clashes detected?

Hard clashes are commonly identified using BIM clash-detection software that compares model geometry and finds physical intersections between selected elements or systems.

What is the difference between a Hard Clash and a Soft Clash?

A Hard Clash involves a direct physical intersection. A Soft Clash generally occurs when required clearance between elements is insufficient even though they do not physically overlap.

Can Hard Clashes be automatically resolved?

Some supported hard clashes can be automatically resolved using movement, bend, or rerouting strategies. Complex cases may still require engineering review.

Are all physical intersections genuine Hard Clashes?

Not necessarily. Some intersections may be intentional, approved, or irrelevant depending on project requirements. Clash results should therefore be reviewed before being treated as coordination issues.

What happens after a Hard Clash is detected?

The clash is reviewed to determine whether it is genuine, assigned to the appropriate discipline, resolved through a suitable model modification, and then rechecked.