How to Use Claude for Meeting Notes — From Rambling Notes to Action Items in 60 Seconds

How to Use Claude for Meeting Notes — From Rambling Notes to Action Items in 60 Seconds

You just left a 45-minute meeting. Your notes look like this:

talked about Q3 launch timeline, sarah thinks we need 2 more weeks
bob wants to cut scope on the analytics dashboard
need to check with legal on the new TOS
budget approved for contractor - max 15k
design review moved to friday
someone needs to update the roadmap
mike's team blocked on API docs

These notes are technically accurate and practically useless. Nobody knows who owns what. There are no deadlines. The decisions are buried in the stream of consciousness. By tomorrow, half the context is gone.

Claude turns this into structured, actionable output in under a minute. Here is exactly how.

The Core Meeting Notes Prompt

This is the prompt you will use for 90% of your meetings. Copy it, bookmark it, and paste your raw notes at the bottom.

Here are my raw notes from a meeting. Transform them into a structured summary with these exact sections:

## Meeting Summary
(2-3 sentences covering what the meeting was about and the key outcome)

## Decisions Made
(Bullet list of every decision that was finalized. If something was discussed but not decided, it goes in Open Questions instead.)

## Action Items
(Table format with columns: Action | Owner | Deadline | Priority)
- If no owner was mentioned, put "UNASSIGNED" and flag it
- If no deadline was mentioned, put "NEEDS DATE" and flag it
- Priority: High / Medium / Low based on context

## Open Questions
(Anything that was raised but not resolved)

## Key Context
(Important background information mentioned that people who were not in the meeting would need to know)

Rules:
- If my notes are ambiguous, flag the ambiguity rather than guessing
- Do not add information that is not in the notes
- Use the actual names mentioned in the notes

Raw notes:
[PASTE YOUR NOTES HERE]

Here is what Claude produces from those messy notes above:

Meeting Summary: Team discussed Q3 launch timeline and agreed to evaluate a 2-week extension. Budget for a contractor was approved with a $15K cap. Several blocking issues were identified around API documentation and legal review.

Decisions Made:

• Contractor budget approved: maximum $15,000
• Design review rescheduled to Friday

Action Items:

Action	Owner	Deadline	Priority
Evaluate 2-week timeline extension and present recommendation	Sarah	NEEDS DATE	High
Define reduced scope for analytics dashboard	Bob	NEEDS DATE	High
Check with legal on new TOS	UNASSIGNED	NEEDS DATE	High
Update product roadmap	UNASSIGNED	NEEDS DATE	Medium
Provide API documentation to Mike's team	UNASSIGNED	NEEDS DATE	High

Open Questions:

• Will the 2-week extension be approved or will scope be cut instead?
• What specific analytics features would be cut in the reduced scope?

Key Context:

• Mike's team is currently blocked waiting on API documentation
• The 2-week extension vs. scope cut appears to be an either/or decision

Notice what happened. Claude separated decisions (done) from action items (to do). It flagged unassigned owners and missing deadlines — exactly the things that cause tasks to fall through cracks. It identified open questions that need follow-up. And it added context that makes the notes useful to someone who was not in the room.

For Transcript-Based Notes

If you record meetings and have full transcripts (from tools like Otter, Fireflies, or even a voice memo you ran through Whisper), use this expanded prompt:

Here is a transcript from a [MEETING TYPE] meeting with [NUMBER] participants.

Extract and organize the following:

1. SUMMARY: 3-4 sentence overview of the meeting
2. DECISIONS: Every decision made, with who made it
3. ACTION ITEMS: Table with Action | Owner | Deadline | Priority
4. DISAGREEMENTS: Any points where participants disagreed (note both positions)
5. OPEN QUESTIONS: Unresolved items
6. FOLLOW-UP MEETING NEEDED: Yes/No, and if yes, what topics need to be covered

Important:
- Attribute statements to the correct speaker
- Distinguish between someone suggesting something and the group agreeing to it
- If someone committed to doing something, that is an action item even if it was said casually

[PASTE TRANSCRIPT HERE]

The DISAGREEMENTS section is particularly valuable. Decisions often get made by whoever talks loudest, and the disagreement gets lost. Having it documented means the team can revisit it if the decision does not work out.

The Weekly Standup Formatter

Standups are a different beast — shorter, repetitive, and focused on blockers. Here is a dedicated prompt:

Here are raw notes from our team standup. Format them as:

For each person:
- **[Name]**
  - Yesterday: [what they completed]
  - Today: [what they are working on]
  - Blockers: [any blockers, or "None"]

Then add a section:
## Team Blockers Requiring Action
(List any blockers that need someone outside the team to resolve)

## Cross-Dependencies
(Anything where one person's work depends on another person's output)

Standup notes:
[PASTE HERE]

The cross-dependencies section is the real value-add. Standups are supposed to surface these, but they usually get mentioned and forgotten. Having them listed explicitly means you can address them immediately.

The 1-on-1 Meeting Formatter

One-on-ones require a different structure — they are about people, not projects.

Here are my notes from a 1-on-1 with [NAME]. Format them as:

## Topics Discussed
(Brief summary of each topic)

## Their Concerns
(Anything they raised as a worry, frustration, or problem — preserve their perspective)

## Commitments
| Who Committed | To What | By When |

## Career/Growth Notes
(Anything related to their development, goals, or feedback)

## Follow Up Next Meeting
(Topics to revisit)

Notes:
[PASTE HERE]

Sending the Notes: The Email-Ready Format

Once Claude structures your notes, you often need to send them to the team. Here is a quick follow-up prompt:

Take the structured meeting notes above and convert them into a brief email.

Format:
- Subject line: [Meeting name] — [Date] — Key Decisions & Action Items
- Open with 1-sentence summary
- List decisions as bullets
- List action items with owners bolded
- Close with "Reply to this email if any owners or deadlines need correction"
- Keep the total email under 200 words

That closing line is important. It gives people a specific, low-friction way to correct the record instead of silently disagreeing with the notes.

Making This a Habit

The prompt itself takes 60 seconds. The hard part is remembering to do it. Here is what works:

1. During the meeting, take rough notes in whatever format is natural for you. Do not try to be structured in real-time.
2. Immediately after the meeting, paste your notes into Claude. Do this before your next meeting, while context is fresh.
3. Send within 10 minutes. The faster you send structured notes, the more your team trusts them as the source of truth.

Sonnet 4.6 handles meeting notes perfectly — you do not need Opus for this. The speed advantage of Sonnet means you get your structured notes back in seconds.

For more productivity-focused prompts like these, browse our prompt collection. Our cheat sheet has a quick-reference section for meeting and workplace prompts you can print and keep at your desk.

The 60-Second Meeting Follow-Up

Here is the workflow: meeting ends, you open Claude, paste raw notes, get structured output, paste into email, send. Total time: about 60 seconds of actual effort. Your team gets clear action items with owners. Nothing falls through the cracks. And you build a searchable record of every decision made.

Start with your next meeting. Take your messiest notes and paste them into the core prompt above. The difference between "we talked about stuff" and "here are 5 action items with owners and deadlines" is the difference between meetings that waste time and meetings that move projects forward.