A dependable clash detection workflow is a repeatable cycle, not a single software command: discipline models are checked for health, federated on a shared coordinate system, tested against agreed rules, triaged by severity, assigned to an accountable party, fixed and then re-tested until the results are closed. This article sets out that cycle step by step, explains how it is run in Navisworks, and shows where it meets the documentation expectations of Dubai and the wider UAE market.
TL;DR
- Clash detection works as a weekly, repeatable cycle: model health check, federation, tests, triage, assignment, re-test and sign-off.
- Separate hard clashes, clearance clashes and workflow (4D) clashes, because each needs a different rule and a different owner.
- A noisy clash report usually points to coordinate or base point errors between models, not to hundreds of real conflicts.
- In Dubai, the process sits inside an ISO 19650 information management framework, so roles, deadlines and the shared data environment must be defined before the first test runs.
- Structural coordination is where most expensive clashes surface, so the structural engineer should be at the table from the first federation.
Table of Contents
- What a clash detection workflow actually covers
- The three types of clash your tests must separate
- Step 1: Agree the rules before anyone models
- Step 2: Check model health before federation
- Step 3: Federate the models and run the tests in Navisworks
- Step 4: Triage the results by constructability
- Step 5: Assign, track and report
- Step 6: Resolve, re-test and close
- Where 3D is not worth the effort
- Dubai and UAE considerations
- Common failure points and how to avoid them
- Our perspective on coordination
- Support from Integra
- FAQ
- Sources
What a clash detection workflow actually covers
Clash detection, also called interference checking, identifies conflicts between elements of a 3D building model, for example a duct passing through a beam or a sprinkler main crossing a column. The workflow is everything around that check: who publishes which model, when, in what format, which tests run, who reviews the results and how a conflict is declared closed.
Treating it as a workflow matters because the software is the easy part. The BIMCamel guide to a practical clash detection workflow makes the same point: running a test in one tool takes a click, while finding, filtering, assigning and resolving clashes across disciplines is a process that needs discipline and rhythm.
For developers and contractors in the UAE, the payoff is practical. A conflict resolved in the model costs a coordination meeting. The same conflict discovered during installation costs rework, programme delay and often a variation order. Our own view is that the structural model is the natural anchor of coordination, since beams, slabs, cores and transfer structures are the least flexible elements on any job.
The three types of clash your tests must separate
Not every conflict is a collision. According to the infralens handbook on BIM clash detection, clashes fall into three families, and a workflow that lumps them together produces reports nobody can act on.
| Clash type | What it means | Typical example | Usual owner |
|---|---|---|---|
| Hard clash | Two solid elements physically occupy the same space | Duct through a post-tensioned beam | Discipline that modelled later or has more routing freedom |
| Clearance (soft) clash | An element violates required space or access | No maintenance clearance in front of an air handling unit | MEP lead, with the architect for access |
| Workflow (4D) clash | Two trades need the same space at different times | Crane lift path blocked by formwork or scaffolding | Contractor planner, with temporary works designer |
The same source notes that clearance tolerances commonly range from 25 mm to 300 mm depending on the project code and element type. That range is a reminder to set each tolerance deliberately, from the specification, the manufacturer’s maintenance requirements and the applicable code, rather than accepting a default.
Step 1: Agree the rules before anyone models
The cleanest clash detection is decided on paper. The BIM Execution Plan should say which disciplines are modelled, to what level of development, which software versions are used, where models are published and how often. An ISO 19650 compliant BEP names the BIM manager, the platforms, the common data environment and the specific BIM uses, with clash detection listed among them.
If you are still drafting that document, our guide on how to map ISO 19650, NBIMS and AIA G203 into your BIM Execution Plan covers the structure. Level of development deserves its own decision, because a clash test between a LOD 200 duct and a LOD 400 beam tells you very little. Our note on enforcing LOD 100 to 500 in a BEP for Gulf teams explains how to tie those levels to project stages.
At this stage also agree:
- A single shared coordinate system and project base point, documented and distributed.
- A discipline matrix defining which model is tested against which.
- A resolution timeframe for each severity level.
- A naming convention for models, clash tests and issues.
Step 2: Check model health before federation
Experienced BIM managers describe clash detection as a predictable cycle, such as weekly model submissions, rather than an ad hoc exercise, because the cadence builds accountability and lets model health checks run before models are federated (BIMCamel). A discipline lead should not publish a model that fails the basics.
A simple health checklist before each submission covers the following points. Linked files sit on the agreed base point and rotation. Elements are assigned to the correct levels and categories. Duplicate elements, unplaced rooms and stray geometry are removed. Warnings are reduced to an agreed threshold. The file is named and versioned according to the convention.
This step is unglamorous and it saves the most time. Practitioners report that a clash report where nearly everything appears to conflict with everything else is almost always a symptom of coordinate drift or inconsistent base points between linked models. The cure is to correct the coordinates at the source rather than to filter the results by hand (BIMCamel).
Step 3: Federate the models and run the tests in Navisworks
Once models pass the health check, they are combined into a federated model. In Navisworks, the sequence described in the Autodesk Clash Detective workflow documentation is to select an existing test or add a new one, define the two selections to compare, choose the test type, apply rules, run the test and review the results.
The test types are hard, clearance and duplicates. Rules allow you to ignore interferences that do not matter, such as elements within the same file or layer, so reviewers see only meaningful results. Selection sets are the practical key: build them by discipline, system and level, so a test reads as, for example, structural frame against ducts on level 12, rather than the whole building against the whole building.
Two habits help. First, keep test names consistent and tied to the discipline matrix, so that the same tests can be rerun each cycle. Second, use a clash matrix to batch-create tests rather than building them by hand; the Clash Detection Matrix add-in on the Autodesk App Store exports selection and search sets and batch-creates tests from a matrix.
Step 4: Triage the results by constructability
The aim is not to find every conceivable overlap. Industry guidance, summarized in the Autodesk construction blog on BIM clash detection, argues that effective clash detection moves beyond geometry toward structured information management, concentrating on constructability issues and holding discipline leads accountable within defined timeframes under ISO 19650.
In practice, triage means sorting results into groups before anyone is assigned work:
- Group clashes by location and root cause. One misplaced riser can create fifty individual results that are really one issue.
- Reject false positives, such as insulation overlapping a pipe by design, and record the reason.
- Rank by consequence: structural impact first, then life safety and statutory clearances, then access and aesthetics.
- Decide who must move. As a rule of thumb, the element with the least routing freedom stays put, so a primary beam rarely moves and a branch duct usually does.
Where a structural element must change, the structural engineer needs to check the effect on the design, not just the geometry. A penetration through a transfer beam or a flat slab near a column is a design question, and the answer may require a revised detail or local strengthening rather than a rerouted service.
Step 5: Assign, track and report
Navisworks gives each clash a status. A new clash is one found for the first time, active means unresolved, then reviewed and approved, and resolved means it is no longer detected in the latest model (Autodesk Navisworks Clash Detective). Those statuses are only useful if the team uses them consistently. Resolved should never be set by the person who caused the clash; it should follow the next model submission, which confirms the conflict is gone.
Reports are then exported and circulated, normally ahead of the coordination meeting, with each issue showing a viewpoint image, location by grid and level, the elements involved and the named owner. Keep the meeting short. Its purpose is to decide, not to discover. Anything that cannot be decided by the people in the room goes to the design manager with a date.
A weekly rhythm typically looks like this:
| Day | Activity |
|---|---|
| Monday | Discipline models published to the shared data environment |
| Tuesday | Health check, federation and test run |
| Wednesday | Triage and issue assignment |
| Thursday | Coordination meeting |
| Following week | Fixes modelled, resubmitted and retested |
The days will shift with project size, but the fixed rhythm is what matters. Schedule control of the process also benefits from sound project controls, and our article on turning EVM and PMB into actionable project controls shows how coordination milestones can be tracked against the programme.
Step 6: Resolve, re-test and close
After fixes are modelled, the same tests are rerun against the new federation. Three outcomes are possible: the clash has gone, it persists, or a new clash has been introduced by the fix. The third is common when a service is moved into a space that another trade was also eyeing, which is why the tests are never retired until the final coordinated model is signed off.
Closing is more than an empty report. The coordinated model should be frozen and issued as the basis for shop drawings and fabrication. For steel and precast, that means detailed models in Tekla Structures feeding the fabricator, and any late change reopens the cycle. Where site constraints force a change after issue, record it as a formal change so the model, drawings and authority submissions stay aligned.
Where 3D is not worth the effort
Many teams fail by attempting to model everything in 3D for clash detection. Successful practitioners use 3D judiciously in congested zones such as corridors, plant rooms and complex MEP areas, and rely on targeted 2D coordination where 3D adds little (BIMCamel). A good rule is to ask what a wrong answer would cost. Above ceilings in a corridor with eight services, the cost is high and the model earns its keep. In an open car park with a single sprinkler line, a section drawing is enough.
This is also where the procurement of coordination effort meets budgeting: project managers who build a structured estimating workflow can allocate modelling and coordination hours to the zones that carry the most risk, instead of spreading them evenly.
For 4D conflicts, link the federated model to the construction programme so that space and time can be tested together, for example crane positions, temporary works and laydown areas. Procore’s overview of BIM clash detection notes that the process usually does not begin in design development, which is a reminder that the contractor and the temporary works designer should join the cycle before construction rather than after it.
Dubai and UAE considerations
In the UAE, technical skill in Navisworks is only part of the requirement. Commentary on the local market states that teams must also show fluency in ISO 19650 information management, including the management of the common data environment, Exchange Information Requirements and the Master Information Delivery Plan, as these tie into Dubai Municipality requirements for larger projects (Kaydenz). Confirm the current thresholds and submission rules with Dubai Municipality directly, because they are revised over time.
A role description for a BIM manager at a regional engineering firm, published on a recruitment platform, shows how this is applied: the lead appointed party has formal authority to accept, reject or delay information deliveries that fail agreed standards and the client’s Exchange Information Requirements. That authority is what gives a clash cycle its teeth. Without it, deadlines for resolution are merely suggestions.
For teams preparing permit submissions, coordinated models and clean structural information shorten review. Our articles on how BIM and DM submissions in 3D structural modeling speed Dubai Municipality approval and on preventing permit delays with BIM for structural engineering in the Gulf go further into this. Teams weighing methods can also read BIM versus CAD in Dubai civil engineering, and our practical guide to BIM for developers, contractors and consultants in the UAE and GCC sets out the wider context.
Common failure points and how to avoid them
Several problems recur on coordination programmes. Each has a direct remedy.
Unclear ownership. If a clash is assigned to a team rather than a person, it ages. Name one individual per issue and one date.
Mismatched levels of detail. Tests between models at different maturity produce false positives and false comfort. Align the development level of each discipline before comparing them.
Late structural input. Services are routed through space that the structure later claims. Bring the structural engineer in at the first federation, and review openings in beams and slabs as a design item.
Tool-led thinking. Hundreds of results are not progress. Fewer, grouped, ranked issues with owners are.
No closing discipline. If resolved clashes are not verified in the next model, they return. Make verification a standing agenda item.
Our perspective on coordination
From the structural side, we see clash detection as a risk control as much as a drawing check. Our work covers structural analysis and design in concrete, steel, timber, pre-engineered metal and tensile structures, authority approvals for Dubai Municipality and DDA, BIM integration and shop drawings, and that mix shapes how we view the process. The cheapest time to move a beam is before it is detailed, and the most expensive is after it is cast.
We also believe the workflow should be proportionate. Not every project needs a daily federation, yet every project needs a defined cycle, an accountable owner for each issue and a clear record of what was changed and why. In the Gulf, where designs are often prepared to ACI, Eurocode or British Standards and then checked against local authority requirements, the coordinated model must reflect the code basis actually used, so that what is submitted is what is built.
The teams that deliver reliably tend to be those that agree the rules early, keep the rhythm and treat the structure as the fixed frame around which the services are organised.
— Aman
Support from Integra
If your project needs a structural design that is coordinated with the other disciplines and ready for authority review, our team can help. We provide structural analysis and design, authority approvals management and construction supervision for projects in Dubai and across the Gulf, and you can see the full range of engineering services on our services page. To discuss a specific project, start from integradxb.com.
FAQ
What is the difference between a hard clash and a soft clash?
A hard clash is a physical overlap between two solid elements, such as a pipe passing through a column. A soft or clearance clash occurs when an element intrudes into space that must stay free for access, maintenance or safety. Hard clashes are usually fixed first, but clearance clashes can be just as costly if they are found after installation.
How do you resolve clashes in Navisworks?
Run the test, review the grouped results, then assign each issue to the discipline that should change. Update the status as work progresses and export a report for the coordination meeting. After the owner remodels and republishes, rerun the same test: a clash is resolved only when it no longer appears in the latest model.
How often should clash detection be run?
A fixed cadence works better than irregular checks, and many teams use a weekly cycle during active design. The right frequency depends on how quickly models change and how many disciplines are involved. Whatever the interval, publish, test, review and re-test on the same days each cycle.
Why does my clash report show thousands of results?
The most common cause is a coordinate or base point mismatch between linked models, which makes everything appear to overlap. Correct the shared coordinates first, then tighten selection sets and rules. Filtering by hand without fixing the source only hides the problem.
Does clash detection replace design coordination meetings?
No. It supplies the evidence, but people still have to decide who moves and how, often with input from the structural engineer where load paths are affected. The meeting turns results into decisions with owners and dates.
Sources
- Autodesk: Clash Detective Workflow
- Autodesk Construction: BIM clash detection
- BIMCamel: A practical BIM clash detection workflow
- infralens: BIM clash detection handbook
- Augmintech: What are BIM standards
- Autodesk App Store: Clash Detection Matrix
- Procore: BIM clash detection
- Kaydenz: Dubai BIM mandate explained
- Renata: BIM Manager role description