Cut a 90-Second Script to 30 Seconds Without Losing the Point

A 30-second version of a long script is not the same script spoken three times faster. It is a smaller promise delivered clearly. When you cut only adjectives and pauses, the viewer still has to process the original number of ideas. The result can be short and exhausting.

Start by deciding what the shorter Reel must accomplish. If the long version teaches a complete process, the short version might show one decision within it. Save the remaining explanation for a separate resource or longer video, rather than quietly removing a necessary warning.

The example below is an original written editing exercise. Its long and short versions have not been recorded or timed. “90 seconds to 30 seconds” describes the editing task: measure your actual draft and final read before applying those duration labels to a finished video.

Write the sentence the viewer should remember

For our example, the topic is vague video feedback. The useful outcome is: give an editor a timecode, a specific problem and a desired change.

That is more precise than “communicate better with your editor.” It also tells us what to remove. A story about how busy the week was does not help the viewer write the note. An example does. A reminder to identify the correct version also helps if otherwise the editor might change the wrong file.

Keep a separate parking document. Good material that does not fit this Reel is not bad material; it belongs in another version. This makes cutting less painful and prevents the short script from accumulating “one more thing.”

The long draft: find the jobs hidden inside it

Here is the illustrative starting script:

If you've ever worked with a video editor, you'll know that feedback can take much longer than you expected. You send a first message, then remember something else, then send a voice note, and by the time the next version arrives you're not sure whether every change was included. I used to think the answer was just to explain everything in more detail.

But more words aren't always clearer. Saying “make the opening better” doesn't tell the editor whether the problem is the picture, the sound, the pacing or the information. They have to guess, and you might end up reviewing a different solution to the problem you actually had.

A useful note has three parts: where it happens, what is wrong and what you want instead. For example, in version two, at six seconds, the product name disappears before I can read it. Keep the name on screen until the demonstration starts.

It also helps to keep all the notes together and say who is approving the final edit. Different people can ask for opposite changes. Before you send feedback, watch the whole version once, collect the changes, check that they refer to the current export and send one organised message.

This contains several jobs: reduce fragmented messages, make a note specific, identify the version, gather feedback and choose an approver. A short Reel cannot develop all of them equally.

Mark each part: keep, cut, show or move

Use four labels rather than deleting sentences at random.

Do not move essential meaning into tiny text merely to claim you cut it. If a viewer needs a visual detail to understand the lesson, describe it naturally in the narration or provide an appropriate text alternative. W3C explains this distinction in its visual-information guidance.

The short version

Here is a tighter illustrative script:

“Make the opening better” leaves your editor guessing. Give them three things: a timecode, the problem, and the change you want. For example: “Version two, six seconds. The product name disappears before I can read it. Keep it up until the demo starts.” A clear note tells them what to fix—not how frustrated you feel.

The example preserves the original method and one concrete application. It does not keep every useful instruction. That is the point of the cutdown.

On screen, show three labels—Timecode, Problem, Change—then the note beneath them. Avoid introducing a separate checklist the narration never explains. Pictures should support the thought, not start a competing lesson.

Budget time for actions as well as words

Record the short version at the pace you would use with a real person. Include the pause while the example appears. Start the timer when the audience-facing video begins and stop when the final meaningful picture ends.

If the measured read is too long, find the least necessary thought. In this example, the final contrast about frustration could go before the useful note does. If the read is too short, do not automatically add more points. The viewer may need that space to understand the example.

A rough planning calculation can help: measured words divided by measured speaking seconds gives your words per second for that read. It is a planning estimate, not your permanent speaking speed. Numbers, unfamiliar words, laughter and demonstrations change the pace.

Do not treat captions as permission to rush. Plan their place and review their timing with the final audio, as part of the broader W3C media-planning approach. A script and its final captions need to reflect what is actually said.

Run a meaning check before a duration check

Ask someone unfamiliar with the long version what the short version teaches. If they answer “give better feedback,” the example may not be clear enough. If they can name the three parts and write a useful note, the smaller promise survived.

Then inspect the cuts for changed meaning. Did removing “in this example” turn a suggestion into a universal rule? Did a missing “not” reverse an instruction? Did a shorter product description drop an important limitation? Restore any sentence required for accuracy, even if that means choosing a narrower topic.

Use the downloadable worksheet for your own before-and-after edit. When the script is stable, map its spoken lines to a shot list. If the wording still feels formal, start with a voice-note rewrite before cutting further. Clear, complete and naturally delivered is a better finish line than exactly thirty seconds at any cost.

LONG SCRIPT TO SHORT REEL
These examples are illustrative, not timed recordings.

BLANK
Current script/version:
Measured current duration:
Target duration:
One thing the viewer should learn:
Essential example:
Important qualifier or warning:
Sentence | KEEP/CUT/SHOW/MOVE | reason:
[copy every sentence into this section]
Material saved for a longer version:
Short script:
Visuals that carry useful information:
Spoken description needed for those visuals:
Measured rehearsal duration:
Pause/demo time included:
Least essential remaining sentence:
Listener's explanation of the lesson:
Accuracy check:
Final version:

COMPLETED EDIT
Topic: useful feedback for an editor.
Promise: timecode + specific problem + desired change.
CUT: long backstory about scattered messages.
KEEP: "make the opening better" as the vague-note example.
KEEP: one version-number/timecode example.
SHOW: three clear field labels.
MOVE: multiple approvers and payment/delivery process.
Short script: "Make the opening better" leaves your editor guessing. Give them three things: a timecode, the problem, and the change you want. For example: "Version two, six seconds. The product name disappears before I can read it. Keep it up until the demo starts." A clear note tells them what to fix—not how frustrated you feel.
Measured duration: not recorded; complete this after your own read.
Meaning check: can a new viewer write a note using the three fields?