When this is useful
Write for a viewer who has not seen your interface before. Establish the starting screen and make changes in state explicit. If the workflow needs a particular role or prepared dataset, mention that briefly so the demonstration does not appear universally reproducible.
Adapt the script
- Define the end state before the opening. Work backwards to identify which actions are essential and which belong in another video.
- Keep screen and narration aligned. Say the name of a control when it is visible, and explain the result after it appears.
- Build in reading time. Pause on the dense view instead of treating every shot as a transition.
Why these scenes belong together
The sample leaves substantial room for the interface because the spoken text is deliberately shorter than a continuous ninety-second voiceover. The final timing should follow the real recording, particularly around filtering and export.
Illustrative 90-second reporting script
Illustrative copy to adapt. Replace bracketed fields and verify every claim against your product.
Limits and checks
“Save” and “export” are different results. Choose the one the footage actually completes; do not leave both in the final narration unless both are shown.
Your next step
Read the complete script while watching the rough cut. Mark any instruction that arrives before its control is visible.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.