Turn a meeting recording into action items with steps, a reusable prompt, and a checklist for checking owners, dates, dependencies, and sources.
To turn a meeting recording into action items, transcribe it, separate commitments from suggestions and decisions, and keep a source reference, such as a quote or timestamp, for each proposed task. Confirm owners and dates that were never stated before treating the list as agreed work.
CoHear is an AI recording and transcription app for iPhone and Android. It supports phone recording and importing existing audio, then organizing the conversation into transcripts, summaries, and action lists. Those outputs give you a starting point; the steps below explain how to check the list before anyone relies on it. Obtain the required permission to record and process the conversation before starting.
Separate decisions, suggestions, and commitments
A useful action list preserves the difference between what the group chose, what someone proposed, and what a person agreed to do. These statements can occur next to one another in a transcript, but they belong in different parts of the meeting record.
A decision answers “What did we choose?” A suggestion answers “What could we do?” A commitment answers “What work did someone accept?” A decision may create work without naming an owner. A suggestion may be worth discussing without becoming a task. Keep both distinctions visible rather than forcing every sentence into an assignment.
Consider this illustrative conversation, not a customer recording: Maya says, “We are keeping the current onboarding flow.” Leo says, “We could interview new users.” Maya replies, “I will draft interview questions after Support sends the complaint examples.” The first statement is a decision, the second a suggestion, and the third a conditional commitment.
The commitment is to draft questions, not to conduct the interviews or redesign onboarding. Its dependency is receiving the examples. Nobody has supplied a deadline, and nobody has accepted responsibility for sending the examples. Extracting “Leo will interview users by Friday” would add an owner, a task, and a date that the conversation never established.
When a statement is unclear, keep it under open questions and ask for confirmation. The Four Piles / Three Gates method offers a way to organize these categories before forwarding notes.
Separate meeting decisions, actions, and open questions
Build a list that survives a source check
Each proposed action needs enough evidence to explain why it belongs on the list. Keep five fields together so that a reviewer can inspect the assignment without searching through an entire summary.
- Task: describe the specific deliverable or next action using a verb. Preserve the original scope instead of expanding it into a project.
- Owner: use the person who explicitly accepted the work. If the recording never establishes an owner, write “Not stated” or “Needs confirmation.”
- Date: preserve an agreed deadline. If someone says “next Friday,” retain that phrase until the meeting date and intended calendar date have been checked.
- Dependency: record conditions such as receiving data, approval, or a customer response. A conditional commitment is not an unconditional delivery promise.
- Source: retain a short quote or timestamp when available. Do not invent a time reference when the transcript has none.
For the example above, the task is “Draft interview questions,” the owner is Maya, the date is “Not stated,” and the dependency is “Support sends complaint examples.” The source is Maya’s quoted commitment. A separate open question asks who will supply those examples. A status field can help later, but it should not replace any of these five fields.
Speaker labels also need checking. A transcript may split one speaker into several labels or attribute a sentence to the wrong person. Listen to the relevant passage before turning a label into an assignment. A plausible name or job title is not evidence that the person accepted responsibility.
Use a consistent format across the list. If one row means a confirmed commitment and another means an editor’s recommendation, label that distinction explicitly. The meeting notes template provides a place to keep actions beside the decision record rather than losing their context.
Start with the meeting notes template
A reusable extraction prompt
An extraction prompt should preserve uncertainty and make the source check possible. Use the following instruction in a transcript analysis tool that accepts custom instructions. This is a reusable prompt, not a claim that every CoHear screen includes a prompt input field. Copy the text, then add the transcript you are authorized to process.
Extract commitments, decisions, suggestions, and open questions into separate sections. For each proposed action, include task, owner, date, dependency, and source quote or timestamp when available. Use “Not stated” for missing information and “Needs confirmation” for ambiguous assignments. Do not infer ownership from job title, topic, speaker order, or attendance. Preserve conditions such as “after approval.” Do not turn suggestions into agreed tasks. Do not invent quotes or timestamps. Flag contradictory statements and identify which passage needs review. Return a proposed action list, not a claim that the team has approved it.
After extraction, inspect a few difficult passages first: an interrupted sentence, an unclear speaker, a conditional promise, or a decision that was reversed later. If the output gets those wrong, revisit the relevant source before using the remainder. A clean format does not tell you whether the distinctions were preserved.
For a long conversation, keep the surrounding discussion available when reviewing an item. A sentence that sounds like a commitment in isolation may be an example, a rejected option, or someone quoting another team. Review later corrections as well as the first occurrence of a task.
Confirm before you distribute
Distribute the list as proposed follow-up until the people responsible have confirmed it. Check names, numbers, dates, dependencies, and permission to share before sending anything outside the original audience. Keep sensitive background out of a broad task list when it is unnecessary for the work.
A short confirmation message can say: “Here is the proposed follow-up list from today’s discussion. Please confirm your items, correct the scope, and supply any missing dates. Items marked Needs confirmation are still open.” Ask a named reviewer to resolve disputed assignments rather than treating silence as acceptance.
Once the assignments are confirmed, move them into the task system your team already uses. Preserve the source reference in a suitable private note and use the task system to track changes, completion, or reassignment. Creating an AI action list does not itself create tasks in that system.
At the next meeting, review unresolved items rather than extracting them again as new work. Check whether an apparent duplicate is a reminder, a changed commitment, or a different deliverable. The weekly team meeting case shows how a recurring discussion can be organized around follow-up rather than another transcript summary.
Review the weekly team meeting to action list case
What an AI action list cannot prove
An AI action list can organize evidence from a conversation, but it cannot prove that a task was accepted, scheduled, completed, or authorized. It also cannot establish an agreement that was never recorded. Keep these limits beside the list when it informs a consequential decision.
Some missing information belongs in a follow-up conversation, not in a more elaborate prompt. An owner may be unavailable, two teams may disagree about scope, or a proposed deadline may be impossible. Ask the people involved and update the record with the confirmed answer. Do not rewrite the historical source to make the new agreement appear to have existed earlier.
If you need a way to capture the conversation before applying this review process, explore CoHear’s phone recording and audio-import workflow. Choose the capture and output that fit your situation, then keep human confirmation between the generated list and assigned work.
Explore CoHear recording, transcription, and action-list workflows