The follow-up is where meetings succeed or fail
Many meetings end with a feeling of agreement and no record of who is doing what. A week later, half the group remembers differently. Turning discussion into a short list of actions, each with an owner and a date, is one of the most useful follow-ups you can do, and also one of the most tedious. This is a task where an AI assistant can save time, provided you stay in charge of accuracy.
What you are asking the tool to do
A good action list separates four things that are often tangled together in raw notes:
- Decisions: what was agreed.
- Actions: specific tasks someone will do.
- Owners: the person responsible for each action.
- Deadlines: when it is due, or “not stated.”
It also helps to keep a separate list of open questions that were raised but not settled. Without that, unresolved points get silently turned into decisions.
Start with usable input
The output can only be as good as the notes. Rough notes written in shorthand may be ambiguous to anyone but you. Automatic transcripts from transcription tools may contain misheard names, missing speakers and chatter that makes the real commitments hard to find. Before submitting:
- fix names and obvious errors;
- add the attendee list with roles;
- note the date and the purpose of the meeting;
- remove side conversations that do not belong in the record.
If the meeting included confidential or sensitive material, such as personnel matters or client details, decide whether it should go into the tool at all. Check whether your organization has approved a tool for this use, and see our guidance on giving context without oversharing. Recording or transcribing people may also require consent where you work, so check the rules before relying on a transcript.
A prompt template
Here is a structure you can adapt:
“Below are notes from a meeting about [TOPIC] on [DATE]. Attendees: [NAMES AND ROLES]. Create:
- A list of decisions made.
- A table of action items with columns: task, owner, due date.
- A list of open questions.
Rules: Use only information in the notes. If an owner or due date is not stated, write ‘not stated’ instead of guessing. Do not assign tasks to people who did not agree to them. Keep each task under 20 words.
Notes: [PASTE NOTES]”
The rules matter. Without them, assistants tend to fill gaps helpfully, assigning an owner who was merely mentioned or inventing a Friday deadline. The “not stated” instruction turns gaps into visible items you can resolve.
Our pillar on writing prompts explains the task, context and format pattern behind this template.
Review against your memory
Treat the first output as a draft. Go through it line by line and ask:
- Was this actually agreed? A suggestion floated in discussion is not a commitment.
- Is the owner right? Check against what you remember and against the notes.
- Are the dates correct? Watch for relative dates like “next week,” which may be interpreted incorrectly. Convert them to calendar dates yourself.
- Is anything missing? Skim the notes for commitments the list left out.
- Is anything duplicated or merged? Two separate tasks sometimes get combined into one.
A brief look at the original notes with the list next to them usually takes only a few minutes.
Confirm with the people involved
Send the list to attendees promptly and ask them to reply with corrections. Include the owners’ names so no one is surprised. A line like “Please reply by [DATE] if anything here is wrong” turns the list into a shared record. Because it is easy for an AI-generated summary to sound authoritative, inviting correction is especially useful.
If your workplace expects it, mention that AI helped prepare the list. See the discussion of AI disclosure for general norms.
Moving the list into your system
Once confirmed, copy tasks into wherever your team tracks work. Many project management tools can create tasks from a pasted list, and some meeting tools offer to generate action items automatically. Whether built in or done by hand, the same checks apply. Automatic features can misattribute tasks or miss context, so a human review is worth keeping.
Things to keep in mind
- Tone and politics: the list shows who is responsible for what. Wording matters, so keep it neutral and factual.
- Sensitive subjects: do not use an AI tool to summarize meetings about individual performance, health or legal disputes unless your organization has clear rules allowing it.
- Accuracy limits: tools can miss sarcasm, hedged commitments (“I’ll try to…”) and decisions made off the record.
- Keep a source: retain the notes or transcript until the actions are done, so questions can be settled.
A quick routine
- Clean up your notes right after the meeting.
- Use a template prompt that forbids guessing.
- Check each action against your notes.
- Send it out with a request for corrections.
- Move confirmed tasks into your tracking system.
Used this way, an assistant handles the formatting and you handle the judgment, which is the part that counts.