Turn a report into a short presentation
The report is finished, and now somebody wants “a few slides for Thursday”. Same document, different room — and the headline that works for the board isn't the one for the team.

What you'll make
a reviewed outline, then a short PowerPoint (or a complete slide script) built around the decision your audience needs to make.
What you'll need
Claude in your work account with Code execution and file creation turned on for the PowerPoint route, a report you’re allowed to use, and the audience, speaking time and decision. Allow about twenty minutes. The outline step also works in ChatGPT, Gemini or Copilot.
Example result.
Slide 1 — Decision: approve a two-week follow-up pilot and name an evaluation owner?
Slide 2 — More customers completed onboarding, but the completion rate fell. (Report R1)
July 180 of 240 (75%); August 216 of 300 (72%).
Slide 3 — 28 of 40 survey respondents found the checklist helpful. Not all customers; no cause shown. (R3)
Slide 4 — Pilot needs 12 staff hours. No budget or launch approval yet. (R4)
1. Upload the report and name the audience
Start a new chat and attach the report: select + in the lower left of the chat box, then Add files or photos. To practise, use the fictional onboarding report.
Say who will see the presentation, how long you have and what they need to decide. “An eight-minute decision slot with the operations director” does more than “make it professional”. If the report has important charts, paste their underlying numbers too, rather than trusting that a chart inside a Word file was read accurately.
Why this works: the decision decides what belongs in the story, and the time limit keeps the number of slides realistic.
What you should see: the report attached and a one-line brief: audience, minutes, decision.
2. Ask for an outline first
Turn [report title] into an outline for [audience]. Speaking time: [minutes]. Decision or takeaway: [decision].
Use only the attached report. Give each slide one clear headline and a few supporting points. Suggest a chart only where it helps. Point to the report passage behind each important number. Keep proposals, uncertainties and sample limits visible. Don't invent approvals or claim cause and effect without evidence. Wait for my review before making slides.
[report title] is the document’s name; [audience], [minutes] and [decision] come from your brief.
Why this works: reviewing the outline catches a weak argument before anyone spends time arranging rectangles.
What you should see: a headline per slide that, read in order, tells the story without the bullets.
Need it for three audiences? Run the prompt again with a different audience, time and takeaway each time. The same evidence lands differently:
| Audience | Headline | Final ask |
|---|---|---|
| Board, 3 minutes | Completions rose 20%; the rate fell from 75% to 72% | Approve a two-week pilot with a named evaluation owner? |
| Team briefing, 10 minutes | More people finished, but a bigger share stalled | Which steps lose people, and what will the pilot test? |
| Customers | We’ve added a checklist to make setup easier | Tell us if it helps |
For a customer version, include only what’s cleared for customers and check it before sharing.
3. Turn the reviewed outline into slides
Correct anything misleading in the outline, then ask:
Create a downloadable PowerPoint from the reviewed outline, for the audience, time and decision in my brief. Use large readable type, simple layouts and a source beside each important number. Keep essential caveats on the slide, not only in speaker notes, and end on the decision. Don't invent approvals. If you can't create a file, return complete slide text, speaker notes and chart instructions, and say no file was made.
Claude creates .pptx files when Code execution and file creation is on: Settings › Capabilities on Free, Pro and Max. On Team and Enterprise it’s on by default, but an owner can turn it off in organisation settings.
Why this works: the fallback keeps the task moving if file creation isn’t available, and “say no file was made” stops a script being presented as a deck.
What you should see: a .pptx to download, or a full slide script with notes.
4. Open the deck and check three things
- Numbers. Recompute the important figures from the report. Check units, periods and denominators. Count bars start at zero.
- Meaning. Counts stay separate from rates, facts from interpretations, and respondents from the wider population. A proposed decision isn’t an approval.
- Presentation. Open every slide in the app you’ll present from. Check labels, notes, type size and clipping; a clean chat preview isn’t a clean export.
Why this works: these are the three places a tidy deck most often drifts from the report.
What you should see: a deck where every number matches the report and every caveat is still on its slide.
Check the result
- Every number on a slide matches the report, with its denominator and period.
- No headline turns a count into a rate, or respondents into “customers”.
- Proposals are labelled as proposals; nothing says “approved” unless the report does.
- The final slide asks for the decision.
The usual failure: a headline that’s true of one measure and implied for another. “Onboarding improved by 20%” is the count; the rate fell. Spot it by asking, for every percentage on a slide, “20% of what?”
Repair slide [number]. Problem: [what is wrong]. Correct source or calculation: [passage or calculation]. Keep all other checked figures and caveats. Return the revised file or slide script and say exactly what changed.
[number] is the slide; [what is wrong] and [passage or calculation] describe the fix. Reopen the revised file afterwards.
Worked example: count up, rate down
Fictional example. From the practice report:
R1. August: 300 customers started onboarding; 216 completed within 14 days. July: 240 started; 180 completed.
R2. A revised checklist went live on 1 August. August also had more new customers and two staff absences. No controlled comparison.
R3. Forty August customers answered an optional survey. Twenty-eight described the checklist as helpful.
R4. The team proposes a two-week follow-up pilot. Operations can spare 12 staff hours. No budget or launch approval.
R5. Decision required: approve the follow-up pilot and name an evaluation owner.
The first outline’s slide 2 read: “Onboarding improved by 20%, and customers love the new checklist.”
| Month | Completed of started | Rate |
|---|---|---|
| July | 180 of 240 | 75% |
| August | 216 of 300 | 72% |
- The failure. Completions rose 20% (180 to 216), but starts rose 25%, so the completion rate fell 3 percentage points. “Customers love” is 28 of 40 optional respondents (70% of respondents, not of customers). And nothing in R2 shows the checklist caused anything.
- The repair. The repair prompt, with R1 and R3 as the source, gave the slide 2 and slide 3 headlines in the example result.
- The ask. The final slide asks for a decision on the pilot. It doesn’t announce one, because R4 says nothing is approved.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Check the claims before building the story
For an important decision, ask for a checking table before any outline.
Using only the attached report, list every claim a presentation might make. For each, give the report section, any calculation (with denominator and comparison period) and the qualification it needs. Separate reported facts, calculated facts, interpretations and open questions. Flag anything that overstates a sample or implies cause and effect. Don't build slides yet.
Correct the table, then use it as the source for step 2. It’s the quickest way to catch “70% of customers” before it reaches a slide.
Optional training: Make the draft in Copilot in PowerPoint
In PowerPoint, select Copilot at the bottom right of the slide, then Add Content in the chat box and choose Agent Mode. Describe the presentation, answer Copilot’s clarifying questions, refine the outline in chat, then ask it to generate slides. Microsoft’s guide says file references aren’t yet supported in Agent Mode, so paste a checked extract rather than assuming it read the whole report.
Create an outline for [audience, speaking time and decision] using only this checked extract: [extract and source name]. Keep denominators, comparison periods and caveats. Separate requested decisions from approvals. Wait before generating slides.
Reject an outline headline that hides the falling rate, then generate from the corrected version.
Optional training: Reuse the storyline next month
For a recurring report, update the claims before you reuse the slides. Check whether denominators, observation windows or definitions changed: a 14-day completion window this month and a 30-day one next month aren’t comparable. Re-run the outline prompt on the new report rather than editing last month’s numbers into last month’s headlines, and compare the effort with your usual process before claiming a time saving.