An object reference helps identify what a record concerns, but it does not tell the audience that the record is unchanged. When a film follows a model object through revisions, distinguish its identity from the state of its geometry and properties. The same selected item can be the subject of different dated information.
buildingSMART's IFC root documentation presents identity and revision control as separate concepts. The client's model owner should confirm the actual identity and version relationship in the featured workflow rather than relying on a generic assumption about identifier persistence.
Decide what is being compared
Ask whether the film follows the same object through two information states, compares two different objects or shows a replacement. Those stories need different captions. Visual similarity alone cannot resolve the question, and a repeated readable name is not enough.
Obtain the approved version pair and a brief statement of the relevant change. The production should not search two complex models for differences and infer a project decision without specialist confirmation.
If the object's identity was regenerated during export, the client may need to provide a separate mapping. The film can use that approved relationship without claiming that one technical identifier survived unchanged.
Give each state a visible time or revision label
A split screen can compare states, but the labels should identify the source versions rather than simply say “old” and “new”. Those words become ambiguous when the film is reused later or when another revision already exists.
Keep the selected object in a consistent visual reference. Camera changes can make an unchanged shape appear different, while identical views can hide a property change. Choose a treatment that matches the actual information being compared.
Do not animate a smooth physical transformation if the story is only about a revised record. A morph can imply an installed component changed shape on site, when the evidence concerns design information.
A hypothetical revision account
Suppose a project team supplies two model states with a traceable object relationship. The first film says that the identifier is unchanged and therefore the object is “the same in every respect”. The later record actually contains an approved property change.
The buyer revises the statement to preserve continuity of identity while showing the changed information. The sequence becomes a clearer account of the revision without inventing a physical event. This example is fictional.
For approval, ask which aspects viewers believe stayed the same and which changed. The answers should come from the client's evidence, not from the stability of an on-screen label.
The commission should preserve an authorised revision narrative. It does not certify model history, guarantee identifier behaviour across applications or replace the project's change-control records.
If the sequence jumps between dates, retain the date beside the object rather than only on an opening title.
Discuss the film
Contact Live Images to discuss whether this approach suits your brief and what production scope would be appropriate.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.