Most meetings end with good intentions and no record of who agreed to do what. A transcript fixes the record, but nobody rereads forty minutes of raw conversation. This workflow turns that transcript into a clean list of decisions and action items in about five minutes, with a verification step that keeps AI mistakes out of your team's inbox.

What you need before you start

You need the transcript as text. Most meeting platforms can produce one automatically, and most notes apps can transcribe a recording. Turn the transcript on before the meeting starts, and tell attendees it is running: in many places recording without consent is not just rude, it is unlawful.

You also need an AI assistant that accepts long pasted text. The exact tool matters less than the prompts below, which are written to force the assistant to stay inside what was actually said.

Step 1: Extract the decisions first

Decisions are the easiest part for an AI to extract reliably, because they are usually stated in clear language. Run this prompt before asking for tasks:

Read the meeting transcript below. List every decision that was
actually made, in one line each. For every decision, include the
exact quote from the transcript that supports it. If something was
discussed but not decided, leave it out completely.

Transcript:
[paste transcript]

If a "decision" appears without a real quote, delete it. That single rule removes most invented content.

Step 2: Extract tasks with owners and dates

Now ask for the work itself. The key is forcing structure: owner, task, deadline, and the quote.

From the same transcript, list every action item as a table:
Task | Owner | Deadline | Supporting quote.

Rules:
- Only include tasks that a named person agreed to do.
- If a deadline was not stated, write "not stated" instead of
  guessing one.
- If the owner is unclear, write "unassigned".
- Never invent names, dates or numbers.

The "write not stated" instruction is doing real work here. Without it, assistants fill gaps with plausible inventions, and a task list with invented deadlines is worse than no task list at all.

Step 3: Draft the follow-up message

With decisions and tasks verified, generating the message is safe:

Write a short follow-up message for the attendees using only the
decisions and action items above. Format: one line of thanks, a
"Decisions" list, an "Action items" list with owners and dates,
and one line asking people to flag mistakes within 24 hours.

Asking attendees to flag mistakes is not a weakness. It is the final verification layer, and it takes seconds of their time instead of a second meeting.

The two-minute verification pass

Before sending anything, check three things against the transcript:

  • Names: every owner is a real attendee who actually agreed.
  • Dates: every deadline was spoken, or honestly marked "not stated".
  • Numbers: budgets, quantities and commitments match the quotes.

This pass is the difference between a helpful summary and a confident hallucination with your name on it.

A privacy note that matters

Meeting transcripts contain strategy, names and sometimes personal information. Use tools your organisation has approved for work content, and be careful pasting transcripts into consumer AI services with unclear data policies. When in doubt, anonymise names before pasting and restore them in the final message yourself.

Common mistakes

  • Asking for a summary instead of structured output. A summary hides missing owners and dates; a table exposes them.
  • Skipping the quote requirement. Quotes are your audit trail.
  • Sending without the verification pass. Five minutes of workflow, two minutes of checking. Both halves are the system.