Prepare assets for a product launch video

Start with the action the film needs to explain. For an illustrative calendar product, the sequence selects an open slot and shows a confirmed booking. It needs a readable starting calendar, the selection state and the confirmation. An attractive settings screen does not replace a missing confirmation.

For each source record the scene, filename, version, owner and permitted use. Record whether it represents shipped behavior, a prototype or an illustrative mockup. These labels help the producer avoid presenting a design concept as a released interface.

• Scene A: calendar before selection; use the approved fictional date and account.
• Scene B: the same calendar with one slot selected; preserve surrounding entries.
• Scene C: confirmation for that exact slot; retain date, time and relevant status.
• Brand: approved logo variant and supplied type guidance.
• Copy: exact product spelling, scene labels and the verified closing action.

Compare the screens side by side before motion production. Check viewport size, theme, account name, date, selected item and visible navigation. A switch from one date to another may look like a product action even if it was just a capture mistake.

Create a short note identifying the important region in each screen. For a dense calendar, the source can remain full size while the scene note recommends a crop around the selected slot. Preserve enough neighboring context to make that crop understandable.

Use fictional or approved example data deliberately. Replacing one person's name while leaving their messages or identifiers visible is not a complete content review. Inspect the whole screen, including notifications and background panels.

If the final interface state is unavailable, list it as a production dependency. A labeled placeholder can support planning, but it is not evidence. Name who will provide the replacement and what it must show.

Keep original source files separate from annotated planning copies. An annotation that says “highlight here” should not accidentally become product UI in the final film. Give the producer one approved folder and a short change log rather than several competing files named final.

Before handoff, walk through the outline using only the prepared packet. Every required claim should have its source, every scene should have its necessary asset and every open issue should have an owner. This review verifies readiness of the packet; it does not assert that an unrendered video has passed QA.