Skip to content

Proposal

Issues white paper 2026

BIM Clash Report 2026

Which clashes HOOK’s BIM coordination finds most, how they happen, why, and how they get fixed. Based on 642 tagged issues from 4 projects.

Live figures from HOOK’s issue log, updated 21 Oct 2026, 01:31 (Bangkok time).

The most common clash behavior was Wrong Elevation: one in every 4 clashes we tagged.

  • Beam
  • Pipe
  • Clash zone
  • After the fix

Beam × Pipe, the pair that clashed most

  • 1,559

    issues reviewed

    642 tagged by type, cause and fix

  • 4

    projects

    Condominium and Factory building

  • 26.3%

    most common clash behavior: Wrong Elevation

  • 62.1%

    most common root cause: Lack of Coordination

Shares on this page are of the 642 tagged issues.

01

What collides

The element pairs that clash most

Beam × Pipe topped the list with 61 clashes, 9.5% of all tagged issues.

Pick a pair to see it in 3D, then switch between the clash and the fix.

  • Beam
  • Pipe
  • Clash zone
  • After the fix

How Beam × Pipe clashes

  1. 01Overlap52.5%Two elements share part of the same space along their length.32 issues
  2. 02Location Conflict42.6%An element is placed where another discipline needs the space.26 issues
  3. 03Hard Clash41%Two solid elements take up the same space, such as a pipe running through a beam.25 issues

Share of this pair’s 61 clashes. One clash can carry more than one behavior.

02

How they collide

Clash behaviors

Wrong Elevation led the behaviors at 26.3%. A behavior describes what two elements do to each other, such as a pipe running through a beam.

Behavior

  1. 01Wrong Elevation26.3%An element sits at the wrong height for the levels and elements around it.169 issues
  2. 02Location Conflict24.6%An element is placed where another discipline needs the space.158 issues
  3. 03Exposed23.8%An element that should be hidden shows below a ceiling or outside a finish.153 issues
  4. 04Overlap19.8%Two elements share part of the same space along their length.127 issues
  5. 05Misalignment17.9%Elements that should line up across disciplines are offset from each other.115 issues
  6. 06Hard Clash13.6%Two solid elements take up the same space, such as a pipe running through a beam.87 issues
  7. 07Clearance Violation6.2%The gap needed for access, maintenance or insulation is missing.40 issues
  8. 08Emerged6.2%An element pokes out of the wall, slab or finish that should contain it.40 issues

Elements found in clashes

How often each element shows up in a tagged clash, on either side.

  1. 01Beam28%180 issues
  2. 02Pipe26.6%171 issues
  3. 03Wall21%135 issues
  4. 04Slab16.2%104 issues
  5. 05Ceiling15.9%102 issues
  6. 06Equipment15.6%100 issues
  7. 07RL Pipe12.5%80 issues
  8. 08Finish Layer11.7%75 issues
03

Why

Root causes

The root cause is why a clash reached the model in the first place. It shows which step of the process needs to change.

62.1%

of the clashes we tagged traced back to Lack of Coordination.

Root cause

  1. 01Lack of Coordination62.1%Disciplines modelled the same zone without agreeing who goes where.399 issues
  2. 02Model Not Linked / Outdated23.7%A team worked against a missing or old copy of another discipline’s model.152 issues
  3. 03Design Change Not Updated18.1%The design changed, but the model did not follow.116 issues
  4. 04Assumption Conflict12%Two teams filled the same gap in the design with different assumptions.77 issues
  5. 05Late Design Input4.5%Design information arrived after the model in that area was built.29 issues
  6. 06Wrong Discipline Reference3.6%A team referenced the wrong discipline’s model or drawing.23 issues
04

How we fix them

Solutions

The most common fix was MEP to reroute, used on 33.6% of tagged issues.

Solution type

  1. 01MEP to reroute33.6%216 issues
  2. 02ST to confirm structure32.7%210 issues
  3. 03AR to revise model30.4%195 issues
  4. 04Revise Layout21%135 issues
  5. 05Reroute (Duct / Pipe / Tray)9.5%61 issues
  6. 06Change Elevation8.1%52 issues
  7. 07Resize Element7%45 issues
  8. 08Shift Element4.8%31 issues

From cause to fix

The root cause and solution pairs that came up most often.

  1. 01Lack of Coordination fixed by MEP to reroute24.6%158 issues
  2. 02Lack of Coordination fixed by AR to revise model21.7%139 issues
  3. 03Lack of Coordination fixed by ST to confirm structure14.2%91 issues
  4. 04Lack of Coordination fixed by Revise Layout13.7%88 issues
  5. 05Assumption Conflict fixed by ST to confirm structure7.3%47 issues
  6. 06Design Change Not Updated fixed by AR to revise model7.2%46 issues
  7. 07Model Not Linked / Outdated fixed by MEP to reroute7.2%46 issues
  8. 08Design Change Not Updated fixed by ST to confirm structure7%45 issues

Disciplines involved

Architecture appeared in more tagged clashes than any other discipline.

Discipline tags

  1. 01Architecture63.9%410 issues
  2. 02Structure49.4%317 issues
  3. 03Sanitary30.8%198 issues
  4. 04Interior26.3%169 issues
  5. 05Mechanical17.1%110 issues
  6. 06Landscape10.1%65 issues
  7. 07Fire Protection6.1%39 issues
  8. 08Plumbing3.9%25 issues

Discipline flags on all 1,559 issues

Set on every issue in the log, tagged or not, so these counts use the larger sample.

Architecture (AR)
683
Structure (ST)
590
Mechanical (ME)
501
Landscape (LA)
242
Interior (ID)
72
Sanitary (SN)
50
Air conditioning (AC)
43
Fire protection (FP)
28
Electrical (EE)
26
Facade (FC)
3
Civil (CV)
1

How this report was made

Source

HOOK’s BIM coordination issue log (hook-tracker)

Issues logged

22 January 2026 to 19 October 2026

Data as of

21 Oct 2026, 01:31

Projects

4 (Condominium and Factory building)

Sample size

1,559 issues logged, 642 of them tagged (41.2%)

Status at cutoff

Closed 969 · Open 590

Priority

Minor 1,257 · Major 279 · Regulation 23

Every share on this page is a share of tagged issues. The coordination team adds the tags by hand, so coverage varies from project to project.

One issue can carry several tags, for example two elements and two behaviors, so the shares in a list can add up to more than 100%.

Project names, drawings and issue descriptions stay private. Only counts are published, grouped by project type.

The figures on this page come straight from the coordination issue log and refresh about every 10 minutes. Each year’s edition is kept as an archive with its figures fixed.

Catch the clash before it reaches site

HOOK runs BIM coordination for contractors and project owners in Thailand, from model checks to clash resolution meetings.

Request a proposalSee our BIM services