Long-form visual planning template

YouTube video shot list template

Map an approved long-form script into visual proof, source notes, and production handoffs before recording or editing.

This free template does not search footage, generate visuals, edit a video, clear rights, connect to YouTube, save entries, or predict performance.

Free working template

Make the long-form sequence reviewable before production

Turn an approved video script into section-by-section visual proof, source context, and a specific production handoff.

Section 1

Section 2

Section 3

Section 4

Section 5

Shot-list changes stay in this page and are not sent to Satura.

Visual planning

Plan what proves each part of the video

A long-form shot list gives the script's major sections a visual purpose, evidence, source context, and a concrete handoff. It keeps the writing, recording, and editing decisions connected without treating the plan as a result.

  1. 01

    Start with an approved script

    Bring the viewer promise, working package, source context, and long-form script into one production record.

  2. 02

    Divide the visual sequence

    Plan the opening, explanation, examples, turning points, and close in sections that a recorder or editor can inspect.

  3. 03

    Attach source and proof notes

    Keep the visual evidence, approved asset, original contribution, and open source question close to the section where it matters.

  4. 04

    Copy the production handoff

    Move the reviewed list into recording or editing, then use the separate edit plan and upload review for their own decisions.

Section purpose

Keep each sequence connected to the promise, explanation, example, turn, or close that the viewer needs next.

Visual proof

Name the recording, demonstration, screen capture, original contribution, or approved asset that makes the point reviewable.

Production handoff

Record the next capture, sourcing, editing, caption, audio, or sequence decision before the timeline fills up.

Review boundary

A shot list is a planning aid. It does not establish permission, accuracy, policy compliance, or a performance outcome.

Planning, not a prediction

A planned sequence still needs human review

Use the list to make source context, original contribution, visual proof, and the next production decision inspectable. It does not prove that a visual is accurate, permitted, policy-compliant, or ready to publish.

After recording or editing, compare the finished work with the approved script and current platform requirements. Use Studio information after publication to inform a later decision, not to turn the shot list into a performance formula.

The goal is an accountable production handoff, not a prediction of reach, views, retention, revenue, or monetization.

Questions

Using the shot list template

What is a YouTube video shot list?

A YouTube video shot list is a long-form pre-production record that connects each important section of an approved script with its visual proof, source context, and next production handoff. It helps a team prepare recording or editing decisions before the timeline fills up.

Is this different from a YouTube Shorts shot list?

Yes. The Shorts template is for a compact vertical sequence and selected clips. This template is for a long-form video's opening, explanation, examples, progression, and close. It does not replace the separate Shorts workflow.

Does the template generate footage or edit a video?

No. This browser-only template does not generate footage, search assets, edit a timeline, upload a video, or create a finished project. It records the choices a person should review before those separate workflows.

Does a shot list clear source rights or predict performance?

No. Source, rights, accuracy, platform, and publication checks remain separate responsibilities. A shot list does not establish permission or predict reach, views, retention, revenue, or monetization.

Does this template save my production notes?

No. The template runs in the browser. It does not connect to YouTube, save the entries, or send production-note text to Satura.