Product Demo Video Shot List: What to Record Before Editing

Before you start recording your screen or camera for a software product demo, you need a clear capture plan. A product demo shot list specifies every screen state, user interaction, spoken line, and backup take required to show a feature clearly. Planning these elements in advance helps you catch common recording errors: forgotten clicks, rushed transitions, erratic cursor movement, and missing confirmation messages that force you to re-record entire workflows during editing.

Quick answer: what belongs on a product demo shot list?

A complete product demo shot list covers four core elements for every step of your software walkthrough:

1. The clean starting state: The exact interface view before interaction begins (browser URL, empty or pre-populated fields, clean notification center, and readable zoom level).
2. The primary action: The deliberate cursor movement, click, menu selection, or keyboard input that triggers the software feature.
3. The visible result: The immediate software response that proves the feature worked (toast notification, refreshed dashboard table, updated status badge, or confirmation modal).
4. Narration and pickups: The spoken explanation aligned with the visual change, plus any safety holds or close-up pickup takes needed if the primary screen take lacks clarity.

Rather than improvising while you click, you record each step with a deliberate pause at the beginning and end. This structure provides clean cutting handles on the editing timeline and helps your demonstration remain easy for prospective users to follow.

Copyable product demo shot-list template

Download the editable CSV shot-list template. Open it in a spreadsheet and replace the illustrative TaskFlow rows with your own shots.

Use this table format to plan your screen recordings. It breaks your walkthrough into individual numbered shots that can be captured and verified systematically:

This table serves as an illustrative planning template. Modify the specific rows to match your product's user journey and interface complexity.

Illustrative sequence: creating a task in a project tool

To see how a shot list functions in practice, consider an illustrative walkthrough for a fictional project-management tool named TaskFlow. This sequence demonstrates creating a high-priority task without exposing real user data or unscripted interface hiccups:

Shot 1: The starting board baseline

• Framing: Browser window maximized at 1080p, interface scaling set to 125% for text readability.
• On-screen setup: The TaskFlow Kanban board contains five synthetic cards across 'To Do' and 'In Progress'. No personal bookmarks, browser extensions, or private account names are visible.
• Action: Cursor remains stationary near the project title for two seconds, then moves in a direct line toward the top-right action button.
• Spoken line: "When your team identifies an urgent deployment fix, you can create and assign a tracked task directly from the sprint board."
• Outcome: Establishes visual orientation so viewers understand where the upcoming action takes place.

Shot 2: Opening the creation modal

• Framing: Same 1080p canvas.
• Action: Single click on the violet + New Task button. The modal animates into view.
• Spoken line: "Click 'New Task' to open the creation dialog."
• Outcome: The form displays with empty fields and default focus set to the 'Task Title' input.
• Review check: Confirm that the cursor does not obscure the modal header or title field placeholder.

Shot 3: Entering synthetic task details

• Framing: Full window view.
• Action: Enter synthetic text: "Deploy staging SSL renewal". Use the dropdown menu to pick synthetic user "Alex Rivera", and toggle priority to "High".
• Spoken line: "Give the item a clear summary, assign your lead engineer, and mark the priority so it automatically flags on your board."
• Outcome: Form fields are visibly filled with high-contrast, legible text. No typing typos or backspacing hesitations.

Shot 4: Executing save and displaying the result

• Framing: Full screen.
• Action: Click Save Task. The modal dismisses, and a green success banner briefly displays at top-right while the card appears in the first board column.
• Spoken line: "Saving updates the board instantly, notifying your assignee without requiring a manual page refresh."
• Outcome: The new card is clearly visible at the top of the column with its 'High' priority badge illuminated.
• Review check: Hold on the completed board state for a full 3 seconds before ending the screen capture.

Shot 5: Optional detail pickup

• Framing: 140% localized crop around the newly created card.
• Action: Cursor hovers briefly over the 'Due Date' badge to show tooltip.
• Spoken line: None (reserved for timeline cutaway or caption emphasis).
• Outcome: High-resolution fallback footage for mobile aspect ratios where full-screen text might appear too small.

What to capture twice during recording

When recording software, certain interface moments carry a high risk of visual ambiguity or awkward cutting boundaries. Capturing these elements twice gives you alternatives when a take is unclear:

1. The clean interface state

Record 3 to 5 seconds of the interface completely still before touching the keyboard or mouse. If you need a clean background plate, a thumbnail still, or a freeze-frame to extend an introductory voiceover sentence, this static hold gives you clean footage without cursor movement.

2. The post-action confirmation hold

Many creators stop recording immediately after clicking a submit button. Start with a few seconds of still footage after the result renders, then adjust the hold to the complexity of the screen. Human viewers need visual processing time to absorb that the card was created, the report was downloaded, or the chart updated. Stopping the take too early forces an abrupt cut.

3. Isolated detail pickups

If your demonstration involves tiny interface controls, dropdown options, or complex code blocks, record a second pass zoomed in to 125% or 150%. Having a dedicated close-up take allows your video editor to cut between wide context and focused detail with enough source detail for the intended output.

Screen recording technical checklist

Before initiating your screen capture software, run through this five-point preparation checklist:

• Browser scaling & resolution: Set your display output to a standard 16:9 ratio (1920x1080 or 3840x2160). Zoom your browser interface to 110%–125% so button labels and menu text remain legible on mobile screens.
• Clean user environment: Disable desktop notifications, browser extension popups, personal bookmarks, and system menu bars that distract from the product.
• Realistic synthetic data: Populate your test workspace with believable, professional sample data. Avoid placeholder text like "test 123", Lorem Ipsum, or sensitive internal company information.
• Cursor smoothing & motion discipline: Move your cursor in direct, steady paths. Click once deliberately and avoid circling controls or fidgeting with the mouse while delivering narration.
• Audio isolation: If recording live voiceover, ensure your microphone input is separate from system audio. Alternatively, record narration as a separate pass after capturing clean screen takes.

Moving from your shot list into editing

A completed shot list is an operational guide for capture; the finished video is constructed during editing. Once you have logged your raw takes:

1. Review takes against the shot list: Verify that every required action, result state, and safety hold was captured cleanly.
2. Select primary takes: Import your screen recordings and select the cleanest attempt for each numbered shot row.
3. Trim unnecessary waiting: Cut out the silence between actions while preserving the visual confirmation holds. For dedicated pacing guidance, consult our guide to editing product demo videos.
4. Evaluate visual progression: If you are unsure whether your sequence needs visual storyboards or a production checklist, read our comparison of storyboard vs shot list.
5. Review on-screen clarity: Preview your draft on a mobile display to confirm that all text inputs, button clicks, and confirmation toasts are immediately legible.

For comprehensive buyer-facing walkthroughs and feature showcases, explore our overview of product demo video creation.

Review the finished recording

Play your downloaded edit with sound. Check that each click has a visible outcome, narration describes the displayed state, captions are accurate and readable, and no private workspace data appears.

Edit my recorded product demo.