Turn Any Meeting Transcript Into Action Items in 90 Seconds

Meeting notes are the silent productivity tax of operator life. Every operator knows meetings without notes don't ship action items. Every operator also skips notes because writing them takes 30-60 minutes after every meeting and nobody has that time.

Claude collapses the cost. With a tuned meeting notes skill, a 30-minute meeting transcript becomes structured notes in 90 seconds of model time + 5 minutes of human review. Total: under 7 minutes per meeting for shipped notes.

Below the friction threshold where it stops getting skipped.

The Four-Section Notes Structure

Every meeting note should have these four sections:

1. Action Items. Specific tasks with owner and due date. Each item is one line. "Cameron to ship dashboard fix by Friday June 6" beats "Need to look at the dashboard."

2. Decisions Made. Specific resolutions reached during the meeting. "Decided to ship v2 on June 15 instead of June 1." Includes who decided if relevant.

3. Open Questions. Things raised but not resolved. With owner of who'll resolve. "Open: pricing for enterprise tier — Cameron to propose by Wednesday."

4. Next Meeting Topics. What to discuss next time. Carries continuity across recurring meetings.

Total length: typically 150-300 words per meeting. Reads in 90 seconds. Acts as the canonical reference for what was agreed.

Why Each Section Matters

Action Items: The output that justifies the meeting existing. Without specific tasks + owners + dates, meetings produce nothing.

Decisions Made: Prevents revisiting settled questions. Without recorded decisions, the same debates re-occur monthly.

Open Questions: Catches what wasn't resolved. Open questions that disappear from notes also disappear from action — which usually means the question becomes a problem 3 weeks later.

Next Meeting Topics: Continuity for recurring meetings. Saves agenda-writing time and prevents drift.

The Claude Meeting Notes Skill

Save this as a Claude Project Custom Instruction or Skill file:

You are a Senior Meeting Facilitator who converts meeting transcripts into structured notes. Your job is to extract Action Items, Decisions Made, Open Questions, and Next Meeting Topics from the raw transcript provided.

Output structure (exactly):

# Meeting Notes — [Topic] — [Date]

Attendees: [list]

Action Items

• [Owner] to [specific action] by [date]
• (repeat per action)

Decisions Made

• [Specific decision], decided by [who if relevant]
• (repeat per decision)

Open Questions

• [Specific question], to be resolved by [owner] by [date]
• (repeat per open question)

Next Meeting Topics

• [Topic to discuss next time]
• (repeat per topic)

Rules:

• Specific over general (named owners, specific dates, specific deliverables)
• Each action item must have an owner AND a date
• Skip filler ("introductions," "small talk," "brief catch-up")
• Capture decisions even if they happened informally during conversation
• Do not invent action items, decisions, or attendees not in the transcript

If the transcript is unclear on any owner or date, mark [TBD: ] and ask one consolidated clarifying question at the end.

Paste the transcript. Claude returns structured notes in 60-90 seconds.

A Real Example

Meeting transcript excerpt:

Cameron: Okay so where are we on the dashboard. Maya you were working on the spec right? Maya: Yeah, I have v1 of the spec done. Going to send around end of week. Cameron can you review by Monday? Cameron: Yeah Monday works. Maya: Cool. Also I think we should push the launch from June 15 to June 22 — the QA pass is going to need more time than we budgeted. Cameron: Agreed, let's move it. Maya: Should I tell the design team? Cameron: Yeah ping Anna by tomorrow. Maya: Done. Oh — open question — are we doing the upsell modal in v2 or v3? Cameron: Let me think about it. I'll have an answer by Wednesday.

Claude output:

# Meeting Notes — Dashboard v2 Sync — 2026-05-29

Attendees: Cameron, Maya

Action Items

• Maya to send v1 dashboard spec by Friday May 31
• Cameron to review spec by Monday June 3
• Maya to ping Anna (Design) by Friday May 30 about launch date change

Decisions Made

• Dashboard launch pushed from June 15 to June 22 to accommodate longer QA pass

Open Questions

• Upsell modal in v2 or v3? Cameron to decide by Wednesday June 5

Next Meeting Topics

• Review of v1 spec (post-Cameron review)
• Confirmation of v2/v3 upsell decision

That's a complete note set. ~140 words. Captured every operational outcome from the conversation.

The 7-Minute Workflow

The full post-meeting workflow:

Minutes 0-1: Transcript pulled from recording tool (Fathom/Otter/Granola auto-transcribes; Apple Voice Memo + manual paste for in-person).

Minutes 1-2: Paste transcript into Claude with the skill.

Minutes 2-3: Claude returns structured notes.

Minutes 3-7: Review the notes. Fix any misheard names, confirm dates, polish unclear items.

Minute 7: Send via email to attendees. Subject: "[Topic] notes — [Date]"

Total: 7 minutes from end-of-meeting to shipped notes. Most operators currently take 30-60 minutes or don't ship notes at all.

The 2-Hour Send Rule

Notes lose value fast after the meeting ends. Attention decays. Memory fades. Other priorities crowd in. The rule:

Send notes within 2 hours of the meeting ending.

Within 2 hours: high adoption, clear understanding, action items get worked.

After 24 hours: 50% adoption, confusion about specifics, action items drift.

After 48 hours: notes become a recap nobody reads.

The 7-minute Claude workflow makes the 2-hour rule trivially achievable.

Distribution Patterns

Three distribution patterns work for operator meetings:

Pattern 1 — Email to attendees. Default. Simple, asynchronous, archivable.

Pattern 2 — Post to project doc. For meetings tied to specific projects, drop the notes into the project's living doc (Notion page, Linear, shared Drive).

Pattern 3 — Slack thread + pinned message. For team-wide visibility, post notes to a #notes channel or pin in the relevant channel. Faster discovery than email for engaged teams.

For solo operators with mostly external attendees (customers, vendors, partners), Pattern 1 is the default. For team-based work, Pattern 2 or 3.

The Recurring Meeting Compounding

Recurring meetings (weekly standups, monthly client check-ins, quarterly board) benefit from continuity. The workflow:

1. Start each meeting by referencing prior notes ("Last week we agreed to ship the dashboard by June 22 — Maya, on track?")
2. Carry forward unfinished action items
3. Close decided items
4. Add to the running history

Over time, the meeting notes archive becomes the canonical record of what the team has decided, shipped, and is working on. Useful for onboarding new team members, settling disputes about "what did we agree?", and continuity during personnel changes.

What This Skill Does NOT Do

A few situations where AI processing is wrong:

1. Sensitive HR / personnel discussions. Don't process. Take notes manually.

2. Legal / contract negotiations. Don't process via AI. Counsel-grade attention required.

3. Crisis incident response. Real-time facilitation matters; post-hoc AI summary misses context.

4. Therapy / coaching sessions with vulnerable content. Don't process. Privacy bar is higher.

5. Confidential M&A or strategic discussions. Don't process via consumer AI tools. Use enterprise-grade tooling with appropriate data handling.

For everything else (~95% of operator meetings), Claude processing is the right approach.

The Cross-Sell

The Meeting Notes skill is one of ten in Claude Skills for Operators ($7.99). The bundle covers project briefs, email triage, SOPs, RFP responses, hiring filter, investor updates, customer reply, vendor negotiation, and weekly review.

$7.99 once. Most operators recoup the cost on the first week the workflow saves 2+ hours of notes drafting time.

The actionable next step: at your next meeting, record it (with attendees' permission), run the Claude skill on the transcript afterward, and send the notes within 2 hours. Notice how much faster action items get worked when notes hit inboxes while the meeting is still fresh. Most operators don't go back to skipping notes once they feel the difference.