How to turn a report into a presentation without a 40-slide deck

Read the report's executive summary and final recommendation. Then write one sentence in your own words:

The room needs to approve the phased rollout on November 14, with the support hire delayed until January.

If the report does not contain a decision, write a sentence about what the audience should understand. “The migration is on schedule” is weaker than “The migration is on schedule only if the content freeze holds on Friday.” A claim gives the deck a spine.

A short work deck usually needs:

1. The decision or conclusion.
2. Why it matters now.
3. The evidence that changes the decision.
4. The strongest alternative and why it was rejected.
5. Risks or dependencies.
6. The next step and owner.

Everything else belongs in notes, an appendix or the read-ahead. If the meeting is a status update rather than a decision, the slide count can be even smaller: what changed, what is at risk, what happens next.

Reports often walk through every workstream because the record needs to be complete. A deck should not. Ask of each paragraph: “If I remove this, does the audience make a worse decision?” If the answer is no, move it to the notes.

Keep the numbers that explain the conclusion, the customer evidence that prevents a predictable objection and the constraint that makes the recommendation possible. Remove the methodology tour unless the audience is going to challenge the method.

The notes are not a transcript. They are the place for:

• the number you may need if challenged;
• the transition from one slide to the next;
• the likely objection;
• the reason an apparently attractive option is not recommended.

This is how a short deck can still be well prepared. The room sees the argument; the presenter keeps the evidence.

Paste the report's summary, recommendation and key evidence into the slide maker, or upload the file. A five-slide free deck is enough to test whether the source contains an argument or only a sequence of activities. If the result reads like a table of contents, the source needs a clearer decision sentence before you pay for a longer deck.

The tool is text-first. If the report's argument lives in a chart you cannot describe in words, add a sentence that states what the chart shows. Do not assume the model can read the image.

Read only the slide titles. They should answer:

• What is the conclusion?
• What changed?
• What is the risk?
• What is the recommendation?
• What happens next?

If the titles are labels — “Background,” “Results,” “Discussion” — the deck is still a report. Rewrite those sections in the source as claims and generate again.

Then check every number that could embarrass you in the room. A fast deck is useful only if you are willing to defend its content. If a number is illustrative, say so. If the report is uncertain, keep the uncertainty visible.

When the meeting ends, send the browser link rather than attaching the original report. The link is the current deck; the report remains the detailed record. If the channel needs an image instead, send the 1200×630 preview card and let the QR code carry the link.

That keeps the distribution simple: one link for presenting, one image for chat, no file to download and no second copy to reconcile.

If the deck depends on complex charts, product screenshots, photographs or a branded layout, this is the wrong tool. The same applies if the deliverable has to be an editable .pptx or a PDF. Use a design or office suite for that job.

For the text-heavy report, the short deck is usually the better meeting artifact. The report can stay long because nobody has to read it aloud.

Take the report you were going to present and copy its summary plus the recommendation into the slide maker. Generate five slides, then test the titles. For the urgent version of this workflow, read the 10-minute last-minute presentation plan. For a recurring team update, see project update to presentation. The PDF to slides guide covers what happens when the report is a PDF.