The Hook-Body-CTA Script Formula

Fictional approved facts: undated A5 planner; weekly spread beside a notes page; black or teal; sample price PKR 1,250. Stock and delivery are unknown. Your own demonstration may show these three sample tasks:

The goal is to demonstrate a layout to a first-time viewer. No productivity, grade or sales result has been measured.

The hook creates an expectation that the body must satisfy. "Weekly tasks scattered?" promises a way to arrange tasks. A body that only lists planner colours would break that promise, even though every colour is accurate. Check the connection by completing this sentence: "After watching, the viewer can ___." For this brief, the answer is "put dated tasks and open questions in different places."

That answer determines your sequence. First show the empty spread so viewers understand the two spaces. Next place one task under its day. Then show that an unresolved question belongs on the notes page. The second and third tasks confirm the pattern; they do not require a fresh explanation of the entire system.

Notice the difference between a feature and a mechanism. "Undated weekly spread" names a feature. "You write the dates yourself, then place each task under its day" explains how someone uses it. The explanation gives the viewer a repeatable action without claiming that owning the planner produces better grades.

Try this focused prompt:

An illustrative draft might open with "Sort your week in seconds", show three fast page turns, then say "Everything organised". Its weakness is not simply tone. "In seconds" creates a speed promise that has not been timed; the page turns hide the placement decisions; "everything" exceeds the three-task example.

Repair the middle first: show "Monday: read chapter 2" being written beneath Monday. Explain, "A task with a day goes here." Move to the notes page and write "Which references are still missing?" Explain, "A question without a settled answer stays beside the plan." Now a hook such as "Where do tasks and unanswered questions go?" accurately prepares the viewer for what follows.

Use the CTA to extend that exact action: "Try separating one task and one question in your notebook." This is easier to attempt than "Transform your entire routine". It also gives you a concrete way to review the script: does the body contain enough information to complete that action?

Imagine a fictional rehearsal: the spoken read takes 23 seconds, but writing and pointing take another 12 seconds when performed without overlap. The full demonstration would take 35 seconds. Adding those times is appropriate only where the actions actually happen after speech; actions performed during speech must not be counted twice.

Mark the script with "speak while writing" or "pause for viewer to inspect". If it runs long, remove a repeated explanation before speeding up the hand movement. A viewer needs time to identify the day and see where the words land. Record the measured rehearsal of the actual sequence; a word-count estimate cannot reveal an unreadable shot.

Now the viewer already uses this planner and only wants to know where to put an unresolved question. Predict which parts of the original script you would remove, and which visible action you must keep. Write your answer before continuing.

You can omit the introduction to the weekly spread and the three repeated task placements. Start with a task and its related question already visible, then demonstrate the distinction. "Friday: submit assignment" belongs under Friday; "Which references are missing?" belongs on the notes page until resolved. Keep the connection between the two pages because that is the new viewer's remaining problem.

The revised version can be shorter without becoming less useful. If you instead retain the full product introduction and cut the question example, the script spends time on what this viewer knows and removes what they came to learn. Audience knowledge changes the necessary explanation, even when the product facts remain identical.