Skip to content

Clash Review

Clash Review brings coordination clash results into Revit, so you can navigate to clashing elements, assign review statuses, and prepare for coordination meetings without switching between applications. Currently supports Navisworks XML imports, with additional clash sources on the roadmap. All review data is saved in the Revit model, so your work travels with the project file.

Find Clash Review on the Amorphous ribbon tab in the Coordination panel.


  • Navisworks XML import - Import clash test results exported from Navisworks Clash Detective
  • Reconcile on re-import - Re-importing a test preserves your existing reviews and marks removed clashes as stale
  • Coordination Worklist mode - Groups clashes by parent group for a higher-level overview
  • Editable review fields - Status, Trade Owner, Notes, and Reviewed By for every clash
  • Pin/favorite rows - Pin important clashes to the top of the list for quick access during meetings
  • Element selection - Highlight the source or target element directly in Revit, including elements in linked models
  • Section Box integration - Isolate the clash area using Smart Section Box with one click
  • Clash point marker - Place a visible marker sphere at the exact clash location
  • Zoom to clash - Jump to the clashing elements in your current view
  • Filters and search - Filter by status, test name, or free-text search, and hide stale clashes
  • Persistent storage - All review data is saved in the Revit model and travels with the project file

Before using Clash Review, export your clash results from Navisworks:

  1. Run clash tests in Navisworks Clash Detective
  2. Export as XML - Right-click the clash test and choose Report > Write Report with XML format
  3. Export each test separately as its own XML file for best results

Make sure your Navisworks XML report includes the following fields:

FieldWhy It’s Needed
Element ID (Object Attributes)Identifies the clashing elements in Revit
Element Properties UniqueId (Smart Tags)Identifies elements in linked models
Clash PointPlaces the marker sphere at the exact conflict location
Parent GroupEnables Coordination Worklist mode grouping

Follow these steps to configure your Navisworks XML export with the correct fields.

Open the Report tab in Clash Detective and configure the export options. The screenshot below shows the minimum required settings. You can enable additional fields, but these must be checked for Clash Review to work correctly:

Contents (minimum required):

FieldRequired
Clash PointYes
Item PathYes
Item IDYes
StatusYes
Clash GroupYes
Quick PropertiesYes

Other fields like Date Found, Distance, Description, and Grid Location are optional but recommended for a more complete report.

Output Settings:

  • Report Type - Set to All tests (separate) to export each test as its own file
  • Report Format - Set to XML

Field Definitions (Navisworks 2025 and Earlier)

Section titled “Field Definitions (Navisworks 2025 and Earlier)”

Add the required fields to your report definition:

UniqueId - Add from Element Properties in Definitions

This field allows Clash Review to locate the exact elements in your Revit model, including elements inside linked models.

Navisworks 2026 changed the report configuration interface. The same field is needed, but the steps to add it are different:

UniqueId - Add from Element Properties in Property Set

  1. Click Clash Review on the ribbon
  2. In the launcher dialog, click Import New
  3. Select your Navisworks XML file
  4. The review window opens with all clash results loaded
  1. Browse the clash list using the data grid
  2. Filter by status, test name, or search text to narrow down results
  3. Click a row to select a clash
  4. Use action buttons to navigate to the clash in Revit:
    • Zoom To Clash to jump to the location
    • Select Source or Select Target to highlight individual elements
    • Section Box to isolate the area
    • Show Clash Point to mark the exact location with a visible sphere
  5. Set review fields for each clash:
    • Status - Current review state
    • Trade Owner - Team responsible for resolution
    • Notes - Free-text comments
    • Reviewed By - Who reviewed this clash
  6. Save Reviews to store your changes in the model

When clash tests are re-run in Navisworks:

  1. Click Re-Import in the review window
  2. Select the updated XML file
  3. The reconcile engine merges the new results with your existing reviews:
    • New clashes are added
    • Existing clashes keep their review data
    • Removed clashes are marked as stale

Click the pin icon on any row to pin it to the top of the list. Pinned clashes stay at the top regardless of sorting or filtering, making them easy to find during coordination meetings.


The launcher dialog appears when you first click the Clash Review button:

OptionDescription
Import NewSelect a Navisworks XML file to import
Review ExistingOpen the review window with previously imported data
Clear Saved DataRemove all stored clash and review data from the model

The review window is a modeless panel that stays open while you work in Revit.

ElementDescription
Mode dropdownSwitch between Individual Clash Results and Coordination Worklist
Status filterShow only clashes with a specific status
Test Name filterShow only clashes from a specific test
Search boxFree-text search across clash names and descriptions
Hide Stale toggleHide clashes that no longer appear in the latest import
Data gridSortable, editable table of all clashes
Pin columnClick to pin/unpin rows to the top
Action buttonsZoom To Clash, Select Source, Select Target, Section Box, Show Clash Point
Re-Import buttonImport an updated XML file
Save Reviews buttonSave all review changes to the model
Settings gearOpen settings popup

Click the gear icon in the title bar to access settings:

SettingDescriptionDefault
Sphere RadiusSize of the clash point marker1 ft

ModeBest ForDescription
Individual Clash ResultsDetailed reviewEvery clash shown as its own row with full details
Coordination WorklistMeeting prepGroups clashes by parent group, showing one representative row per group. Reduces hundreds of clashes to a manageable list.

StatusIntended Use
PendingNot yet reviewed (default for new clashes)
AcceptedClash acknowledged, action planned
In ProgressResolution underway
Needs InfoMore information required before a decision
Not An IssueFalse positive or acceptable condition
Ready For MeetingFlagged for coordination discussion
ResolvedClash has been fixed

Click Show Clash Point to place a visible orange sphere at the exact clash location. This helps identify the precise point of conflict, especially in dense areas with many elements nearby.

  • The marker appears as a semi-transparent orange sphere
  • Click Show Clash Point again to remove it
  • The marker is automatically removed when you close the review window
  • Adjust the sphere size in Settings if the default is too large or small for your model scale

After selecting a source or target element, click Section Box to invoke Smart Section Box on that element. This isolates the clash area so you can inspect it without surrounding elements blocking the view.

The Section Box button tracks which element you last selected (source, target, or both) and applies the section box accordingly.


  • Save reviews frequently to avoid losing work if Revit closes unexpectedly
  • Use Coordination Worklist for meetings, switch to Individual mode for detailed review
  • Pin clashes before meetings so the important items are always visible at the top
  • Re-import regularly as the design evolves to keep your clash data current. Existing reviews are preserved.
  • Combine Section Box with clash point markers for the clearest view of each conflict
  • Use status filters to focus your review session (e.g., show only “Pending” clashes to work through the backlog)
  • Assign Trade Owner for each clash so team members can filter for their responsibilities
From the developer

Clash Review was designed to replace the back-and-forth between Navisworks and Revit during coordination. The goal is simple: see the clash, look at it in your model, make a decision, move on. If your coordination workflow involves formats or tools beyond Navisworks XML, open an issue on GitHub and let me know what you’d like supported.


LimitationDetails
Navisworks XML onlyCurrently the only supported import format. Other formats (BCF, BIM 360, etc.) are not yet available.
Clash point marker is a model elementThe sphere is a real element in the model. It is automatically cleaned up when you close the review window.
Section Box requires Smart Section BoxThe Section Box button depends on the Smart Section Box add-in being installed and enabled.
Linked element selectionYou can select elements in linked models, but only one linked element at a time.
Revit 2022 linked element selectionIn Revit 2022, selecting Source/Target for elements in linked models will select the link instance, not the element within it. This is an API limitation in Revit 2022. Select the element in the host model first, then create a section box if needed.

Possible causes:

  • The XML file does not contain clash test results
  • The file was exported in a format other than XML

Solution: Verify the file is a Navisworks Clash Detective XML export. Open the file in a text editor and check that it contains <batchtest> or <clashtest> elements.

Possible causes:

  • No clash data has been imported yet
  • Saved data was cleared

Solution: Use Import New to load a Navisworks XML file first.

Clash point marker appears in the wrong location

Section titled “Clash point marker appears in the wrong location”

Possible causes:

  • The Revit model’s shared coordinates do not match the Navisworks coordination setup

Solution: Verify that shared coordinates are properly configured between your Revit model and the Navisworks file. The clash point position depends on matching coordinate systems.

Possible causes:

  • No source or target element has been selected yet

Solution: Click Select Source or Select Target first, then click Section Box.

Possible causes:

  • The element may have been deleted or modified since the clash test was run
  • The linked model containing the element may not be loaded

Solution: Re-import the clash data after updating the model. Ensure all relevant linked models are loaded.