Writing Prompts
Meeting Notes Summarizer
Turn raw meeting notes or transcripts into a clean summary with decisions, action items, and owners.
Prompt
You are an efficient executive assistant skilled at turning messy meeting notes into structured, actionable summaries. Read the raw notes or transcript below and produce a clean summary in the format specified. Meeting type: [MEETING_TYPE] Raw notes or transcript: [MEETING_NOTES_OR_TRANSCRIPT] Produce the following four sections in order: 1. Meeting Summary (3–5 sentences) — a neutral, factual summary of what was discussed and the overall outcome or conclusion of the meeting. Do not editorialize. 2. Key Decisions (bullet list) — list every decision that was agreed upon during the meeting. Each bullet should state the decision clearly in one sentence. If no explicit decisions were made, write "No formal decisions recorded." 3. Action Items — present a table with three columns: Action (what needs to be done), Owner (who is responsible — use the name from the notes, or "TBD" if not assigned), and Deadline (from the notes, or "Not set" if unspecified). List every action item mentioned, even informally. 4. Open Questions — bullet list of any questions raised during the meeting that were not resolved. If none, write "None." Calibrate formality to the meeting type: standup notes warrant a brief, scannable output; client call notes should be more polished and free of internal shorthand.
How to Use
Paste your notes or transcript into [MEETING_NOTES_OR_TRANSCRIPT] — raw, messy notes work fine. Specify the meeting type so the model calibrates its formality and focus appropriately. The output is ready to paste into Notion, Confluence, Slack, or an email recap. Share the action items table directly with attendees to confirm owners and deadlines.
Variables
| Variable | Description |
|---|---|
| [MEETING_NOTES_OR_TRANSCRIPT] | Your raw notes, a copy-pasted transcript, or bullet points from the meeting — format does not need to be clean |
| [MEETING_TYPE] | The type of meeting: standup, sprint planning, retrospective, design review, client call, all-hands, 1:1, or other |
Tips
- If attendee names appear inconsistently in your notes (e.g., "Mike", "M.", "Michael"), add a note before pasting: "Mike, M., and Michael all refer to Michael Chen." This ensures the action items table assigns ownership correctly.
- After generating, ask: "Are there any implied action items I may have missed?" — the model will often surface informal commitments that were not phrased as direct asks in the notes.