VO Tone Guide for AI Explainers: Authority Without Stiffness
Specify coach, peer, or expert VO tone for AI explainers—with banned phrases and sample rewrites—so narration stays authoritative without stiffness.
VO Tone Guide for AI Explainers: Authority Without Stiffness
Specify narration tone so AI voiceovers and scripted hosts stay on-brand: pick a point on the coach / peer / expert spectrum, ban stiff phrases, and lock VO notes per beat beside scene notes.
Stiffness usually comes from corporate filler, not from intelligence. Authority comes from precise claims and calm pacing—not from jargon density.
The tone spectrum
| Tone | Sounds like | Best for | Risk |
|---|---|---|---|
| Coach | “Here’s the move—try this next.” | How-tos, enablement | Can feel soft if claims are vague |
| Peer | “Most teams trip here; do this instead.” | Mistake / contrast hooks | Can undersell expertise |
| Expert | “The mechanism is X; ignore Y.” | Architecture, compliance-adjacent | Can stiffen into lecture |
Pick one primary tone per series, not per sentence. Shift only when the Reel intent changes (e.g. Gotcha clips lean peer; architecture clips lean expert).
Authority without stiffness: rules
- Prefer concrete nouns over abstract virtues (“routing rule” > “powerful capability”)
- Prefer short sentences for claims; allow one longer sentence for mechanism
- Cut throat-clearing (“Today we’re excited to…”)
- Keep warmth in verbs and pacing, not in hype adjectives
- Put numbers only when true and necessary
Pair tone with modality: expert VO still needs sparse captions for mute (text vs VO when each wins).
Banned phrases (starter list)
Customize for your brand, then enforce in review:
- “We’re thrilled to announce”
- “In today’s fast-paced world”
- “Leverage / utilize” (prefer “use”)
- “Seamless / robust / powerful” without a proof beat
- “Simply / just” (often hides complexity and frustrates learners)
- “As you can see” when the viewer cannot yet see it
- “Game-changer / secret weapon”
Sample rewrites
| Stiff / hype | Authoritative rewrite |
|---|---|
| “We’re thrilled to leverage our robust SSO to empower teams.” | “SSO cuts password-reset tickets. Here’s the setup path.” |
| “Simply click around until it works.” | “Open Admin → Security → SSO, then paste the metadata URL.” |
| “In today’s fast-paced world, onboarding matters more than ever.” | “Onboarding stalls when checklists live in five docs—centralize them.” |
| “Our powerful AI seamlessly routes every ticket.” | “Intent labels route tickets before the queue fills. Here’s the rule.” |
| “As you can see, it’s intuitive.” | “Watch the lane labels change when intent flips to Billing.” |
Lock VO notes per beat
On each storyboard beat, add a VO note field:
- Tone tag: coach | peer | expert
- Line: spoken script (word ceiling by length)
- Stress: which word carries emphasis
- Do not say: beat-specific bans
Keep VO notes separate from scene notes and style lock (what belongs where). Approve lines muted-as-text so stakeholders catch stiffness before voice synthesis.
Word ceilings by length
| Length | Spoken words (guide) |
|---|---|
| 30s | ~70–90 |
| 45s | ~100–130 |
| 60s | ~130–160 |
If you overrun, cut adjectives before cutting the demo beat. Align with pacing templates.
Review checklist
- Series primary tone named
- Banned list attached to the board
- VO notes filled per beat
- Rewrites applied to hype lines
- Captions planned for accessibility without duplicating the full essay
AI voice settings that interact with tone
Tone is not only word choice. When using AI VO:
- Prefer slightly slower rates for expert tone; slightly brighter energy for coach
- Avoid exaggerated “radio ad” styles for B2B teach
- Keep one voice ID per series (matches character bible thinking)
- Re-bake after line edits; do not stretch old audio to new scripts
Document voice ID + rate + style tags next to the tone spectrum in your series bible.
Multilingual tone transfer
When localizing, translate tone intent—not idioms. “Just click” bans may need local equivalents. Rebuild VO notes per locale; do not assume a literal translation preserves peer vs expert stance.
Stakeholder review of VO
Play lines as text first, then audio. Many stiffness fights are wording fights. Catch them before synthesis so you do not pay for emotional reads of bad scripts.
Series tone sheet (one page)
Include:
- Primary tone + when peer/expert exceptions are allowed
- Banned phrases
- Preferred verbs
- Example good/bad paragraph
- Voice ID settings
- Escalation owner for tone disputes
Attach the sheet to every board template so freelancers do not improvise “premium narrator” energy.
Teaching vs selling tone
Teach Reels can mention the product honestly without sliding into pitch VO. If a line only exists to impress investors, cut it. Authority in education is usefulness under time pressure.
Side-by-side paragraph lab
Stiff: “Organizations today must utilize seamless workflows in order to empower stakeholders across the customer journey.”
Authoritative coach: “If handoffs drop context, route by intent before the queue grows—here’s the rule setup.”
Authoritative expert: “Intent labels are the control plane for assignment. Configure them before you enable auto-assign.”
Same product. Different spectrum points. Pick one per series and stick to it.
If two stakeholders disagree on tone, adjudicate with the series sheet—not with live rewrites in the recording booth or the synthesis queue.
Soft tool note
Whatever stack you use, lock VO notes per beat beside scene notes before render so tone stays consistent when teaching a process. Platforms such as Scro are built around that storyboard-first gate; the spectrum and rewrite table still work in a script doc next to your stills.