How to Write for a Teleprompter

Writing for a teleprompter is different from writing for the page. The best scripts sound like natural conversation—not like a document being read aloud. Whether you're preparing remarks for a corporate event at Cleveland's Rock & Roll Hall of Fame, a political town hall in Columbus, or a nonprofit fundraiser in Cincinnati, these principles apply.

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
• Avoid complex punctuation: Semicolons and em-dashes create delivery confusion
• Read it aloud: If it sounds awkward spoken, rewrite it

For example, instead of "The implementation of such methodologies facilitates organizational efficiency," write "This helps our team work better."

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 your text will likely be converted to caps.

Avoid Special Formatting

Bold, italic, underline, and colored text often don't transfer to 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—2-3 sentences maximum. White space helps readers keep their place.

Use Phonetic Spellings

For names, technical terms, or foreign words that might be mispronounced, include phonetic pronunciation in parentheses. For Ohio-based clients, this might include industrial terms like "Elyria" (eh-LEER-ee-uh) or "Cuyahoga" (ky-uh-HOH-guh).

Structure for Natural Delivery

Include Breath Points

Mark natural pause points with ellipses (...) or [PAUSE]. Readers need to breathe, and pauses create 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.

Number Your Sections

For longer scripts, numbered sections help both the reader and operator track position and make it easier to jump to specific points if needed.

Numbers, Dates, and Technical Content

• Spell out numbers: Write "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

Timing Your Script

A typical speaking pace is about 150 words per minute. Use this to estimate 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.

What File Format to Use

Most teleprompter operators can work with:

• Microsoft Word (.docx)
• Plain text (.txt)
• PDF (though editing 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 often change right up to showtime. To make updates easier:

• Use clear version numbering: "Script_v3_FINAL.docx"
• Track changes or use different colors for revisions
• Send a clean final version before the event
• Designate one person to communicate changes to the operator

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—especially important for Ohio cities like Xenia (ZEE-nyuh) and Zanesville (ZAYNS-vil).