BIM Coordination & Quality Control

How to compare two Revit models and see what changed in a linked file

Whenever consultants reload structural, MEP, or architectural links, unannounced geometric shifts and parameter changes threaten design coordination. Here is how leading BIM teams audit revisions, detect coordinate drift, and eliminate blind spots.

By(Architect & Revit API Developer)
Updated: October 2026Revit 2023 - 202710 min read
Quick answer

Revit cannot list every difference between two RVT versions on its own. For linked consultant models, set up Copy/Monitor and run Coordination Review after each reload: it reports changes to monitored levels, grids, columns, walls and floors. For a full list of added, modified and deleted elements, use Navisworks Compare, ACC Model Compare, or a local diff add-in.

In large-scale BIM projects, model coordination breaks down not because teams fail to communicate major design milestones, but because of unannounced micro-changes. A structural engineer shifts a grid line 25mm to accommodate connection plates; an MEP coordinator lowers ductwork 150mm; a facade consultant replaces a curtain wall profile with a thicker extrusion.

When you click Reload in Revit's Manage Links dialog, Revit simply redraws the model. It offers zero native feedback on what was added, what was modified, and what was silently deleted.

Native method: Copy/Monitor and Coordination Review

Revit's built-in way to watch a consultant model is Copy/Monitor. It ties your levels, grids and selected elements to their counterparts in the linked model, and Coordination Review lists what moved or changed after each reload.

  1. Link the consultant model (Insert > Link Revit), positioned by shared coordinates.
  2. Collaborate > Copy/Monitor > Select Link, then pick the linked model.
  3. Use Copy for levels and grids you want in your model, or Monitor for elements you already have, then Finish.
  4. When a new version arrives, reload the link in Manage Links.
  5. Collaborate > Coordination Review > Select Link: Revit lists changed monitored elements, and you can accept, reject or postpone each change.

The limit: it only sees elements you set up for monitoring, in a handful of categories. Ducts, pipes, families, type swaps and parameter changes outside that set are not reported.

5 ways to compare Revit model versions

MethodWhat it detectsLimits
Visual overlay (toggle links, colour overrides)Obvious geometry moves you happen to noticeManual; misses small shifts, deletions and parameter changes
Copy/Monitor + Coordination ReviewChanges to monitored levels, grids, columns, walls, floorsNeeds setup in advance; limited categories; no parameter diff
Navisworks Manage: CompareDifferences between two loaded models or versionsNeeds NWC exports of both versions and a Navisworks licence that includes Compare; results live outside Revit
ACC / Autodesk Docs Model CompareAdded, removed and modified elements between published versionsBoth versions must be uploaded to the cloud; ACC access for every user
Local diff add-in (e.g. Karo.WhatsChanged)Added, modified, deleted elements and parameter deltas, inside RevitPaid add-in; keeps snapshots locally, so it tracks changes from its first run

Navisworks Clash Detective finds intersections, not changes: a wall that moves away from a duct produces no clash. Use the Compare tool, not Clash Detective, for version differences.

Standard Operating Procedure

The 5-Point Linked Model Audit Protocol

5 Critical Checks

Follow this systematic checklist whenever a consultant submits an updated milestone file:

01Site & Positioning

Coordinate System & Shared Site Drift

Consultants frequently modify survey points, base points, or project north without notifying the lead architect, shifting the entire linked building relative to grids.

How to verify: Check the Survey Point and Project Base Point coordinates between the previous version and current link reload. Verify the link's Shared Site and positioning in Insert > Link > Manage Links and the link instance Properties.
Risk if missed: Multi-discipline model misalignment, erroneous clash test results, and catastrophic on-site footing/grid discrepancies.

How to detect and fix shared coordinates drift →

02Geometry

Structural & Envelope Geometric Shifts (> 10mm)

Columns, shear walls, slab edges, or major MEP risers shifting subtly between design milestones without explicit revision clouds or notification.

How to verify: Overlay previous milestone RVT as an underlay with a high-contrast override (e.g., magenta vs green), or inspect critical grid-to-element dimension strings.
Risk if missed: Pipes clashing with relocated structural beams, facade panels failing to align with shifted slab edges, and costly structural redesigns.
03Parameters

Type Swaps, Fire Ratings & Structural Parameter Deltas

A wall remains in the exact same spatial location, but its Type has changed (e.g. 2-hour drywall changed to 1-hour drywall, or acoustic insulation stripped).

How to verify: Spot-check critical schedule parameter fields or extract full element schedules to Excel and perform VLOOKUP/diff comparison on Element IDs.
Risk if missed: Code compliance failures during permitting, acoustic test failures post-construction, and incorrect material cost estimates.
04Integrity

Silent Deletions of Shared Datum Elements (Grids & Levels)

A consultant deletes or re-creates a level or grid line instead of modifying it, breaking hosted elements in other disciplines.

How to verify: Compare element count schedules by category. Ensure grid letters and level names match historical project milestones with exact Element IDs.
Risk if missed: Disassociated dimensions, orphaned hosted tags, and views failing to show proper elevation annotations.
05Re-hosting

Workset & Level Re-Hosting Modifications

Elements reassigned to different worksets or re-hosted from Level 01 to Level 02 with negative offsets, causing false schedule grouping.

How to verify: Inspect element properties for 'Schedule Level' and 'Workset' attributes across major structural and MEP packages.
Risk if missed: Erroneous floor-by-floor quantity takeoffs and elements vanishing when standard discipline view templates filter by workset.

How to fix linked model phase mapping and link display →

Automated Revit Diffing

Eliminate blind spots with Karo.WhatsChanged

Karo.WhatsChanged v1.15.1

Instead of spending hours manually searching for consultant shifts or waiting for slow cloud uploads, Karo.WhatsChanged performs 100% on-premise SQLite diffing inside Revit in seconds:

  • Local SQLite diffing - zero cloud lag or file limits
  • Focus Dim & automated 3D section boxes around shifts
  • Exact Old → New parameter and dimension deltas
  • Formatted Excel & PDF reports for coordination meetings

Frequently Asked Questions

Can Autodesk Revit compare two models natively?

Only partly. Copy/Monitor plus Coordination Review tracks changes to monitored levels, grids, columns, walls, floors and a few other categories in a linked model, and reports them when the link is reloaded. Revit has no built-in tool that lists every added, modified and deleted element between two RVT versions; for that you need Navisworks Compare, ACC Model Compare or an add-in.

How do I see what changed in a linked Revit model after reloading it?

Reload in Manage Links does not report changes. If you set up Copy/Monitor before the change, run Coordination Review (Collaborate tab) to see changes to monitored elements. For a full element-by-element list you need a snapshot of the previous version to compare against: export both versions to Navisworks and use Compare, publish both to Autodesk Docs and use Model Compare, or use a local diff add-in such as Karo.WhatsChanged.

How does local Revit model compare differ from Autodesk Construction Cloud (ACC)?

ACC Model Compare works on model versions published to Autodesk Docs, so both versions have to be uploaded and processed in the cloud, and every user needs ACC access. A local diff runs inside Revit on your machine, which suits confidential projects and links that never go to the cloud.

How does local comparison perform on very large Revit models (500MB+)?

Karo.WhatsChanged indexes geometry and parameters in a local SQLite database instead of uploading files, so the comparison time depends on element count rather than file size, with no upload step.

Related WhatsChanged guides