When this is useful
Without a shot list, a recorder may tour every screen yet miss the one confirmation that proves the promise. A motion designer cannot reliably reconstruct that evidence from unrelated screenshots.
The working process
- Break the script into claims and assign one visible proof to each. Record the actual action where the transition itself matters.
- Describe framing in terms of the region that must remain readable. Include separate mobile instructions when navigation or layout changes.
- Give every shot an identifier and reset condition. After capture, record its source filename and useful timestamps so the editor can locate it without replaying the whole session.
A production example
An illustrative shot S03 might read: “Open fictional task Atlas, assign Mira, save, then hold on the owner label.” Its result is a visible assignment, not a generic screenshot of the task list. S03-mobile may require opening a drawer first.
Shot record
Illustrative copy to adapt. Replace bracketed fields and verify every claim against your product.
Limits and checks
A shot list describes what to capture, while a storyboard describes how the edited sequence should look. Keep both linked, but do not assume a storyboard illustration is proof that the underlying action was recorded.
Your next step
Review the captured shot list for missing results before asking the editor to build transitions.
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.