Skip to content

CHANGETRACE / BIM & IFC

Understand the change. Review the impact.

A model revision can affect more than geometry. ChangeTrace is a planned h.ai product concept for comparing BIM / IFC revisions and preparing a source-linked impact review across project disciplines.

Planned product · illustrative concept walkthrough

16-second silent concept walkthrough · synthetic examples · no live AI · not a client result.
Read the walkthrough transcript

Compare two agreed model revisions. Identify added, removed and changed elements using agreed identifiers. Carry quantity differences and source references into engineering, BOQ / QS, procurement and planning review. An authorized reviewer decides what the change means for the project.

Compare an agreed revision pair

Begin with two authorized model exports, their revision history and a defined comparison scope. Check IFC version, model origin, units, property naming and identifier consistency. If identifiers are missing or unstable, agree a matching method and flag uncertainty rather than treating the comparison as exact.

Build an evidence-led change register

The proposed output records added, removed and changed elements, relevant property or quantity differences, and the source revisions involved. Distinguish a model change from a confirmed project impact. A dependency can be flagged for review without claiming that a programme delay or payable variation has been established.

Connect the right reviewers

Engineering assesses design and coordination implications. QS / commercial checks quantity and valuation assumptions. Procurement checks affected orders and lead times. Planning reviews programme dependencies against the current plan. The project manager retains release authority under the agreed approval process.

Validate before wider use

A sensible pilot would use a small, representative revision pair and a manually reviewed reference set. Agree how to measure change-detection precision, missed changes, traceability and reviewer effort. Supported model formats, element coverage and integrations would be confirmed during scoping, rather than assumed.

Questions before you start

Does this automatically approve a variation?

No. The concept assembles changes and evidence for review. It does not determine contractual entitlement, approve cost or authorize changed work.

Is the video a deployed product?

No. It is a short, synthetic motion walkthrough of the planned workflow, not a recording of production software or live model inference.

Start with one workflow.

Tell us where your team keeps searching, waiting or repeating work. We will discuss a sensible first step and the information needed to scope it.

Email h.ai → Explore the interactive prototypes