Playbooks · Everyday tasks · last verified 2026-10-23

Turn meeting notes into action items and a follow-up email

For an office worker × turning rough meeting notes into action items plus a follow-up email draft × with ChatGPT, uploading or pasting the notes.

Before you start

You need your meeting notes as a file (DOCX, PDF, or TXT) or as text you can paste, and the meeting date. OpenAI's help page lists turning a recording or notes into structured notes, a meeting recap, or a follow-up email draft as a described use of working with files in ChatGPT, and states that document uploads are available on Free and paid plans subject to limits (Free: 3 file uploads per day).

Time and cost: NOT_MEASURED. The value here is a cleaner handoff, not a measured time saving.

Before uploading, strip anything the recipients do not need: salaries, personal remarks about colleagues, passwords, and internal-only details. If the notes contain something sensitive, paste only the relevant section instead of the whole document.

What "done" looks like

At the end of one sitting you have a short list of action items — each with an owner and a date, or marked as missing one — plus a follow-up email draft you can paste into your mail app. Nothing has been sent yet; sending is your decision after the checks below.

Steps

1. Attach or paste the notes, with the date. Attach the notes file to a new chat, or paste the notes text. Start with one line of context the notes themselves may not carry:

   These are my notes from a meeting on 2026-10-23. Turn them into
   action items and a follow-up email draft. Do not add decisions,
   owners, or dates that are not in the notes.

2. Ask for decisions, actions, and open questions — separately. Paste:

   First, list three separate sections: (1) decisions made, (2)
   action items as a table with columns Task / Owner / Due date,
   (3) open questions. For any action item where the owner or due
   date is not in the notes, write UNKNOWN in that cell — do not
   guess.

   Keeping the three sections separate matters: a decision restated as an action, or an open question restated as a decision, is how a follow-up email quietly misstates what was agreed.

3. Draft the email from the table, not from the raw notes. Paste:

   Now draft a follow-up email of no more than 200 words using
   only the decisions and action items above. List the action items
   with owner and due date, and list the UNKNOWN items as questions
   for the group, not as assigned tasks. Use a neutral, plain tone.

4. Fill the UNKNOWNs yourself. For each UNKNOWN owner or date, check with the person involved or with the meeting organiser. Do not let the chatbot fill them, and do not send the email with UNKNOWNs still in it unless you have deliberately turned them into questions for the group.
5. Copy the email into your mail app. Paste it, add the recipients yourself, and re-read the subject line and the recipient list before sending. The chatbot does not send email in this playbook.

Check the agent's work

• Every action item traces back to a line in your notes. If you cannot find the line, delete the item.
• Every owner is a person who was in the meeting or was named in the notes — not a plausible-sounding name the draft invented.
• Every due date is a date stated in the notes, or one you supplied in step 4. A date that "sounds right" is not a verified date.
• Decisions, actions, and open questions have not been mixed: nothing marked as decided was only discussed, and nothing merely discussed is assigned as a task.
• Names, project names, and numbers in the email match the notes exactly — these are the details a reader will act on.

What can go wrong

• It invents an owner or a deadline. This is the main failure mode for this task. The UNKNOWN rule in step 2 is the guard; if a table arrives with no UNKNOWNs at all, be suspicious and re-check it against the notes.
• It upgrades a discussion into a decision. Phrases like "we should" in notes become "we agreed" in drafts. Compare the decision section against the notes before the email goes out.
• It drops a quiet action item. An item mentioned once, in passing, is easy for a summary to lose. Skim your original notes once against the table — the table should not be shorter than the notes' actual commitments.
• Sensitive notes get uploaded whole. Uploading is convenient and hard to undo in a chat. Paste a trimmed section when the full notes contain material the group does not need.

Limits

• The chatbot was not in the meeting. It cannot know tone, side conversations, or anything said but not written down, and it cannot resolve a disagreement about what was decided.
• It does not send the email, update a task tracker, or notify owners in this playbook. Those are your steps, in your own tools.
• Audio uploads are not part of this playbook: OpenAI's help page states audio uploads are not available on the Free plan at this time. If your notes are a recording, use a written transcript you already have, or write the notes out first.

Verification

Checked 2026-10-23. This page was not run end to end; its capability claims rest on provider documentation fetched this run. Sources: OpenAI Help Center — Uploading files and audio to ChatGPT (attach a supported file and describe what to do with it; "turn a recording into structured notes, a meeting recap, or a follow-up email draft" as a described transform use; DOCX, PDF, TXT supported; Free and paid availability; Free limit of 3 file uploads per day; audio uploads not available on the Free plan). Omitted: no claim is made that the chatbot can send email, update a task system, or transcribe a recording on the Free plan — those steps were cut because they are not grounded in the fetched page for this stack, and the playbook says so in Limits. Limits of this verification: provider pages describe the transform capability, not whether a given draft matches a given meeting — that check is the "Check the agent's work" section above.

Back to: Everyday playbooks hub · Skills index

Also: Small-team hub