Running clash detection is easy. Turning the results into fewer RFIs and less rework on site is harder. Many projects generate thousands of clash items that never get properly triaged, owned or closed. This guide outlines a practical process that focuses effort where it matters.
1. Start with a Clear Coordination Strategy
Before the first clash run, agree with the design and construction teams:
- Which systems will be federated and in what order (structure first, then architecture, then major MEP, then secondary systems)
- Tolerance rules for hard clashes, soft clashes and clearance zones
- Who owns resolution for each discipline
- The cadence of model submission and federated review (typically weekly during detailed design)
Document these rules in the BIM Execution Plan so expectations are shared from day one.
2. Federate with Purpose, Not Automatically
A useful federated model is current, correctly positioned and free of obsolete geometry. Establish a simple naming and versioning convention for model exports. Reject or quarantine models that arrive late or with known major issues so the clash results remain trustworthy.
3. Prioritize Ruthlessly
Not every clash deserves the same attention. Group results by:
- Critical path / high risk — elements that affect structure, primary services, life safety or major equipment
- High volume but low impact — many small intersections that can be resolved by rule or batch decision
- False positives — temporary objects, intentional penetrations, or modeling artifacts that should be filtered out
Spend coordination meeting time only on the first category. Everything else should be handled offline with clear owners and deadlines.
4. Make Ownership and Status Visible
Every open issue needs an owner, a due date and a status (Open / In Progress / Resolved / Accepted Risk). Tools such as Navisworks issues, BIM 360 / ACC issues, or a shared tracker all work if the team actually uses them. The goal is that no critical clash disappears into an email thread.
5. Run Focused Coordination Workshops
Effective coordination meetings are short and visual. Share the federated model view, zoom to the problem area, capture the decision, and move on. Avoid turning the meeting into a general design review. Keep a running log of decisions so the same clash is not re-discussed next week.
6. Close the Loop with Verification
After a resolution is claimed, re-run the relevant clash tests on the updated models. Only then mark the issue closed. This simple verification step prevents “resolved” clashes from reappearing later as RFIs on site.
Hard Clash vs Soft Clash vs Clearance
Hard clash: two elements physically occupy the same space.
Soft clash: elements violate a required clearance or maintenance zone.
Clearance / workflow clash: installation sequence or temporary works conflict even if permanent geometry is clean.
All three types matter. Soft and clearance clashes are often the ones that cause the most disruption during installation if left unresolved.
The best coordination processes treat clash detection as continuous quality control, not a single gate at the end of design.
Measurable Outcomes
Projects that follow a disciplined prioritization and ownership model typically see:
- Dramatic reduction in open critical clashes before construction start
- Fewer spatial RFIs during structural and primary services installation
- Clearer accountability when issues do arise
- Better use of limited coordination meeting time
Need support setting up or running a coordination process on your project? Contact BIMwave Solutions — we provide clash detection, issue tracking and workshop facilitation for architecture and structure focused teams.
Related reading: BIM Levels of Development Explained · Case Studies · Clash Coordination Services