<!-- last-reviewed: 2026-06-01 · owner: Growth (Video Producer / Script Writer) -->
SOP-093 — Script from brief (episode package)
SOP · owner: Growth (Video Producer / Script Writer). Layer: SOP/Runbook (
docs/canon.md). The canonical 8-step episode format and the chunk list live indocs/concept.md; the chunk-tag rulings live in SOP-094; the unit boundary lives indocs/units/growth/charter.md— not restated here. This is one of the Video Producer’s two required SOPs (artifact-matrix §3 ✓): the recurring procedure that turns an approved content brief into a complete, production-ready episode package.
Interface Contract
- Inputs: content brief ← from Content Strategist · trigger:
content brief issued - Inputs: brand-reviewed package ← from <Creative Director> · trigger:
review passed - Outputs: script package (script + editing notes + newsletter) → to Creative Director · trigger:
review requested - Outputs: finished package → to Principal (execution) · trigger:
review passed - Outputs: script + editing notes + newsletter → to Archivist · trigger:
artifact approved - Handoff trigger (in): the Content Strategist issues an approved content brief
- Handoff trigger (out): a four-part package (script · editing notes · chunk manifest · newsletter) is assembled and handed to the Creative Director for brand-coherence review, then to the Principal for execution
- Definition of Done before handoff:
- [ ] Script follows the fixed 8-step format (Cold Open → Map → Goal+Scoreboard → Lap 1 → Radio → Setup Change → Lap 2 → Takeaways+Artifact); no step skipped or reordered
- [ ] Every spoken line is scripted (not bullet notes);
[ON-SCREEN: …]callouts and[BEAT]/[DIRECT TO CAMERA]delivery notes placed; per-section durations given - [ ] Every claim/result traceable to the source material named in the brief (show-the-work; no invented beats)
- [ ] Editing notes produced: cut rhythm · montage guidance · face-cam vs. screen-capture per section · Shorts in/out timestamps
- [ ] Chunk manifest produced per SOP-094 (tagging is a separate, mandatory procedure)
- [ ] Newsletter copy assembled from MAP + SCOREBOARD chunks + the CTA artifact (assembled, not rewritten)
- [ ] Package cleared Creative Director brand-coherence review (hard gate) — the package is held, not finalized, until the review verdict returns
- [ ] Learnings captured to
docs/knowledge/growth/if the work surfaced one - [ ] Script/editing-notes/newsletter handed to the Archivist (0 drift)
Triggers — registration status.
artifact approved,review requested, andreview passedare registered (seed block);content brief issued(Content Strategist → Video Producer) is registered (docs/handoff-triggers.md, Waves 3+4 block). The brand-coherence seam reuses the registeredreview requested/review passedhandshake (the IC block above). The Creative Director is authored (SOP-098), so the brand-review edges reconcile point-to-point; the→ Principaledge isexempt (Principal)perinterface-contract-spec.md§3.1.1 R2.
Purpose
Turn an approved content brief into a complete, production-ready episode package — a fully structured 8-step script, editing notes, a chunk-tagged manifest (SOP-094), and newsletter copy — so the Principal (or an editor/producer) can execute the episode without guessing, and every beat is grounded in the real work named in the brief.
When to use
Whenever the Content Strategist issues an approved content brief (content brief issued). Also when the Creative Director returns a brand-review verdict on a previously
handed package (incorporate feedback before finalizing).
Flow
flowchart LR
A["Brief issued"] --> B["Read source +<br/>8-step format"]
B --> C["Draft the<br/>8-step script"]
C --> D["Produce<br/>editing notes"]
D --> E["Apply chunk taxonomy<br/>(SOP-094)"]
E --> F["Assemble<br/>newsletter copy"]
F --> G["→ Creative<br/>(brand review requested)"]
G --> H["→ Principal<br/>(execution)"]
F --> AR["→ Archivist"]
classDef s fill:#1d4ed8,color:#fff,stroke:#1e3a8a
class A,B,C,D,E,F,G,H,AR s
Text fallback: a brief is issued → read the source material and the 8-step format → draft the full script (lines · callouts · delivery notes · durations) → produce editing notes (cuts · montage · face-cam/screen direction · Shorts timestamps) → apply the chunk taxonomy and manifest (SOP-094) → assemble newsletter copy from MAP + SCOREBOARD + the CTA artifact → hand the package to the Creative Director for brand-coherence review → on pass, hand to the Principal for execution and all docs to the Archivist.
Steps
- Orient — read the content brief (premise · source paths · format · key beats ·
title · CTA),
docs/concept.md(the fixed 8-step format),docs/content/formats.md(the named format’s length/requirements), the brand voice guide if present, and the exact source material. If the brief is incomplete or source is missing, surface to the Content Strategist and stop — do not invent beats. - Draft the script — the full 8-step structure; for each section write all spoken
lines,
[ON-SCREEN: "text"]callouts,[BEAT]/[SLOWER]/[DIRECT TO CAMERA]delivery notes, and a target duration. The Cold Open earns attention in <60s and does not restate the title; every section does real work or is cut. Write todocs/content/scripts/<slug>.md. - Produce editing notes — cut structure/pacing per section, montage/B-roll guidance,
face-cam vs. screen-capture per section, and Shorts in/out timestamps keyed to the
chunk tags (HOOK · RADIO · DELTA · PIT). Write to
docs/content/editing-notes/<slug>.md. - Apply the chunk taxonomy — run SOP-094 to tag every section and produce the
manifest at
docs/content/chunks/<slug>.md. Tagging is mandatory and separate; do not shortcut it inside the script. - Assemble the newsletter — extract the MAP and SCOREBOARD chunks + the CTA artifact;
assemble (not rewrite) into subject · lead · scoreboard · artifact · CTA. Write to
docs/content/newsletters/<slug>.md. - Submit for brand-coherence review — hand the package (script + editing notes +
newsletter) to the Creative Director (
review requested); flag any sections where voice/tone conformance was uncertain. Do not finalize without sign-off. Hold the package until the brand-review verdict (review passed) returns. - Hand off — on brand-review pass, hand the finished package to the Principal for
execution and all docs to the Archivist (
artifact approved); hand the chunk manifest to Data & Analytics per SOP-094. - Capture the learning — record any durable scripting/structure pattern to
docs/knowledge/growth/.
Roles / approvers
Run by the Video Producer. The Content Strategist authors the brief (the authoritative input). The Creative Director holds the brand-coherence gate (required before finalize). The Principal executes (records) the package. The Archivist preserves every artifact. Data & Analytics receives the chunk manifest (SOP-094).
Guardrails
- Format discipline — the 8-step format is fixed; do not skip, reorder, or invent sections. If a brief’s beats cannot fit, escalate to the Growth Director.
- Script grounding — every claim/result traces to the source material in the brief; no invented beats, results, or narrative.
- Brand gate is hard — a package to the Principal without Creative Director review has skipped a required step; never fabricate the review verdict.
- Stay in lane — do not own content strategy/format library/calendar (Content Strategist), define brand voice (Creative), score chunks (Data & Analytics — SOP-094), or publish/upload (Principal).
- Surface conflicts in writing — brief vs. format conflicts, unresolved brand issues → Growth Director (GR-3); do not silently bend the format or the brief.
- Never touch the Principal’s personal information — PA-only.
- Do not restate the 8-step format or the chunk taxonomy — link to
docs/concept.md; the chunk-tag rulings live in SOP-094.
Job aid: JA-094-chunk-tagging-cheat-sheet.md
(covers the tagging step). See also: SOP-094 (chunk-tagging) · SOP-092
(content-calendar) · docs/units/growth/charter.md · docs/concept.md ·
docs/handoff-triggers.md.