Snapshot and diff
- Save a JSON snapshot of the model at any milestone
- Compare two snapshots: added, modified, deleted, moved
- See exactly which parameter changed, from which value to which
Compare two moments of the same model through JSON snapshots: which elements were added, deleted, edited or moved — know what changed before you issue.
The model changes with every save, but Revit keeps no earlier version to compare against — the only way to know what was added, deleted or moved is to open two files side by side and spin through every viewing angle hoping to spot the difference by eye.
Old file and new file open side by side, spinning through every level and zone in 3D to spot what changed — on a model with a few thousand elements this is slow and things slip through.
When the client or a subcontractor disputes a quantity change, there is no earlier snapshot to compare against — who's right comes down to memory and hearsay.
Revit keeps no record of a parameter's previous value once you save — a mis-edited elevation, material type or code only surfaces after the drawing set or take-off has already gone out.
An element deleted by accident, or swept up in a cleanup, triggers no warning in Revit at all — whether anyone notices depends entirely on somebody happening to spot it missing.
TrackChanges — Jeremy Tammik's free, open-source add-in — uses this exact mechanism: periodic snapshots, hash-compared for changes, but it stops at logging and never colours the 3D view or exports a report. Autodesk Assemble can show a visual diff through its Visual Variance tool, but that's a separate Autodesk Construction Cloud add-on, priced through an enterprise contract and detached from the Revit session itself. Element Tracker keeps snapshot, diff and presentation in one add-in:
The interface is matched to the tool window running in Revit.
Detect clashes in Revit, drop duplicates, generate screenshots and key plans, promote to issues and sync with the CDE.
A pane that follows cloud issues — click to zoom and section-box the clash, edit status and comment in place.
Check and author model data-quality rules. Rules run locally or sync from the cloud so the whole team shares one standard.