5 Claude Prompts for Presentations, Reports and Documents

Plan a presentation for me, slide by slide.

Topic: [TOPIC]
Audience: [WHO, AND WHAT THEY ALREADY KNOW]
Goal: [WHAT THEY SHOULD THINK, DECIDE OR DO AFTERWARDS]
Length: [MINUTES], roughly [NUMBER] slides
Setting: [E.G. BOARD MEETING, CONFERENCE TALK, SALES PITCH, CLASS]
Material: [PASTE NOTES, DATA OR KEY POINTS]

First, write the core message in one sentence. Every slide should support it.

Then, for each slide:
- Title: a takeaway sentence ("Switching suppliers cut our delivery costs"), not a label ("Costs")
- Key message: the one point the audience should remember
- Content: 3 bullets at most, or the single chart or image that carries the point
- Visual suggestion: chart type, diagram or image, and what it shows
- Speaker notes: what I say, 60 to 120 words, in a natural spoken style

Order the slides as a story: situation, problem, insight, recommendation, next steps, adapted to the setting. Use only figures from my material and mark gaps as [DATA NEEDED].

If this Claude app has file creation enabled, also build the deck as a .pptx file with a clean, consistent layout.

<report>
[PASTE THE REPORT OR UPLOAD THE FILE]
</report>

Turn the report above into a slide deck structure for [AUDIENCE], about [NUMBER] slides. The purpose of the presentation: [E.G. GET THE BUDGET APPROVED, UPDATE THE TEAM].

A report covers everything; a deck carries one storyline. So:
1. Identify the 3 to 5 findings that matter most for this audience and purpose, and list them before building slides.
2. Write a one-slide executive summary that states the conclusion up front.
3. Build the slides. For each: an action title stating the takeaway, the supporting evidence from the report (figures quoted exactly, with the report section they come from), and a suggested visual (chart type and the data it plots).
4. Put detail that does not serve the storyline in an appendix list, so nothing is lost.
5. End with a slide on the decisions needed or next steps.

If the report's conclusions are unclear or contradict each other, flag that before the slides rather than picking one.

If file creation is enabled in this app, offer to produce the deck as a .pptx.

<document>
[PASTE THE DOCUMENT OR UPLOAD THE FILE]
</document>

Write an executive summary of the document above for [AUDIENCE, E.G. THE LEADERSHIP TEAM]. They will spend about two minutes on it and need to [DECISION OR ACTION REQUIRED].

Structure:
1. Bottom line, 2 to 3 sentences: the conclusion and what is needed from them, stated first.
2. Why it matters: the impact in concrete terms (money, time, risk, customers), using figures from the document.
3. Key findings: 3 to 5 bullets, each a complete takeaway.
4. Options or recommendation, if the document contains them, with the cost and risk of each.
5. Risks and unknowns that could change the picture.
6. Decision or next step: who needs to do what, by when.

Keep it under 400 words, in plain language the audience would use themselves. Take every number from the document and add its section reference in brackets. Leave out background they already know. If the document does not support a clear recommendation, say so rather than inventing one.

<transcript>
[PASTE MEETING NOTES OR TRANSCRIPT]
</transcript>

Turn the meeting notes above into a clear record. Meeting: [NAME AND DATE]. Attendees: [NAMES AND ROLES, IF NOT IN THE NOTES].

Output:
1. Summary: 3 sentences on what the meeting covered and where it landed.
2. Decisions: each as one clear sentence, with who made or agreed it.
3. Action items: a table with Action | Owner | Deadline | Notes. Start each action with a verb, and make it specific enough that the owner knows what done looks like.
4. Open questions: issues raised but not resolved, and who should resolve each.
5. Follow-up message: a short email or chat message to attendees with the decisions and actions, ready to send.

Include only what the notes support. Where an owner or deadline was not stated, write "unassigned" or "not set" and list those items at the end for me to fill in. Where people seemed to disagree, record it as an open question rather than a decision.

If file creation is enabled in this app, also give me the action items as an .xlsx tracker.

Turn my bullet points into a professional [REPORT / PROPOSAL].

Audience: [WHO WILL READ IT AND WHAT THEY CARE ABOUT]
Purpose: [E.G. WIN THE CONTRACT, GET BUDGET APPROVED, REPORT QUARTERLY RESULTS]
Length: [PAGES OR WORDS]
Tone: [E.G. FORMAL, CONFIDENT, PLAIN]
Required sections or template: [PASTE, OR "SUGGEST ONE"]

<bullets>
[PASTE YOUR BULLET POINTS, DATA AND NOTES]
</bullets>

1. Choose a section structure that suits the purpose (for a proposal, for example: summary, the client's problem, approach, deliverables and timeline, pricing, why us, next steps) and show it as a short list at the top.
2. Write the document in full prose, with headings, short paragraphs, and tables where they make numbers or comparisons easier to scan.
3. Open with an executive summary that states the main conclusion or offer.
4. Use only facts and figures from my bullets. Wherever the document needs something I have not given (a date, price, name or piece of evidence), insert [TO CONFIRM: what is needed].
5. After the document, list every [TO CONFIRM] item and the weak spots a skeptical reader would question.

If file creation is enabled in this app, also deliver it as a formatted .docx file.