Your last meeting produced 47 minutes of audio, three people talking over each other, and one action item that nobody wrote down. You know this because you were there. Now it's two days later and someone is asking for the notes.

AI meeting notes prompts can fix this. Not perfectly, not magically, but fast enough to matter. This article gives you a reusable formula and 10 copy-paste prompts you can use today without buying any special software.

Why meeting notes are the perfect AI task

AI is good at one specific category of work: taking messy language and turning it into clean, structured language. That's it. It can't tell you if the decision was right, it can't know if the client was lying, and it definitely can't read the room when your VP went quiet for 10 seconds after hearing the budget number.

But taking a wall of rambling text and pulling out the decisions and action items? That's exactly the kind of pattern-matching it was built for.

The Microsoft Work Trend Index found that AI users increasingly report being able to produce work they couldn't a year ago. Meeting notes are the most obvious place to start, because the raw material (the transcript or your rough notes) already exists. You're not asking AI to invent anything. You're asking it to compress and reshape something you already have.

That's the right use of the tool.

The one formula behind every good meeting prompt

Before the 10 prompts, here's what makes any of them work. Rule #13 in Don't Replace Me puts it plainly: useful AI output starts with role, context, task, constraints, and desired format. Think of it as writing a brief for a smart intern who's fast, tireless, and occasionally wrong.

Every prompt in this article follows the same structure:

Role (who the AI is playing) + Context (what the meeting was) + Task (what you want done) + Constraints (what to avoid or include) + Format (how you want the output)

When a prompt gives you garbage output, it's almost always because one of those five pieces is missing. Usually context or constraints.

You don't need a $200/month AI meeting tool. You need ChatGPT or Claude and this formula. The full starter guide for using AI at work walks through the same logic for other work tasks if you want to go deeper.

Before you paste anything: a safety check

This is not a legal disclaimer you should skim. It matters.

A lot of meeting transcripts contain things you should not paste into a commercial AI tool: client names, revenue figures, unreleased product details, HR conversations, legal strategy, anything covered by an NDA.

Before you paste a transcript anywhere:

If your company uses Microsoft 365 Copilot or Google's Workspace AI, those tools process data within your company's environment, which is a different security posture than pasting into a public chatbot. Know which situation you're in.

This came from a book.

Don't Replace Me

200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.

Get the Book →

The 10 prompts

Use these as-is or adjust them. The square brackets are your fill-in spots.

Prompt 1: Clean up a raw transcript

What it's for: You have an auto-generated transcript full of speaker errors, filler words, and run-on sentences. You want it readable before you do anything else.

You are an editor cleaning up a meeting transcript for internal use. The meeting was [a weekly project standup / a client kickoff / a team planning session]. Remove filler words, fix obvious transcription errors, and break the text into clear speaker turns. Do not add information that isn't in the transcript. Do not summarize yet. Output clean, readable paragraphs by speaker. Here is the transcript: [paste transcript]

Prompt 2: Executive summary

What it's for: Your boss wasn't in the meeting and needs the three-sentence version.

You are a business analyst summarizing a meeting for a senior leader who was not present. The meeting was [describe topic and attendees]. Write a 3-sentence executive summary covering: what was decided, what is in progress, and what requires a decision or follow-up. Be specific and factual. Do not include anything that wasn't clearly stated in the notes. Here are the raw notes: [paste notes]

Prompt 3: Action items only

What it's for: You need a clean list of who does what by when.

You are an executive assistant extracting action items from meeting notes. For each action item, identify: the task, the person responsible (if named), and the deadline (if mentioned). If a deadline was not mentioned, write "deadline not set." Do not invent owners or dates. Format as a numbered list. Here are the notes: [paste notes]

Prompt 4: Decisions log

What it's for: Tracking what was actually decided, separate from what was just discussed.

You are a project manager documenting decisions from a meeting. Extract only the decisions that were clearly made during this meeting. A decision is something that was agreed upon, not something that was discussed or proposed. For each decision, write: what was decided, who made or approved it (if stated), and any noted conditions or caveats. If something was discussed but not decided, do not include it. Here are the notes: [paste notes]

Prompt 5: Risks and blockers

What it's for: Flagging what could go wrong before it does.

You are a risk analyst reviewing meeting notes. Identify any risks, blockers, dependencies, or concerns that were raised during this meeting. For each one, note: what the issue is, who raised it (if named), and whether any mitigation or next step was discussed. Format as a bulleted list. Do not include items that were mentioned only in passing without any concern being expressed. Here are the notes: [paste notes]

Prompt 6: Client recap email

What it's for: Sending a professional follow-up to a client after a call without spending 45 minutes drafting it.

You are a client-facing account manager writing a follow-up email after a call with [client type, e. g., "a marketing agency client"]. Use a professional but warm tone. The email should include: a brief thank-you, a summary of what was discussed, confirmed next steps with owners and deadlines, and any open questions or items we said we'd follow up on. Do not include internal commentary or anything marked as confidential. Subject line should be specific, not generic. Here are the call notes: [paste notes]

Prompt 7: Standup summary

What it's for: Turning daily standup notes into a two-minute async read for the team.

You are a team lead writing a brief standup summary for a development/marketing/ops team [pick one]. The standup covered [number] people. For each person or workstream, summarize: what they completed yesterday, what they're working on today, and any blockers they mentioned. Keep each entry to 1-2 sentences. Do not pad. Here are the standup notes: [paste notes]

Prompt 8: Project status update

What it's for: Taking messy internal notes and turning them into a structured update for stakeholders.

You are a project coordinator writing a weekly status update for a [type of project] project. The audience is [internal team / executive leadership / a client]. Write the update in the following sections: Overall Status (one sentence with a RAG rating: Red / Amber / Green), Progress This Week, Planned Next Week, Key Decisions Made, and Issues or Risks. Use bullet points within each section. Base this only on what's in the notes. Here are the notes: [paste notes]

Prompt 9: Follow-up questions to send

What it's for: Identifying what was left unclear that you need to go back and ask.

You are a project manager reviewing meeting notes for gaps. Identify questions that were left unanswered, topics that were discussed but not resolved, and anything that seems to be missing context or a decision. Write these as clear, specific questions ready to send in a follow-up email. Do not include questions that were already answered in the notes. Here are the notes: [paste notes]

Prompt 10: Turn notes into a task list

What it's for: Getting everything into your task manager without retyping it all by hand.

You are a productivity assistant converting meeting notes into a task list. Extract every action, task, or commitment mentioned. For each task write: the task description, the assignee (if named, or "unassigned" if not), the due date (if mentioned, or "TBD" if not), and the priority if it was mentioned. Format as a table with four columns: Task, Owner, Due Date, Priority. Here are the notes: [paste notes]

These same patterns work across many kinds of work documents, not just meetings. The 12 AI prompt templates for general work tasks covers the same structure applied to emails, reports, and decisions.

Quality checks you cannot skip

This section is short because it should be obvious, but people skip it anyway.

Read the output before you send it. Every time. AI will occasionally invent an action item, misattribute something to the wrong person, or confidently state a decision that was actually still being debated. It does this with complete calm and zero indication that it's guessing.

Verify every owner, date, and decision. Cross-check against your own memory or the recording. If you can't verify it, flag it as "to confirm" rather than asserting it happened.

Do not pretend a decision was made if it wasn't. If the prompt produces a decision that wasn't in your notes, delete it. "We should probably think about switching vendors" is not a decision.

Check the tone on client-facing outputs. The client recap email prompt is useful, but AI defaults to a particular flavor of professional warmth that might not match your relationship with that specific client. Adjust it.

The ChatGPT at work prompt guide has more on how to iterate when you get a bad first output.

What this won't fix

AI meeting notes prompts won't fix a meeting that shouldn't have happened. They won't help if nobody was taking notes at all, if the recording cut out halfway through, or if the "decision" was really just whoever spoke last.

They also won't save you from the political dimension of meetings. If the real outcome of that call was that your VP is quietly furious about the budget and nobody said anything directly, no prompt on earth is going to surface that. Understanding what AI can and can't do matters here: the tool compresses language, it doesn't read subtext.

What these prompts will do is compress the busywork. If you're spending 30 minutes after every call writing up notes, that's a reasonable task to get to 10 minutes. Use the saved time to actually think about what happened in the meeting, which is the part that requires a human.

Frequently asked questions

What's the best AI tool for meeting notes?

You don't need a dedicated tool. ChatGPT (GPT-4) or Claude work fine with the prompts in this article. Dedicated tools like Otter.ai, Fireflies, or Microsoft Copilot in Teams add transcription and real-time features, which is genuinely useful, but the prompting logic is the same. Start with what you already have before adding another subscription.

Is it safe to paste meeting transcripts into ChatGPT?

It depends on what's in the transcript and what your employer's AI policy says. Remove customer names, financial figures, and anything covered by confidentiality obligations before you paste. If you're on a paid ChatGPT or Claude plan, your data handling is different from the free tier. When in doubt, check with your IT or legal team.

How do I get better output when the prompt doesn't work?

Add more context. The most common reason a prompt fails is that the AI doesn't know what kind of meeting it was, who the audience is, or what you actually need. Reread the formula: role, context, task, constraints, format. Something is usually missing. See the no-BS guide to using AI at work for more on this.

Should I tell my manager I'm using AI to write meeting notes?

Probably, yes, and sooner is better than later. The AI disclosure question at work has a full breakdown, but the short version is: if your company has no policy against it and you're not compromising confidentiality, transparency protects you more than secrecy does.

Can AI make up things that weren't in the meeting?

Yes. It's called hallucination, and it happens. The model will sometimes invent an owner for an action item or state a decision with more certainty than the conversation warranted. This is why the verification step is not optional. Read the output against your notes or the recording before you send anything.

Do I need a meeting recording or can I use rough notes?

Both work. A clean transcript gives you more to work with and more accurate attribution. But rough notes, even messy ones, are usually enough for the summary, action items, and email prompts. The cleaner your input, the better your output. That's what Rule #13 in the book means by "garbage in, garbage out."