How to Turn Messy Meeting Notes Into an Exec Summary With AI

The exact four-minute process I use to turn two pages of notes into something a sponsor will actually read.

The meeting ran 55 minutes. You took two pages of notes. And the one person who needed them — your sponsor — read none of it.

That’s not a notes problem. It’s a “nobody reads two pages” problem, and writing faster won’t fix it. What fixes it is handing the cleanup to AI and keeping the judgment for yourself. Below is the exact process I use to turn a wall of raw meeting notes into a clean executive summary in about four minutes, plus the prompt I actually use, so you can steal it.

Why the usual fixes don’t work

Most people try to write neater notes or summarize faster. Both miss the point. Your sponsor doesn’t want your meeting. They want the verdict: what got decided, who owns what, what’s at risk, and what they need to do about it. Bury that under a play-by-play and they’ll either skim past the one thing that mattered or quietly resent the time it cost them. Lead with the verdict and everything else gets easier.

Step 1: Dump the raw notes in

Paste your notes exactly as they are. Typos, half-sentences, “john said maybe we push the date??”, all of it. Don’t tidy up first. Cleaning the mess is the AI’s job now, and tidying by hand is the slow step you’re trying to delete.

Step 2: Ask for decisions first

Tell it to lead with outcomes and owners, not the discussion. What was decided goes at the top. Who said what goes at the bottom, if it goes in at all. This one instruction is the difference between a transcript and a summary.

Step 3: Force the structure

Give it the exact shape you want back: decisions, owners and due dates, risks, open questions. Then cap it. “Under 150 words” keeps it skimmable and stops the AI from padding to look thorough. A summary that runs long is just the meeting again, in a smaller font.

Step 4: Read it the way your sponsor will

Skim the output in about 30 seconds, exactly the way the person receiving it will. Fix the one thing that’s off, then send. And add a line that makes the AI flag anything you committed to without realizing, because the quiet promises you make in a meeting are the ones that come back to find you.

The exact prompt

Here’s the one I use, every time. Swap the bracketed parts for your details.

You are my project coordinator. Summarize the notes below for [STAKEHOLDER].
Structure as: 1) Decisions, 2) Owners + due dates, 3) Risks, 4) Open questions.
Under 150 words. Plain English, no filler. Also flag anything I committed to
without realizing. Notes: [PASTE]

Why each line earns its place:

• “for [STAKEHOLDER]” — the same meeting reads differently to a sponsor than to your team. Name the reader and the AI pitches it at the right altitude.
• “Decisions first” — front-loads the verdict, which is the only part a busy reader is guaranteed to see.
• “Under 150 words” — forces ruthlessness. Length is where summaries go to die.
• “Flag anything I committed to without realizing” — catches the offhand “sure, I’ll take that” you’d otherwise forget by the time you’re back at your desk.

Before and after

Here’s what it looks like in practice. The “before” is a real-feeling pile of war-room notes: ten people talking over each other, topics bouncing around.

And the “after,” run through the prompt above:

Four minutes, no rewriting. And the thing you’d have quietly forgotten — that 2pm review — is sitting right there at the bottom where you can’t miss it.

What to watch

A few honest guardrails so this helps instead of hurts:

• Check any number it gives you. AI will state a confident figure it made up. Never pass on a number you haven’t verified yourself.
• Keep your voice on the parts that matter. The summary can be AI-clean, but the judgment call and the framing should still sound like you.
• Strip the sensitive stuff. Swap real names and figures for placeholders before pasting if privacy matters.

The better version: shorten the meeting, don’t just clean it up

The fastest meeting summary is the one you never had to write, because the meeting was 20 minutes and ended on time. There’s a prompt for that too: a pre-read that does half the meeting before it starts. I send one workflow like that every week in The Status Update, my newsletter for project managers. One workflow, one tip, one job done faster.

AI can summarize the meeting in four minutes. It still can’t explain why the meeting happened.