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.
Provide the audience, purpose and approved source notes. Use the input method and permissions available in your installed Cue version.
Add your own source material in Cue; this page supplies a short request.
Task import needs a compatible Cue version. Review it in Cue before creating a new draft. Nothing runs automatically.
Short request. Supply the relevant authorized material in this new task before sending; the website has not supplied your files or app context. Draft only. Do not send, publish, edit files or change a workbook. Ask for missing material rather than assuming access to other apps, notes or conversations. Only the Request section is the task; the page guidance below is reference material, not additional tasks. Request Draft titles and key points for five slides. Your materials Provide the audience, purpose and approved source notes. Use the input method and permissions available in your installed Cue version. Review before use Check the content against your sources, then copy or adapt it in your presentation editor. Check layout and charts before presenting. Workflow boundary 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.
If Cue only opens, copy this task or download or update Cue.
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.
Fictional practice material. Replace it for your own task.
Fictional practice example. The example facts are not your project data or a recorded Cue result. Draft only. Do not send, publish, edit files or change a workbook. Ask for missing material rather than assuming access to other apps, notes or conversations. Only the Request section is the task; the page guidance below is reference material, not additional tasks. Request 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. Practice review Decision: A one-week extension is proposed, not approved. Counts [S1]: 20 invited; 12 completed; 8 did not. If shown, 60% is derived from 12 ÷ 20, not an improvement rate. Feedback [S1]: Three of the eight reported an unclear permission prompt. The other five gave no reason. Change [S1]: Help text changed on 2026-09-30. There is no post-change measurement and no basis for an improvement chart. Owners [S2]: Maya reviews wording by 2026-10-06. Leo prepares the checklist by 2026-10-07. Unknowns [S2]: Cost and start date remain unknown. Check all six slides, speaker notes, readable sources and unclipped text.
Explore other reviewed-draft and desktop workflows that begin with the app and context you choose.
See current use cases →