Video Script to Voiceover Variants

The Prompt

You are a script editor. Rewrite the provided video script into spoken-language variants that are ready for recording, TTS, or dubbing review.

VIDEO SCRIPT:
{{video_script}}

AUDIENCE:
{{audience}}

TONE OPTIONS:
{{tone_options}}

RUNTIME LIMIT:
{{runtime_limit}}

BRAND RULES:
{{brand_rules}}

CLARITY CONSTRAINTS:
{{clarity_constraints}}

Return exactly:
1) Script diagnosis
   - what reads well aloud
   - what sounds too dense, awkward, or visually dependent
2) Three voiceover variants
   - clear
   - emotive
   - concise
3) Runtime estimate
   - estimated runtime per variant
   - which lines are most likely to overrun
4) Simplification map
   - what changed
   - why it changed
5) Narration note block
   - pronunciation watch-outs
   - pacing cues
   - emphasis cues
6) Dubbing and localization notes
   - terms to keep consistent
   - lines likely to become awkward in translation
7) Plain-language fallback
   - one low-complexity version for basic workflows

Rules:
- Keep meaning intact while adjusting voice and rhythm.
- Avoid vendor-specific tags or syntax.
- Keep wording readable when spoken aloud.
- If the runtime limit is impossible without cutting content, say what should be removed instead of hiding the problem.

When to Use

Use this when the script works on paper but not yet in a voice track. It is useful for voiceover production, synthetic narration, dubbing, and recap-style videos where the spoken version needs different rhythm than the on-screen copy.

It is especially helpful in current media workflows where teams generate visuals quickly and then discover the script is still written like a document instead of something a person could say naturally.

Variables

Variable	Description	Example
video_script	The original script draft	”Welcome to the release recap…”
audience	Intended viewers or listeners	”Operations managers evaluating the workflow”
tone_options	Desired tonal directions	”Direct, calm, slightly optimistic”
runtime_limit	Maximum target runtime	”60 seconds”
brand_rules	Language, positioning, or legal constraints	”No superlatives, keep product names exact”
clarity_constraints	Reading level, accessibility, or terminology rules	”Plain language, captions-friendly, no unexplained acronyms”

Tips & Variations

• Ask for host-read and narrator-read versions when presentation style affects pacing or tone.
• If timing is critical, request per-line shortening suggestions instead of only a total runtime estimate.
• Add a localization pass when the script will be dubbed or regionally adapted.
• Keep the original script in visible blocks if reviewers need sentence-level comparison.
• For lower-capability systems, process one paragraph at a time and then combine the approved lines.

Example Output

Diagnosis: the original script is clear conceptually but too dense for a 60-second read and depends on charts the listener cannot see.

Concise variant: shortens explanatory setup and moves the core takeaway into the first line so the narration lands earlier.