How to Write Speaker Notes for a Presentation

A simple test separates the two: the slide is what the room reads, the notes are what only you see. If a sentence is doing work by being visible — supporting a claim, showing a number, making an argument scannable — it belongs on the slide. If a sentence is doing work by being said out loud — background context, the reasoning behind a number, a story that illustrates a point — it belongs in your notes. Confusing the two is why so many decks end up with slides packed with paragraphs nobody reads and speakers who have nothing left to say beyond restating the bullet in front of them.

In practice, notes tend to hold four kinds of content. Full explanations: the reasoning or context behind a headline claim that would clutter the slide if written out. Data sources: where a number came from, so you can answer a follow-up question without scrambling. Transitions: the one line that connects this slide to the next, so the talk flows instead of restarting with each click. And reminders: a prompt to pause, make eye contact, take a question, or slow down on a point that matters more than the slide shows.

Resist the urge to write your notes as a restatement of the slide. If your slide says "Revenue up 22%" and your note says "Revenue is up 22 percent this quarter," the note is not doing anything the slide is not already doing. A better note explains why: "Up 22% mostly from renewals, not new logos — call out that we retained the two accounts we almost lost in Q1." That is information the audience needs to hear but does not need to read.

Cue-style notes look like this: "Renewals drove growth — mention the two accounts we saved in Q1." They are prompts, not prose, enough to remind you what to say without dictating exactly how to say it. A full script for the same moment reads like this: "Our revenue grew 22 percent this quarter, and that growth came primarily from renewals rather than new business, including the two accounts in our renewals pipeline that we were at risk of losing back in the first quarter." Same information, a very different experience for the person delivering it.

Cues keep you talking to the room instead of reading at it. Because you are constructing the sentence live, your delivery sounds like a person speaking, your eye contact stays with the audience instead of the page, and you can adjust the wording on the fly if the room's energy or a question changes what needs saying. The tradeoff is that cues only work if you know the material — you need to have rehearsed enough that the cue reliably unlocks the right sentence, not a blank stare.

A full script removes that risk. If you have not rehearsed, or the content is complex, unfamiliar, or carries legal or numerical stakes, a script guarantees you say the correct words in the correct order. The cost is that most people who read a script sound like they are reading one — flatter tone, less eye contact, slower recovery if they lose their place. In practice, the strongest approach is a hybrid: cues for most of the talk, with two or three exact sentences fully scripted where the wording genuinely matters — a legal disclaimer, a precise statistic, or the line you use to close.

1. Finish the slide content first. Speaker notes explain and extend what is on the slide, so writing them before the slide content is settled usually means rewriting them the moment that content changes. Get the headline and evidence on the slide locked in, then move to notes.

2. Draft in full sentences first. For each slide, write out what you would actually say if you were explaining it to a colleague, in complete sentences. This is a drafting step, not the final format — writing in full sentences first surfaces gaps in your reasoning that a fragment might hide.

3. Compress into cues. Once the full version exists, cut it down to the shortest phrase that will reliably bring the whole sentence back to mind when you glance at it mid-presentation. A rule of thumb: three to six words per beat, not three to six sentences.

4. Mark anything that must be exact. Flag the handful of lines — a legal line, a precise number, a name you must not mispronounce, your closing line — that you want to say verbatim, and write those out in full even though the rest of your notes stay as cues.

5. Rehearse out loud with the notes in front of you, at delivery speed, not reading speed. This is where you find out whether a cue actually triggers the sentence you meant, or whether it needs another pass. Notes that work on the page and notes that work under mild nerves in front of a room are not always the same notes — rehearsal is what catches the difference.

The right length depends on how long you plan to spend on that slide, not a fixed rule for the whole deck. A slide you are moving through in fifteen seconds needs one or two cues, not a paragraph. A slide carrying the core argument of your talk, where you might spend two full minutes, can support more — additional context, an anticipated question, a supporting anecdote — because you have the time on screen to use it.

As a starting target: cue-style notes usually run two to four short lines per slide. A fully scripted passage usually runs three to five sentences before it starts working against you, because a script much longer than that becomes a passage you read rather than one you have rehearsed well enough to deliver naturally. Either way, if your notes for one slide run longer than a paragraph, that is usually a sign the slide itself is trying to cover more than one idea.

The real test is not a word count, it is whether you can deliver the note without your face buried in the page. Read your notes for a slide, then look up and try to say the same thing from memory using only the cue. If you cannot, either the cue is too thin or the content is too dense for one slide — and dense content is more often the actual problem than the notes.

AI is genuinely useful for the sentence-level part of this work. Give it a rough note — "renewals mattered, mention the two we saved" — and it can turn that into a smoother transition, suggest a cleaner way to phrase a data point, or shorten a note that has drifted into a full paragraph. What it cannot do is know how the room will feel on the day, how fast you naturally talk, or which line you personally need memorized versus cued — those are decisions only rehearsal answers.

In Eazy, notes live alongside your content in the same document-first editor you use to write and shape the deck, so your cues stay next to the slide they belong to as the deck changes. You can refine that writing by chatting with Eazy in plain language — asking it to tighten a note, suggest a transition, or rephrase something that reads stiffly — the same way you would ask it to improve any other line in your document. Eazy does not auto-generate or export a separate speaker-notes script for you today; the notes stay something you write and refine, not something the tool hands you finished.

If you specifically want more help drafting notes with AI, our guide on using an AI speaker notes generator goes deeper on that workflow. And if you are still deciding between cue-style notes and a full script, or how to write the script itself, see how to write a presentation script — and for the other half of this decision, what actually belongs on the slide, see what to put on presentation slides.