ClashWise
For a BCF handoff, agree which issues the recipient needs and how they will open them in their review tool. Test a small package first, including its issue details and viewpoints.
This guide starts with a Navisworks clash test and uses ClashWise to export the published results as BCF 2.1.
What BCF contains
BCF is BIM Collaboration Format, a standard for exchanging issues about a model. A BCF package does not contain the model geometry itself.
In a ClashWise BCF 2.1 export, each clash in scope becomes a topic with issue details, comments, a snapshot and a viewpoint where available. A compatible receiving tool can use that viewpoint to show the issue against the recipient's model.
The recipient needs the matching model context. Camera restoration, element matching and other details depend on the importing tool, so check the result together before making it the routine handoff.
Step 1: Publish the clash set from Navisworks
Run the required tests in Navisworks Manage, then use the ClashWise plugin to publish the results. Download the plugin and check the supported versions if you have not installed it yet.
Each published clash has a stable number within its set, such as #1, #47 or #312. Keep that reference and add a descriptive title. Review any AI-generated title before sending it to another team.
Step 2: Open the clash set on the web
Sign in to ClashWise and open the published set. Check that the results and model revision match the issue you intend to send.
Filter by the recipient's scope, such as responsibility or location, and review the list. A facade consultant should receive the relevant facade issues, with enough context to understand what each action requires.
Step 3: Choose the export scope
Open the export dialog and choose BCF. The scope choices are:
- All clashes in the set: the complete list.
- Matching current filter: the clashes matching your active filter.
- Selected clashes: the entries you selected for this handoff.
Check the live count before exporting. The scope choices also apply to Excel and CSV, but each format carries different information.
Step 4: Export and download
Download the .bcfzip when it is ready. Larger exports run in the background and appear in the export tray on the toolbar; wait for Ready, then download the file.
ClashWise delivers the file through the browser. Upload it to the common data environment or send it using the project's agreed issue procedure, with the model revision and intended recipient scope.
For eligible member review packages, check any chosen saved or current viewpoints and the annotations or measurements you intend to include. Exporting those details does not guarantee that every receiving tool will restore them identically.
Step 5: Import into the target tool
Ask the recipient to import a small sample into their BCF 2.1 workflow, whether that is BIMcollab, Solibri or another compatible tool. Then check:
- The expected number of topics arrived.
- Clash references, titles and comments remain readable.
- Snapshots and viewpoints show the intended issue.
- The correct model revisions and elements are available.
- Status and assignment mappings fit the recipient's workflow.
Agree how later updates will be handled. A downloaded file is a snapshot; it does not establish automatic two-way synchronisation between the tools. See the BCF export page for the ClashWise workflow.
Availability and practical checks
BCF export belongs to the Clash Management workflow. Check plans and allowances and the permissions for the set you intend to export.
Existing read access and export behaviour during a read-only subscription state should be checked with your organisation's account. Do not assume that member access, guest sharing and every export option have the same permissions.
When updating an existing set, keep the publication destination and clash identities consistent. Recheck the export count after a test rerun or filter change.
Common questions
Why BCF 2.1? ClashWise produces BCF 2.1 packages. Confirm that your recipient's tool supports that version and test the fields and viewpoints your project needs.
One large file or one per consultant? Use the agreed recipient scope. The current-filter option is useful when each consultant has a separate worklist.
What happens after the clashes change? Export again from the updated set. Stable clash numbers help people compare issues, but the importing tool determines how it matches topics and handles updates.
Do I need to keep Navisworks open? Once the set is published, this export runs in the browser. Use the plugin when publishing or updating the Navisworks results.
Check the handoff before repeating it
Publish the correct results, confirm the scope, download the package and inspect a sample in the receiving tool. Keep that checked sample as the basis for your project's handoff procedure.
Start a 14-day ClashWise trial to test the process with your own clash set.
Tags: Navisworks, BCF, Tutorial, Interoperability
