A bulk operation can produce more than one outcome. Some records may update while others remain unchanged. If that is a relevant behaviour of the demonstrated product, the film should not replace the result with one large success graphic. Viewers need to understand what the operation completed and what still requires attention.
Ask the product owner for an approved, harmless example of a mixed result. Do not deliberately damage live records or introduce an artificial failure into a customer account. A controlled demonstration environment and fictional records let the team explain the result without creating an operational problem for the sake of the camera.
Choose a legible mixed set
The audience should be able to distinguish the affected items before and after the action. A small group with clear fictional names works better than an anonymous wall of rows. Include enough variation to make the mixed outcome meaningful without requiring viewers to remember a long list.
Keep the product's own per-item status information visible where possible. If editorial annotation is necessary, distinguish it from native interface feedback. A production-added green tick must not imply that the software supplies a confirmation it does not actually provide.
Follow the unchanged items
In a fictional asset catalogue, a bulk label change applies to several records while two retain their earlier labels because of an approved demonstration constraint. The useful story follows those two records far enough to explain that they remain outside the completed result.
The film need not teach every recovery route. It should establish whether the user is expected to inspect details, seek another person's action or take a documented next step. The product owner must approve that boundary. A vague instruction to try again can be misleading if the completed records would be affected a second time.
Separate the summary from the evidence
A result banner can summarise the operation, but it may not communicate every item-level consequence. Give the audience a moment to connect the summary with the detailed list. This is a pacing decision, not an invitation to display confidential diagnostic information.
If the summary uses counts, keep their categories explicit. Completed, skipped and failed may have different meanings in the product. Do not merge them into a simpler two-colour graphic merely because that looks cleaner. The simplification must preserve the distinctions viewers need for the next decision.
Check the second action carefully
Where the film continues with a retry or correction, confirm which items that action includes. The recording should not accidentally imply that the entire original set needs to be processed again. Preserve any selection change that makes the second action safe and intelligible within the fictional scenario.
At review, ask which records now have the intended result and which do not. Then ask what evidence on screen supports that answer. A useful demonstration makes partial completion understandable without either disguising it as total success or presenting a recoverable mixed outcome as complete system failure.
Discuss the proposed explanation with Live Images and confirm suitability, production scope and the content owner’s review responsibilities. This unpublished draft uses a fictional example, not a claimed client project.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.