Write a YouTube Shorts script about [TOPIC] for [TARGET VIEWER]. The goal is [GOAL], and the viewer should leave knowing or doing [TAKEAWAY]. My creator voice is [VOICE AND EXAMPLES]. The factual material I can support is [APPROVED FACTS OR SOURCES]. Make one script designed for [TARGET LENGTH] seconds in a 9:16 vertical video. Start with a spoken hook in the first 1.5 seconds that creates a specific information gap or stakes; do not begin with a greeting, channel introduction, or vague promise. Use one central idea only. Build the script as a sequence of short beats that can be understood with sound off and without prior context. Return: 1. A one-line title or on-screen opening text, under 55 characters. 2. A beat-by-beat table with timecode, spoken words, on-screen text, visual or B-roll direction, and edit note. 3. A caption of 90 to 150 characters and three relevant hashtags, avoiding spammy tags. 4. Two alternate hooks that preserve the same factual claim. Keep spoken language conversational, concrete, and easy to say in one take. Put the key payoff before the midpoint, then add proof, an example, or a useful qualification. Make on-screen text shorter than the spoken line rather than duplicating it word for word. End with a single low-friction call to action matched to [GOAL], not a generic request to like and subscribe. Do not invent results, quotes, demonstrations, or credentials. Do not give legal, medical, financial, or safety instructions beyond what [APPROVED FACTS OR SOURCES] supports. If a required input is missing, ask up to 3 clarifying questions. Before answering, check that the script fits the target duration at roughly 2.2 to 2.7 spoken words per second and that every factual assertion is supported by my materials.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TOPIC] | Enter the single idea, lesson, product feature, or story the Short covers. | A two-step inbox rule that stops small requests from taking over the day |
| [TARGET VIEWER] | Enter the specific audience and its relevant level of knowledge. | Busy team leads who manage email and Slack all day |
| [GOAL] | Enter the desired action, such as save the video, visit a product page, or try a technique. | Save the video and try the rule tomorrow |
| [TAKEAWAY] | Enter what the viewer should understand or be able to do after watching. | Sort messages into reply-now, schedule, or decline instead of reopening them repeatedly |
| [VOICE AND EXAMPLES] | Describe the creator’s tone and include a short example line or two if available. | Practical and calm; “If it takes two minutes, decide it now, not later.” |
| [APPROVED FACTS OR SOURCES] | Enter the facts, links, product details, or source notes that can be used. | My own workflow: I batch non-urgent replies at 11:30 a.m. and 4:30 p.m.; no performance claims. |
| [TARGET LENGTH] | Enter the intended running time in seconds. | 35 |
How to use
- Paste in one topic, one audience, and facts you can actually show or support.
- Read the spoken column aloud with a timer before filming; shorten any line that makes the payoff arrive late.
- Prepare the visual directions as a shot list, especially screenshots and B-roll that prove the point.
- Follow up with: “Give me three new endings that invite saves without repeating the hook.”
Variations
Product demo
Use this for a feature demonstration that needs clear visual proof.
Write a [LENGTH]-second YouTube Short demonstrating [PRODUCT FEATURE] for [TARGET USER]. Use these verified details: [PRODUCT FACTS]. Return a timecoded table with spoken line, screen-recording action, on-screen text, and edit cue. Open by naming the frustrating task the feature removes, show the before-and-after workflow, and state one accurate limitation or requirement. Keep each screen step visible long enough to follow. End with one call to action: [CTA]. Do not claim integrations, results, or availability not listed in the facts.
Myth correction
Use this to correct a common misconception without making the viewer feel scolded.
Create a [LENGTH]-second YouTube Short correcting this misconception: [MYTH]. The accurate explanation is [SUPPORTED EXPLANATION], supported by [SOURCES OR NOTES]. Write a cold open that states the myth, a quick correction, one concrete example, and a closing takeaway. Return timecodes, spoken words, on-screen text, and visual ideas. Keep the tone [TONE]. Avoid straw-man versions of the myth and do not overstate the evidence. Flag any sentence that needs a stronger source before publication.
Founder story
Use this when a short personal story can make a business lesson memorable.
Turn this founder moment into a [LENGTH]-second YouTube Short: [STORY NOTES]. The lesson is [LESSON] for [AUDIENCE]. Write a script with a tension-filled opening, only the essential context, the turning point, and a practical lesson the viewer can apply. Return a beat sheet with spoken words, on-screen captions, and simple B-roll or cutaway suggestions. Preserve uncertainty where the notes are uncertain and do not invent dialogue, revenue figures, or outcomes. End with a CTA asking viewers to [CTA].
Tips
- Write the first frame as a complete thought because viewers often decide before audio starts.
- Use a visual change every few seconds, but keep the same idea moving forward instead of adding unrelated proof points.
- If you show a number or comparison, put its source in the description or make the qualification visible on screen.
- Record two hooks before recording the full script; a better opening usually matters more than adding another edit.
FAQ
How long should a YouTube Short script be?
A 30-second Short often needs roughly 65 to 80 spoken words, depending on pace and pauses. Time the final read rather than trusting word count alone.
Should I use a hook that withholds the answer?
Use a specific promise, then deliver the useful point early. A hook that delays the payoff too long often loses viewers.
Can I use AI-generated facts in a Short?
Use AI to organize and phrase facts, but verify claims, numbers, quotes, and product details against your own sources before posting.