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 1,087 tagged issues from 1 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

514 issues
  • Architecture × MEP129
  • MEP × MEP122
  • Structure × MEP113
  • Structure × Architecture78
  • Architecture41
  • Structure30
  • Discipline not recorded1
Most frequent pairs
  • Ceiling × Pipe · 49
  • Beam × Pipe · 35
  • Ceiling × Terminal (Diffuser, Sprinkler, Lighting) · 30

1 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.

  • 1,087

    issues reviewed

    1,087 tagged by type, cause and fix

  • 1

    projects

    Residence

  • 34.5%

    most common clash behavior: Hard Clash

  • 67.1%

    most common root cause: Lack of Coordination

Shares on this page are of the 1,087 tagged issues.

01

What collides

The element pairs that clash most

Beam × Pipe topped the list with 92 clashes, 8.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. 01Hard Clash71.7%Two solid elements take up the same space, such as a pipe running through a beam.66 issues
  2. 02Penetration26.1%A service passes through a wall, slab or beam where no opening was planned.24 issues
  3. 03Location Conflict9.8%An element is placed where another discipline needs the space.9 issues

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

02

How they collide

Clash behaviors

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

Behavior

  1. 01Hard Clash34.5%Two solid elements take up the same space, such as a pipe running through a beam.375 issues
  2. 02Misalignment17.4%Elements that should line up across disciplines are offset from each other.189 issues
  3. 03Wrong Elevation17.1%An element sits at the wrong height for the levels and elements around it.186 issues
  4. 04Exposed14.9%An element that should be hidden shows below a ceiling or outside a finish.162 issues
  5. 05Location Conflict11.1%An element is placed where another discipline needs the space.121 issues
  6. 06Penetration7.6%A service passes through a wall, slab or beam where no opening was planned.83 issues
  7. 07Clearance Violation6.7%The gap needed for access, maintenance or insulation is missing.73 issues
  8. 08Size Conflict5.6%An element is too big for the space or opening it has to fit into.61 issues

Elements found in clashes

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

  1. 01Pipe32.8%357 issues
  2. 02Beam22.2%241 issues
  3. 03Ceiling19.8%215 issues
  4. 04Slab17.8%193 issues
  5. 05Terminal (Diffuser, Sprinkler, Lighting)14.1%153 issues
  6. 06Equipment12.7%138 issues
  7. 07Wall11.4%124 issues
  8. 08Duct10%109 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.

67.1%

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

Root cause

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

How we fix them

Solutions

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

Solution type

  1. 01MEP to reroute25.9%282 issues
  2. 02BIM to coordinate & recheck22.9%249 issues
  3. 03Change Elevation21.3%231 issues
  4. 04Shift Element20.6%224 issues
  5. 05AR to revise model12.9%140 issues
  6. 06ST to confirm structure11.1%121 issues
  7. 07Reroute (Duct / Pipe / Tray)9.9%108 issues
  8. 08Refer to Consultant7.2%78 issues

From cause to fix

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

  1. 01Lack of Coordination fixed by MEP to reroute22.2%241 issues
  2. 02Lack of Coordination fixed by Shift Element16.6%180 issues
  3. 03Lack of Coordination fixed by Change Elevation14.1%153 issues
  4. 04Lack of Coordination fixed by Reroute (Duct / Pipe / Tray)8.9%97 issues
  5. 05Lack of Coordination fixed by ST to confirm structure7.6%83 issues
  6. 06Incorrect LOD fixed by BIM to coordinate & recheck7.3%79 issues
  7. 07Lack of Coordination fixed by AR to revise model7.3%79 issues
  8. 08Lack of Coordination fixed by BIM to coordinate & recheck6.8%74 issues

Disciplines involved

Structure appeared in more tagged clashes than any other discipline.

Discipline tags

  1. 01Structure51.2%557 issues
  2. 02Sanitary37.2%404 issues
  3. 03Architecture32.8%357 issues
  4. 04Interior25.2%274 issues
  5. 05Mechanical24.6%267 issues
  6. 06Electrical15.5%169 issues
  7. 07Landscape7.4%80 issues
  8. 08Fire Protection2%22 issues

Discipline flags on all 1,087 issues

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

Mechanical (ME)
754
Structure (ST)
563
Architecture (AR)
351
Interior (ID)
215
Landscape (LA)
42
Facade (FC)
21

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

1 (Residence)

Sample size

1,087 issues logged, 1,087 of them tagged (100%)

Status at cutoff

Closed 924 · Open 163

Priority

Minor 686 · Major 400 · Regulation 1

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.

Request a proposalSee our BIM services