AI meeting notes that turn into action items

Most meetings end with a fuzzy sense that things were decided and a vague memory of who was going to do what. Two weeks later, half of it hasn’t happened. An AI assistant is very good at the mechanical part of fixing this: reading a transcript or messy notes and producing a clear list of decisions, tasks, owners and dates.

It is not good at knowing what was meant when the discussion was ambiguous. That part stays with you. This guide, current as of September 2026, walks through getting the raw material, using prompts that produce usable action items, and checking the result.

Step 1: Get something for the AI to read

You need text. There are three common sources, in rough order of quality.

A transcript from your meeting platform. Some meeting tools can record and transcribe, and some include their own AI summary. For example, Microsoft’s documentation lists Teams meeting summaries and transcription, including capturing action items, as part of Microsoft Copilot in Microsoft 365. Whether this is available depends on your Microsoft license and on your administrator’s settings, so ask your IT team if you don’t see it. Other platforms have similar features under their own names.

Your own notes. Even messy typed bullets work. You know the context and can add it.

A voice memo you record afterwards. If nothing else exists, spend two minutes talking through what you remember, then have it transcribed by whatever tool your company approves.

Before recording or transcribing any meeting, make sure everyone knows and that recording is allowed. Rules differ by state, country and company, and external participants may object. When in doubt, ask.

Also decide whether the content may go into the AI tool you plan to use. Board discussions, personnel matters, client confidential details and legal strategy often shouldn’t. See our company AI policy template.

Step 2: Clean the input in one minute

A transcript without speaker names produces action items without owners. Spend a minute:

• Make sure names appear next to their comments. If the transcript says “Speaker 2,” add a line at the top: “Speaker 1 is Dana (operations), Speaker 2 is Marcus (finance).”
• Add the meeting title, date and purpose.
• Note anything decided before the meeting that isn’t in the transcript.
• Remove parts that shouldn’t be shared, such as an unrelated personal aside.

Step 3: Use a prompt that asks for a specific structure

The difference between a useful summary and a wall of text is the structure you request. Copy this:

You are helping me write up a meeting. Below are the meeting details and the transcript.

Meeting: [title], [date]
Attendees: [names and roles]
Purpose: [one sentence]

Transcript:
[paste]

Produce:
1. Summary: three sentences maximum.
2. Decisions made: a bullet list. Only include something if it was clearly agreed, and quote the words that show it.
3. Action items: a table with columns Task, Owner, Due date, and Evidence (a short quote from the transcript). If the owner or date was not stated, write "Not stated" instead of guessing.
4. Open questions: things raised but not resolved.
5. Follow-ups I should double-check: anything ambiguous, where two people might read it differently.

Use only what is in the transcript.

Three parts of that prompt do most of the work.

• “Quote the words.” Requiring evidence keeps invented tasks out and lets you verify quickly.
• “Not stated” instead of guessing. Without this, assistants often fill in an owner because it looks tidy.
• A separate section for ambiguity. It surfaces the things you’d otherwise discover the hard way.

Step 4: Check the result against the meeting

This is the step people skip and regret. Read the output with these checks.

1. Every action item has evidence. Confirm each quote exists in the transcript and means what the table says. Delete tasks without evidence.
2. Owners are right. Confirm each person actually agreed. “We should update the pricing page” isn’t a commitment by anyone.
3. Dates are right. Relative dates like “next Friday” or “end of the month” are easy to misread. Convert them to actual dates and verify against your calendar.
4. Nothing important is missing. Skim the transcript for commitments, especially ones made quickly near the end. Ask: “Did I miss any commitments made in the last ten minutes?”
5. Decisions are real decisions. A suggestion that got a nod is different from an agreement. If unsure, move it to open questions.
6. Names and figures. Check spelling, amounts and project names.

A useful follow-up prompt for the last check:

Re-read the transcript. List every place where someone said they would do something, even casually, and tell me whether it appears in your action item table.

Step 5: Write the follow-up message

Once the list is verified, turn it into an email or chat message people will read.

Turn the verified action items below into a follow-up email to the attendees.
Rules: Subject line includes the meeting name and date. Start with a two-sentence summary. Then list decisions, then a table of action items with owner and due date. End with one line asking people to reply by [date] if anything is wrong. Tone: plain and friendly. Under 200 words.

[paste verified decisions and action items]

Notice that this prompt uses the checked list, not the raw transcript. Sending the correction request, “reply if anything is wrong,” builds in a second check by the people who were there.

If you use Gmail, our guide on automating Gmail with Claude shows how to have drafts saved for you to review rather than sent automatically.

Step 6: Keep a running list across meetings

The best payoff is a standing view of what is open. Keep one document or spreadsheet with columns for Task, Owner, Due date, Status and Source meeting. At the start of each recurring meeting, paste the previous list and this prompt:

Here are the open action items from last time. Here is the new transcript. Update the list: mark items completed if the transcript shows they were, keep unresolved ones, and add new ones using the same rules as before. Show me what changed.

You can also start the meeting with the list on screen, which turns the review into a five-minute habit instead of a rambling recap. If your action items live in a spreadsheet, AI for Google Sheets and AI with Excel cover keeping it tidy.

Different meetings, different prompts

Adjust the structure to the type of meeting.

• One-on-one: ask for topics discussed, feedback given, commitments each person made, and anything to bring next time. Be careful with personal or HR content.
• Client call: ask for the client’s stated needs, objections, promises we made, and the next step with a date. Do a careful check on any pricing or timeline promise.
• Project status: ask for status by workstream, new risks, blocked items and who is blocking them.
• Brainstorm: ask for grouped themes and the top three ideas with reasons rather than a task list.

What the meeting tools document

Details from Microsoft and Google help pages on the built-in note features, which you can compare with your own transcript.

• Microsoft says Copilot in Teams suggests action items and answers any questions you have, in real time during or after a meeting.
• To see Copilot’s conversation history after a meeting ends, Microsoft says to turn on live transcription during the meeting.
• Microsoft says Copilot won’t work in meetings that are hosted outside the participant’s organization.
• Google says “Take notes for me” in Google Meet is recommended for meetings of 15 minutes to a maximum of 8 hours.
• Google says the Meet notes document is generated shortly after the meeting ends.

What to watch for

• Confident but wrong attribution. Assistants sometimes assign a comment to the wrong person, especially in unlabeled transcripts.
• Tone flattening. A tense disagreement can come out as “the team discussed timing.” If nuance matters, read that section yourself.
• Transcription errors. Names, product terms and numbers are commonly garbled. Fix them first, because errors in the input flow into the output.
• Over-sharing. The summary is usually shorter than the discussion, but it may still include things some recipients shouldn’t see. Check the distribution list.
• Compliance. Some industries have retention or disclosure rules for meeting records. Confirm what applies before you store or share AI summaries.

A quick checklist to keep

1. Confirm recording is allowed and the content may go into the tool.
2. Add names, date and purpose to the input.
3. Use a prompt that demands evidence and “Not stated.”
4. Verify owners, dates and decisions against the transcript.
5. Send the follow-up within 24 hours and ask for corrections.
6. Track open items in one list.

For a shorter answer to the question, see how to use AI for meeting notes. Good prompts make all of this easier: how to write AI prompts that work covers the fundamentals.

In our two-day class, meeting transcripts and shared documents are one of the labs: you practice summarizing a provided transcript and pulling out action items.

Sources

• Microsoft Support, Catch up on meetings with Microsoft 365 Copilot in Teams: “It also suggests action items and answers any questions you have, in real time during or after a meeting”
• Microsoft Support, Catch up on meetings with Microsoft 365 Copilot in Teams: “make sure to turn on live transcription during the meeting”
• Microsoft Support, Catch up on meetings with Microsoft 365 Copilot in Teams: “Copilot won’t work in meetings that are hosted outside the participant’s organization”
• Google Meet Help, “Take notes for me” in Google Meet: “recommended for meetings of 15 minutes to a maximum of 8 hours”
• Google Meet Help, “Take notes for me” in Google Meet: “generated shortly after the meeting ends”