Who this is for: Teams explaining data-import preparation in their own products.
What to prepare
- Illustrative file
- Actual field requirements
- Mapping and preview screens
- Observed validation feedback
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
State the preparation task
Show the sample file and destination object type with a clear illustrative label.
On screen:Prepare a sample request import
- 02
8–18s
Inspect the file
Show three fictional rows and headers Request title, Reviewer and Status. Keep sample identities consistent.
On screen:Check headers and required values
- 03
18–29s
Map the fields
Use the actual mapping controls to connect Request title to the verified destination title field. State other required mappings.
On screen:Match source columns to destination fields
- 04
29–39s
Inspect the preview
Show the actual preview with the three sample records and their mapped values.
On screen:Preview before committing
- 05
39–49s
Resolve a validation issue
Show a supplied missing-reviewer warning, correct the sample value through the supported method and rerun validation.
On screen:Correct the missing reviewer
- 06
49–56s
Verify the prepared state
Hold the validated preview and exact product status. Do not activate a live import.
On screen:Sample preview validated
- 07
56–60s
State the boundary
Use an explicit closing label separating preparation from execution.
On screen:Preparation complete · Import not committed
Make it your own
- Sample file and fields
- Supply harmless rows, required headers and actual destination field definitions.
- Validation issue
- Use one observed issue and the product-supported way to correct and revalidate it.
- Commit boundary
- Keep this preparation asset short of import execution unless a separately evidenced execution sequence is intentionally added.
Prepare validation rules
Supply required columns, accepted values and actual preview behavior. Use a harmless sample file. If validation happens only after commitment in the real product, change the storyboard rather than inventing a preflight feature.
Adapt the file
A contact or inventory file needs its own field definitions and identity checks. For 30 seconds, focus on one mapping and one preview check, with other prerequisites stated. Do not imply all file formats are supported.
Review the commit boundary
Keep the final action clearly short of execution when the lesson is preparation. If a later version demonstrates import, add separate authorization, execution and destination verification evidence. A successful preview does not prove records arrived.
Review checklist
- Required mappings are accounted for.
- Correction addresses the shown validation issue.
- The film does not imply a committed import.