Clash Detection
An automated check that scans a coordinated [[concept-bim|BIM]] model for elements from different trades occupying the same physical space, such as a duct crossing through a structural beam or a sprinkler line clashing with a light fixture, flagging conflicts for resolution before construction.
Why it matters
A conflict between two trades' work is far cheaper to fix as a flagged item in a model than as a real problem discovered in the field, where resolving it can mean cutting into or relocating already-installed work. Clash detection exists specifically to move that discovery as early as possible.
On a real project
A weekly clash detection run flags a plumbing line routed through a structural beam's reinforcement zone. The mechanical and structural teams resolve it by rerouting the line in the model, weeks before either trade is actually on site to install it.
Who this matters most to
A BIM/VDC Specialist runs clash detection reports regularly throughout design and routes each conflict to whichever trade needs to resolve it. A Project Engineer often files the RFI that results when a clash can't be resolved without a design decision from the architect or engineer.
Where this goes wrong
A project skips a clash detection pass late in design to save schedule time, assuming the trades have coordinated closely enough on their own. An unresolved conflict between ductwork and a structural member isn't caught until the ductwork is already fabricated to the clashing dimensions, forcing an expensive re-fabrication that an earlier pass would have avoided entirely.
Explore next