Skip to content

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 299 tagged issues from 2 projects.

Live figures from HOOK’s issue log, updated 10 Nov 2026, 01:53 (Bangkok time).

The most common clash behavior was Hard Clash: one in every 3 clashes we tagged.

Share this report
  • Structure × MEP
  • Architecture × MEP
  • Structure × Architecture
  • MEP × MEP
  • Structure
  • Architecture

Hover or tap a floor to see its clashes. Click a dot to see that clash up close. Drag to turn, right-drag or two fingers to move, scroll or pinch to zoom.

Basement & foundations

154 issues
  • MEP × MEP57
  • Architecture × MEP26
  • Structure21
  • Structure × Architecture18
  • Structure × MEP17
  • Architecture15
Most frequent pairs
  • Beam × Pipe · 22
  • Beam × Door / Window · 8
  • Door / Window × Pipe · 8

Each dot stands for about 50 clashes from HOOK’s issue log, drawn on the floor they were recorded on, where the two elements involved meet, and coloured by the disciplines involved. The building is illustrative.

  • 299

    issues reviewed

    299 tagged by type, cause and fix

  • 2

    projects

    Hotel

  • 35.5%

    most common clash behavior: Hard Clash

  • 71.2%

    most common root cause: Lack of Coordination

Shares on this page are of the 299 tagged issues.

01

What collides

The element pairs that clash most

Beam × Pipe topped the list with 36 clashes, 12% 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. 01Clearance Violation55.6%The gap needed for access, maintenance or insulation is missing.20 issues
  2. 02Hard Clash50%Two solid elements take up the same space, such as a pipe running through a beam.18 issues
  3. 03Penetration25%A service passes through a wall, slab or beam where no opening was planned.9 issues

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

02

How they collide

Clash behaviors

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

Behavior

  1. 01Hard Clash35.5%Two solid elements take up the same space, such as a pipe running through a beam.106 issues
  2. 02Clearance Violation33.4%The gap needed for access, maintenance or insulation is missing.100 issues
  3. 03Misalignment16.7%Elements that should line up across disciplines are offset from each other.50 issues
  4. 04Location Conflict9.7%An element is placed where another discipline needs the space.29 issues
  5. 05Size Conflict7.7%An element is too big for the space or opening it has to fit into.23 issues
  6. 06Wrong Elevation6.7%An element sits at the wrong height for the levels and elements around it.20 issues
  7. 07Penetration5%A service passes through a wall, slab or beam where no opening was planned.15 issues
  8. 08Exposed3%An element that should be hidden shows below a ceiling or outside a finish.9 issues

Elements found in clashes

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

  1. 01Beam43.5%130 issues
  2. 02Pipe30.8%92 issues
  3. 03Slab17.4%52 issues
  4. 04Door / Window15.4%46 issues
  5. 05Equipment13.4%40 issues
  6. 06Shaft10.7%32 issues
  7. 07Wall9%27 issues
  8. 08Duct8%24 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.

71.2%

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

Root cause

  1. 01Lack of Coordination71.2%Disciplines modelled the same zone without agreeing who goes where.213 issues
  2. 02Model Not Linked / Outdated8%A team worked against a missing or old copy of another discipline’s model.24 issues
  3. 03Incorrect LOD7.4%An element was modelled at too low a level of detail to check properly.22 issues
  4. 04Late Design Input6%Design information arrived after the model in that area was built.18 issues
  5. 05Design Change Not Updated5.4%The design changed, but the model did not follow.16 issues
  6. 06Assumption Conflict0.3%Two teams filled the same gap in the design with different assumptions.1 issue
04

How we fix them

Solutions

The most common fix was ST to confirm structure, used on 34.8% of tagged issues.

Solution type

  1. 01ST to confirm structure34.8%104 issues
  2. 02AR to revise model26.8%80 issues
  3. 03MEP to reroute25.8%77 issues
  4. 04BIM to coordinate & recheck22.7%68 issues
  5. 05Shift Element16.7%50 issues
  6. 06Resize Element15.7%47 issues
  7. 07Change Elevation13.7%41 issues
  8. 08Reroute (Duct / Pipe / Tray)10.4%31 issues

From cause to fix

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

  1. 01Lack of Coordination fixed by ST to confirm structure23.1%69 issues
  2. 02Lack of Coordination fixed by MEP to reroute22.4%67 issues
  3. 03Lack of Coordination fixed by AR to revise model20.7%62 issues
  4. 04Lack of Coordination fixed by Resize Element13.7%41 issues
  5. 05Lack of Coordination fixed by BIM to coordinate & recheck12.4%37 issues
  6. 06Lack of Coordination fixed by Shift Element11%33 issues
  7. 07Lack of Coordination fixed by Reroute (Duct / Pipe / Tray)10%30 issues
  8. 08Lack of Coordination fixed by Change Elevation9.7%29 issues

Disciplines involved

Architecture appeared in more tagged clashes than any other discipline.

Discipline tags

  1. 01Architecture71.2%213 issues
  2. 02Structure67.6%202 issues
  3. 03Sanitary24.1%72 issues
  4. 04Mechanical23.4%70 issues
  5. 05Fire Protection13.4%40 issues
  6. 06Electrical9.4%28 issues
  7. 07Interior1.3%4 issues

Discipline flags on all 299 issues

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

Mechanical (ME)
148
Structure (ST)
147
Architecture (AR)
146

How this report was made

Source

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

Issues logged

23 October 2026 to 23 October 2026

Data as of

10 Nov 2026, 01:53

Projects

2 (Hotel)

Sample size

299 issues logged, 299 of them tagged (100%)

Status at cutoff

Closed 160 · Open 94 · In progress 45

Priority

Major 153 · Minor 127 · Regulation 19

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.

Share the BIM Clash Report

Know someone who coordinates BIM models? Send them the figures.

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.