A video ad script and storyboard template for clearer production

A video ad script tells the producer what will be said. A storyboard explains what the viewer will see while hearing it. Putting both in one working document exposes gaps before they become editing problems: an unsupported promise, a missing demonstration, or a scene too short to communicate its point.

The template below is intended for short promotional videos, but its fields can expand for a longer explanation. Use it as a planning aid, not a mandatory story formula. Some offers need a demonstration first; others need a recognizable problem before the product makes sense.

Write a one-paragraph production brief

Place a compact brief above the scenes so every contributor understands the same objective. Include the intended viewer, relevant situation, specific offer, desired next action, and source of product facts. Name the person who can approve the script and resolve missing information.

For an illustrative reusable lunch-container brand, the brief might read: "Help commuters understand the removable divider in the current container. Show the actual product being packed. Invite viewers to inspect sizes on the product page. Use the supplied product specification for materials and dimensions. Do not claim that the container prevents every spill."

That paragraph provides enough direction to evaluate scene ideas. It also sets a boundary: a dramatic bag-spill demonstration would require evidence and may imply a performance claim beyond the approved brief.

Copy these fields for each scene

Repeat the following block for every beat. Keep the words spoken separate from text shown on screen so reviewers do not accidentally approve one while overlooking the other.

• Scene ID and approximate timing.
• Scene job: what the viewer should understand or believe.
• Exact narration or spoken dialogue.
• Visual action: subject, action, setting, and important detail.
• On-screen text, including any necessary qualification.
• Required asset and its source or production method.
• Evidence supporting the scene's explicit or implied claims.
• Transition, audio notes, and unresolved questions.

You can add framing, camera movement, or technical delivery details when the producer needs them. Avoid specifying elaborate movement before the scene has a useful job. "Camera circles a container" describes activity; "show how the divider lifts out" describes the information the customer needs.

Work through an illustrative opening sequence

For the lunch-container example, scene one could establish the packing situation. Narration: "Packing lunch around whatever fits in the box?" Visual: hands arranging a sandwich and fruit in the actual container, with the divider visible. Scene job: make the everyday constraint recognizable. Required asset: a simple tabletop capture with the current product.

Scene two could explain the feature. Narration: "This divider lifts out when you need a different layout." Visual: an uninterrupted close-up of the divider being removed, followed by the alternative arrangement. Scene job: demonstrate the mechanism. Evidence: the supplied physical product and approved feature description.

Scene three could move toward consideration. Narration: "See the available sizes and choose the layout that suits your lunch." Visual: the real size options with clearly labeled dimensions. Scene job: make the next step concrete. Required asset: current product information checked against the destination page.

This is an illustrative structure, not a tested ad or a claim about results. Its purpose is to show how a scene connects a line of copy to observable evidence and a production requirement.

Time the script with the intended delivery

Read the full narration aloud in the intended tone, leaving space for demonstrations and comprehension. A line can be spoken quickly while its visual requires several seconds. Let the information determine the scene's duration rather than forcing every scene into an equal slot.

Check where the viewer needs to read, listen, and inspect a detail simultaneously. If all three compete, simplify the on-screen copy or give the visual more room. Essential qualifications should be readable in the actual format, not merely present in the document.

Use approximate timing during planning. Lock exact timing during assembly, when you can assess the real voiceover and visuals together. If the runtime is too long, remove a redundant idea before accelerating every line.

Mark uncertainties before assets are created

Give unresolved items a visible status and owner. Examples include "dimensions awaiting product confirmation," "music permission pending," and "replacement close-up needed." A blank field is easy to overlook; a named dependency makes the next action clear.

Distinguish placeholders from approved copy. If a scene uses simulated interface footage or an illustrative situation, document how the final video will prevent viewers from mistaking it for actual product behavior or a real customer result. Keep the original approved narration available when experimenting with visual treatments.

Use the storyboard as a review document

Before production, review the sequence for a clear argument, supported claims, available assets, and a specific call to action. After assembly, compare the actual video with those requirements. A polished render can still omit the one shot that explains why the product matters.

In MediaWriter, an approved script can become the basis of a video plan. Bring the scene jobs and source requirements into that planning work, then review the resulting creative. Follow the broader video production workflow to keep script approval, asset checks, and final playback connected.