Who this is for: Teams teaching version recovery.
What to prepare
- Version history
- Current and selected content
- Restore confirmation
- Post-restore current state
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Identify the current state
Show sample document D-022 with the heading Sample release notes — revised.
On screen:Inspect the current document
- 02
7–16s
Open version history
Use the actual history control and show supplied version labels.
On screen:Choose a restore point
- 03
16–27s
Preview an earlier version
Select the earlier sample snapshot and hold Sample release notes — draft.
On screen:Preview the earlier content
- 04
27–37s
Compare the difference
Align the changed heading or short passage with the current version using verified comparison behavior or a labeled editorial layout.
On screen:This is the content that will return
- 05
37–47s
Commit the restoration
Show the real confirmation, including material consequences, then the actual restore action.
On screen:Restore the selected version
- 06
47–56s
Verify the current result
Open or inspect the resulting current document and its actual version label.
On screen:Restored content is now visible
- 07
56–60s
Close on the boundary
Hold the restored heading without implying erased history or universal recovery.
On screen:Recovery verified for this sample document
Make it your own
- Restore point
- Use an exact supplied version label distinct from the current version.
- Compared content
- Choose a short meaningful difference that remains readable before and after restoration.
- Restore consequences
- Preserve confirmation warnings and actual post-restore version/history behavior.
Prepare version facts
Supply the exact current, historical and restored states. Record how the product handles history after restoration. Do not invent a new version number or claim that later content is deleted unless that is the real behavior.
Adapt the recovery scope
For a settings snapshot, compare one consequential value and preserve the confirmation scope. For 30 seconds, use a short passage and fewer camera moves; keep preview, commitment and verification. A simple Undo task belongs in a separate sequence.
Review the decision
Confirm that the viewer sees what will change before the action. Preserve warnings that affect the choice. The final state must be current content, not merely a historical preview that resembles a successful restoration.
Review checklist
- The selected version is unambiguous.
- Consequential confirmation text is preserved.
- The resulting current state is verified.