Guide

How to turn meeting notes into clear action items with AI

Prompts for writing a tight agenda, turning messy meeting notes into decisions and action items, and sending a follow-up people actually read.

Most meetings don't fail in the room. They fail afterwards, when nobody is quite sure what was decided, who owns the next step, or when it is due. A week later the same topic is back on the agenda, and the meeting that was supposed to settle it has quietly become two.

An AI assistant is surprisingly good at the dull, important part: turning half-sentences and bullet fragments into a short record of decisions and actions. It can't know what your team meant, so you still check the result. But it can save you the twenty minutes of tidying that usually gets skipped. Below is a simple routine for before, during and after a meeting, with prompts you can copy and adapt.

Before the meeting: write an agenda with a purpose

A good agenda states what the meeting is for, not just what will be discussed. "Q3 budget" is a topic. "Decide whether to move 10% of the events budget to hiring" is a purpose. When the purpose is clear, people come prepared, and you know when you are done.

I'm running a [length]-minute meeting with [who attends] about [topic]. The outcome I need is [decision or output]. Write an agenda with 3–5 items. For each item, give the goal (decide, discuss or inform), the owner, and a time box. Add one line at the top stating the purpose of the meeting, and suggest anything people should read beforehand.

If the assistant suggests more items than fit the time, that's useful information. It usually means the meeting is really two meetings, or that some items could be an email.

During the meeting: take rough notes on purpose

You don't need beautiful notes. You need notes that capture three things: what was decided, what still needs doing and by whom, and what was left open. Shorthand is fine. Something like "budget: move 10% yes, Anna checks w/ finance by Fri, events team unhappy – revisit Oct" is perfect raw material.

A small habit that helps: mark decisions with D:, actions with A: and open questions with ? as you type. It takes no extra time and makes the next step much more accurate.

After the meeting: turn notes into decisions and actions

This is where the assistant earns its place. Paste your rough notes and ask for a structured summary. Be explicit that it should not invent owners or dates. If something is missing, you want to see a gap, not a guess.

Here are my rough notes from a meeting about [topic] with [attendees, first names or roles only]: [paste notes]. Turn them into: 1) a two-sentence summary, 2) a list of decisions made, 3) a table of action items with owner, task and due date, 4) open questions. If an owner or date is not in the notes, write "unassigned" or "no date" instead of guessing. Keep the wording close to mine.

Read the output against your memory of the meeting. The most common error is a discussion point recorded as a decision, so check that list carefully before you send anything.

Write a follow-up email people will actually read

Long minutes get skimmed. A follow-up that leads with the actions, names people clearly and fits on one screen gets read. You can ask for exactly that.

Using this meeting summary [paste], write a short follow-up email to the attendees. Start with the action items, each with owner and due date, then the decisions, then open questions. Friendly, plain tone, under 180 words. End by asking people to reply within a day if anything is wrong.

That last line matters. It turns the email into a quick check rather than a final record, and it catches misunderstandings while they are still cheap to fix.

Close the loop at the next meeting

Actions that are never reviewed tend to drift. Start the next meeting with a two-minute look at the previous list. The assistant can prepare it for you.

Here are the action items from our last meeting [paste] and the updates I've received since [paste]. Make a status list: done, in progress, blocked or no update. For anything blocked or without an update, suggest one short question I could ask the owner. Don't assume progress that isn't mentioned.

Over a few weeks this builds a calm rhythm: the agenda states the purpose, the notes are rough, the summary is quick, and nothing quietly disappears.

A few habits that make the prompts work better

Give context once. Say what the team does and what the meeting is for. The same notes mean different things in a design review and a budget meeting.
Ask for gaps, not guesses. Telling the assistant to write "unassigned" is the single most useful line in these prompts.
Keep your own words. Asking it to stay close to your wording stops summaries from sounding grander or more certain than the meeting was.
Short beats complete. A five-line follow-up that is read is worth more than a page that isn't.

Keep it private and keep it honest

Meeting notes often contain things that shouldn't leave the room: personnel matters, client names, numbers that aren't public. Use first names or roles, remove anything sensitive before pasting, and follow your organisation's policy on AI tools. And treat every summary as a draft. You were in the meeting; the assistant wasn't.

If you'd like a fuller set of ready-made prompts for agendas, facilitation, minutes and follow-ups, The Meeting Master collects them in one place. For the wider admin around it, such as invoices, emails and weekly planning, see the Small Business Back Office pack. Or start with a few free prompts to see if the style suits you.