TaskbyTask.Practical AI guides for work
ChatGPT · Practical walkthrough

Use ChatGPT to extract actions from meeting notes

The meeting ended ten minutes ago, your notes are half sentences, and someone has already asked for "the actions". An impressively full task board is the last thing you want, if half of it was never agreed.

Task by Task13 min read + practice
Three colleagues around a table linked to cards for owners, dates and action status.

What you'll make

three short lists from your meeting notes (decisions, agreed actions and open questions), each tied to the note that supports it, plus a follow-up message.

What you'll need

your typed notes, including any later corrections, a ChatGPT work account and about 10 minutes. The same prompts work in Claude, Gemini or Copilot. Leave out sensitive employee matters; this route needs only typed text, not a recording.

Example result.

Confirmed decision: defer the redesign until the next planning meeting; its date isn’t in the notes. [N5] Agreed action: Alex to send revised figures by Monday 12 October 2026, replacing 9 October. [N1, N2] Open questions: Is a second analysis needed? [N3] Should a pilot happen if the figures support it? No owner or date agreed. [N4]

1. Prepare the notes you actually have

Bring the relevant notes, including later corrections. Keep the original deadline as well as any accepted change, so the change can be checked. Mark the difference between “we agreed” and “could we?”, and say where acceptance was unclear.

Headings, timestamps or line labels help you find a passage again. A source reference is that location or a short exact quote; you don’t need a special numbering system.

Why this works: the model can only tell an agreement from a suggestion if the notes do.

What you should see: readable notes in which agreements, questions and changes are distinguishable.

2. Ask for supported commitments

Send this with your notes in a fresh chat:

From these notes, produce three sections: Confirmed decisions, Agreed actions and Open questions.
For each agreed action, give the action, explicitly agreed owner, latest agreed date and a short supporting quote or source location.
Keep missing owners or dates as "to agree"; don't assign them yourself.
If a later note changes an earlier deadline, use the later accepted date and show the evidence for both the old date and the change.
Don't turn questions, suggestions or conditional ideas into agreed actions. Keep conditions visible. Don't infer agreement from silence. Use only these notes and flag ambiguity.

[your notes]

Paste your notes, with accepted corrections, in place of [your notes].

Why this works: three sections stop a discussion becoming an accidentally ambitious task list. Asking for evidence of each owner, date and change protects people from commitments the meeting never made.

What you should see: short lists with a reference after every item, and gaps marked “to agree”.

3. Check against the meeting record

For each action, find the agreement, the named owner and the latest accepted date in your notes. Check that open questions and conditions stayed open, and that every decision has a source.

Why this works: the references turn checking into a quick lookup rather than a re-run of the meeting in your head.

What you should see: every item traced to a note. Fewer actions than you expected is often the right answer.

4. Turn the checked list into a follow-up

Turn this checked list into a concise meeting follow-up. Separate the agreed action and decision from points still needing confirmation. Invite corrections without implying that silence means agreement. Don't add commitments.

[checked list]

Paste the list from step 3 in place of [checked list].

Why this works: the message is drafted from what you’ve checked, not from the original notes, so nothing you removed sneaks back in.

What you should see: a short message like the one in the worked example, ready for you to edit and send yourself.

Check the result

  • Every action has evidence of agreement, not just a name nearby.
  • Each owner is explicitly named as responsible.
  • Each date is the latest one actually accepted.
  • Conditional ideas and open questions are still separate.

The usual failure: an invented owner. Someone who raised a question or made a suggestion becomes the person doing it. Spot it by checking whether the note says they agreed, or only that they spoke.

Keep [the disputed item] under Open questions. The notes don't establish agreement or ownership; don't assign either.

[the disputed item] is the action you spotted. Ask the meeting owner to confirm the gap, and add their answer to the notes before updating the list.

Worked example: a deadline changes

Fictional example. The notes:

N1: Alex agreed to send revised figures by Friday 9 October 2026.
N2: Later, Alex changed the date to Monday 12 October; the group accepted it.
N3: Rory asked whether a second analysis was needed. No decision.
N4: Lee suggested a small pilot if the revised figures support it. No owner or date agreed.
N5: The group agreed to defer the redesign until the next planning meeting.

The first draft read: “Actions: Alex to send figures by Friday 9 October. Rory to do the second analysis. Lee to launch the pilot on Monday.”

Three of those are wrong. Alex’s date was changed and accepted. Rory asked a question; Lee made a conditional suggestion; neither agreed to anything. The repair prompt, once for Rory’s item and once for Lee’s, plus a reminder to use the latest accepted date, gave the example result at the top of this page. The follow-up drafted from it:

Alex will send the revised figures by Monday 12 October, replacing the earlier 9 October date. We agreed to defer the redesign until the next planning meeting; its date isn’t in these notes. Two points are still open: whether a second analysis is needed, and whether to run a pilot if the figures support it. Neither has an owner or date yet. Please flag anything I’ve missed or recorded incorrectly.

  • Both deadline notes matter. N2 records an accepted change, so N1 stays as evidence of what it replaced.
  • One agreed action is correct here. An impressively full task board would have been a warning sign.
  • “Monday” for the pilot came from nowhere. It borrowed Alex’s new date. Invented dates often travel from a neighbouring line.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Audit the list for invented commitments

A second pass catches what the first missed. Then read it yourself: a second model answer is another draft to check, not an independent witness to the meeting.

Audit this draft against the notes. Identify any invented owner or date, outdated deadline, suggestion promoted to an action, lost condition or decision without a source. For each, quote or locate the relevant note and suggest a correction. Keep ambiguity visible; don't resolve it by choosing the most plausible owner or deadline.

Extracting fewer commitments accurately is more useful than creating a full set by enthusiasm.

Update the list when agreement arrives

When a missing owner or date is agreed, add it to your notes as a dated entry, then ask in the same chat for an update that quotes the new evidence for each changed item, shows what changed and keeps remaining gaps as “to agree”. Check each changed row; if another row moved without support, restore it. If a project system demands an owner and date on every row, don’t satisfy it by guessing. Keep unagreed ideas in a separate list until they’re real commitments.

Start from a Zoom or Teams summary instead

Zoom: summaries arrive by email and, if meeting chat is enabled, in the meeting’s group chat. In the web portal, select your profile picture, My account › Summaries: My Summaries for meetings you hosted, Shared with me for others. Only the host can edit a summary; if a wrong version went out, tell recipients what changed, because editing a stored copy doesn’t correct their inbox. Summaries don’t run in breakout rooms.

Teams: after the meeting, open Copilot from the meeting chat, or from Recap if the meeting was transcribed (Teams Premium or a Microsoft 365 Copilot licence). If the organiser chose Copilot Only during the meeting and nobody started a transcript, what was said aloud isn’t kept: a later answer covers the chat, not the conversation.

Either way, run the step 3 checks against your own notes before relying on the summary.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.