The construction industry spends an estimated $65 billion a year on preventable rework. A single international airport in the Middle East saved $7 million in six months after moving MEP coordination into a LOD 400 federated model with rigorous clash detection. The gap between those two numbers is the thing most project teams get wrong about clash detection: it is not the report that saves money. It is the timing, the process behind it, and the discipline to run it before the steel is on the truck.
On our own work on the Lusail F1 Circuit, more than 1,200 conflicts were resolved before steel fabrication. Not after. Not during installation. Before. That is the difference this post is about.
What BIM Clash Detection Actually Is
Clash detection is the process of identifying conflicts between building elements inside a federated BIM model before they become conflicts on site. The federated model is the combined view of every discipline’s work: architectural, structural, MEP, facade, and landscape, pulled into one coordinated environment. Navisworks is the most common platform for running the checks. Revit, ArchiCAD, and Tekla feed the model content.
The “detection” word is slightly misleading. Good clash coordination is not about finding problems. It is about making sure problems have already been resolved by the time a model reaches the contractor. The report is the evidence. The resolution is the product.
For GCC clients working under ISO 19650 workflows, clash detection is an embedded quality gate, not a separate service. Ashghal, Qatar Rail, and the Saudi mega-project authorities expect coordinated models at each delivery milestone. If the first coordination cycle happens at IFC stage, something has already gone wrong.
The Three Types of Clashes That Matter
Most teams only track the first type. That is the first mistake.
Hard Clashes
Two physical elements occupying the same space. A duct running through a structural beam. A pipe crossing a wall with no sleeve detail. These are the easiest to catch automatically. Navisworks will flag them in minutes once the model is federated.
Soft Clashes
Clearance, access, and tolerance violations. A valve that technically fits but cannot be reached for maintenance. A ceiling height that drops below minimum egress clearance because an unexpected HVAC run crosses the corridor. Soft clashes do not stop fabrication. They stop operations. For owners and facility managers, these are often more expensive than hard clashes because they surface after handover, when fixes require retrofitting an FM-ready asset that is already live.
Workflow or 4D Clashes
Conflicts in sequence, not geometry. Two trades scheduled to work in the same zone on the same day. A structural pour blocking MEP rough-in by a week. 4D BIM reduces schedule overruns by up to 30% according to published benchmarks, but only when clash detection extends into the time dimension, not just the spatial one.
A serious coordination process tracks all three. Most project reports only capture the first.
How the Process Runs End to End
A clash detection cycle on a complex GCC project moves through five stages. Each has a distinct deliverable.
Federation. Models from every discipline are published to the Common Data Environment and federated into a single Navisworks file. Version control matters here. A clash report against the wrong model version wastes a coordination meeting.
Automated clash runs. The BIM coordinator sets up clash tests by discipline pairs: architectural vs structural, structural vs MEP, MEP internal, and so on. Rule sets define what qualifies as a clash and what counts as ignorable, for example acceptable tolerances on insulation wrap. Defining these rules is usually specified in the project BIM Execution Plan.
Categorization and prioritization. Raw clash lists are useless. A federated run on a mid-complexity building can generate thousands of hits, most of which are duplicates, false positives, or low-severity overlaps. Good coordinators categorize by severity, trade responsibility, and resolution owner.
Resolution tracking. Each live clash is assigned to a responsible party with a due date. Progress is tracked through the CDE, not through email. This is where ISO 19650 information management earns its keep. The standard is defined by the International Organization for Standardization and expects an auditable trail from clash identification through sign-off.
Sign-off and re-federation. Resolved clashes are verified against a new model issue. The cycle repeats at agreed milestones, typically weekly on active design phases and at every design stage gate. On Msheireb Bus Station, this cadence is what produced coordination signed off in writing by Al Sraiya.
On mega-projects, this cycle runs for months. The number of clashes caught is not the scorecard. The number that survive into construction is.
Why Timing Is the Variable That Actually Matters
Rework typically accounts for up to 12% of total construction cost on traditional projects. With BIM clash detection, published benchmarks show that number dropping by 30% to 50%. But the saving is not uniform across the project timeline. The earlier a clash is caught, the cheaper it is to resolve. See our breakdown on the ROI of BIM for a fuller picture of where the saving actually lands.
A clash caught at concept design costs a meeting. The same clash caught at LOD 300 costs a redesign. At LOD 400 during shop drawing coordination, it costs a procurement change. On site, it costs demolition, new material, and a schedule hit. The cost curve is roughly exponential, not linear.
This is why “clash-free is not a milestone, it is a standard” is not a tagline. It is an operating principle. A BIM team that runs coordination once before IFC is running damage control. A team that embeds clash detection into every design issue is delivering execution certainty.
On the Lusail F1 Circuit, the 1,200+ conflicts resolved before steel fabrication were caught across multiple coordination cycles, not one final review. The $7 million Middle East airport saving cited in industry reports came from the same pattern: continuous coordination, not end-of-design audits.
What Separates Real Clash Detection From a Checkbox Deliverable
Three things.
First, the process is auditable. Under ISO 19650, every clash has a version-tagged origin, a tracked resolution, and sign-off evidence. The model history is the audit trail.
Second, the team runs the full three-clash-type workflow. Soft and 4D clashes are not extras. They are where the facility management and scheduling savings live.
Third, coordination sits upstream, not downstream. The BIM manager is in the design review meetings, not receiving finished models at the end. BIM DESIGN LLC operates Qatar-based coordination paired with India-based production specifically to keep coordination close to client design teams while production scales with the model demand.
The checkbox version of clash detection produces a PDF. The rigorous version produces a clean construction phase.
| Checkbox Clash Detection | Rigorous Clash Coordination |
|---|---|
| One clash run near the end of design | Continuous clash cycles from LOD 200 onward |
| Tracks hard clashes only | Tracks hard, soft, and 4D workflow clashes |
| Clash lists distributed by email | Resolutions tracked through an ISO 19650 CDE |
| Deliverable is a PDF report | Deliverable is a coordinated, constructible model |
| Rework surfaces on site | Rework resolved before fabrication and procurement |
Frequently Asked Questions
Navisworks Manage is the standard for multi-discipline clash detection in the GCC market, because it handles large federated models and supports auditable clash reports compatible with ISO 19650 workflows. Autodesk Construction Cloud and Solibri are also used on specific project types. The software is the tool. The methodology and discipline behind it determine the outcome.
At concept design, not at IFC. The first coordination cycle should run as soon as there is enough model content to federate, usually around LOD 200. Waiting until construction documentation is the most common and most expensive mistake project teams make.
Hard clashes are physical overlaps between two elements. Soft clashes are clearance, access, or tolerance violations where elements technically fit but create operational problems. Soft clashes often surface only during facility management, which is why ignoring them until handover is costly.
On active design phases, weekly. On mega-projects with large coordination teams, more frequently. Running clash detection only at design stage gates generates a backlog that is harder and more expensive to resolve than a continuous cadence.
Smaller projects benefit proportionally. The absolute numbers are smaller, but the rework percentage is often higher because smaller projects run with leaner design teams and fewer checks. A LOD 300 clash detection cycle on a mid-size commercial project typically pays for itself many times over in avoided site rework.
Conclusion
BIM clash detection is not a service line. It is a discipline. The value is not in the report. It is in how early the process starts, how rigorously it runs, and how it is tracked under an ISO 19650 information management workflow.
Teams that treat it as an end-of-design audit are paying rework costs that a continuous coordination cycle would have prevented. Explore how this applies on the portfolio of mega-projects we have coordinated, or look at how the same process ran on Msheireb Bus Station and the LOD 500 Panda Zoo upgrade.