Technology

What is clash detection in construction?

Clash detection is the process of running coordinated 3D models against each other to find where pipes, ducts, steel, and other systems would collide, so the conflict gets fixed on screen instead of in the field.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

Clash detection is a coordination step in BIM work. Each trade's model (structure, ductwork, plumbing, sprinkler, electrical, and so on) is combined into one federated model, and software checks every element against every other element for overlaps or tight spots. The output is a list of clashes, each with a location and the two objects involved. The coordination team then decides who moves.

Types of clashes

  • Hard clash: two objects occupy the same space. A 14-inch duct runs straight through a steel beam.
  • Soft clash (clearance clash): objects do not touch but violate a required clearance, like access space in front of an electrical panel or insulation thickness around a pipe.
  • Workflow or time clash: the sequence does not work, such as a crane pick scheduled where another trade's lift is staged. Some teams track these through 4D scheduling.

How clash detection works on a real job

Say a GC is building a three-story medical office building. The MEP subs each model their systems for the second floor ceiling. The BIM coordinator combines them and runs a test. The first run returns 1,100 clashes, which sounds alarming until you group them: 700 are sprinkler branch lines passing through light fixtures that are just placeholders, 300 are duplicates of the same pipe crossing the same joist, and maybe 60 are real problems.

At the weekly coordination meeting, the team works the real ones. Gravity drains have priority because they need slope. Large ducts come next. Sprinkler and electrical are usually the most flexible. Each clash gets an owner and a due date. When the area runs clean, the subs sign off and that model becomes the basis for shop drawings and prefabrication. Anything the team cannot solve inside the design goes out as a request for information.

On smaller jobs without full BIM, the same idea shows up as coordination drawings: each trade overlays its layout on a shared background, usually in the ceiling plenum or mechanical rooms, and the conflicts are resolved in a meeting with markers instead of software. It is slower but catches many of the same problems.

Common mistakes and disputes

  1. Running tests with bad tolerances, which buries the real problems under thousands of trivial hits.
  2. Coordinating from models that are not at the right level of detail. A duct modeled without insulation will pass the test and fail in the ceiling.
  3. No agreed priority rules, so every clash becomes a negotiation between subs.
  4. Treating a clean model as proof the field will match. Existing conditions in a renovation still need field verification or a scan.
  5. Unclear contract language about who pays for rework when a sub installs outside the coordinated model.

Related terms

Clash detection is the core of 3D model coordination and builds on CAD and BIM models. It reduces rework, which is covered in how to reduce rework on construction projects. Unresolved clashes often turn into RFIs and then change orders, so track them in the same place you track other open issues. Smart Business Automator tracks RFIs and submittals by job so coordination questions do not get lost between meetings.

Frequently asked questions

What software is used for clash detection?

Most teams use a BIM coordination tool that can combine models from different authoring programs and run clash tests. The process matters more than the brand: clean models, sensible tolerances, and clear ownership of each clash.

Who is responsible for clash detection?

It depends on the contract. On many design-build and CM jobs, the GC or CM runs coordination and the subs model their own trades. On some jobs the design team runs it. The contract and BIM execution plan should say.

Does clash detection eliminate field conflicts?

No. It reduces them. Field conditions, late design changes, and installation that strays from the model still cause conflicts.

Is clash detection worth it on small jobs?

On small jobs with simple ceilings, a coordination drawing review may be enough. It pays off most where ceilings are tight and MEP systems are dense, such as healthcare, labs, and data centers.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment