<aside> 🔖

Table of Contents

</aside>

Now we've successfully identified, documented, and assigned all clash issues in our project. Each issue now has a responsible person assigned.

The next crucial step is to communicate these issues clearly and effectively to those responsible, ensuring they're aware and can take necessary action.

How do we do that?

Typically, clash issues are shared using one of several common file formats. Each has its advantages, and the choice usually depends on your project's workflow or specific software requirements.

The most popular formats include:

• Spreadsheets - static
• Documents (.pdf or .txt) - static
• HTML files - static
• XML files - static
• BCF (BIM Collaboration Format) files - dynamic

<aside> 🗣 I don’t recommend using static reports → I recommend to create issue reports as BCF!

</aside>

1. Why I don’t recommend statis issue reports?

Using static reports like PDF, HTML, or Excel files for clash management in BIM projects is not the best approach. Here's why:

1. Not Interactive: You can't easily click or move directly to the clash in the 3D model. This makes understanding and fixing the problem harder.