The meeting ended 40 minutes ago. You have three pages of notes that look like a crime scene. Everyone nodded at the end. Nobody wrote anything down. By tomorrow, two people will remember different decisions, one person will claim they never agreed to anything, and the action items will live and die in someone's notebook.

AI action item prompts can help with this. Not by replacing your judgment, but by doing the extraction work you'd otherwise skip because you're already late for the next meeting.

Here's exactly how to use them, what to paste in, and where to stop before AI starts inventing things that never happened.

Why meetings produce noise instead of work

Most meetings generate three things: decisions, suggestions, and vibes. The problem is that all three sound identical in the notes. "We should probably look into the vendor pricing" is not a task. It's a thought someone had out loud. AI can't tell the difference unless you tell it to look.

The other issue is that clean formatting isn't the same as real agreement. A neat numbered list with names and dates looks like accountability. It isn't, unless those names and dates came from what was actually said and were confirmed by the actual people.

This is Rule #5 from Don't Replace Me: It's Not Smart. It's Fast. AI will give you a beautiful action list in ten seconds. Whether the tasks are real, whether the owners agreed, whether the deadlines are possible: that's still on you.

One more thing worth naming. Most meetings have a graveyard of action items from previous meetings that nobody followed up on. The new list doesn't fix that. If you're going to use these prompts, pair them with a habit of actually checking last week's list before the next meeting starts. AI can help you extract. It can't force closure.

What to paste in, and what to leave out

Before we get to the prompts, the input matters as much as the template. Paste in your rough notes, a transcript, or a bullet summary. Be specific about what was said.

What you should never paste into an unapproved AI tool:

If your meeting touched any of that, get internal approval for the tool you're using before anything goes in. When real risk is involved, escalate to legal, security, privacy, HR, finance, or whoever owns that area. AI action item prompts are useful. They're not a compliance function.

Also worth noting: the quality of AI output here is directly proportional to the quality of your notes. If your notes say "discussed the thing with marketing" you'll get useless output. If they say "Sarah and Tom disagreed on timeline for the campaign launch, Tom said he needs two more weeks, Sarah pushed back, no resolution" you'll get something you can actually work with. The prompts below are designed to get the most out of messy notes, but they can't perform miracles on three words and a doodle.

The reusable AI action item prompt formula

Every prompt in this article follows the same structure. You can use it as a template for anything not covered below.

You are an action item assistant. I'll give you [notes / transcript / summary].

Your job is to [specific task].

Rules:
- Only use what's in the source material. Do not invent owners, deadlines, or decisions.
- Flag anything unclear or missing as an open question.
- Mark confidence level: HIGH (explicitly stated), MEDIUM (implied), LOW (unclear).
- Do not guess. Ask.

[Paste notes here]

Keep that formula. It's the difference between useful output and confident fiction.

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 →

AI action item prompts: 10 copy-paste templates

Prompt 1: Extract action items from rough notes

Use this when your notes are a mess and you need a starting point.

You are an action item assistant. I'll give you rough meeting notes.

Extract every action item mentioned. For each one, note:
- The task (what needs to happen)
- Who was mentioned as responsible (or flag as "owner unassigned")
- Any deadline mentioned (or flag as "no deadline stated")
- Confidence level: HIGH (explicitly agreed), MEDIUM (implied), LOW (unclear)

Do not invent owners or deadlines. Flag gaps as open questions.

[Paste notes here]

Prompt 2: Turn a transcript into owners and due dates

Use this after an auto-transcribed meeting. Expect gaps. That's fine.

You are an action item assistant. I'll give you a meeting transcript.

For each action item you find:
- State the task clearly
- Name the owner (use exact name from transcript, or flag "owner not named")
- State the deadline (exact date if mentioned, or "no deadline given")
- Quote the relevant line from the transcript as your source

Do not summarize. Do not infer. Quote and flag.

[Paste transcript here]

Prompt 3: Separate decisions from suggestions

This one is genuinely useful and underused. Most action item lists mix the two, and then people argue about it for three weeks.

You are an action item assistant. I'll give you meeting notes.

Sort the content into two lists:

DECISIONS: things that were agreed, confirmed, or signed off
SUGGESTIONS: things that were raised, proposed, or "we should probably..."

For each decision, note who made it or confirmed it.
For each suggestion, note who raised it and whether next steps were agreed.
Flag anything where you can't tell which category it belongs to.

[Paste notes here]

Prompt 4: Find tasks with no owner

Nothing dies faster than an action item with no name attached.

You are an action item assistant. I'll give you a meeting action list.

Identify every task that has no clearly named owner.
Group them into:
- Tasks where the owner can probably be inferred (explain your reasoning)
- Tasks where the owner is genuinely unclear (flag for follow-up)

Do not assign owners. Flag and explain. I will assign them.

[Paste action list here]

Prompt 5: Identify dependencies and blockers

For anything with moving parts, this saves you a week of surprises.

You are an action item assistant. I'll give you a meeting action list.

For each task, identify:
- Whether it depends on another task being completed first
- Whether it requires input, approval, or resources from someone else
- Any blockers mentioned or implied in the notes

Flag dependencies as: SEQUENTIAL (can't start until X is done) or PARALLEL (can run at the same time).
Flag anything uncertain as an open question.

[Paste action list here]

For more on managing outputs like this into a real plan, the AI project management prompts article has templates for turning action lists into proper briefs.

Prompt 6: Draft a follow-up email

This is the prompt most people want first. Use it last. Get the action list right, then draft the email around it.

You are a meeting follow-up assistant. I'll give you a verified action list from a recent meeting.

Draft a follow-up email that:
- Opens with a one-sentence summary of what was decided
- Lists each action item with owner, deadline, and any noted dependency
- Ends with a clear next meeting date or check-in point if mentioned
- Uses plain, professional language (no jargon, no filler)

Tone: clear and direct, not corporate.

[Paste verified action list here]

See also the AI meeting follow-up prompts article for more templates in this area.

Prompt 7: Create a client-safe action list

Not everything in your internal notes belongs in a client email. This prompt helps you filter.

You are an action item assistant. I'll give you an internal meeting action list.

Create a client-safe version that:
- Includes only tasks relevant to the client
- Removes any internal comments, budget discussions, or team-only notes
- Uses clear language a client would understand without internal context
- Flags anything you're unsure whether to include

Do not edit the substance of what was agreed. Only filter and clarify.

[Paste internal action list here]

If the meeting involved sensitive client information, get sign-off before using any AI tool. When client trust is on the line, a human review isn't optional.

Prompt 8: Write an internal team task recap

Different from the client version. This one is for your team and should include context, dependencies, and risk flags.

You are a team update assistant. I'll give you a meeting action list.

Write an internal recap that includes:
- What was decided and by whom
- Each task with owner, deadline, and dependency notes
- Any open questions that still need resolution
- Any risks or blockers flagged during the meeting
- A brief note on what happens if any task slips

Keep it short. Teams don't read long updates.

[Paste action list here]

This pairs well with AI status report prompts when you need to push the recap up to stakeholders.

Prompt 9: Check for unrealistic commitments

Someone in your meeting said "I'll have that done by Friday." It's Wednesday. The thing takes two weeks. This prompt helps you catch it before it becomes an incident.

You are a task review assistant. I'll give you an action list with owners and deadlines.

Review each task and flag:
- Deadlines that seem tight given the scope of the task
- Tasks where one person owns multiple heavy deliverables in the same window
- Dependencies that make the deadline impossible (X can't finish until Y is done)
- Anything where the task description is too vague to estimate effort

Do not rewrite the tasks. Only flag concerns and explain your reasoning.

[Paste action list with owners and deadlines here]

Prompt 10: Audit whether the action list is safe to send

Use this before anything goes out. External, internal, doesn't matter.

You are an action list reviewer. I'll give you a draft action list I'm about to send.

Check for:
- Tasks with no named owner
- Deadlines with no date (just "soon" or "ASAP")
- Decisions that appear in the list but weren't explicitly agreed in the notes
- Anything that could be misread as a commitment the team didn't make
- Sensitive content that shouldn't be in a written record without review (flag the category, don't repeat it)
- Open questions that haven't been addressed

Return a clean pass/fail and a list of issues to fix before sending.

[Paste action list here]

What AI gets wrong about action items, and when it matters

AI is good at extraction. It's bad at politics.

It doesn't know that when Sarah said "that sounds fine," she meant she'd think about it. It doesn't know that the deadline Dave mentioned was aspirational. It doesn't know that one of the "decisions" on the list was a suggestion someone floated that nobody actually confirmed.

This is the core thing to understand: AI processes text. It doesn't process subtext. The meeting transcript might say "Marcus will handle the budget review." What the transcript can't tell you is that Marcus has a conflict with the finance lead, has three other deliverables due that week, and said "sure" in the tone of someone who absolutely didn't mean it. You know that. The model doesn't.

That gap matters most in two situations. One is when the action list will be used as a record, something people refer back to in disputes or reviews. The other is when the stakes are high enough that a misattributed task or a fictitious deadline creates real problems downstream. In those cases, the AI does the first draft and you do the verification. Not the other way around.

The AI decision log prompts article is worth reading before you turn meeting outputs into a record people will refer back to.

A quick word on recurring meetings

One-off meetings are easy. You run the notes, you send the list, done.

Recurring meetings are where action items go to die. Every week the same items show up, slightly reworded, with new deadlines. Nobody calls it out because calling it out is awkward. The list looks productive. The work doesn't move.

If you're using these prompts for a recurring meeting, add one step: before running the new notes, paste in last week's action list and ask the AI to flag which items are appearing for the second or third time. It won't know why they're repeating. But it can surface the pattern, which is usually enough to start a real conversation about what's actually blocking those tasks.

That's not a prompt people think to write. But it's probably the most useful one in this list for anyone running a team that meets regularly.

Frequently asked questions

What's the best way to use AI for action items after a meeting?

Start with raw notes or a transcript and use a prompt that extracts tasks with source quotes rather than summaries. Always verify owner names, deadlines, and decision status against what was actually said. AI is good for structure, but the accountability has to be human.

Can AI assign owners to action items automatically?

It can suggest owners based on what's in the notes, but it shouldn't assign them without confirmation. If the meeting notes don't name someone explicitly, the right move is to flag it as unassigned, not guess. Unconfirmed owners cause more confusion than no owner at all.

What if my meeting transcript is messy or incomplete?

Use it anyway, but tell the AI what's missing. A prompt like "flag anything where you're uncertain" gives you a list of gaps to fill rather than a confident fabrication. Garbage in produces garbage out, but flagged garbage is easier to fix than confident fiction. See what AI can and can't do for more on this.

Should I paste confidential meeting notes into ChatGPT?

Not if they contain client PII, employee data, legal disputes, financial forecasts, unreleased product information, or anything subject to regulatory or contractual restrictions. Check your company's approved tools policy first. When in doubt, escalate to legal, security, or whoever owns data governance at your organization.

How do I handle action items that weren't explicitly agreed in the meeting?

Keep them off the list, or flag them separately as "suggested but not confirmed." Sending out action items that weren't agreed creates false consensus. Someone will come back to that email later and dispute it. Better to send a shorter, accurate list than a complete one that includes things nobody signed up for.

What's the difference between an action item and a decision?

A decision is something agreed or confirmed in the meeting. An action item is a task someone agreed to complete. Decisions create context. Action items create work. Mixing them up is how people end up confused about what was resolved versus what still needs doing. Use Prompt 3 above to separate them before you send anything out.