How to Write a Presentation Script

People often use "script" and "speaker notes" interchangeably, but they solve different problems. A script is prose: complete sentences, deliberate phrasing, and a fixed order of ideas, the kind of thing a keynote speaker rehearses word for word before a high-stakes talk. Speaker notes are a lighter memory aid: short prompts that sit next to your slides so you can speak naturally instead of reading.

Slides are a third, separate layer: the visual content your audience actually looks at while you talk. A slide might show one chart and three words of headline. Your script might spend two full paragraphs explaining the story behind that chart. Getting this right in order matters: shape the content and structure first, then write the script or notes, then let the design of the deck support what you are saying rather than repeat it.

The mistake most presenters make is skipping straight to slides and hoping the talking part will sort itself out on the day. A script forces you to think through your argument in full sentences before you stand in front of anyone, which is exactly why it is worth the extra writing even when you do not plan to read from it word for word.

A script is worth the extra writing time whenever precision matters more than spontaneity. Investor pitches and board updates often fall here, since a single loose sentence about growth or runway can create a problem you did not intend. Legal disclosures, regulated industries, product recalls, and media interviews are the same: the cost of misspeaking is high enough that exact wording earns its keep, and a script lets you rehearse the precise phrase instead of hoping you land on it live.

A script can also hurt you. In a casual team update, a sales conversation, or any talk with heavy back-and-forth, a full script tends to make you sound like you are reading rather than talking, and it leaves you brittle the moment someone asks a question that is not in the text. Presenters who over-script often lose the very thing that makes a talk land: the sense that they are speaking to this room, right now, not performing a memorized passage.

The practical answer for most talks is a hybrid. Write a full script for your opening line, your closing line, and any passage where the exact words matter, such as a statistic, a legal line, or a difficult message you need to get right the first time. For everything in between, work from an outline or speaker notes instead, so you stay flexible enough to actually talk to the people in the room.

1. Start from a finished outline, not a blank page. Your script should follow the same order as your slides and outline, section by section, so the two never drift apart. If your outline is not locked yet, fix that first, because a script written against a shifting structure gets rewritten twice.

2. Draft the opening and closing lines before anything else. These two moments carry the most weight and get rehearsed the most, so writing them first gives you something concrete to build the rest of the script toward, instead of discovering your ending while you are already exhausted from writing the middle.

3. Write each section in full sentences, matching one script section to one slide or one beat of your talk. Say the sentence out loud as you write it; if it is hard to say in one breath, it is probably hard to deliver, and you should break it into two shorter sentences instead.

4. Add verbal transitions between sections. A script that is just slide content read aloud feels choppy. Write a short bridging sentence between each section: what you just said, why it matters, and what comes next. These transitions are what make a script sound like a talk instead of a list of slides.

5. Read it aloud and time it, then cut. Almost every first draft of a script runs long and sounds more like an essay than speech. Reading aloud catches both problems at once: you will hear the sentences that only work on paper, and a phone timer will tell you honestly whether the script fits your slot.

Written language and spoken language are not the same thing, and a script that reads beautifully on the page can sound stiff the moment you say it out loud. Formal sentence structures, semicolons, and long strings of clauses work fine for an essay. In a script they force you to either slow down and sound like you are reading, or restructure the sentence on the fly, which is exactly the moment you lose your place.

Contractions help more than most people expect: a phrase like "we're seeing growth" sounds like a person talking, while "we are seeing growth" sounds like a document read aloud. The same goes for shorter sentences: a script sentence that runs more than about twenty words is usually two ideas trying to share one breath. Split it, and both ideas will land harder.

A useful habit while drafting is to say each sentence out loud as you write it, not after. If a sentence trips you up while you are typing it, it will trip you up again on stage, and it is far cheaper to fix at the keyboard than in front of an audience.

The single biggest gap between a script that works on paper and one that works on stage is rehearsal out loud. Reading a script silently tells you nothing about pacing, breath, or which sentences trip you up; saying it out loud, ideally standing up and at the volume you will actually use, is the only way to find those problems before your audience does.

As a rough guide, most speakers land somewhere around 130 to 160 words per minute in a conversational delivery, though nerves tend to push people faster on the day, not slower. That puts a ten-minute talk at roughly 1,300 to 1,600 words of script. Use this as a sanity check, not a target: read your own draft aloud at a natural pace and time it, since your pace is the only number that actually matters.

Rehearse section by section against your slide order, not just start to finish once. If a section is consistently running long, the fix is almost never to talk faster: it is to cut a sentence from the script. And rehearse the transitions between sections at least as much as the sections themselves. That is where scripts fall apart live, because the gap between one slide and the next is exactly where presenters forget what they planned to say.

A large language model is a solid first draft partner for a script, precisely because expanding a bullet outline into full sentences is a mechanical, well-defined task. Give it your section headings and key points in order and ask it to write out what you would say for each one, in a conversational tone, at roughly the length you need for your time slot. You will still rewrite most of it in your own voice, but a rough draft to react to is faster than a blank page.

Where this connects back to Eazy is upstream, in the outline itself. Eazy is a content-first editor: you write your ideas as headings, bullets, and slide-by-slide structure in a real document, or you drop in a source you already have, a PDF, a Word doc, a PowerPoint, a spreadsheet, or a link, and Eazy reads it into that same editable structure. That structure, the order of your ideas and what each slide is actually there to say, is the backbone your script has to follow anyway.

Once that structure is set in Eazy and you have shaped the content of the deck the way you want it, you can lift the same section-by-section outline into a script draft, using an AI writing tool or your own hand to turn each slide point into full sentences you will actually say. The job of Eazy is getting the content of the deck right and designed for you by default; the script that goes with it is yours to write, informed by a document you already trust.