Home / Operations and admin / KA-008

Turn meeting notes into action items and follow-up emails

Turn meeting notes or a transcript into actions with owners and due dates. Draft a follow-up email per owner that waits for approval.

Who it suits

Small business owner, operations manager, project lead, freelance virtual assistant

Time saved

About 20 to 40 minutes per one hour meeting (estimate)

Level

Easy

Updated

Oct 13, 2026

Why this task

Meetings often end with a vague sense of who agreed to what. Notes sit in one person's notebook, and actions slip because nobody wrote down an owner or a date. An agent can turn raw notes into a clear action list within minutes of the meeting. It also drafts a short email per owner, so the chair only has to check and send.

You turn meeting notes into an action list and draft follow-up emails for [BUSINESS NAME].

Meeting: [MEETING NAME], held on [DATE].
Attendees (name, role, email): [ATTENDEE LIST]
Chair who will send the emails: [CHAIR NAME]
Default due date when none was said: [RULE, e.g. one week from the meeting]

Notes or transcript:
[PASTE NOTES OR TRANSCRIPT]

Part 1. Action table.
List every action someone agreed to do. For each row give: action in plain words, owner, due date, source quote, and confidence.
- Owner must be a name from the attendee list. If the notes do not make the owner clear, write UNASSIGNED.
- Use the due date only if someone said it. Otherwise apply the default rule and mark the date GUESSED.
- Source quote is the short line from the notes that supports the action.
- Confidence is HIGH, MEDIUM or LOW.
Do not invent actions, owners or dates that the notes do not support.

Part 2. Decisions and open questions.
List decisions made, then questions left open with who raised them.

Part 3. Follow-up emails.
Write one email per owner, from [CHAIR NAME]. Each email should:
- Use a subject line with the meeting name and date.
- Thank them briefly, then list only their actions with due dates.
- Ask them to reply if an action or date is wrong.
- Stay under 150 words, in a [TONE, e.g. friendly and direct] tone.
Leave out side comments, jokes, personal remarks and anything about other attendees' performance.

End with a list of rows marked UNASSIGNED, GUESSED or LOW so the chair can check them first. Do not send anything.

Replace each highlighted placeholder with your own details before you run it.

Steps

1. Decide who chairs the follow-up. That person checks the action list and sends every email.
2. Collect the source: typed notes, a shared document, or a transcript. Record meetings only when every attendee has agreed.
3. Remove anything that should not go to an AI tool, such as personal matters, salary talk or client account numbers.
4. Fill in the prompt placeholders: meeting name, date, attendee list with roles and email addresses, and the default due date rule.
5. Run the prompt as a one off chat right after the meeting. Ask for the action table first, then the emails.
6. Check every row against your memory of the meeting. Fix wrong owners, and change any date the agent marked as GUESSED.
7. Read each draft email. Make sure it lists only that owner's actions and does not repeat side comments from the meeting.
8. Send the approved emails yourself and copy the table into your task tracker or spreadsheet.
9. For a regular meeting, you can save the prompt as a reusable project or template. If your setup lets an agent run on a schedule and read a shared notes folder, it can prepare drafts after each meeting. Keep sending manual either way.

What you get

A table lists each action with an owner, a due date and a supporting quote. A short list of decisions and open questions follows. One short, polite email per owner lists only their tasks. Every unclear owner or guessed date is flagged for the chair to confirm.

What can go wrong, and the check for each

Related playbooks