Skip to main content

Frame Versions

What changed between two versions.

Added, removed, modified, with the property that moved and by how much.

Start free
Frame Versions template in Power BI showing added, removed, and modified element counts with a version control page

Report pages

Overview Version Control

“What changed?” is the question every model review starts with, and the one usually answered by opening two files side by side.

How it’s made

Frame matches elements across the two versions on the key that is actually stable for the source — external ID for Revit and Navisworks, IFC GlobalId for IFC — then classifies what moved. Anything it cannot match is reported as added or removed rather than quietly paired with the wrong counterpart.

How Frame builds it

Matched first, then classified

Version A baseline Version B target Match key external ID · GlobalId Property changed a value moved Geometry changed the shape differs Transform changed moved or rotated
A wall whose fire rating was corrected is not the same event as a wall that moved 400mm. Frame keeps the three apart instead of calling them all “modified”.

The property table carries the before and after: section, name, old value, new value, unit, and a numeric delta where the values are numeric. So you can report on the total area added, not just on how many elements were touched. Every comparison also states its own fidelity, so a degraded run never reads as a complete one.

Datasets in this report

FRAME_CHANGES
One row per element, with its change status, the match key used to pair it across versions, and separate flags for whether its properties, geometry, or transform changed.
FRAME_PROPERTY_CHANGES
Field-level before and after. Section, property name, old value, new value, data type, unit, and a computed numeric delta.

Read more

All report templates

Build reports that drive action

Discover the benefits of Frame today.

Get Started for free Contact Us