Not every clash-detection hit means two objects actually occupy the same space — and treating them as if they do misses two entirely different kinds of real problems.
Ask most coordination teams what a "clash" is and they'll describe two solids literally occupying the same 3D space — a duct punched straight through a beam. That is a real category, and it is the one automated clash-detection software is built to find first. But BIM coordination practice recognizes two other kinds of conflict that never show up as a geometric intersection at all: one is about violated clearance, the other is about violated time. All three get called "clashes." Only one of them is caught by checking geometry alone.
A hard clash is a genuine, literal overlap between two modeled elements' actual geometry — a structural beam and a duct occupying the exact same coordinates. If built exactly as designed, it is physically impossible. A soft clash (also called a clearance clash) is not a geometric overlap at all — it is a violation of a required minimum buffer zone around an element, such as the code-mandated clear working space in front of an electrical panel, the insulation clearance a pipe needs, or the access space ductwork needs for future maintenance. The objects themselves never touch; the design still violates a real requirement. A workflow clash (also called a 4D or sequencing clash) is not spatial at all — it is a conflict in the construction schedule, where two activities are planned to occupy the same physical zone during overlapping windows of time, even though their final as-built geometry never overlaps.
Standard automated clash detection runs a Boolean intersection test between element solids — it asks "do these two shapes share any coordinates?" That question is exactly what a hard clash is, which is why software finds hard clashes reliably and by default. A soft clash never trips that test, because the objects genuinely don't intersect — catching it requires someone to explicitly model the required clearance envelope (the code-mandated working space, the insulation buffer, the access zone) as its own volume and run the same intersection test against thatvolume instead of the equipment itself. Skip that modeling step and the clearance violation is invisible to the software, no matter how thorough the hard-clash run was. A workflow clash sits in an entirely different dimension: it isn't about where things are, it's about when construction activities occupy a zone. Finding it requires linking the 3D model to 4D schedule data and simulating the sequence — a separate analysis discipline (4D coordination) that many teams never run at all, or run only for major milestones rather than every trade handoff.
False, and dangerously incomplete. Standard geometric clash detection — the default report most teams run and circulate — primarily catches hard clashes: actual solid-to-solid overlaps. It does not automatically catch soft clashes, because a clearance violation isn't a geometry overlap at all — finding one requires explicitly modeling or checking required clearance zones as their own objects, a separate modeling step most teams skip unless it's built into their coordination standard. It also does not catch workflow/4D clashes, because those require combining the model with construction schedule data and simulating the sequence — an entirely separate analysis that a geometry-only clash run never performs. A model that passes a hard-clash-only check with a zero-conflict report can still have serious code-clearance violations sitting in front of every panel and unbuildable trade sequencing baked into the schedule. "Zero hard clashes" means exactly one thing: no two solids currently overlap. It says nothing about clearance and nothing about time.
Explains why 'clash' in BIM coordination actually covers three distinct problems — a literal geometric overlap (hard clash), a violated required clearance zone with no geometry overlap at all (soft clash), and a construction-schedule sequencing conflict with no spatial overlap at all (workflow or 4D clash) — and why a standard automated clash report only reliably catches the first one.
Most people picture a clash as two solids visibly punched through each other, because that's the case automated clash-detection software is built to find by default: a Boolean intersection test between element geometry. That default report gets treated as a complete conflict check, when it is really only testing one of three separate conditions coordination teams care about. Soft clashes and workflow clashes exist precisely because 'no two objects overlap' does not mean 'nothing is wrong.'
A hard clash is a genuine physical overlap between two modeled elements' actual geometry — a beam and a duct in the same coordinates, physically impossible if built as designed. A soft (clearance) clash is not a geometry overlap; it's a violation of a required minimum buffer around an element — the code-mandated clear working space in front of an electrical panel, insulation clearance on a pipe, or maintenance access around ductwork. The objects never touch, but the design still breaks a real requirement. A workflow (4D/sequencing) clash is not spatial at all — it's a construction-schedule conflict, where two activities are planned to occupy the same zone during overlapping time windows, even though their final built geometry never overlaps. It's detected by combining the 3D model with 4D schedule data, not by geometry checking.
A coordination workflow that only runs a default geometry clash pass and reports 'zero clashes' is not conflict-free — it has only cleared one of three checks. Catching soft clashes requires the team to explicitly model or define required clearance envelopes as their own checkable volumes, which has to be built into the modeling standard or BIM Execution Plan rather than assumed. Catching workflow clashes requires a separate 4D simulation step — linking the model to the actual construction schedule and simulating trade sequencing — which is a distinct coordination discipline from spatial clash detection and is often skipped or run only at a coarse, milestone level. Teams that conflate 'zero hard clashes' with 'coordinated and buildable' are the ones who discover clearance violations at inspection and sequencing conflicts in the field.
Only if the required clearance zone is itself modeled as a volume and included in the clash test. Out of the box, these tools test element geometry against element geometry — they have no inherent knowledge that a panel needs 36 inches of clear space in front of it unless that space is represented as a checkable object in the model.
A soft clash is still fundamentally a spatial problem — a real-world buffer distance is violated in the finished design, even though the objects' geometry doesn't overlap. A workflow clash isn't spatial at all in the final design; the finished geometry can be completely fine. The conflict exists only in time, in the construction schedule, where two trades are planned into the same zone during overlapping weeks.
Yes, and this is the core misconception this page addresses. A zero-hard-clash report only confirms no two solids currently overlap in the model. It says nothing about whether required code or maintenance clearances are respected, and nothing about whether the construction sequence implied by the design is actually achievable.
A 4D coordination process: linking the 3D model elements to their corresponding activities in the construction schedule (in tools such as Navisworks TimeLiner or Synchro) and simulating the sequence over time. This surfaces cases where an activity requires a zone that another trade's schedule has that zone occupied or inaccessible during the same period — a check that geometry-only clash detection cannot perform.
This is typically set out in the BIM Execution Plan and coordination standard for the project — specifying which disciplines must model clearance/access envelopes as explicit, checkable volumes (not just the equipment itself) so they can be run through the same clash-detection workflow as hard clashes.
Try our BIM, CAD & Digital Design Studio
More calculators, simulators, and guides for this discipline.