Tell Cue who the presentation is for and what it should achieve. Ask for an outline, slide titles and speaker-note drafts, then review them in your presentation workflow.
Draft an outline and slide content, then review and refine them before presenting.
This page teaches slide drafting. Its copyable example produces no PDF conversion, PPTX file or audio. Before starting, check your chosen service’s supported formats, account requirements and usage limits.
| Your goal | What to request | What to check |
|---|---|---|
| Present the findings to an audience | A concise story, slide titles and speaker notes | Names, numbers, sources and the decision to discuss |
| Preserve the PDF’s page layout | A layout-preserving conversion | Page order, fonts, charts and which elements remain editable |
| Continue editing a presentation file | Your required format, such as PPTX | Open it in your presentation editor, edit a slide, save and reopen it |
| Explain the material in audio | A source-linked script, then a separate audio file if supported | Review the script against its sources; listen to the full audio and compare it with the script |
Provide the audience, purpose and approved source notes. Use the input method and permissions available in your installed Cue version.
Ask for slide titles, key points and speaker notes. Have missing facts and unsupported claims marked for review.
Check the content against your sources, then copy or adapt it in your presentation editor. Check layout and charts before presenting.
Method example — not a verified Cue run
Prepare a six-slide review that separates what happened, what is proposed and what still needs a decision.
Start with the facts, audience and decision you need. The fictional Cedar example shows what to check before you share a slide draft.
This example does not start a task in Cue. Copy the brief to use in a tool you have access to, then check the result yourself.
Editor-written input and expected slide structure. Not generated by Cue.
Copies the fictional task brief below. It does not start a run, save an assistant or share your materials.
Project: Cedar onboarding pilot (fictional)
Audience: Internal product review group
Decision requested: Approve or decline a one-week pilot extension; no decision has been made.
Language: English
Target: 6 slides, plain presentation style, no decorative stock images
[S1 — fictional project note, 2026-10-01]
The pilot invited 20 testers. 12 completed onboarding; 8 did not.
Three of the 8 reported an unclear permission prompt. The other 5 gave no reason.
The team changed the help text on 2026-09-30. There is no post-change measurement yet.
[S2 — fictional planning note, 2026-10-02]
Maya will review the revised permission wording by 2026-10-06.
Leo will prepare the next measurement checklist by 2026-10-07.
A one-week extension was proposed, not approved. Cost and start date are unknown.
Use only S1 and S2. Draft slide titles, concise points and speaker notes.
Keep source labels next to factual claims. Separate observations, proposals and unknowns.
Do not claim the wording change improved completion. Do not invent cost, launch dates,
customer quotes or approval. Mark any derived percentage and show its calculation.
End with the decision requested and open questions. Do not publish or send the deck.
Explore other reviewed-draft and desktop workflows that begin with the app and context you choose.
See current use cases →