ClashWise
One consultant wants a spreadsheet, the project manager needs a meeting record, and another team wants issues it can import into its own BIM tool. Each recipient needs a different output from the coordination record.
Choose the format for the recipient's next action, then check that it contains the scope and evidence they need.
Excel: when the data needs analysis
A spreadsheet is useful for filtering a clash list, counting issues by level or responsibility, and preparing a consultant's worklist. It gives recipients a format they can inspect and adapt.
Strengths: sortable rows, formulas and familiar analysis tools.
Limits: an exported workbook is a snapshot. Edits in the file do not automatically update ClashWise or Navisworks. A row can describe a clash, but it does not provide an interactive model view.
Use it for: working lists and analysis. If your project accepts spreadsheets as issued records, apply the same revision control and scope checks as any other deliverable.
PDF: when the record needs a fixed layout
A PDF is useful for distributing a readable record with a consistent layout. It suits meeting minutes and issued summaries when recipients need to read the decision rather than manipulate the data.
Strengths: familiar viewing tools and a layout that is easy to circulate and archive.
Limits: PDF is less useful for filtering a large list or importing issues into another tool. It still needs revision control; the format alone does not make a record immutable.
Use it for: meeting records and formal distribution. ClashWise session minutes use recorded clash changes and saved decisions and action items. Review that content before generating and issuing the PDF.
BCF: when another tool receives the issues
BCF is BIM Collaboration Format. A ClashWise BCF 2.1 package carries topics with issue details, comments, snapshots and viewpoints where available. It carries information about model issues, rather than the model geometry itself.
Strengths: a compatible issue tool can import the topics and use viewpoints to help locate them in the recipient's model.
Limits: the recipient needs compatible software and the right model context. Field mapping, element matching and viewpoint restoration depend on the importing tool. File export does not provide automatic two-way sync.
Use it for: handing issues to a team that works in another BIM review tool. ClashWise's BCF export lets you choose all clashes, the current filter or selected entries, with a live scope count.
Side by side
| Excel | BCF 2.1 | ||
|---|---|---|---|
| Main use | Analyse rows | Share a readable record | Import issues |
| Typical recipient | Coordinator or spreadsheet user | Project manager, client or meeting participant | Team using a compatible BIM issue tool |
| Model context | Data fields | Included images and written context | Snapshots and viewpoints, where available |
| Automatic changes back to ClashWise? | No | No | No; a file handoff is not a sync connection |
| Check before sending | Fields, scope and revision | Recorded content, layout and revision | Import behaviour and matching model context |
Other formats you may need
CSV is useful for scripts, reporting systems and importers that need plain rows. ClashWise offers the same scope choices as Excel. Confirm delimiters, field names and identifiers with the recipient.
Navisworks HTML reports can suit a project that needs a browsable export from Clash Detective. Check the included images and how the report will be stored and opened before adopting it as a regular deliverable.
Presentation slides can help explain a small number of design decisions. They take preparation and should reference the underlying issue record, especially when the model changes after the slides are assembled.
Choose the format and record its scope
Use the published clash set as the reference for clash exports and the saved session record for meeting minutes. Keep stable #N clash references visible so recipients can connect the output to the issue under review.
Different outputs can contain different scopes or be generated at different times. Record those choices and check them before sending; sharing a source does not guarantee that two files contain the same information.
During a 14-day trial, export a scoped worklist, create a meeting record and test a BCF sample with a recipient. Compare the result with what each person needs to do next. Plans and pricing explain the available coordination features and allowances.
Tags: Navisworks, Reports, BCF, Exports
