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 3,036 tagged issues from 11 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
  • Discipline not recorded

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.

Ground floor & mezzanine

1,401 issues
  • MEP × MEP298
  • Architecture270
  • Structure × Architecture245
  • Structure × MEP243
  • Architecture × MEP203
  • Structure141
  • Discipline not recorded1
Most frequent pairs
  • Beam × Pipe · 111
  • Foundation × Pipe · 66
  • Ceiling × Pipe · 44

163 issues had no floor recorded and are not drawn.

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.

  • 3,819

    issues reviewed

    3,036 tagged by type, cause and fix

  • 11

    projects

    Condominium

  • 32.9%

    most common clash behavior: Hard Clash

  • 70.1%

    most common root cause: Lack of Coordination

Shares on this page are of the 3,036 tagged issues.

01

What collides

The element pairs that clash most

Beam × Pipe topped the list with 191 clashes, 6.3% 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. 01Hard Clash70.2%Two solid elements take up the same space, such as a pipe running through a beam.134 issues
  2. 02Overlap17.8%Two elements share part of the same space along their length.34 issues
  3. 03Location Conflict16.2%An element is placed where another discipline needs the space.31 issues

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

02

How they collide

Clash behaviors

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

Behavior

  1. 01Hard Clash32.9%Two solid elements take up the same space, such as a pipe running through a beam.999 issues
  2. 02Misalignment18.9%Elements that should line up across disciplines are offset from each other.573 issues
  3. 03Wrong Elevation15.5%An element sits at the wrong height for the levels and elements around it.471 issues
  4. 04Exposed15.1%An element that should be hidden shows below a ceiling or outside a finish.457 issues
  5. 05Location Conflict12.3%An element is placed where another discipline needs the space.373 issues
  6. 06Clearance Violation9.1%The gap needed for access, maintenance or insulation is missing.275 issues
  7. 07Overlap5.7%Two elements share part of the same space along their length.174 issues
  8. 08Size Conflict5.5%An element is too big for the space or opening it has to fit into.167 issues

Elements found in clashes

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

  1. 01Pipe29.6%899 issues
  2. 02Beam23.6%715 issues
  3. 03Slab18.5%561 issues
  4. 04Ceiling15.1%458 issues
  5. 05Wall13.6%414 issues
  6. 06Equipment11.5%350 issues
  7. 07Column8.6%260 issues
  8. 08Door / Window7.9%241 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.

70.1%

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

Root cause

  1. 01Lack of Coordination70.1%Disciplines modelled the same zone without agreeing who goes where.2,127 issues
  2. 02Model Not Linked / Outdated10.4%A team worked against a missing or old copy of another discipline’s model.316 issues
  3. 03Design Change Not Updated9.2%The design changed, but the model did not follow.280 issues
  4. 04Late Design Input5.7%Design information arrived after the model in that area was built.174 issues
  5. 05Assumption Conflict3.3%Two teams filled the same gap in the design with different assumptions.99 issues
  6. 06Incorrect LOD3.2%An element was modelled at too low a level of detail to check properly.97 issues
  7. 07Wrong Discipline Reference0.8%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 34% of tagged issues.

Solution type

  1. 01MEP to reroute34%1,031 issues
  2. 02ST to confirm structure31.8%966 issues
  3. 03AR to revise model27.3%830 issues
  4. 04Change Elevation16.1%490 issues
  5. 05Shift Element13.8%418 issues
  6. 06Reroute (Duct / Pipe / Tray)12.8%388 issues
  7. 07Revise Layout12.2%371 issues
  8. 08Resize Element9.3%282 issues

From cause to fix

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

  1. 01Lack of Coordination fixed by MEP to reroute28.9%878 issues
  2. 02Lack of Coordination fixed by AR to revise model20%606 issues
  3. 03Lack of Coordination fixed by ST to confirm structure19.5%592 issues
  4. 04Lack of Coordination fixed by Change Elevation12.6%383 issues
  5. 05Lack of Coordination fixed by Reroute (Duct / Pipe / Tray)11.2%339 issues
  6. 06Lack of Coordination fixed by Shift Element11%335 issues
  7. 07Lack of Coordination fixed by Revise Layout8.4%254 issues
  8. 08Lack of Coordination fixed by Resize Element6.9%209 issues

Disciplines involved

Structure appeared in more tagged clashes than any other discipline.

Discipline tags

  1. 01Structure56.8%1,725 issues
  2. 02Architecture55.9%1,696 issues
  3. 03Sanitary35.6%1,080 issues
  4. 04Interior17.4%527 issues
  5. 05Mechanical16.5%502 issues
  6. 06Landscape14.2%430 issues
  7. 07Electrical7.2%220 issues
  8. 08Fire Protection4.6%139 issues

Discipline flags on all 3,819 issues

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

Structure (ST)
1,681
Mechanical (ME)
1,665
Architecture (AR)
1,612
Landscape (LA)
487
Interior (ID)
320
Air conditioning (AC)
39
Sanitary (SN)
35
Fire protection (FP)
15
Electrical (EE)
9
Facade (FC)
2

How this report was made

Source

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

Issues logged

22 January 2026 to 9 November 2026

Data as of

10 Nov 2026, 01:53

Projects

11 (Condominium)

Sample size

3,819 issues logged, 3,036 of them tagged (79.5%)

Status at cutoff

Closed 2,412 · Open 1,395 · In progress 12

Priority

Minor 2,423 · Major 1,329 · Regulation 38 · Critical 29

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.