Meeting notes fail when they’re a wall of text. Good notes separate three things: decisions, action items, and the parking lot. The 17 prompts below force that separation, then convert it into the artifacts you actually distribute — recap emails, Slack updates, decision docs, and 1:1 follow-up trackers. Paste them into ChatGPT, Claude, or Gemini; the model picker further down tells you which one handles a long transcript best as of June 2026.
TL;DR
- A 60-minute meeting holds roughly 20 minutes of substance buried in 40 minutes of meandering. A bare “summarize this meeting” hands the meandering back to you as paragraphs.
- The fix is structure-forcing prompts: decisions / actions / parking lot, then a meeting-type-specific output (recap email, CRM summary, exec brief, weekly digest).
- For raw transcripts, model context matters. Claude Pro ($20/mo) and Gemini 3.1 Pro both expose a 1M-token window in-app; ChatGPT Plus ($20/mo) caps the in-app window near 272K tokens (full 1M only on the $200 Pro tier). A 90-minute transcript is ~20K-30K tokens, so all three fit it — context only bites on multi-meeting digests.
- Always attach an owner and a due date to every action item. Items without both rot.
What these prompts solve
Vanilla “summarize this meeting” returns paragraphs you have to re-read to find the one thing you needed. These templates force the structural separation — decisions / actions / parking lot — and then convert that structure into the artifacts you distribute downstream: recap emails, Slack updates, decision docs, 1:1 follow-up trackers. The output is skimmable, owner-attributed, and ready to send.
Who this is for
PMs and tech leads running 10+ meetings a week, founders compressing customer calls into CRM updates, managers preparing 1:1 follow-ups, executive assistants drafting recap emails, and anyone who has ever sent a 600-word recap and wondered why no one acted on it.
Which tool to paste these into (June 2026)
You can run every prompt here in any chat model. Two practical questions decide which: does the transcript fit the context window, and do you want the AI to capture the meeting too, or just process a transcript you already have?
| Tool | Plan / price (June 2026) | In-app context | Best for |
|---|---|---|---|
| Claude Pro | $20/mo ($17 annual) | 1M tokens | Cleanest decisions/actions structuring; multi-meeting digests |
| Gemini 3.1 Pro (Google AI Pro) | $19.99/mo | 1M tokens | Meetings already in Google Meet / Docs |
| ChatGPT Plus | $20/mo | ~272K tokens in-app | General use; one transcript at a time |
| Otter Pro | $16.99/mo ($8.33 annual) | n/a (capture tool) | Live transcription, 1,200 min/mo |
| Fireflies | $10-19/seat/mo | n/a (capture tool) | Multilingual, searchable archive |
| Granola | $14/seat/mo (free tier 30-day history) | n/a (capture tool) | Bot-free; enhances your own rough notes |
Notes on the numbers: a 90-minute meeting transcript runs ~20K-30K tokens, so it fits comfortably in all three chat models — context only constrains you on template #17 (a weekly digest of four transcripts) or very long all-hands. Capture tools (Otter, Fireflies, Granola) handle recording and transcription; export their transcript, then paste it into a chat model and run these prompts for the structured output. Google Meet’s built-in “Take notes for me” (Gemini, included with most Workspace Business/Enterprise editions as of January 2026) auto-drafts notes into a Google Doc — a fine first draft, but it still benefits from running template #1 or #14 over the raw transcript for tighter structure.
When not to use these prompts
Skip them for brainstorming sessions where the value is the divergent thinking, not the artifact. Skip them when speaker attribution is missing — meeting notes without owners attached to actions are dangerous. And don’t paste highly confidential meetings into a consumer AI tool without checking its retention policy first; transcripts routinely contain things that shouldn’t leave your environment.
Prompt anatomy / structure formula
A meeting-notes prompt should always carry six elements:
- Transcript or notes: pasted or referenced.
- Meeting type: team sync / customer call / 1:1 / strategy / planning — each needs different output.
- Output structure: decisions / actions / parking lot — or a meeting-type-specific shape.
- Audience: notes for me / recap for team / brief for an absent person / customer summary for CRM.
- Length cap: e.g., 200-word recap, 5-bullet TL;DR, full-section detail.
- Owner attribution rule: actions must name an owner; “we” must be resolved to a person.
Best for
- Weekly team syncs (decisions + actions + parking lot)
- Customer / sales calls (pain, resonance, next step)
- 1:1s (wins, blockers, asks, follow-ups)
- Strategy / planning meetings (decision docs)
- Standups (status, blockers, asks for help)
- Executive briefings (TL;DR + risk + ask)
- Async meeting summaries for absent teammates
- Recap emails and Slack updates
17 copy-ready prompt templates
1. Decisions + actions + parking lot
Below is a meeting transcript. Output 3 sections only: (1) Decisions made (verb-led, ≤1 line each), (2) Action items with owner + due date + 1-line context, (3) Parking lot (deferred topics with why deferred). Nothing else. Skip discussion that didn't land on a decision or commit.
{paste}2. 5-bullet TL;DR
Compress this 60-min transcript into 5 bullets: who was there, the main topic, key decision, top tension, what's next. ≤20 words per bullet. No marketing tone.
{paste}3. Action items only (with chase email drafts)
Extract action items from transcript. For each: owner, action, due date, why it matters. Then draft a one-line chase email I can send to each owner restating their commitment. Tone: friendly, not nagging.
{paste}4. Customer call summary for CRM
This is a sales / customer call. Output: customer pain (3 bullets), our pitch resonance (what landed / what didn't), next step agreed (with date), 1 quote worth saving verbatim. ≤200 words total.
{paste}5. 1:1 notes from transcript
This is my 1:1 with {direct report / manager}. Extract: their wins (1–3 bullets), blockers (with what unblocks each), asks of me, follow-ups for me, follow-ups for them. Skip personal / private items.
{paste}6. Strategy meeting → decision doc
Below is a strategy discussion transcript. Synthesize into a decision doc: question we were answering, options discussed, decision, dissenting view captured (with whose name), owner of execution, follow-up checkpoint date.
{paste}7. Translate notes for an absent teammate
Write a 200-word summary of this meeting for {absent person}, focused on what they need to know to be unblocked. Skip recap of what they already know; emphasize what changed and what's expected of them.
Transcript: {paste}8. Identify misaligned moments
Read this transcript and identify 3 moments where participants seemed to be talking past each other. For each: the misalignment, why it happened (terminology mismatch / assumption gap / different goals), suggested follow-up message to resolve it.
{paste}9. Notes → Slack channel update
Below are my raw meeting notes. Convert to a Slack channel update (≤150 words). Voice: matter-of-fact, no marketing. Use a single emoji at the start. End with the one decision the channel needs to react to.
{paste}10. Open question tracker
Extract every open question from this transcript. For each: who raised it, why it's still open (no owner / no info / waiting on external), what info would resolve it. Output sorted by urgency.
{paste}11. Executive briefing summary
Summarize this meeting for an executive who wasn't there. Output: (a) 1-sentence headline of what was decided or learned, (b) 3-bullet TL;DR, (c) 1 risk to flag, (d) 1 explicit ask of the executive (or "no ask"). Total ≤120 words.
{paste}12. Standup notes
This is a standup transcript. For each person: yesterday (1 line), today (1 line), blockers (or "none"). Mark blockers requiring help from another teammate. Output as a clean table.
{paste}13. Meeting health audit
Audit this meeting: (a) % of time spent on the stated agenda vs off-topic, (b) participants who spoke less than 5% of the time, (c) decisions per minute, (d) one suggestion to make the next meeting better. Be specific, not generic.
{paste}14. Recap email from notes
Below are my raw meeting notes. Draft a recap email to attendees (≤200 words): 1-line subject, opening line ("Recap of today's {meeting}"), 3-bullet decisions, action-items section in standard format, closing line with next-meeting date. Voice: tight, no fluff.
{paste}15. Customer-meeting → CRM + follow-up tasks
This is a customer call. Output: (a) CRM-ready summary (3 sentences), (b) updated stage / health score recommendation with reason, (c) follow-up tasks for me with due dates, (d) follow-up tasks for the customer with due dates and how I'll nudge if they slip.
{paste}16. Strategy meeting → 1-pager for circulation
Below is a 90-minute strategy discussion. Produce a 1-pager (≤500 words) for circulation: question, context, options considered (with one trade-off each), decision, dissents captured, next step, owner. Format ready for paste into Notion.
{paste}17. Multi-meeting weekly digest
Below are notes / transcripts from 4 meetings this week. Synthesize into a 1-page weekly digest: top 3 decisions across all meetings, top 5 action items by owner, themes that came up in multiple meetings (with which meetings), open questions still unresolved.
Meetings: {paste each}Common mistakes
- Treating notes as a wall of text. Even great prose loses to a 5-bullet TL;DR for skimmers.
- No owner / due date on action items. Without both, items rot.
- Capturing everything instead of decisions. A 2,000-word “summary” no one reads is worse than 200 words covering only what changed.
- One template for every meeting type. A 1:1 doesn’t get the same structure as a customer call.
- Sending notes only to attendees. Absent stakeholders who needed to know find out late; surface them in the recap routing.
- Skipping the parking lot. Items defer and disappear; an explicit parking-lot section keeps them visible for the next meeting’s agenda.
- Recap email = bullet dump. Lazy recap = lazy follow-up. Use template #14 to make the recap drive action.
How to push results further
- Match the meeting type to the template (templates #1, #4, #5, #6, #11, #12). Generic “summarize” output is always worse.
- For any meeting with action items, run two prompts: notes (template #1) then action-item extraction. Different shapes serve different downstream uses.
- For customer-facing meetings, always include a CRM-formatted block (template #4, #15). Saves an extra copy-paste step.
- Run the meeting-health audit (template #13) periodically on your recurring meetings. Most weekly syncs converge on the same 3 fixes.
- For executives, default to template #11 — they want 1 sentence and 1 ask, not your meeting structure.
- Standardize a single recap email template (template #14) across your team. Cross-team recap consistency is more valuable than per-person creativity.
- Pair with stakeholder update email prompts when the recap needs to flow upward, not just sideways.
FAQ
- Which AI handles a long meeting transcript best? All three fit a normal transcript: a 90-minute meeting is ~20K-30K tokens, well under every in-app limit. Claude Pro and Gemini 3.1 Pro both expose 1M tokens in-app, so they win on template #17 (digesting four meetings at once) and on all-hands transcripts; ChatGPT Plus caps the in-app window near 272K tokens, which is still plenty for a single meeting. In side-by-side tests, Claude Opus 4.7 tends to produce the cleanest decisions/actions structure.
- Should I record meetings and use transcripts, or take notes live? Transcripts are higher fidelity but need scrubbing for sensitive content. Live notes are faster and skip the recording-policy question. For high-stakes meetings, do both: take notes live, use the transcript for verification.
- What about confidentiality? Don’t paste transcripts containing personnel info, customer PII, or unannounced strategy into a consumer AI tool without checking its retention / training-data policy. When in doubt, redact names and dollar amounts, or use a business/enterprise tier with a no-training guarantee.
- How short should a recap email be? Under 200 words for routine meetings; executives skim under 150. The decision and the actions are the recap; everything else is filler.
- Should the recap include the full discussion? No. The discussion is what produced the decision; the decision is what gets distributed.
- Can I combine multiple meetings into one weekly digest? Yes — template #17. It’s most valuable when the same theme shows up across three different meetings; the digest catches the pattern a single recap can’t.
- What’s the right cadence for action-item tracking? Weekly. Daily is over-managing; bi-weekly lets too much rot.
Related
- Action item extraction prompts — chained workflow for extracting actions from any meeting input
- Meeting agenda prompts — agenda templates that make the post-meeting recap easier
- Stakeholder update email prompts — upward-flowing recap when the meeting affects stakeholders not in the room
- Weekly planning prompts — turn the action list into a personal week plan
- Weekly report prompts — weekly status report combining notes across meetings
- Project planning prompts — broader project structure that absorbs meeting decisions
- Meeting action items use case — end-to-end example with extraction
- AI meeting summary tutorial — full workflow from transcript to distribution
- How to Use AI for Meeting Notes: From Recording to Executable Action Items
External references: Google Meet “Take notes for me” support and Otter.ai pricing for current capture-tool limits.