Use Case
AI Meeting Notes with Claude Cowork
Your meetings become structured summaries, instantly.
45 min
→
5 min
writing up a 1-hour meeting
The Problem
Meetings end. The write-up takes forever. It's one of the most universally dreaded post-meeting tasks: turning your rough notes into a structured summary with clear actions, owners, and deadlines that you can actually share and track. It takes 30 to 60 minutes to do properly — time that most people don't have immediately after a meeting, so it gets pushed back, details fade, and action tracking becomes inconsistent.
Claude Cowork solves this in minutes. You paste in your rough notes — they can be genuinely rough, just fragments and bullet points jotted during the meeting — and Claude returns a structured write-up: meeting summary, decisions made, action items with owners and deadlines, and next steps. The output is ready to share in Slack, email, or your project management tool immediately.
Teams that adopt this workflow find a secondary benefit: the discipline of pasting notes into Claude creates a useful archive. Every meeting gets written up consistently. Actions don't get lost. People can search previous meeting summaries to resolve disputes about what was decided. The habit builds institutional memory without any extra effort.
What Claude Does Here
- Converts rough notes into structured meeting summaries
- Extracts action items with owners and deadlines automatically
- Identifies decisions made during the meeting
- Produces formats suitable for email, Slack, Notion, or project tools
- Works from voice transcriptions and auto-generated transcripts
- Handles follow-up emails to attendees from the notes directly
How to Set It Up
1
Take rough notes during the meeting
Don't worry about formatting or completeness. Jot down the key points, decisions, and any actions discussed. Fragments and bullet points are fine. Even very rough notes ("Sarah — chase invoices by Friday, Tom presenting Q1 data next week") give Claude enough to work with.
2
Add meeting context to your prompt
Tell Claude the meeting name, date, and attendees. This gives it the context needed to properly attribute actions and write a coherent summary. You can include this in your saved template so you only need to update the variable details each time.
3
Paste your notes and generate the write-up
Use your meeting notes prompt template, paste in your rough notes, and submit. Claude will return a structured document typically covering: meeting summary, decisions made, action items (with owner and deadline), and any items for discussion next time.
4
Review and send within minutes
Read through the output — it usually needs minimal changes. Correct any misattributed actions or factual tweaks, then distribute. Most teams do this immediately after the meeting while it's fresh, turning a 45-minute chore into a 5-minute task.
5
Use the write-up to generate follow-up emails
Once you have the structured meeting notes, Claude can immediately turn them into follow-up emails for specific attendees or action owners. "Using these meeting notes, write a brief follow-up email to Tom confirming his Q1 presentation for next week."
Example Prompt
Prompt
Write up structured meeting notes from my rough notes below.
Meeting: Weekly Operations Standup
Date: 15 January 2026
Attendees: Emma (Operations Manager), James (Finance), Priya (Project Lead), Tom (IT)
Format I need:
- Meeting summary (3-4 sentences)
- Decisions made
- Action items (with owner and deadline in a table)
- Items to carry forward to next week
Rough notes:
- James — invoicing backlog now cleared, 3 outstanding >60 days, will chase by Friday
- Priya — Phase 2 delivery on track, minor scope creep discussed, will raise change request
- Tom — server migration postponed to Feb, no impact on current projects
- Agreed: weekly report goes to board monthly not weekly (Emma to update template)
- Next week: Tom to demo new ticketing system
What Claude Returns
Claude's Output
MEETING NOTES — Weekly Operations Standup
15 January 2026 | Emma, James, Priya, Tom
Summary
The team reviewed operational progress across finance, project delivery, and IT infrastructure. Invoicing is largely current with three aged accounts being actively chased. Project Phase 2 remains on schedule, with a minor scope change to be formally documented. The server migration has been rescheduled to February without impact to live projects.
Decisions Made
- Weekly operations report will be distributed monthly to the board (not weekly), effective from February
- Phase 2 scope change to be raised as a formal change request rather than absorbed informally
Action Items
| Action | Owner | Deadline |
|--------|-------|----------|
| Chase 3 invoices outstanding >60 days | James | Friday 17 Jan |
| Raise formal change request for Phase 2 scope | Priya | Friday 17 Jan |
| Update board report template (monthly format) | Emma | Friday 24 Jan |
| Demo new ticketing system to the team | Tom | Next standup |
Carry Forward to Next Week
- Tom's ticketing system demo (scheduled for next standup)
- Update on Phase 2 change request status
Frequently Asked Questions
Can Claude work with voice transcriptions from tools like Otter.ai or Teams?
Yes — paste the transcript directly into Claude. Auto-generated transcripts are often rough and repetitive, but Claude handles this well. Specify that you're working from a transcript and ask it to focus on key decisions and actions rather than a verbatim summary.
What format should my rough notes be in?
Whatever you can write quickly during a meeting. Fragmented bullet points, shorthand, incomplete sentences — all fine. Claude is very good at inferring meaning from rough notes. The more you use it, the more you'll find your natural note-taking style works without modification.
Can Claude assign action items to specific people from rough notes?
Yes, if the names or initials appear in the notes. "Sarah — chase supplier" becomes "Chase supplier" attributed to Sarah in the action table. For cleaner attribution, include attendee names in your context and use those names in your rough notes.
How do I make sure the tone matches our company's style?
Include a short style note in your prompt template: "Professional and direct, no jargon, British English" or "Concise and informal, bullet points preferred." If you have an example of a previous write-up in your preferred style, include a short extract as a reference.
Can I do this for external client meetings where I can't share the notes?
You can use Claude to structure meeting notes from any meeting where sharing the content with Claude is acceptable. For highly sensitive client meetings, consider whether the information in the notes is appropriate to paste in. Our
safety guide has more detail on this.
Related Use Cases