BRIEFING SCRIPT — SKILL FILE
For Writing Voiceover Narratives That Accompany the Briefing Interactive
WHAT THIS SKILL PRODUCES
A word-for-word recording script that the practice owner reads on a second screen while screen-recording the briefing interactive HTML. The script includes stage directions for scrolling and hovering, timing cues per section, and production notes.
This is NOT:
- The briefing interactive itself (the HTML page — see
briefing-interactive-SKILL.md) - The briefing landing page (the timer-based video wrapper — see
briefing-landing-page-SKILL.md) - A LinkedIn post or email (different formats, different writing)
- An article script (articles are read, not narrated)
This IS:
- A voiceover script synced to a scrolling interactive HTML page
- A behind-the-scenes client walkthrough told in the presenter's speaking voice
- Stage directions that map to hover and scroll interactions in the HTML
Golden examples:
- The Subtract/Add Briefing Script (
subtract-add-briefing-script.md) — slide-based format - The Silent List Briefing Script (from
no-show-revival-remaining-assets.md) — interactive HTML format
THE RELATIONSHIP BETWEEN SCRIPT AND INTERACTIVE
The briefing interactive is the visual layer. The script is the audio layer. Together they form the recorded briefing.
What the interactive shows: Practice profile, discovery items, findings with hover-expand detail, before/after comparisons, results cascade, gap layers, offer cards.
What the script adds: Story context, emotional texture, diagnostic reasoning, commentary on what the viewer is seeing, the "why" behind each finding, and the conversion argument.
The script should never just narrate what's visible on screen ("As you can see, there are six categories..."). It should add what ISN'T on screen — what the client said, what surprised them, why you looked where you looked, what the viewer should be thinking about their own practice.
Division of Labor
| On Screen (Interactive) | In Voice (Script) |
|---|---|
| Practice profile cards | Who she is, what she told you, what she thought the problem was |
| Category count rows appearing | Why each category matters, how you discovered it together |
| The 53 reveal | Her reaction, the silence in the room, what that number means |
| Wound barrier hover details | Why each barrier is invisible to the practice owner, your read vs. hers |
| Before/after message zones | Why generic fails for each wound type, what you changed and why |
| Results cascade building | Commentary between each number, pacing the revelation |
| $62K hero number | What she'd been spending on ads, the comparison that makes the point |
| Gap layers | What she could do alone, what required you, what's still unbuilt |
| Offer cards | What each path gives them, which to choose based on where they are |
STAGE DIRECTIONS
The script uses specific cues that map to how the presenter interacts with the HTML. Since the briefing interactive uses scroll reveals and hover expansions (no buttons, no clicks), the stage directions must match.
Stage Direction Vocabulary
[SCROLL] — Scroll down to trigger the next reveal or reach the next section
[HOVER on X] — Mouse over an element to expand its detail panel
[HOVER off] — Move mouse away to collapse the detail panel
[PAUSE] — Stop scrolling. Hold on the current visual for a beat (2–3 seconds)
[PAUSE — X sec] — Hold for a specific duration (used for hero numbers, big quotes)
What NOT to use
[CLICK] — No click interactions in the briefing interactive
[REVEAL] — Reveals happen via scroll, not explicit triggers
[TOGGLE] — No toggle elements — side-by-side zones use hover
[CAMERA] — No camera in this format (screen recording only)
[SLIDES] — No slides — this is a scrolling HTML page
How Stage Directions Appear in the Script
Stage directions go on their own line, formatted as code blocks, before the narration they accompany:
`[SCROLL to section header: "Five Different Silences."]`
Here's the part that changes everything. Those 53 people aren't one problem.
When hovering over multiple items in sequence:
`[HOVER on "Her 8 no-shows" — detail expands]`
She assumed they weren't interested. When we dug in, most had canceled same-day...
`[HOVER on "Her 4 quiet proposals" — detail expands]`
All four had engaged deeply through the proposal process...
NARRATIVE ARC
The script follows the same 7-beat arc as the briefing interactive, but the script adds the connective tissue — the transitions, the commentary, the "sit with this" moments.
Beat 1: The Practice (0:00–2:00)
On screen: Profile cards stagger in. Problem card appears in red. In voice: Who she is. What she came to you saying. What she thought the problem was. The quote that reveals her mindset.
Script pattern:
- Open with the presenting problem (what she told you)
- Describe the practice in human terms (not just reading the cards)
- End with the question you asked that started the real work
Tone: Conversational. You're telling a story, not opening a show. Mid-thought, not "Welcome to this briefing."
Beat 2: The Discovery (2:00–5:00)
On screen: Count rows stagger in with numbers. Each category appears with a beat. In voice: What each category is and why it matters. How you found them together. The growing realization.
Script pattern:
- Describe the counting exercise ("I asked her to pull up her calendar...")
- Narrate each category as it appears — not just the label, but what it means
- Let the numbers accumulate — the script should create the sense of "wait, there's more"
- Land on the total with a pause
Key moment: The guess-vs-reality reveal. The script needs to hold the beat here. "She said five. Maybe ten. We found fifty-three." Then silence. Let the visual do the work.
Beat 3: The Findings (5:00–8:00)
On screen: Hover-expand items showing what you found in each group. In voice: Your read vs. her read. What surprised you. What she couldn't see from inside.
Script pattern:
- Hover over each finding, narrate what you discovered
- Include her reaction or her assumption for contrast
- Show the diagnostic reasoning: "My read was sticker shock with no smaller entry point. Her read was rejection."
- Don't hover over every single item — pick the 3–4 most compelling and narrate those
Key principle: The hover detail on screen is the WHAT. The narration is the WHY and the SO WHAT. Don't read the hover text aloud — add what isn't written.
Beat 4: The Rewrite (8:00–11:00)
On screen: Side-by-side before/after zones. Hover reveals the "after" content. In voice: Why the standard message fails for this specific wound type. What you changed and why. What makes the matched version work.
Script pattern:
- Read or paraphrase the "before" message (it's visible on screen)
- Hover to reveal the "after" — then narrate what's different and why
- For each pair, one sentence on what's wrong with the standard, one sentence on what the matched version does instead
- Don't explain all three pairs with equal depth — go deep on one, medium on one, brief on one
Beat 5: The Results (11:00–13:00)
On screen: Result lines stagger in. Hero number appears. Comparison block. In voice: Commentary between each number. The pacing creates anticipation.
Script pattern:
- Let each number land before narrating the next
- Add context the viewer can't see: "Nineteen out of 41. That's a 46% response rate on contacts she'd written off."
- The hero number ($62K) gets a pause and a reframe: what she'd been spending on ads, where the revenue actually was
- The comparison block (ad spend vs. recovered) should speak for itself — minimal narration
Key principle: Less narration here, not more. The numbers tell the story. The script holds the beats.
Beat 6: The Gap (13:00–15:00)
On screen: Layer stack with hover-expand. Three layers building. In voice: The conversion hinge. What she could do once vs. what she can't sustain. The difference between a project and a capability.
Script pattern:
- Hover over each layer and narrate what it means
- Frame as "she did / we did / still open" — shows the progression from DIY to system
- Land on: "the count tells you revenue is leaking. The diagnostic tells you where the break is."
Tone shift: This is the conversion hinge. Slower, more deliberate. Not a pitch — a reframe. The viewer should feel the gap between knowing the framework and having the system.
Beat 7: The Offer (15:00–17:00)
On screen: Two offer cards. Hover reveals details. In voice: What each path gives them. Which to choose based on where they are.
Script pattern:
- Hover over the free tool card: "If you want to find your number, this does that in two minutes."
- Hover over the diagnostic card: "If you already know the number is big and want to figure out what to build..."
- Close with a line that reframes the whole briefing: "You start with what's already there. Not new leads."
Tone: No pressure. Two options. Either one starts the process. The diagnostic is for people who are ready to build, not people who need convincing.
TIMING
Target runtime: 15–20 minutes. Each section has a time range. These are guides, not hard constraints.
| Beat | Section | Time | Duration |
|---|---|---|---|
| 1 | The Practice | 0:00–2:00 | ~2 min |
| 2 | The Discovery | 2:00–5:00 | ~3 min |
| 3 | The Findings | 5:00–8:00 | ~3 min |
| 4 | The Rewrite | 8:00–11:00 | ~3 min |
| 5 | The Results | 11:00–13:00 | ~2 min |
| 6 | The Gap | 13:00–15:00 | ~2 min |
| 7 | The Offer | 15:00–17:00 | ~2 min |
The longest sections are the Findings and the Rewrite (beats 3–4) — this is the core of the briefing where the real work is shown. The Results and Offer should be tighter.
VOICE AND TONE
What It Should Sound Like
- Someone telling a colleague about an interesting client engagement over coffee
- Direct, specific, unhurried
- Mid-thought on the first line — not "Welcome to this briefing" or "Thanks for watching"
- First person singular ("I asked her..." "My read was..." "What I saw was...")
What It Should NOT Sound Like
- A webinar host ("Today we're going to cover three key insights...")
- A slide deck presentation ("As you can see on this slide...")
- An article read aloud (too polished, too structured)
- A sales pitch ("And that's why you need to book the diagnostic RIGHT NOW")
Specific Patterns
Opening line: Start mid-story. Not with a greeting, not with an agenda. "I've been asking practice owners the same question for the last few weeks." or "There's a pattern I keep running into in advisory practices."
Transitions between sections: Don't announce them. "Now let me show you what this actually looks like" is fine. "Moving on to section three" is not.
Client quotes: Paraphrase in your own voice unless the exact words matter. "She said — and this is almost exactly what she told me — 'I don't even know where to spend the next dollar.'" Use sparingly.
Hover narration: When hovering over expandable items, don't read the detail text verbatim. Add what's NOT written — the context, the reasoning, the pattern you've seen in other practices.
Closing: No big wrap-up. No "thanks for watching." End with the offer framed as two paths, a reframe line that echoes the briefing's core insight, then a pause and stop recording.
PRODUCTION NOTES SECTION
Every script ends with a Production Notes section that documents:
- Format: Screen-recorded walkthrough of interactive HTML + voiceover
- Recording workflow: Open HTML in Chrome full-screen, screen record + audio, scroll and hover through as you narrate
- Interactive elements table: Each element, which section it's in, what it does, and why it works on video
- What's different from the article: Explicit list of how the briefing differs from the article — different case details, different emphasis, no content overlap
- What stays in voice only: Story context, emotional texture, diagnostic reasoning — things that aren't on screen
- What appears on screen: Visual elements the viewer sees
- Design notes: Theme, type size, interactive behavior
This section is for the presenter's reference during recording prep.
WRITING SEQUENCE
- Read the briefing interactive HTML. Scroll through the actual page. Note every section, every hover-expand item, every visual element. The script must map to exactly what's on screen.
- Map the story. Before writing any script, outline the client story: who they are, what they thought the problem was, what you found, what you changed, what happened, where they got stuck. This is the narrative backbone.
- Write beat by beat. Start with Beat 1. Write the narration. Add stage directions. Move to Beat 2. The stage directions should reference actual elements in the HTML — section headers, item labels, visual transitions.
- Check the voice/visual split. For each section: is the narration adding something the screen doesn't show? If you deleted the narration and just watched the screen, would you miss the story? If the narration just describes what's visible, rewrite it.
- Read it aloud. Time each section. The script should feel conversational at speaking pace — not rushed, not dragged. Cut anything that feels like filler.
- Write the Production Notes. Document everything the presenter needs to know for recording day.
COMMON FAILURE MODES
Narrating the screen
"As you can see, there are six categories of silent contacts." — The viewer CAN see. Tell them what they CAN'T see: "I asked her to pull up her calendar. We counted category by category."
Teaching the framework
The article teaches. The briefing shows. If a sentence could appear in the article, it probably doesn't belong in the script. "There are five wound types" is article language. "Her 8 no-shows were embarrassed — three of them had even looked at her website again in the last 60 days" is briefing language.
Equal depth on every item
Not every hover-expand item needs full narration. Pick 3–4 per section and go deep. Skim the rest. The viewer gets the pattern from the first few — they don't need equal time on every one.
Missing the conversion hinge
Beat 6 (The Gap) is where the viewer realizes they can't do this alone. If this section is too brief or too abstract, the offer in Beat 7 feels disconnected. Take your time here. This is where "I could probably do this myself" becomes "I need someone who's done this across dozens of practices."
Generic offer close
"Book the diagnostic" is not a close. "If you watched this and your number is already bigger than you thought — that's exactly why this matters" is a close. The offer should feel like a natural next step from the story, not a pitch bolted onto the end.
Stage directions that don't match the interactive
If the script says [CLICK] but the interactive uses hover, the presenter will be confused during recording. Verify every stage direction against the actual HTML. Scroll = IntersectionObserver reveals. Hover = CSS :hover expansions. No clicks.
WHAT THIS SKILL DOES NOT COVER
- The briefing interactive HTML: The visual layer. See
briefing-interactive-SKILL.md. - The briefing landing page: The timer-based delivery wrapper. See
briefing-landing-page-SKILL.md. - Video recording/editing: How to actually record the screen, which software to use, video editing.
- The article: The thought leadership piece. Different format, different writing approach.
- Distribution emails/posts: Campaign launch assets that promote the briefing.
Skill file extracted from: The Subtract/Add Briefing Script + The Silent List Briefing Script Created: February 2026