Clash Detection.

Each run is compared with the previous one: clashes that no longer exist are moved to resolved automatically and reported here, so nobody has to check by hand which ones were fixed.

Zoom to the clash in 3D or on the key plan, import BCF from another party, and export the report — the run of tasks that normally follows reading the table.

Choose the rule, severity, status, label group and level in the comboboxes; the table keeps only matching rows without expanding the UI into extra information blocks. For example, Hard clashes on L03 become an immediate meeting and assignment list.

Save the rule set for reuse, export it for another team, import theirs, then run — a rule set is shared property, not a one-off configuration.

Raw clashes stay local; only once you promote one to an issue can it be pushed and synced to the cloud — the gate that keeps the CDE from flooding with unreviewed noise.

Total issues with open, active, resolved and dismissed counts — the measure of coordination progress between two meetings.

Pick the cloud project, sync both ways, export standard BCF for partners on other software, and clean out issues that are closed.

Each row is an issue with severity, grid and level, status, priority, assignee, due date and the promoted timestamp — enough to assign work without a separate spreadsheet.

States how many issues are shown out of the total — so you never think the work is done while a filter is still on.

The chips show which subset the charts below are reading (severity, level, rule); clear them all to go back to the full data.

Total clashes and how many rules are enabled, with the share of each kind — the first numbers to read when opening a coordination report.

Breaks out hard, soft, clearance and duplicates — hard is what must be cleared before site work, the rest can be scheduled.

Compares the last eight runs to show whether clashes are dropping or growing — far more convincing at a coordination meeting than a single figure.

The heatmap points to the levels where severe clashes cluster, so you can put people where it matters instead of spreading thin.

Click a segment on a chart and this list narrows to that group — the path from a headline number down to individual clashes without leaving the dashboard.

Shows the two clashing elements with their category, system, level and grid right next to the charts — enough to judge which side should give way before opening Revit.