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,966 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 2 clashes we tagged.
- 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
742 issues- Structure × MEP262
- MEP × MEP212
- Architecture × MEP208
- Structure × Architecture29
- Structure24
- Architecture7
- Beam × Pipe · 70
- Duct × Pipe · 48
- Pipe × Slab · 38
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,966
issues reviewed
1,966 tagged by type, cause and fix
- 2
projects
Mixed-use building
- 50.9%
most common clash behavior: Hard Clash
- 53.7%
most common root cause: Lack of Coordination
Shares on this page are of the 1,966 tagged issues.
What collides
The element pairs that clash most
Beam × Pipe topped the list with 191 clashes, 9.7% 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
- 01Hard Clash93.2%Two solid elements take up the same space, such as a pipe running through a beam.178 issues
- 02Penetration4.7%A service passes through a wall, slab or beam where no opening was planned.9 issues
- 03Missing Opening4.2%A service needs an opening, sleeve or shaft that is not in the model.8 issues
Share of this pair’s 191 clashes. One clash can carry more than one behavior.
How Pipe × Slab clashes
- 01Hard Clash50%Two solid elements take up the same space, such as a pipe running through a beam.67 issues
- 02Missing Opening33.6%A service needs an opening, sleeve or shaft that is not in the model.45 issues
- 03Misalignment17.2%Elements that should line up across disciplines are offset from each other.23 issues
Share of this pair’s 134 clashes. One clash can carry more than one behavior.
How Duct × Pipe clashes
- 01Hard Clash96%Two solid elements take up the same space, such as a pipe running through a beam.72 issues
- 02Clearance Violation5.3%The gap needed for access, maintenance or insulation is missing.4 issues
- 03Exposed1.3%An element that should be hidden shows below a ceiling or outside a finish.1 issue
Share of this pair’s 75 clashes. One clash can carry more than one behavior.
How Pipe × Wall clashes
- 01Hard Clash52.3%Two solid elements take up the same space, such as a pipe running through a beam.34 issues
- 02Exposed27.7%An element that should be hidden shows below a ceiling or outside a finish.18 issues
- 03Missing Opening21.5%A service needs an opening, sleeve or shaft that is not in the model.14 issues
Share of this pair’s 65 clashes. One clash can carry more than one behavior.
How Terminal (Diffuser, Sprinkler, Lighting) × Wall clashes
- 01Hard Clash41.1%Two solid elements take up the same space, such as a pipe running through a beam.23 issues
- 02Location Conflict23.2%An element is placed where another discipline needs the space.13 issues
- 03Misalignment21.4%Elements that should line up across disciplines are offset from each other.12 issues
Share of this pair’s 56 clashes. One clash can carry more than one behavior.
How Beam × Duct clashes
- 01Hard Clash98.1%Two solid elements take up the same space, such as a pipe running through a beam.51 issues
- 02Clearance Violation3.8%The gap needed for access, maintenance or insulation is missing.2 issues
- 03Redundant Element3.8%The same element is modelled twice, or by two disciplines.2 issues
Share of this pair’s 52 clashes. One clash can carry more than one behavior.
How they collide
Clash behaviors
Hard Clash led the behaviors at 50.9%. A behavior describes what two elements do to each other, such as a pipe running through a beam.
Behavior
- 01Hard Clash50.9%Two solid elements take up the same space, such as a pipe running through a beam.1,000 issues
- 02Misalignment12.3%Elements that should line up across disciplines are offset from each other.242 issues
- 03Missing Opening9%A service needs an opening, sleeve or shaft that is not in the model.176 issues
- 04Clearance Violation8.2%The gap needed for access, maintenance or insulation is missing.162 issues
- 05Wrong Elevation7%An element sits at the wrong height for the levels and elements around it.137 issues
- 06Exposed5.5%An element that should be hidden shows below a ceiling or outside a finish.108 issues
- 07Location Conflict4.5%An element is placed where another discipline needs the space.89 issues
- 08Size Conflict3%An element is too big for the space or opening it has to fit into.58 issues
Elements found in clashes
How often each element shows up in a tagged clash, on either side.
- 01Pipe46.3%910 issues
- 02Beam20%393 issues
- 03Wall18.8%369 issues
- 04Slab15.2%298 issues
- 05Duct11.8%232 issues
- 06Equipment8.1%159 issues
- 07Terminal (Diffuser, Sprinkler, Lighting)7.4%145 issues
- 08Ceiling7.2%141 issues
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.
of the clashes we tagged traced back to Lack of Coordination.
Root cause
- 01Lack of Coordination53.7%Disciplines modelled the same zone without agreeing who goes where.1,056 issues
- 02Late Design Input11.6%Design information arrived after the model in that area was built.228 issues
- 03Model Not Linked / Outdated11.4%A team worked against a missing or old copy of another discipline’s model.225 issues
- 04Incorrect LOD6.7%An element was modelled at too low a level of detail to check properly.132 issues
- 05Design Change Not Updated3.6%The design changed, but the model did not follow.71 issues
- 06Assumption Conflict0.5%Two teams filled the same gap in the design with different assumptions.10 issues
- 07Wrong Discipline Reference0.2%A team referenced the wrong discipline’s model or drawing.4 issues
How we fix them
Solutions
The most common fix was MEP to reroute, used on 36.3% of tagged issues.
Solution type
- 01MEP to reroute36.3%714 issues
- 02AR to revise model17.2%339 issues
- 03ST to confirm structure13.8%271 issues
- 04Reroute (Duct / Pipe / Tray)12.1%238 issues
- 05Change Elevation11.3%222 issues
- 06Shift Element8.4%165 issues
- 07BIM to coordinate & recheck8.1%159 issues
- 08Add Sleeve6.6%130 issues
From cause to fix
The root cause and solution pairs that came up most often.
- 01Lack of Coordination fixed by MEP to reroute27.2%535 issues
- 02Lack of Coordination fixed by Reroute (Duct / Pipe / Tray)11.3%223 issues
- 03Lack of Coordination fixed by Change Elevation7.7%152 issues
- 04Lack of Coordination fixed by AR to revise model7.2%142 issues
- 05Lack of Coordination fixed by ST to confirm structure7.2%142 issues
- 06Lack of Coordination fixed by Shift Element7%137 issues
- 07Lack of Coordination fixed by Add Sleeve5.8%115 issues
- 08Late Design Input fixed by Hold for Design Decision4.4%86 issues
Disciplines involved
Structure appeared in more tagged clashes than any other discipline.
Discipline tags
- 01Structure51.3%1,009 issues
- 02Architecture43.1%847 issues
- 03Sanitary37%728 issues
- 04Mechanical26.7%524 issues
- 05Fire Protection14.6%288 issues
- 06Electrical7.9%156 issues
- 07Landscape3.8%74 issues
- 08Interior3.2%63 issues
Discipline flags on all 1,966 issues
Set on every issue in the log, tagged or not, so these counts use the larger sample.
- Mechanical (ME)
- 1,482
- Structure (ST)
- 1,059
- Architecture (AR)
- 745
- Facade (FC)
- 119
- Landscape (LA)
- 52
- Electrical (EE)
- 1
How this report was made
- Source
HOOK’s BIM coordination issue log (hook-tracker)
- Issues logged
23 October 2026 to 24 October 2026
- Data as of
10 Nov 2026, 01:53
- Projects
2 (Mixed-use building)
- Sample size
1,966 issues logged, 1,966 of them tagged (100%)
- Status at cutoff
Closed 1,565 · Open 353 · In progress 48
- Priority
Minor 1,085 · Major 881
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.