RobotsHelp

ChatGPT: Turn Meeting Notes Into a Report People Can Act On

Written by

in

The meeting ended an hour ago. Your manager wasn’t there, and she wants “a short write-up” before tomorrow’s leadership call. All you have is a page of half sentences, three arrows and a number with a question mark next to it. The fast way: paste those notes into ChatGPT, tell it who the report is for and what they need to decide, give it the sections you want, and make it mark every gap instead of filling it. You turn meeting notes into a report in about ten minutes, and the checking takes longer than the writing.

Imagine it’s 5:40 pm. You paste your notes, paste one prompt, and a minute later there’s a one-page report on your screen: the bottom line in two sentences, the three decisions, the open risk, and what you need from your manager. Two lines say [CHECK], because your notes never said who owns the budget. You fix those two lines, send it, and close the laptop.

Want more practical AI workflows like this one, free? Join Launchpad.

No password needed, your reset opens instantly.

No password. Just your email, and you’re in.

Short answer

Give ChatGPT four things with your notes: who will read the report, what they need to do with it (approve, decide, stay informed), the sections you want in order, and one hard rule: use only what’s in the notes and write [CHECK] where something is missing or unclear. Ask for the bottom line first. Then read every name, number, date and decision against your notes before you send it.

That’s it. The rest of this page is how to make each of those four parts good, which report shape fits which reader, and how to catch the mistakes ChatGPT makes most often with meeting notes.

A summary and a report are different jobs

A meeting summary is for the people who were in the room. They already know the background. They want the decisions, who owns what, and the deadline, in as few lines as possible. If that’s what you need, our guide on how to use ChatGPT to summarize meeting notes covers it, including action items and the follow-up email.

A report is for someone who wasn’t there. Your manager, a client’s director, a board, the colleague who takes over the project next month. They need three things a summary skips:

  • Context. Why the meeting happened and what was on the table.
  • Reasons. Not just “we chose supplier B”, but why, and what you gave up.
  • The ask. What you need from the reader, by when.

That changes the prompt. If you ask ChatGPT for “a summary”, you get a summary. If you tell it who the reader is and what they have to do next, you get a report.

Before you paste: three quick checks

  1. Are you allowed to paste it? Meeting notes often hold client names, salaries, prices or people issues. Check your company’s rules on AI tools first, and take out anything you don’t need for the report. On a personal ChatGPT plan you can turn off “Improve the model for everyone” under Settings, Data controls, so new chats aren’t used for training. OpenAI says it doesn’t train on Business and Enterprise workspace content by default (OpenAI Help Center, data controls).
  2. Messy is fine, missing is not. ChatGPT copes well with fragments, abbreviations and arrows. It can’t know what you didn’t write down. If the decision was made in the last five minutes and you stopped typing, add one line about it now, while you still remember.
  3. Add three lines of context on top. The meeting’s purpose, who was there (roles, not only names), and who the report is for. Thirty seconds of typing, and it’s the biggest quality jump you’ll get.

How to use ChatGPT to turn meeting notes into a report (step by step)

  1. Open a new chat so old conversations don’t leak into this one.
  2. Paste your three context lines, then your notes underneath, exactly as they are.
  3. Paste the report prompt below and fill in the reader and the sections.
  4. Read the [CHECK] lines first. Answer them in the chat (“budget owner is Sam, deadline is 14 November”) and ask for the corrected version.
  5. Ask for the gap list: “List every sentence in the report that is not directly supported by my notes.” Delete or fix what comes back.
  6. Read it once as the reader. If your manager only reads the first two lines, does she know what happened and what you need? If not, ask ChatGPT to rewrite the bottom line.
  7. Paste it where it goes: an email, a Word or Google Doc, or your team’s project page.

The report prompt (copy and adapt)

You are helping me turn my meeting notes into a short written report.

Reader: [e.g. my manager, who was not in the meeting]
What the reader needs to do with it: [e.g. approve the budget change by Friday]
Tone: plain, factual, no sales language.

Write the report with these sections, in this order:
1. Bottom line (2 sentences max: what happened and what I need from the reader)
2. Background (why the meeting happened, 2 to 3 sentences)
3. Decisions made, each with the reason given in the meeting
4. Open questions and risks
5. Next steps: what, who, by when
6. What I need from you

Rules:
, Use only information that is in my notes. Do not add facts, numbers, names or dates.
, If something is missing, unclear or contradictory, write [CHECK: what is missing] instead of guessing.
, Keep “decided” and “discussed” separate. Only list something as a decision if my notes say it was agreed.
, Do not attribute quotes or opinions to a person unless my notes do.
, Maximum one page.

My notes:
[paste here]

The two rules that do the most work are the [CHECK] rule and the “decided versus discussed” rule. Without them, a language model tends to smooth your notes into something that sounds complete. A report that sounds complete but turns a suggestion into a decision is worse than no report.

Pick the right report shape for the reader

Swap the six sections in the prompt for the shape that fits. Four common ones at work:

  • Internal report to your manager or leadership. Bottom line, decisions with reasons, risks, what you need. Keep it to one screen. This is the default prompt above.
  • Client meeting report. Attendees from both sides, what was agreed, open points, next steps per side, next meeting date. Leave out internal opinions and pricing thoughts you wouldn’t say to the client’s face. Ask ChatGPT: “Write this so it can be sent to the client as is.”
  • Formal minutes. Date, attendees, apologies, one heading per agenda item, the decision under each, actions with owners. Minutes record what was decided, not every word that was said, so tell ChatGPT to leave out the discussion unless it changed the outcome. If your organization has a fixed minutes template, paste the template into the chat and ask ChatGPT to fill it.
  • Handover report. For the colleague taking over: background, decisions so far, who the contacts are, what’s still open, where the files live. Add “assume the reader knows nothing about this project”.

If your report is really a weekly status update built from a tracker or spreadsheet, not from one meeting, our guide to automated status updates with Gemini fits that job better.

Put the bottom line first

Most people write a report in the order the meeting happened. The reader doesn’t care about the order. They want the outcome. The US military’s habit of “bottom line up front” (BLUF) is a simple fix: the first sentence says what was decided and what you need, everything after it is detail (Harvard Business Review, how to write email with military precision).

A bad first line: “On Tuesday the project team met to discuss several topics related to the Q1 launch.”

A good first line: “We agreed to move the Q1 launch two weeks to 3 March, and I need your OK on the extra €4,000 for the agency by Friday.”

If ChatGPT gives you the first kind, reply: “Rewrite the bottom line so the first sentence says the decision and my ask, with the date and amount from the notes.”

Check the report before you send it

ChatGPT is good at structure and wording. It’s not a witness to your meeting. Spend two minutes on these, in this order:

  1. Numbers and dates. Compare every one with your notes. A “3” in your notes that becomes “30” in the report is the mistake that costs you most.
  2. Names and owners. Is each action owned by the person your notes say? Did it give an owner to something nobody owned? That should be a [CHECK], not a name.
  3. Decided versus discussed. Read the decisions list and ask yourself: was each of these really agreed?
  4. Tone about people. Make sure the report doesn’t make someone sound like they blocked or failed something, unless that’s both true and needed.
  5. The gap list. Run the “not directly supported by my notes” question from step 5 above, even when it looks fine.

When you have a transcript instead of notes

If your meeting tool gives you a full transcript, the same prompt works, but add one line: “First remove small talk and repeated points, then write the report.” A transcript of an hour can be very long, so if ChatGPT drops the end, split it in two halves, ask for the decisions and open points of each half, and then ask for one report from both lists. Our meeting notes summary guide has a section on cleaning messy notes and long transcripts. If you only have the recording, start with our guide on how to transcribe audio with AI, then come back to this prompt.

One report from several meetings

Sometimes the report covers a series: three workshop sessions, or a month of client calls. A ChatGPT project helps here. OpenAI’s Help Center describes projects as a place that keeps related chats, files and instructions together, with project instructions that apply to every chat in it, and suggests them for recurring work like weekly reporting (OpenAI Help Center, projects in ChatGPT).

A simple setup:

  • Create a project for the client or initiative.
  • Put your report prompt and rules in the project instructions, so you don’t paste them every time.
  • Add each meeting’s notes as a file or paste them in a new chat inside the project after every meeting.
  • At the end, ask: “Using all meeting notes in this project, write one report with the sections from the instructions. Show which meeting each decision came from.”

The “which meeting” line matters. It lets you check a decision back to the right notes in seconds. The Help Center also lists file limits per plan (for example 5 files per project on Free and 25 on Plus), so on a long series, paste notes into chats instead of uploading every one as a file.

Common mistakes

  • Not saying who the reader is. You get a generic summary. One line about the reader fixes most of it.
  • Letting it fill the gaps. Without the [CHECK] rule, missing owners and dates get invented. Always keep the rule in.
  • Writing in meeting order. The decision and the ask go first. Background goes second.
  • Too long. If the reader needs to scroll on a laptop, cut it. Ask: “Shorten to one page without losing any decision or action.”
  • Sending it unchecked because it reads well. Smooth writing says nothing about whether the numbers are right. The two-minute check does.

If the raw notes came from Google Meet, you can let Gemini write them during the call and pull action items from the notes doc before you ask ChatGPT for a longer report. Our guide to Gemini for meeting notes covers that earlier step.

Related guides

Start with your last meeting

Take the notes from the last meeting you still owe someone a write-up for. Add the three context lines, paste the prompt, answer the [CHECK] lines, run the gap list. Next time, save the prompt where you can paste it in five seconds, and change only the reader and the sections.

Want a new practical AI workflow like this every week? Join Launchpad.

No password needed, your reset opens instantly.

No password. Just your email, and you’re in.

Want a ready-made template? Try our AI meeting minutes generator prompt for a clean list of decisions and action items.

Recording Teams calls first? Read how to use Otter AI for Microsoft Teams to get a transcript you can paste into this workflow.

🇳🇱 Deze pagina in het Nederlands