Notes written as full sentences get read aloud as full sentences, and the audience hears a monotone recital instead of a person talking. The fix is not “write better paragraphs” — it is to make the notes a cue sheet: key phrases, a number to hit, a transition to say, and a list of things to leave out. The 12 prompts below force that format. Paste a prompt, swap the bracketed inputs, and you get notes that survive eye contact with the room.
TL;DR
- Ask for cues, not sentences: bullets of key phrases, one transition line per slide, a hard word cap (≤ 60 words is enough for most slides).
- The single highest-value prompt is “What NOT to say” — caveats and jargon, not missing content, are what sink a talk.
- Native tools now do the first draft: PowerPoint Copilot generates notes for one slide or the whole deck via Agent mode, and Gemini in Google Slides writes per-slide notes from the side panel. Both need a paid license; both still produce script-shaped paragraphs you have to thin out.
- For pure generation from raw content (no slides yet), any frontier chat model works — GPT-5.5, Claude Sonnet 4.6, or Gemini 3.1 Pro (all June 2026). Quality differences are marginal here; the prompt structure matters far more than the model.
Who this is for
Founders pitching, IC engineers presenting at a review, salespeople running a deck, comms teams writing notes for an executive who didn’t build the slides, and trainers who present the same material weekly and want a tighter cue sheet each time.
When not to use these prompts
Skip them if your slides already contain every sentence you plan to say — that is a leave-behind handout, and notes would just duplicate it. Skip the cue-only format if the speaker is genuinely new and needs a full script for the first one or two runs; in that case generate the script, rehearse it, then re-run prompt #1 to compress it back into cues for the real talk.
Native tools vs. a chat prompt (June 2026)
If your deck already lives in PowerPoint or Google Slides, generate the first pass where the slides are, then thin it with the prompts here. If you only have raw content (a doc, talking points, a transcript), generate directly in a chat model.
| Tool | How it makes notes | Scope | Access (June 2026) |
|---|---|---|---|
| PowerPoint Copilot (Agent mode) | Chat on the slide: “Generate speaker notes for all slides” or current slide | Whole deck or one slide | Microsoft 365 Copilot add-on, ~$18–21/user/mo Business, $30 Enterprise |
| Gemini in Google Slides | Side panel: “Write speaker notes for this slide…” | One slide at a time (multi-slide announced, not shipped) | Paid Google Workspace plan; no free-account access |
| GPT-5.5 / Claude Sonnet 4.6 / Gemini 3.1 Pro (chat) | Paste slide content or raw doc, run a prompt below | Anything you paste | Free tiers exist; long decks favor the 1M-token windows on Gemini 3.1 Pro and Claude Sonnet 4.6 |
The native generators are convenient but verbose: Copilot and Gemini both tend to write full-sentence notes that read like a script. That is exactly the failure mode this article fixes — so after the native draft, run prompt #1 (“cue-based”) and prompt #12 (“hygiene”) over the result.
A separate but useful tool: PowerPoint Speaker Coach (Slide Show tab, included with Microsoft 365) listens while you rehearse and flags filler words, pace, monotone, and whether you are reading the slide verbatim. Use your AI-generated cue notes, rehearse with Coach, and you have a closed loop from draft to delivery.
Prompt anatomy
Every prompt below already encodes four things; when you write your own, keep them:
- Format constraint — bullets/cues, never paragraphs (this is what stops the script).
- Hard length cap — a word or line limit per slide, so notes stay glanceable.
- A “leave out” instruction — what the speaker should not say, which most note generators ignore.
- Slide context — paste the actual slide title and content so the model has something concrete to react to.
12 copy-ready prompt templates
1. Cue-based notes (not scripts)
Slide: `[slideTitle]`. Slide content: `[content]`. Write speaker notes as: 3-5 bullets of key phrases + 1-2 transition cues. Skip full sentences. Total <= 60 words.Swap: [slideTitle], [content]
2. Per-slide opener / closer
For each slide, give: (a) Opening sentence (<= 10 words), (b) Key message (<= 15 words), (c) Closing transition to next slide (<= 10 words). Total: 3 lines per slide.3. Anticipated-question prep
For this deck, predict the 5 questions the audience is most likely to ask. For each: which slide triggers it, a 2-sentence answer, and a fallback if pressed harder. Keep these in notes, not on slides - the speaker handles them.4. Transition cue notes
Audit my deck for awkward transitions. For each slide pair, write a one-line bridge sentence the speaker says ("So far we've seen X. Next, Y."). Output as a 2-column table: from-slide, bridge line.5. Timing notes per slide
My talk is `[minutes]` minutes across `[nSlides]` slides. Allocate time per slide (some get more than others), output a timing plan, and flag any slide too dense for its time slot.Swap: [minutes], [nSlides]
6. Energy / pace cues
Add pacing cues to my notes: where to pause (after a hard number), where to speed up (recap slides), where to slow down (a counter-intuitive claim). Mark each as a one-word cue on the relevant slide.7. What NOT to say
Audit my deck for things speakers commonly over-share that hurt the talk: (a) caveats that erode confidence, (b) jargon a general audience won't get, (c) tangents. List per slide, with a shorter replacement line.8. Demo-fail backup
My deck has a live demo at slide `[n]`. If it fails, what does the speaker say? Write 3 backup lines: (a) acknowledge and continue, (b) screen-share or screenshot alternative, (c) "let's pick this up offline" pivot.Swap: [n]
9. Story-anchored notes
For my data-heavy slides, add one story anchor each: a real customer, a real moment, or a single real number. The speaker tells the story BEFORE the data, not after. Mark which slides got an anchor.10. Per-slide one-word summary
Add a one-word tag to each slide's notes ("Problem", "Hook", "Proof", "Ask") so the speaker can re-orient at a glance if they lose their place mid-talk.11. Q&A close cue
Write my closing line plus the Q&A open: (1) recap the headline takeaway in 1 sentence, (2) the one thing to remember, (3) a Q&A invite. Avoid "Any questions?" - it kills engagement. Suggest a more specific opener.12. Speaker-note hygiene
Audit my speaker notes for: (1) any note that reads like a script (full paragraphs), (2) any slide with no notes (mistake or intentional?), (3) any note that just restates what's already on the slide. Output a per-slide cleanup list.Mistakes specific to speaker notes
- Generating notes that are full sentences. Native tools (Copilot, Gemini) default to this. If you don’t cap length and demand bullets, you get a script. Always re-run prompt #1 over a native draft.
- Notes that restate the slide. If the slide says “Revenue up 40%” and the note says “Tell them revenue is up 40%,” the note is dead weight. The note should say why it’s up or what to do with it.
- No “leave out” list. The fastest way to ruin credibility is over-caveating. Prompt #7 is the one most people skip and need most.
- Asking AI to invent the numbers. If you give soft inputs, the model fills gaps with plausible-but-fake figures. Paste your real slide data; the model should frame numbers, never source them.
- One long block per slide. Presenter view shows a few lines; anything past line 5 won’t be seen in the moment. Keep it glanceable.
- No timing pass. A deck that runs 18 minutes in your head runs 31 minutes live. Run prompt #5 and rehearse against it with Speaker Coach.
How to push results further
- Always name the audience and their seniority in the prompt — notes for a board read differently than notes for a team standup.
- Generate, then rehearse out loud once and re-run prompt #12 to cut anything you stumbled on.
- For a recurring talk, save your best prompt + slide content as a reusable block and refresh only the data each cycle.
- Pair the cue notes with a rehearsal in PowerPoint Speaker Coach (filler words, pace, monotone) or Gemini in Slides for the first draft.
- Never ship AI notes unread. The model formats well; only you know what you’ll actually say.
FAQ
- Can Copilot or Gemini write speaker notes automatically? Yes. As of June 2026, PowerPoint Copilot (Agent mode) generates notes for a single slide or the whole deck, and Gemini in Google Slides writes per-slide notes from the side panel (one slide at a time, with multi-slide announced but not shipped). Both need a paid license, and both tend to produce full-sentence drafts you should thin with prompt #1.
- Do I need a paid plan? For the native generators, yes — Microsoft 365 Copilot is an add-on (about $18–21/user/mo on Business, $30 on Enterprise as of June 2026), and Gemini in Slides requires a paid Workspace plan. If you only need to turn raw content into notes, a free chat tier (ChatGPT, Claude, or Gemini) handles it fine.
- Which model is best for this? It barely matters. GPT-5.5, Claude Sonnet 4.6, and Gemini 3.1 Pro all write good cue notes from a clear prompt. For a long deck pasted in full, the 1M-token windows on Gemini 3.1 Pro and Claude Sonnet 4.6 mean you can drop the whole thing at once.
- How long should each slide’s note be? Aim for what fits on screen in presenter view without scrolling — roughly 3–5 bullets, under 60 words. If you can’t glance at it and keep talking, it’s too long.
- Should I generate a full script or just cues? Cues, unless the speaker is brand new to the material. New speakers can generate a script, rehearse it, then compress it back to cues with prompt #1 for the live run.
- Will AI invent the numbers in my notes? It will if you let it. Paste your real slide data; the model should frame and sequence your numbers, never source new ones.