An editable visual model can still be expensive to update if a new design export overwrites the work that made it presentable. Before relying on a quick refresh process, ask the proposed supplier to demonstrate one representative model update through the actual visualisation workflow.
The demonstration should answer a practical question: which changes can arrive from the design team while preserving the accepted camera work, surface treatment and animation structure? A general statement that the files are linked is not enough.
Pick a realistic change
Choose something likely to happen during the commission. It might be a revised panel size, a relocated opening or a replacement product component. Include the surrounding scene, because the consequences may extend beyond the object being changed.
Avoid testing only a cosmetic edit if the design team expects geometric revisions. Equally, do not demand a complete rebuilding exercise when the only foreseeable change is a named finish. The test should reflect the uncertainty the buyer actually carries.
Epic's reimport guidance distinguishes preserved overrides from asset changes that may be overwritten. Different kinds of editing therefore need different update handling.
Compare the scene before and after
Review what was meant to change and what was meant to remain. Has the revised part arrived? Do its materials still refer to the right surfaces? Are camera targets and animated attachments intact? Has a deleted design element survived as a separate visual copy?
Ask the supplier to identify manual steps rather than concealing them behind an apparently seamless demonstration. A short, repeatable correction may be perfectly acceptable. The commercial issue is knowing that it exists and who will perform it each time.
Also ask what happens when the source team changes object names or grouping. If the visual workflow relies on stable identities, that dependency should be communicated upstream. The film supplier cannot guarantee continuity that the incoming data does not support.
A hypothetical reception revision
A fictional contractor commissions a visual sequence of a proposed reception area. After an early review, the designer moves the desk and changes its profile. The visual artist has already refined the desk surface and attached a camera target to it.
A trial update shows that the new geometry imports but a surface assignment needs repair. The camera relationship survives. The buyer can now understand the actual revision task instead of assuming either that everything must be rebuilt or that every future change will be automatic. This is an invented workflow example, not a time or price estimate.
Agree what triggers another check
Use the test to define a practical update boundary. Minor source changes may follow the demonstrated route; changed hierarchy, missing references or a substantially different shot may require reassessment. Record those triggers in language both the project team and production can recognise.
Keep the previous accepted scene available for comparison. A successful update is not merely a file that opens. It is a scene containing the intended new information without silently losing unrelated approved work. The buyer should receive a concise account of any differences still awaiting review.
This preparation is particularly useful when animation begins before design information has settled. It does not remove the need to agree which version the film represents. Discuss the expected model revisions with Live Images and ask how a suitable specialist workflow would be scoped, tested and maintained for the proposed film.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.