Turn Meeting Transcripts Into Automated Follow-Ups
Every meeting produces action items that nobody tracks. Three prompts that extract commitments, assign owners, and generate follow-up messages before you leave the room.
The Problem
A one-hour meeting with six people costs the company six hours of salary. That is the visible cost. The invisible cost is what happens after the meeting ends.
Someone said they would "circle back" on the vendor pricing. Someone else agreed to "take a look at" the Q2 forecast assumptions. A third person volunteered to "connect with" the product team about the timeline. These are not action items. They are vague gestures toward future work, and by Thursday nobody remembers who committed to what.
The person who took notes captured a summary of the discussion. Topics covered. Key points raised. General alignment on direction. What they did not capture: the specific commitments, the deadlines (explicit or implied), the dependencies between tasks, or the decisions that were made versus the options that were merely discussed.
The meeting was productive. The follow-through was not. And nobody notices until the next meeting, when the same topics come up again because nothing actually happened in between.
The Fix
Separate commitments from conversation. A transcript contains two types of content: discussion (people exploring ideas, asking questions, sharing opinions) and commitments (someone accepting responsibility for a deliverable). Most meeting notes treat everything the same. The fix is to scan the entire transcript and pull out only the moments where a person said they would do something. "I can have that ready by Friday" is a commitment. "We should probably think about that" is not. This distinction eliminates 80% of the noise.
Extract decisions separately from action items. A decision is a choice the group made: "We are going with Vendor B." "We are pushing the launch to April." "We are not hiring for that role this quarter." Decisions constrain what happens next but are not themselves tasks. They need to be recorded because people forget what was decided and relitigate it in the next meeting. Most notes bury decisions inside discussion summaries, making them invisible two weeks later.
Generate follow-up messages, not just a list. An action item list that lives in a shared document is better than nothing, but it still requires someone to chase people. The real output should be ready-to-send messages: a Slack message to the person who owns each item, an email summary for stakeholders who were not in the meeting, and a calendar reminder for the next check-in. If the output requires human effort to distribute, it will not get distributed.
Copy-paste prompt: commitment extractor
"I am going to paste a meeting transcript. Your job is to extract every commitment, decision, and open question from the conversation. For each item, classify it as one of three types: COMMITMENT (a specific person agreed to do a specific thing), DECISION (the group chose a direction that constrains future action), or OPEN QUESTION (a topic was raised but not resolved, requiring follow-up). For each COMMITMENT, extract: (1) Owner: the person who made the commitment. If someone said 'we should' without naming who, flag it as UNASSIGNED. (2) Deliverable: what exactly they committed to produce or do. Rewrite vague language into specific deliverables. 'Look into vendor pricing' becomes 'Compile pricing comparison for Vendors A, B, and C.' (3) Deadline: explicit if stated ('by Friday'), implied if suggested ('before the board meeting'), or NONE if no timeline was mentioned. (4) Dependencies: does this task require input from someone else first? For each DECISION, extract: (1) What was decided. State it as a clear, unambiguous sentence. (2) What alternatives were considered and rejected. (3) Any conditions or caveats ('we go with Vendor B unless the security audit raises red flags'). For each OPEN QUESTION, extract: (1) The question itself. (2) Who needs to answer it. (3) Why it matters (what is blocked until this is resolved). At the end, produce a summary table with columns: Type | Owner | Item | Deadline | Status. Sort by deadline (soonest first), then by type (commitments, decisions, open questions)."
Copy-paste prompt: follow-up message generator
"Using the extracted commitments, decisions, and open questions from the previous step, generate three types of follow-up messages: (1) INDIVIDUAL FOLLOW-UPS: For each person with one or more commitments, write a short, direct Slack or Teams message. Include: what they committed to, the deadline, any dependencies they need from others, and a single sentence of context so they do not have to re-read the full notes. Tone: professional, concise, assumes they were paying attention but might not remember the details. Not passive-aggressive. Not overly formal. Example: 'Hey Sarah, from today's product sync: you are pulling the pricing comparison for Vendors A, B, and C by Friday. Miguel's security audit results (due Wednesday) might affect the final recommendation. Let me know if you need the original RFP responses.' (2) STAKEHOLDER SUMMARY: A 150-word email for people who were not in the meeting but need to know what happened. Lead with decisions made, then key commitments and their deadlines, then open questions that may affect their work. No discussion recap. Only outcomes. (3) NEXT MEETING AGENDA SEED: Based on the open questions and pending commitments, draft a 3-5 item agenda for the follow-up meeting. Each item should reference the specific commitment or question it resolves. Include suggested time allocations based on complexity."
Copy-paste prompt: accountability tracker
"Using the commitments extracted from the meeting, build a lightweight accountability system. For each commitment, generate: (1) A CHECK-IN MESSAGE to send 48 hours before the deadline. Keep it under 30 words. Not a reminder that sounds like nagging. A genuine check-in that offers help if the person is blocked. Example: 'Quick check on the vendor pricing comparison due Friday. Need anything from me to finish it up?' (2) A COMPLETION CONFIRMATION to send when the deadline arrives. If the deliverable was shared, acknowledge it. If it was not, send a brief follow-up. Example: 'Did the vendor comparison land somewhere? Want to make sure I have the latest version before Monday's meeting.' (3) A DEPENDENCY ALERT for any commitment that depends on someone else's work. If the upstream task is late, notify the downstream owner immediately with context. Example: 'Heads up: Miguel's security audit was due Wednesday but is still in progress. Your vendor recommendation depends on those results. Suggesting we push your deadline to next Tuesday. Does that work?' (4) A WEEKLY DIGEST that lists all commitments from all meetings that week, grouped by person, with status (complete/in progress/overdue/blocked). This becomes the team's single source of truth for 'what did we agree to do and did it happen.' Format everything as copy-paste-ready messages. Include the platform (Slack, email, or calendar invite) for each message type."
What you get
A complete follow-through system from a single meeting transcript. Every commitment extracted with owner, deliverable, and deadline. Ready-to-send messages for each participant. A stakeholder summary for people who were not in the room. Pre-written check-in messages timed to deadlines. A weekly digest that makes accountability visible without requiring a project management tool. The meeting happened once. The follow-up happens automatically.
Processing time
5 min
Typical follow-through
30-40%
With tracking
85-90%
Why meeting notes fail
Meeting notes capture what was discussed. They do not capture what was decided or who committed to what. A typical set of notes reads like a summary of a conversation: "The team discussed the Q2 roadmap. There was alignment on prioritizing the mobile experience. Several concerns were raised about the timeline." This tells you what topics came up. It does not tell you who is doing what by when.
The gap between "we discussed it" and "someone is doing it" is where most organizational productivity disappears. Not in the meetings themselves, but in the silence between meetings where commitments dissolve into good intentions.
The real output of a meeting is not notes
A meeting that produces a list of action items is better than one that produces notes. A meeting that produces action items, individual follow-up messages, deadline reminders, and a stakeholder summary is better still. The goal is not to document what happened. The goal is to make sure what was agreed actually happens.
The transcript is the raw material. The action items are the intermediate product. The follow-up messages, check-ins, and accountability tracker are the finished product. Most organizations stop at the intermediate step and wonder why nothing changes between meetings.
Works for
Chiefs of Staff or Executive Assistants who manage follow-up for leadership meetings
Project managers running cross-functional meetings where accountability spans multiple teams
Team leads who want meetings to produce action, not just discussion
Operations managers tracking commitments across weekly standups, retros, and planning sessions
Anyone who has ever left a meeting thinking "that was productive" and then watched nothing happen
Every meeting already produces the data you need. The transcript is there. The commitments are buried inside it. Five minutes to extract what took an hour to discuss. Then the system follows up so you do not have to.