The Plainline chat after a report is attached: Plainline asks who will watch the presentation and offers answers. Next to it, the audience menu with Colleagues, Clients and Management, and the presentation type: For presenting or For reading

Workflow

How to Turn a Long Report Into a Presentation: Give AI Six Answers About Your Meeting

Nick SkorobogatkoDesigner, Plainline

You have a forty-page report and a meeting on Thursday. At that meeting, your manager expects the whole story in fifteen minutes.

The main thing first: to turn a report into a presentation, you don’t cut it down by hand. You give it to AI. It reads the forty pages and builds the slides in a few minutes.

But the report alone is not enough for AI. If you give it only the report, it retells the report section by section.

My name is Nick, and I make Plainline. It is a tool that builds presentations from text you already have. While I build it, I give AI reports, notes, and emails every day and look at what it puts together. And every day I see the same thing: the less I tell AI about the task, the more its presentation looks like any other.

This article has six questions about your meeting. If you give AI your answers together with the report, it builds a presentation for your meeting specifically. There is also a prompt builder in the middle of the article: you pick your answers, and it assembles a ready prompt for AI from them.

AI retells a report section by section when it doesn’t know who the presentation is for

AI doesn’t know who will be in the room. It doesn’t know how many minutes you have, what these people have already heard, or what you want from them.

So it takes one slide from each section: introduction, method, results, conclusions. That presentation looks tidy. But it repeats the table of contents and doesn’t answer your audience’s questions.

AI isn’t making a mistake here. A colleague would do the same if you silently put the report on their desk and asked for a presentation. But a colleague would ask you some questions first. Here are six of those questions.

Four slides in a two-by-two grid titled Introduction, Method, Results and Conclusions, each with three generic bullet points

Without your answers, AI repeats the report’s table of contents.

Answer six questions before you give the report to AI

1. Explain what company and project your report is about

Authors write reports for their own colleagues. That’s why reports say “Project North,” “the second wave,” and “KR3.” You know what these mean. AI doesn’t, and it starts to guess.

Add three lines to the report. In the first, say what the company does. In the second, name the project and its stage. In the third, spell out the abbreviations the report doesn’t explain.

If the author wrote the report for people outside the company and already explained the project in it, skip this question.

2. Say how well you know the report’s subject

This decides how much text goes on a slide.

If you wrote the report, a slide needs only the conclusion and one number. You’ll say the rest yourself, and extra text will only pull people’s attention away from you.

If you got the report from a colleague, ask for a complete thought on every slide. Otherwise, on slide three you’ll be staring at a number and trying to remember what it means.

3. Say whether you’ll present the slides yourself or people will read them without you

Authors forget about this question. And all the text on the slides depends on the answer.

When you present yourself, the slide carries the conclusion and one number, and you explain out loud. When you send the presentation as a file, you aren’t there. So every slide explains itself.

Check a presentation like that this way: read only the slide titles, in order. A reader should understand your conclusion from them.

Two slides with the same conclusion under the Plainline switch For presenting and For reading. For presenting: a short title and one large number, $40,000 a month. For reading: a title that states the conclusion and three short explanations

One conclusion, two slides: one for presenting, one for reading.

4. Name who will listen: senior leadership or your direct manager

“My manager” is not enough of an answer for AI. Your direct manager and a senior leader expect two different presentations from the same business report.

Your direct manager needs the details: what happened, why, who is fixing it, and when they’ll finish. They’ll start working with those details tomorrow.

Senior leaders don’t need those details. They want to know how much money and time the problem costs and what it breaks next. And they want to know what decision you expect from them.

Here is the same fact from a report in two slide titles. The example is made up.

For Slide title
Your direct manager Manual account setup adds three days to each customer’s onboarding
Senior leadership Slow customer onboarding costs us $40,000 a month in support

There are three more kinds of audience. A team wants to know what changes in its work and who takes the next step. A client wants to see their own result, without your internal names. For people outside the subject, first say on one slide what the project is, and explain every term.

Two slides from the table. For the direct manager: the title and a list of three details. For senior leadership: the title and one large number, $40,000 a month

The same fact for your direct manager and for senior leadership.

5. Write what the audience should decide after your presentation

There are three options: people make a decision, people get the news, or people give you their opinion.

If you expect a decision, write it out in words: “Decide whether we delay the launch in the fourth region by two weeks.” Then AI leads the presentation toward that decision. And on the last slide it shows the options and what you recommend.

If you don’t write this, AI ends the presentation with a “Thank you” slide.

6. Name the meeting length and the number of slides: two minutes per slide

Without that number, AI decides for itself how many slides to make. And you get more slides than you have time to present.

I count slides by two rules. I leave a quarter of the meeting for questions, and I allow two minutes per slide. Presenters came up with these rules; researchers haven’t tested them. But they are enough for a first estimate.

Meeting You speak Questions Slides
5 minutes 4 minutes 1 minute 2–3
10 minutes 7–8 minutes 2–3 minutes 4
15 minutes 11 minutes 4 minutes 5–6
30 minutes 22 minutes 8 minutes 10–11
45 minutes 34 minutes 11 minutes 15–17

Fifteen minutes means five or six slides. That number is a surprise: forty pages won’t fit into six slides. They don’t have to fit. You attach the full report to your email, and the audience finds the details there.

Build your prompt from your six answers

Pick your answer to each of the six questions. When you change an answer, the prompt text changes too. Then fill in the fields in brackets and copy it. You give this prompt to AI together with the report.

Context
Your knowledge
Delivery
Audience
Goal

Your prompt

Fill in the fields in brackets, then copy.

Build a presentation from this report. Context: the company is [what it does]. The project is [what it is and its stage]. Abbreviations in the report: [abbreviation — meaning]. I know the subject and speak without notes. Leave the conclusion and one piece of evidence on each slide. I’m presenting out loud. A slide supports what I say; it doesn’t replace it. The audience is senior leadership. Show how much money and time the problem costs and what it breaks next. Remove process details. Put the main conclusion on the first slide. After the meeting, people need to decide: [decision]. End the presentation with the options and my recommendation. I have 15 minutes. Make no more than 6 slides.

Here is a prompt for one such meeting. I wrote the report myself, and I’m presenting it to senior leadership. I expect a decision from them. We have fifteen minutes for the meeting.

Build a presentation from this report. Context: the company is an online booking service for clinics. The project is a launch in new regions; three regions are already live. I know the subject and speak without notes. Leave the conclusion and one piece of evidence on each slide. I’m presenting out loud. A slide supports what I say; it doesn’t replace it. The audience is senior leadership. Show how much money and time the problem costs and what it breaks next. Remove process details. Put the main conclusion on the first slide. After the meeting, people need to decide whether we delay the launch in the fourth region by two weeks. End the presentation with the options and my recommendation. I have 15 minutes. Make no more than 6 slides.

One report gives two different presentations when you change the prompt

To show the difference, I took one report and gave it to AI twice. It is a 42-page quarterly report about launching a service in three regions. I didn’t touch the report; I changed only the prompt.

The first time, I present the report to senior leadership in fifteen minutes and expect a decision from them. The second time, I send the presentation as a file to my team, and people read it without me.

For senior leadership, presented by me For my team, read without me
1. The launch is on plan, but support costs more than planned 1. Quarter summary: onboarding is on plan, support load is above plan
2. Customers go live on time in all three regions 2. We lose time in two places: implementation questions and manual account setup
3. Two causes account for three quarters of the overspend 3. The heaviest load falls in the first weeks after launch
4. Without changes, the fourth region will repeat the overspend 4. What we change in customer onboarding before the next launch
5. Decide: a two-week delay or higher costs 5. What we change in account setup
6. Who owns what, and by when
7. What happens to the fourth region’s schedule

The first presentation is short: five slides lead to one decision. The second has seven slides, and three of them say what the team changes in its work. Neither repeats the report’s table of contents.

For senior leadership, presented by me, 5 slides. Two of them: the launch is on plan, but support costs more than planned, with the number 3 of 3 regions; and Decide: a two-week delay or higher costs, with two options and a recommendation

For senior leadership: five slides that lead to one decision.

For my team, read without me, 7 slides. Two of them: the quarter summary and what we change in customer onboarding, each with three points in full sentences

For the team: seven slides, three of them about what the team changes.

Check the finished presentation in five minutes: numbers, titles, caveats, sources

Don’t check every line of the presentation. Check four places where AI can get things wrong.

  1. Numbers. Compare every number on the slides with the report. Look at the unit AI uses and the period it covers: it can write “per year” where the report says “per quarter.” After one such error, the audience stops trusting the other numbers.
  2. Titles. Read only the titles, in order. They should add up to one connected thought.
  3. Caveats. The report said “based on preliminary data” or “for two regions only.” Check that the conclusion on the slide doesn’t sound more certain than the report.
  4. Source. For every claim, you should be able to point to the place in the report. If there is no such place, AI added it on its own.

Plainline will ask these six questions itself and check the numbers against your report

I haven’t launched Plainline yet; I’m finishing it. But I can already tell you how it works as a report to presentation AI tool.

Plainline asks these questions itself. You attach your materials, it asks about what is missing from them, and it offers answer options. So you don’t write the prompt.

Plainline adds its own writing rules to your answers. I wrote these rules myself, because I think the text is the main thing on a slide. Under them, the title states the conclusion, and a sentence has no more than fifteen words.

Plainline checks the numbers against the report and flags the ones that aren’t in it. Next to each piece of text on a slide, it shows the fragment of the report that text came from. That way it does two of the four checks for you: numbers and sources.

Plainline doesn’t suit every report. If your report has more tables than text, it will do a poor job. I’m making it for reports where the author explains the conclusions in words.

Leave your email, and I’ll write when Plainline can take your report

If you want to be among the first to try Plainline, leave your email. I’ll write to you when it can take your report.

Frequently asked questions

Can AI turn a report into a presentation on its own?

Yes. AI reads the report, picks out the conclusions, and builds the slides. You do two things: tell AI about the meeting and check the numbers against the report.

Do I need to summarize the report for the presentation before I give it to AI?

No. Give AI the whole report. If you shorten it yourself, AI won’t see the numbers and conditions you cut. Let AI do the shortening: tell it who will listen and how many minutes you have.

How many slides does a forty-page report need?

That depends on the length of the meeting, not the length of the report. Five or six slides are enough for fifteen minutes, and ten or eleven for half an hour.

What should I write to AI in the prompt, besides the report itself?

Write six answers. Say what the company does and what the project is. Say how well you know the subject and whether you’ll present yourself. Name the audience, the decision you expect from them, and the length of the meeting. The prompt builder above assembles the prompt text from those answers.

Sources

  1. How many slides do I need for my presentation? — Plus AI
  2. Developing Executive Style Presentations — Bay Path University

Join now

Subscribe to Plainline’s newsletter

Hi, there

Join the waitlist

    By continuing, I agree to the privacy policy.