Meeting notes are only valuable if they become decisions and next steps. ChatGPT can turn rough notes or a transcript into a clean follow-up, but the prompt needs to separate real action items from general discussion.

What to prepare

  • Raw notes or transcript. For a long meeting, split it by agenda section or 10-15 minute chunk.
  • Names of people who attended and any speaker labels you trust.
  • Project name and meeting goal.
  • Any deadline, priority, or dependency rules, such as “anything urgent means this week” or “client approval blocks design work.”
  • The task system you use, such as Asana, Notion, Jira, Trello, or a simple checklist.
  • Any open action items from the previous meeting.
  • A version with private client, employee, or customer details removed.
  • Confirmation that recording, transcription, and AI processing are allowed for this meeting.

The workflow

  1. Paste the notes or transcript. For long transcripts, paste one section at a time and ask ChatGPT to keep a running decision and action-item list.
  2. Ask for decisions, open questions, action items, owners, and deadlines.
  3. Ask ChatGPT to mark unclear owners, vague tasks, and missing deadlines instead of inventing details.
  4. Turn the confirmed actions into task-tracker wording that can be copied into your system.
  5. Generate a short follow-up email from the cleaned summary.

Copy this prompt

Turn these meeting notes into a useful work summary. Project: [project name] Meeting goal: [goal] Attendees: [names] Task system: [example: Notion task database, Asana, Jira, email checklist, or none] Deadline, priority, and dependency rules: [example: anything urgent means this week, client approval blocks design work, budget decisions block purchasing, or no rule] Speaker labels: [reliable labels, rough auto-caption labels, no labels, or unknown] Transcript source and meeting date: [example: Zoom transcript from July 10, typed notes, or mixed notes] What counts as evidence: [example: exact quote, speaker label, timestamp, agenda section, or line from notes] Open action items from the previous meeting: [paste if available] Transcript length or chunk plan: [short notes, full transcript, or section 1 of 4] Finalization command: [example: wait until I type FINALIZE before writing final minutes] Raw notes or transcript: [paste notes or one transcript section] Return: 1. Neutral meeting minutes with key topics, decisions, and source notes 2. Evidence-backed commitment scan: possible promises, owners, dates, and the note line or timestamp that supports each one 3. Final action items in a table with task, single owner, deadline, priority, dependency or blocker, source evidence, and definition of done 4. Open questions 5. Risks, blockers, and follow-ups that do not yet have a clear owner 6. Items that need confirmation because the notes are unclear 7. A missed-action check: any clear commitment that might have been skipped 8. A task-tracker version I can copy into my system 9. A short follow-up email I can send to the group Rules: - Focus only on concrete next steps, not general discussion. - Treat only the notes or transcript pasted in this prompt as evidence unless I explicitly say to use earlier chat context. - If an owner is unclear, write "Unassigned". - If a deadline is unclear, write "TBD". - Do not assign a task to someone who is not listed as an attendee unless the notes clearly say they own it. - Do not invent decisions, promises, or dates. - For each final action item, include a source quote, timestamp, agenda section, or note line when available. - Do not turn a discussion topic into an action item unless someone clearly committed to doing something. - If one task has multiple people attached, choose the accountable owner and put the others in notes. - If a task depends on another decision, approval, reply, file, budget, or meeting, mark that dependency instead of hiding it inside the task wording. - If speaker labels are missing or unreliable, do not guess who said a quote, decision, or commitment. - Use neutral language. Do not label anyone as frustrated, defensive, confused, or aligned unless those words appear in the notes. - For long transcripts, keep a running list after each chunk and wait for my finalization command before creating final minutes. - If the transcript appears incomplete, say what section seems missing and ask for the next section. - When detail is missing, write "not stated in the notes" instead of filling the gap. - Keep the follow-up email under 160 words.

Quick quality check

Before sending the result, check whether each action item has a clear verb, owner, deadline, priority, dependency, source evidence, and enough context that someone who missed the meeting would know what to do. Also check that every owner was in the meeting or was clearly assigned in the notes, that old chat context was not used by accident, and that long transcripts were scanned for missed commitments only after the final section was provided. The minutes should stay neutral and not guess speakers, feelings, blame, or agreement that the notes do not show. If not, ask ChatGPT to rewrite only the weak sections.

Fix a weak output

Review the action items you just created. For each item, check: 1. Is the task specific enough? 2. Does it have one accountable owner, not a group? 3. Is the deadline explicit, inferred from the notes, or marked TBD? 4. Is the priority stated, inferred from an explicit rule, or marked normal? 5. Does the task depend on another decision, approval, reply, file, budget, or meeting? 6. Is there a source note that proves where the task came from? 7. Is there a clear definition of done? 8. Did you separate confirmed decisions from open questions? 9. Did you assign a task to anyone who was not in the attendee list or clearly named in the notes? 10. Did you miss any sentence where someone clearly promised, agreed, or committed to do something? 11. Did you use neutral wording without guessing speaker identity, emotion, blame, or intent? 12. Did you use only the pasted notes and not earlier chat memory or old meeting context? Rewrite the list for a task tracker and mark anything uncertain as "needs confirmation".

Follow-up email template

After ChatGPT creates the summary, ask it to rewrite the follow-up in a friendly, concise tone. The best email should be short enough that busy people actually read it.

The money value here is not the summary. It is fewer missed tasks, fewer repeated meetings, and faster handoffs.

Best fit

This workflow is useful for project managers, freelancers, agencies, consultants, startup teams, real estate teams, and anyone who ends meetings with scattered notes and no clear owner list.

Related guides

Create a meeting agenda Write a project status report Use ChatGPT at work safely