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 104 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 Clearance Violation: 41.3% of the 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

36 issues
  • Architecture × MEP9
  • MEP × MEP9
  • Structure8
  • Structure × Architecture5
  • Structure × MEP4
  • Architecture1
Most frequent pairs
  • Beam × RL Pipe · 6
  • Equipment × Slab · 3
  • Beam × Duct · 2

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.

  • 104

    issues reviewed

    104 tagged by type, cause and fix

  • 1

    projects

    Hospital

  • 41.3%

    most common clash behavior: Clearance Violation

  • 69.2%

    most common root cause: Lack of Coordination

Shares on this page are of the 104 tagged issues.

01

What collides

The element pairs that clash most

Beam × Slab topped the list with 9 clashes, 8.7% of all tagged issues.

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

  • Beam
  • Slab
  • Clash zone
  • After the fix

How Beam × Slab clashes

  1. 01Clearance Violation88.9%The gap needed for access, maintenance or insulation is missing.8 issues
  2. 02Misalignment22.2%Elements that should line up across disciplines are offset from each other.2 issues
  3. 03Wrong Elevation11.1%An element sits at the wrong height for the levels and elements around it.1 issue

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

02

How they collide

Clash behaviors

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

Behavior

  1. 01Clearance Violation41.3%The gap needed for access, maintenance or insulation is missing.43 issues
  2. 02Hard Clash24%Two solid elements take up the same space, such as a pipe running through a beam.25 issues
  3. 03Location Conflict17.3%An element is placed where another discipline needs the space.18 issues
  4. 04Misalignment10.6%Elements that should line up across disciplines are offset from each other.11 issues
  5. 05Wrong Elevation6.7%An element sits at the wrong height for the levels and elements around it.7 issues
  6. 06Exposed5.8%An element that should be hidden shows below a ceiling or outside a finish.6 issues
  7. 07Size Conflict5.8%An element is too big for the space or opening it has to fit into.6 issues
  8. 08Penetration1%A service passes through a wall, slab or beam where no opening was planned.1 issue

Elements found in clashes

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

  1. 01Beam35.6%37 issues
  2. 02Slab19.2%20 issues
  3. 03Pipe16.3%17 issues
  4. 04Equipment14.4%15 issues
  5. 05Wall14.4%15 issues
  6. 06Door / Window12.5%13 issues
  7. 07RL Pipe11.5%12 issues
  8. 08Column9.6%10 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.

69.2%

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

Root cause

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

How we fix them

Solutions

The most common fix was AR to revise model, used on 47.1% of tagged issues.

Solution type

  1. 01AR to revise model47.1%49 issues
  2. 02ST to confirm structure34.6%36 issues
  3. 03MEP to reroute22.1%23 issues
  4. 04Change Elevation21.2%22 issues
  5. 05Shift Element13.5%14 issues
  6. 06Resize Element11.5%12 issues
  7. 07Reroute (Duct / Pipe / Tray)8.7%9 issues
  8. 08Accept with Condition7.7%8 issues

From cause to fix

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

  1. 01Lack of Coordination fixed by AR to revise model34.6%36 issues
  2. 02Lack of Coordination fixed by ST to confirm structure26.9%28 issues
  3. 03Lack of Coordination fixed by MEP to reroute21.2%22 issues
  4. 04Lack of Coordination fixed by Change Elevation17.3%18 issues
  5. 05Lack of Coordination fixed by Shift Element13.5%14 issues
  6. 06Lack of Coordination fixed by Resize Element9.6%10 issues
  7. 07Lack of Coordination fixed by Reroute (Duct / Pipe / Tray)8.7%9 issues
  8. 08Design Change Not Updated fixed by AR to revise model5.8%6 issues

Disciplines involved

Architecture appeared in more tagged clashes than any other discipline.

Discipline tags

  1. 01Architecture71.2%74 issues
  2. 02Structure60.6%63 issues
  3. 03Sanitary35.6%37 issues
  4. 04Mechanical14.4%15 issues
  5. 05Interior11.5%12 issues
  6. 06Electrical6.7%7 issues
  7. 07Fire Protection6.7%7 issues
  8. 08Landscape6.7%7 issues

Discipline flags on all 104 issues

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

Architecture (AR)
63
Structure (ST)
44
Mechanical (ME)
38
Interior (ID)
8
Landscape (LA)
6

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 (Hospital)

Sample size

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

Status at cutoff

Open 74 · Closed 30

Priority

Major 58 · Minor 44 · Regulation 2

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