A short content script has three visible parts: the hook earns attention, the body delivers the promised value, and the call to action (CTA) offers one sensible next step. The formula works across short-form surfaces, but it does not guarantee reach or engagement.

By the end, you will be able to build and audit a complete short script. You will also create three scripts across at least two body structures, with source notes and an aloud timing check attached to each one.

// concept

Keep Promise, Proof, Qualification, and Action Aligned

The three-part formula needs a four-part reasoning spine: the hook makes a promise, the body supplies proof, the qualification sets the honest boundary, and the CTA asks for the logical next action. Place the qualification naturally inside the body or just before the CTA.

Script decision	Question to answer	Weak version	Aligned version
Promise	What useful thing will this piece deliver?	"This changes everything"	"Here are three checks for a readable product label"
Proof	What can the viewer see, verify, or apply?	Unexplained opinion	A screen demo, sourced fact, or numbered method
Qualification	What condition or limit changes the advice?	Hidden exception	"Test the final label on your smallest package"
Action	What is the single logical next step?	"Like, follow, share, buy"	"Save the three checks for your next label review"

Before drafting, list each factual claim, its approved source, and the check date. Product details can come from an owner-approved brief or the product itself; broader claims need a current primary source. If proof is absent, narrow the promise.

// concept

Match the Hook to the Content Goal

A hook is the first meaningful line or visual, not a loud adjective. Choose its type from the job the content must do.

Content goal	Useful hook type	Sample opening
Help someone notice a problem	Diagnostic question	"Can you find the price on your product card in one glance?"
Teach a method	Outcome preview	"In this video, you will turn one messy brief into a three-shot product script."
Prove how something works	Demonstration first	Show the before/after layout, then say what changed.
Build identification	Specific situation	"Your client approved the caption, but the product detail changed before posting."
Correct a misconception	Qualified correction	"A shorter hook is not automatically clearer; the promise still has to be specific."

Do not use suspense the body never resolves or promise a result when the body only offers a process. Writing the hook last often makes its promise more accurate.

// concept

Build the Body, Then Choose One CTA

Pick a body structure that fits the material:

List: promise → three distinct points → recap. Use parallel transitions: "First," "Next," and "Finally."
Story: situation → friction → decision → observable outcome → lesson. A changed draft or completed task is enough; do not invent dramatic success.
Tutorial: finished state → inputs → demonstrated steps → final check. Use action transitions: "Open," "Replace," "Compare," and "Check."

Match the CTA to the relationship. A new audience may save a checklist or follow a named series. An engaged audience can answer one specific question, not "comment YES." An intent audience that understands the offer may receive a product, booking, or download link with current terms and availability. These are editorial choices, not algorithm rules; check current platform guidance.

Read the script aloud with a stopwatch. Record the real time instead of trusting an AI estimate. If it runs long, remove repeated setup before cutting proof; if short, add demonstration rather than filler.

// concept

Draft With AI Without Losing the Evidence

Give the model the alignment decisions and source pack explicitly, then review its output for invented claims.

// prompt — copy me22 lines

Write one short-form video script.

Audience: [specific audience and platform]
Content goal: [problem recognition / tutorial / demonstration / story]
Target aloud duration: [seconds; I will verify with a stopwatch]
Hook type: [diagnostic / outcome preview / demonstration / situation / correction]
Body structure: [list / story / tutorial]
CTA stage: [new / engaged / intent]

Alignment:
- Promise: [exact value the hook may promise]
- Proof: [approved facts, demonstration, or steps the body must deliver]
- Qualification: [condition, exception, or uncertainty that must remain visible]
- Action: [one CTA that logically follows]

Use only facts inside <sources>. Do not invent results, scarcity, reviews,
performance, or product details. Mark any unsupported point [VERIFY].
Return: HOOK, BODY, QUALIFICATION, CTA, then SOURCE NOTES.

<sources>
[paste redacted, approved notes and links]
</sources>

// worked_example

Worked Example

This labelled sample uses a fictional Lahore stationery seller. Its approved brief says: an undated A5 planner has a weekly spread beside a notes page, comes in black or teal, and has a sample price of PKR 1,250. Stock and delivery are unknown; no productivity result is claimed.

Actual sample prompt used:

// prompt — copy me9 lines

Audience: Pakistani students seeing this seller for the first time on Instagram.
Goal: demonstrate the planner layout in a 30-second video.
Hook type: specific situation. Body: tutorial. CTA stage: new.
Promise: show how to turn scattered weekly tasks into one visible plan.
Proof: film the weekly spread and notes page; write three sample tasks on camera.
Qualification: this is a layout demonstration, not a productivity guarantee.
Action: save the layout idea for the next weekly planning session.
Facts allowed: undated A5; weekly spread plus notes page; black or teal;
sample price PKR 1,250. Stock and delivery are unknown.

Draft one output:

This planner will fix your routine in seven days. Everyone is buying it, so get yours before it sells out. Tap the link now!

That draft invents a seven-day outcome and scarcity, provides no demonstration, hides unknown availability, and asks for a purchase before proof.

Corrected, annotated sample script:

Part	Time target	Spoken line or visual
Hook / promise	0:00–0:04	"If your weekly tasks are split across three pages, try putting the plan and notes side by side."
Body / proof	0:04–0:20	Show the open planner. "On this sample page, classes go on the left, deadlines on the right, and questions for later in the notes area. The planner is undated, so you write the week yourself."
Qualification	0:20–0:25	"This layout will not manage the week for you; test whether seeing both pages together suits how you plan."
CTA / action	0:25–0:30	"Save this three-part layout and copy it into any notebook for your next weekly reset."

Source notes: owner-approved sample brief for format, colours, and sample price; planned close-up footage for the visible layout; unconfirmed stock and delivery omitted. Record the actual aloud duration before filming.

// failure_cases

Failure Cases to Diagnose

7 cases to diagnose

Hook overpromises body
"a complete system" leads to one tip. Narrow the hook or expand the proof.
Body changes subject
a label-readability question leads to a brand story. Return to the opening question.
Proof is adjectives
"powerful" and "premium" demonstrate nothing. Add a sourced fact, visible comparison, or reproducible step.
Qualification disappears
"availability varies" becomes "available now." Restore the condition and recheck it on publishing day.
CTA is too advanced
a first-time viewer receives a booking link without decision information. Lower the commitment or supply the missing proof.
Several CTAs compete
replace "follow, comment, share, and buy" with the one action matching the audience stage.
Timing is assumed
time a natural reading and trim repeated setup.

// pakistan_angle

Pakistan Angle

English-Roman-Urdu scripts can sound natural in Pakistani short video, but hooks still need clarity. "Aaj ka game-changing hack" is vague; "Aaj invoice bhejne se pehle yeh teen fields check karein" names the value. Choose aap, tum, or tu deliberately. Karachi, Lahore, Peshawar, Quetta, and smaller-city audiences are not interchangeable test groups.

For a WhatsApp seller taking JazzCash, easypaisa, or bank transfers, never script "payment ho gayi" from a screenshot alone; verify the merchant record. Redact phone numbers, addresses, order IDs, and CNIC details before using AI. During load-shedding, keep the approved brief offline, compress reference clips, and upload after saving the source check.

// hands_on

Hands-On Exercise

6 steps

Create three scripts for one evidence-safe topic, using at least two body structures.

Write one source note containing approved facts, links or first-party observations, check date, and unknowns.
Make a promise–proof–qualification–action card for each script.
Draft A with a list body, B with a tutorial body, and C with a story or a different goal.
Label the hook, body, qualification, and CTA in every draft. Keep exactly one CTA per script.
Time each script aloud and revise any section that crowds the proof.
Apply the failure cases and save corrected versions beside the originals.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

3 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

1 / 4 · diagnose
Your work shows this failure mode: “Body changes subject.” The lesson describes it like this: “A label-readability question leads to a brand story.” What does the lesson tell you to do about it?