---
title: "Voice Over Script Template With a Timing Table"
description: "Copy a reusable voice over script template with a beat list, timecodes, a worked 30-second example, and a word budget table for timing any narration."
canonical: "https://www.murmurtts.com/blog/voice-over-script-template"
---
[Murmur](https://www.murmurtts.com/)/[Blog](https://www.murmurtts.com/blog)/Guide

Guide

# Voice Over Script Template With Timing

Copy a reusable voice over script template with a beat list, timecodes, a worked 30-second example, and a word budget table for timing any narration.

![](https://www.murmurtts.com/murmur-icon.webp)Murmur·October 24, 2026·8 min read[Download free (3-day Pro trial)](https://murmur-updates.tarunyadav9761.workers.dev/download/latest)[Buy $49](https://murmur-licenses.tarunyadav9761.workers.dev/checkout)

Free plan with Kokoro voices, scripts up to 1,500 characters · 3-day Pro trial, then $49 once

On this page

What a reusable voice over script template should containThe blank voice over script templateA worked example: 30-second product explainer with timecodesEstimate timing before you recordMatch the template depth to the jobTurn the template into a finished scriptAccessibility and the recorded voice overWhere Murmur fits, and when it is not the right choiceFrequently asked questions

[Back to the journal](https://www.murmurtts.com/blog)

**Short answer:** A voice over script is the spoken text plus a timing plan: what each line says, roughly how long it should run, and where pauses or cues belong. A reusable template fixes those beats in the same order every time, so you fill in the words once you know the target duration. The template and tables below work for ads, explainers, e-learning, and long-form narration, and you can copy them as they are.

This guide gives you three things an empty template lacks: a beat list with a timing field, a worked 30-second example with timecodes, and a word budget table built from a speech rate you can check yourself. The products, controls, and domains in the examples are fictional. Adapt the structure and replace every example fact with a verified one before you record.

## What a reusable voice over script template should contain

A script template earns its keep when it separates four things that writers tend to mix: the spoken words, the time budget for each beat, the production directions (music, pauses, speaker changes), and the approval notes. If all four sit in one paragraph, the timing gets guessed and the directions get read aloud by mistake. Keep the clean spoken copy in one place and everything else beside it.

- A target duration and the speaking rate you measured, written at the top of the file.
- A beat list in the order the listener hears it, not the order you researched it.
- A time budget or timecode field for each beat, so an overrun shows up early.
- A separate column for production directions such as pauses, music, and speaker changes.
- One action and one destination, stated once.
- A version note and a date, so a reviewer knows which draft they heard.

## The blank voice over script template

Fill the beats in this order: hook, promise, two body beats, result, action. Each beat gets a timecode, and the timecodes should add up to your target duration before you write a single finished sentence. The final tag is optional and should repeat the identity only if the listener needs to hear it.

> [0:00 to 0:0X] HOOK: one situation or question the listener recognizes. [TIMECODE] PROMISE: what this piece will show, explain, or give. [TIMECODE] BODY ONE: the first necessary point, step, or detail. [TIMECODE] BODY TWO: the second necessary point, step, or detail. [TIMECODE] RESULT: what the listener can now expect or check. [TIMECODE] ACTION: one next step and one destination. [OPTIONAL TAG: short identity or sign-off.]
>
> Blank voice over script template

The timecodes are a budget, not a measurement. A five-second hook at a conversational pace holds about twelve or thirteen words; at a slower, deliberate pace it holds fewer. The next sections turn that rule of thumb into tables you can read before you record. Write the hook and the action first, because those two beats decide how much room is left for the middle.

## A worked example: 30-second product explainer with timecodes

> [0:00 to 0:05] Every packed desk starts the same way: cables, a notebook, and a screen sitting at the wrong height. [0:05 to 0:12] The Foldwell stand opens flat, then locks into three positions. Set your sample laptop on it and choose the height that matches the chair. [0:12 to 0:21] The base stays planted while the support moves. That is the sample combination shown here, not a claim about every laptop. [0:21 to 0:27] Fold it back, slide it into the bag, and carry the same setup with you. [0:27 to 0:30] Check dimensions and finishes at foldwell dot example.
>
> Original fictional voice over script example

Read the example against its timecodes. The hook takes five seconds, the two body beats take sixteen, the action takes six, and the tag takes three. If the second body beat runs long, cut the phrase that repeats the first instead of speaking faster. The domain and product are fictional; replace both, and confirm any dimension or compatibility claim with the manufacturer before you record.

## Estimate timing before you record

Timing starts with a rate, not a feeling. Voices.com reports that the National Center for Voice and Speech puts average US conversational talk at about 150 words per minute, and its words-to-time calculator uses that figure. Treat 150 words per minute as a planning default, then replace it with your own measured rate: read a 150-word passage aloud for exactly one minute, then count the words you actually covered. A calm documentary read and an energetic ad read will not land on the same number.

| Target duration | Words at 120 wpm (slow) | Words at 150 wpm (conversational) | Words at 180 wpm (fast) |
| --- | --- | --- | --- |
| 15 seconds | 30 | 38 | 45 |
| 30 seconds | 60 | 75 | 90 |
| 60 seconds | 120 | 150 | 180 |
| 2 minutes | 240 | 300 | 360 |
| 5 minutes | 600 | 750 | 900 |
| 10 minutes | 1200 | 1500 | 1800 |

These figures are planning estimates for spoken words only. They exclude pauses, music, effects, speaker changes, and any moment a viewer needs to read on-screen text. A finished file almost always runs longer than the word count suggests, which is why you cut beats rather than speed the read up. Time the actual recording before you commit to a slot.

## Match the template depth to the job

| Format | Typical target | Beats to keep | Watch out for |
| --- | --- | --- | --- |
| Ad or promo | 15 to 30 seconds | Hook, reason, action | Finishing early by rushing the brand name |
| Product explainer | 30 to 90 seconds | Hook, promise, body, result, action | Claiming an outcome the capture does not show |
| E-learning module | 2 to 10 minutes | Repeated beats per section, plus a recap | Reading a slide instead of narrating it |
| Voicemail or IVR | 15 to 45 seconds | Greeting, one instruction, one menu | Listing every option the caller rarely needs |
| Audiobook chapter | 5 minutes and up | Scene beats with steady pacing | Uneven pace across recording sessions |

The same beat list scales up or down by repeating the middle. A fifteen-second ad keeps the endpoints and drops most of the middle, and the [radio ad script examples](https://www.murmurtts.com/blog/radio-ad-script-examples) show how that sounds on a strict slot. A product walkthrough needs its own promise and result, which is why the [product demo script template](https://www.murmurtts.com/blog/product-demo-script-template) pairs each line with a visible action. A short format such as a [voicemail greeting](https://www.murmurtts.com/blog/voicemail-greeting-script-examples) uses three beats at most. That is what makes this template reusable: the frame stays, the number of beats changes.

## Turn the template into a finished script

1. Write the target duration and your measured speaking rate at the top of the file.
2. Draft the hook and the action first, since they set the length of everything between them.
3. Fill each body beat with one idea, not a list of features.
4. Read the draft aloud and write a timecode next to each beat as you go.
5. Count the words in each beat and compare them with the budget for that slice.
6. Cut whole beats that repeat an earlier point before you tighten the pace.
7. Record or generate the narration, then mark the real elapsed time and revise once.

Step five is the one people skip. Counting words per beat catches the overrun before a client or a slot deadline discovers it. If a thirty-second ad is running at thirty-eight seconds, the fix is usually a missing cut, not a faster voice. A [podcast intro](https://www.murmurtts.com/blog/podcast-intro-script-examples) often needs a tighter hook for the same reason, since a listener decides in the first few seconds whether to keep going.

## Accessibility and the recorded voice over

A clean script is also an accessibility asset. Apple's iMovie voiceover guide describes recording narration with an input source and a volume slider, and it advises setting the level so the audio meter stays green even at the loudest point; the recorded clip attaches to the clip under the playhead. Those details matter because a script that reads cleanly in one pass is easier to caption and sync later. The W3C's guidance on transcripts notes that prerecorded audio-only content needs a transcript to meet WCAG Level A, and that a basic transcript covers speech while a descriptive transcript adds the visual information a listener cannot hear. Keeping timecodes in your script makes both the caption pass and the sync pass faster, because each beat is already a small, labeled unit.

## Where Murmur fits, and when it is not the right choice

Murmur is a local-first voice studio for Apple Silicon Macs running macOS 15 or later. It generates speech on your machine, so scripts are not uploaded and there are no per-character fees. The download includes a bundled Kokoro engine with preset voices; additional local models add voice cloning, voice design, and multi-speaker projects, and you can export WAV or M4A for editing (the [voiceover export guide](https://www.murmurtts.com/blog/wav-m4a-mp3-tts-voiceover-export) distinguishes a master file from a delivery file). Because the models run locally, hearing a full read of your script costs nothing but time, which makes the timing pass practical for a script you keep revising.

Murmur is not the right choice if you need Windows, a phone or browser app, live streaming text to speech, cloud team collaboration, or speech-to-text transcription; a hosted service will serve those cases better. It also does not do the writing for you, so the template and tables above still matter. If you only want a rough read of a short passage, the free online text to speech tool is enough and you do not need to buy anything. Check the in-app model list for the exact voices and languages each model supports before you build a project around one.

## Frequently asked questions

## Sources

- [Apple Support: Record a voiceover in iMovie on Mac](https://support.apple.com/guide/imovie/record-a-voiceover-mov44e3a4427/mac)Accessed 2026-10-14
- [W3C WAI: Transcripts (Making Audio and Video Media Accessible)](https://www.w3.org/WAI/media/av/transcripts/)Accessed 2026-10-14
- [Voices.com: Words to Time Conversion Calculator (cites the National Center for Voice and Speech figure of about 150 words per minute)](https://www.voices.com/tools/words_to_time_conversion)Accessed 2026-10-14

## Time your voice over script in Murmur

Murmur is a local voice studio for Apple Silicon Macs running macOS 15 or later. The website edition costs $49 one-time, with a free plan and a 3-day Pro trial, and a 7-day refund policy. Listen to the public samples before buying.

[Download free (3-day Pro trial)](https://murmur-updates.tarunyadav9761.workers.dev/download/latest)[Buy Murmur · $49](https://murmur-licenses.tarunyadav9761.workers.dev/checkout)

macOS 15+ · Apple Silicon required · 7-day refund policy

Made for your Mac

## Less reading. More making.

[Download free (3-day Pro trial)](https://murmur-updates.tarunyadav9761.workers.dev/download/latest)[Buy $49](https://murmur-licenses.tarunyadav9761.workers.dev/checkout)[Explore Murmur](https://www.murmurtts.com/#product)