How to Prepare Your Script for a Teleprompter

A well-prepared script makes teleprompter delivery dramatically easier. After formatting thousands of scripts for speakers across the country — from corporate CEOs and elected officials to first-time speakers — we've learned exactly what works and what creates problems on set.

Follow these guidelines to prepare scripts that read naturally and help your talent deliver their best performance, whether the event is a corporate keynote in New York, a product launch in San Francisco, a press conference in Chicago, or a campaign rally in any major market.

Write for the Ear, Not the Eye

Teleprompter scripts are heard, not read. This fundamental difference shapes everything about how you should write:

• Use conversational language. Write how people talk, not how they write.
• Keep sentences short. Long sentences are hard to deliver naturally and force awkward breaths.
• Avoid complex punctuation. Semicolons and em-dashes create delivery confusion and on-camera hesitation.
• Read it aloud. If a sentence sounds awkward spoken, rewrite it. Always.

Formatting Best Practices

Use ALL CAPS or Large Font

Most teleprompter operators display scripts in all capitals or very large fonts for readability. Write in whatever format is comfortable, but know that your text will likely be converted to caps before it goes on the glass.

Avoid Special Formatting

Bold, italic, underline, and colored text often don't transfer cleanly into teleprompter software. Use plain text. If you need to indicate emphasis, write (EMPHASIS) before the word or phrase.

Break Into Short Paragraphs

Large blocks of text are hard to track on a teleprompter. Break content into small paragraphs — two to three sentences maximum. White space helps readers keep their place and gives them visual breath.

Use Phonetic Spellings

For names, technical terms, or foreign words that might be mispronounced, include phonetic pronunciation in parentheses. Example: "The CEO of Huawei (HWAH-way) announced…"

Structure for Natural Delivery

Include Breath Points

Mark natural pause points with ellipses (...) or [PAUSE]. Readers need to breathe, and pauses create dramatic emphasis.

Indicate Transitions

Use clear markers when topics shift: [NEW TOPIC], [TRANSITION], or simply leave extra space. This helps readers mentally prepare for content changes rather than getting caught mid-thought.

Number Your Sections

For longer scripts, numbered sections help both the reader and the operator track position and make it easier to jump to specific points if needed. Operators can also use section numbers to find a place quickly when talent gets lost.

Numbers, Dates, and Technical Content

Numerals slow speakers down: a reader has to decide in the moment whether "250,000" is "two hundred fifty thousand" or "a quarter million," and dates like "1/15" can be read several ways. Write numbers the way you want them said:

• Spell out numbers: "two hundred fifty thousand" not "250,000"
• Write dates in full: "January fifteenth, twenty twenty-five" not "1/15/25"
• Avoid abbreviations: Write "versus" not "vs." and "approximately" not "approx."
• Simplify statistics: Round numbers when precision isn't critical. "About three-quarters" lands better than "74.3%."

Timing Your Script

A typical speaking pace is about 150 words per minute. Use this to estimate run time:

Word Count	Approximate Run Time
300 words	~2 minutes
750 words	~5 minutes
1,500 words	~10 minutes

Build in extra time for pauses, applause breaks, and natural variation in pace. A 10-minute script rarely runs exactly 10 minutes on stage.

What File Format to Use

Most teleprompter operators can work with:

• Microsoft Word (.docx)
• Plain text (.txt)
• PDF (though editing on the fly is limited)
• Google Docs (shared link)

When in doubt, plain text is safest — formatting can't get corrupted if there isn't any.

Last-Minute Changes

Scripts almost always change right up to showtime. To make updates easier:

• Use clear version numbering: "Script_v3_FINAL.docx" — and yes, we've seen that exact filename, plus every variant you can imagine.
• Track changes or use different colors for revisions so the operator can see what shifted.
• Send a clean final version before the event so the operator has a known-good baseline.
• Designate one person to communicate changes to the operator. Five people emailing edits at midnight is a recipe for the wrong version going live.

Common Script Problems We See

Run-On Sentences

If a sentence has multiple commas and clauses, it's too long for comfortable delivery. Break it up.

Corporate Jargon

Business-speak that works in documents often sounds terrible spoken aloud. "Leverage synergies" should become "work together."

Too Much Information

Teleprompter delivery is slower than reading. Scripts that look short on paper can feel endless when delivered. Edit ruthlessly.

Missing Pronunciations

Don't assume talent knows how to pronounce every name or term. When in doubt, include pronunciation guides. Even seasoned politicians have been caught on technical acronyms they don't normally say aloud.

---

A great teleprompter performance starts long before show day — it starts with a script that's been prepared the way it will be delivered: out loud, on cue, in front of an audience. Get that right, and the technology becomes invisible.