Skip to content
KitWren
AdvancedFree BIM course about 20 min

Coordination and clash detection

Coordination turns separate discipline models into a buildable whole. Learn how professional teams run clash detection so it resolves real problems instead of producing noise.

In this lesson you will

  • Set up a federated model and clash matrix
  • Choose tolerances and rules
  • Group, prioritise and assign clashes
  • Run effective coordination meetings

Federation

Each discipline exports or publishes its model at the agreed cadence. The coordinator combines them in a coordination tool, checks they align (shared coordinates), and saves a federated file referencing the latest versions.

A duct from the mechanical model passing through a steel beam from the structural model, with the intersection highlighted as a hard clash.Steel beam (structural model)Duct (mechanical model)Hard clashtwo objects occupy the same space
Figure: A clash between two models. Original KitWren diagram.

The clash matrix

Don't test everything against everything. A clash matrix lists which model sets are tested, with which rules and tolerances — e.g. Structure vs Mechanical ducts: hard clashes over 25 mm; Mechanical vs Electrical: clearance 50 mm for cable trays. Include priorities: structure and large ducts first, small services later.

TestTypeTolerance (example)
Structure vs ductsHard25 mm
Ducts vs pipesHard10 mm
Cable trays vs anythingClearance50 mm
Architecture vs structureHard10 mm

From clashes to issues

A single duct through a beam may produce dozens of clash results. Group them by element, level or zone into issues, set status (new, active, reviewed, approved, resolved), assign a responsible party and a due date, and share them as BCF or through the platform. Track counts over time — the trend matters more than the number.

Meetings

Keep coordination meetings short and visual: review new high-priority issues in the model, agree who moves what, and confirm resolved items. Record decisions. Designers fix their own models; the coordinator verifies in the next round.

Common mistakes

  • Testing whole models against each other with zero tolerance.

    Use a clash matrix with sensible tolerances; otherwise real issues drown in noise.

  • Reporting raw clash counts as progress.

    Report grouped issues and trends; one duct can create fifty results.

  • Coordinating models with different origins.

    Check shared coordinates on every model before running tests.

Exercise

Write a clash matrix

  1. List the models for a small hospital wing (architecture, structure, mechanical, electrical, hydraulic, fire).
  2. Write a clash matrix with types, tolerances and priorities.
  3. Describe how you'd group results into issues for the first meeting.

You should end up with: A clash strategy that produces actionable issues.

Checklist

0 of 5 checked · saved on this device

Lesson quiz

1 / 4

Why use a clash matrix?

Finished this lesson?

Taking the quiz marks it complete too. Your course page picks up where you stopped.

Free KitWren tools that help

Free, independent learning material written for KitWren. We never provide software downloads, licence keys or cracks — use the official sources.