How I Used Claude to Turn 40 Hours of Meeting Notes into 5 Clean Project Briefs (And Got My Evenings Back)
How I Used Claude to Turn 40 Hours of Meeting Notes into 5 Clean Project Briefs (And Got My Evenings Back)
I'm not a "productivity guru." I don't use fancy note-taking apps. I don't have templates for everything. I just take notes in Google Docs — messy, stream-of-consciousness, with half sentences and "???" when I missed something. For years, this was fine. But last month, we kicked off three new projects simultaneously: a mobile app redesign, a customer portal rebuild, and a data migration. Fourteen meetings. Nine stakeholders. Seven external vendors. My notes were chaos. One document had a random "remember to order birthday cake" in the middle of technical requirements. Another had three different versions of the same decision because I asked the same question to three different people. I spent Monday morning trying to sort through it. By Wednesday, I was still lost. Then I asked a friend: "How do you handle meeting notes?" He said: "I don't. I paste them into Claude and ask it to organize them." That Sunday, I tried it.
The Mess I Started With (So You Know I'm Not Exaggerating)
Here's an actual example from my raw notes (unedited, embarrassing):
📝 Raw note snippet from a 90-minute stakeholder meeting:
"Mobile app — home screen redesign — Sarah says too cluttered — maybe remove bottom nav? or keep? John disagrees — push notifications need opt-in by default?? GDPR?? — check with legal — also performance issue on Android reported by 3 users (see ticket #4421) — timeline: Sarah wants June 15 but John thinks July 1 — budget? ask finance — oh and we need analytics integration — who owns that? — follow up with Maria — also cookie banner missing on checkout — legal says fix urgently — backend API for user preferences not ready — Vikram estimated 2 weeks — also Sarah mentioned something about dark mode but I didn't catch it — need to ask again — coffee break at 10:30 — remember to order snacks for next meeting."
That's one paragraph from one meeting. Multiply that by 14 meetings. I had 40 pages of this. Buried in there were actual decisions, real action items, and critical deadlines — but finding them felt like archaeology. I needed to extract 5 clean project briefs: one for the mobile app redesign, one for the customer portal, one for the data migration, plus two internal process documents. I also needed a master action item list with owners and deadlines. Before Claude, this would have taken me 2-3 full workdays. Instead, it took one Sunday afternoon.
My 5-Prompt System That Does the Whole Job
I don't have a paid Claude subscription. I used the free Claude 3.5 Sonnet on claude.ai. The free tier gives you enough context for a few thousand words at a time. Since my 40 pages were too big for one prompt, I split the notes into 5 chunks (roughly one chunk per project). Then I ran the same 5 prompts on each chunk, and combined the outputs at the end. Here's the exact sequence.
Prompt #1: Extract Decisions (The Most Important One)
"You are a project manager assistant. Below are messy meeting notes from a stakeholder meeting about [Project Name]. Extract every single decision that was made in this meeting. A decision is any statement where someone agreed on something, chose an option, or finalized a requirement. Ignore opinions, questions, and ideas that weren't agreed upon. For each decision, write: (1) What was decided, (2) Who made/agreed to the decision, (3) Any caveats or dependencies mentioned. Output as a numbered list."
This prompt alone saved me hours. On my first chunk (mobile app meeting notes), Claude found 9 decisions that I hadn't even realized were decisions. Things like: "Sarah agreed that bottom navigation stays but with only 4 icons" and "John confirmed push notifications require explicit opt-in by May 30." These were buried in paragraphs of waffle. Claude extracted them cleanly.
Prompt #2: Extract Action Items
"From the same meeting notes, extract every action item. An action item is a task assigned to a specific person with a deadline or expected completion time. If the notes don't specify a person or deadline, mark as '[OWNER MISSING]' or '[DUE MISSING]'. For each action, output: Task, Owner, Deadline, Priority (High/Medium/Low based on urgency mentioned in notes)."
My notes had dozens of "we need to..." and "someone should..." statements with no owners. Claude flagged these as missing owners — which forced me to actually follow up with stakeholders. After running this prompt across all 5 chunks, I had 37 action items. 21 had clear owners. 16 needed clarification. That alone was worth the Sunday afternoon.
Prompt #3: Extract Open Questions & Risks
"From the meeting notes, extract all open questions (things that need answers) and risks (things that could go wrong). For open questions, note who was supposed to answer it. For risks, note the potential impact if not addressed. Output as two separate lists."
My notes were full of "???" and "check with legal" and "not sure about X." Claude turned these into a clean list. One risk I had completely missed: "Legal review of cookie banner — no timeline assigned — risk of non-compliance if not fixed by June 1." That was buried in a paragraph about something else. Claude found it.
Prompt #4: Generate Project Brief Summary
"Using the extracted decisions, action items, and open questions from above, write a 1-page project brief for [Project Name]. Include sections: Background (1 paragraph), Key Decisions (bullet list), Open Questions (bullet list), Timeline (if mentioned), Stakeholders (list who is involved). Write in clear, professional language suitable for sharing with the team. Do not add information not present in the notes."
This is where the magic happened. From 40 pages of chaos, Claude generated clean, shareable documents. I ran this for each of the 3 main projects. Each brief was 1-2 pages. I sent them to stakeholders the next morning. Three people replied: "This is so clear — thank you!" One person asked: "How did you get this from the meeting notes?" I told him: "Claude." He didn't believe me.
Prompt #5: Create Master Action Item Tracker
"Combine all action items from all 5 meeting note chunks into a single master list. Remove duplicates (same task mentioned in multiple meetings). Sort by priority (High first). For each action, include: Project, Task, Owner, Deadline, Status (Not Started/In Progress/Waiting). Output as a markdown table."
This gave me a single source of truth. I copied the table into a Google Sheet, added a "Notes" column, and shared it with the team. Now we use it in every weekly status meeting. No more "what did we agree to last time?"
The Before and After: Real Numbers
40 pages of messy notes
14 meetings to re-listen to
2-3 full days to organize
37 action items (16 unclear)
0 clean project briefs
Stakeholders: confused
5 clean project briefs
37 action items (all clear)
1 master tracker sheet
16 open questions to follow up
1 Sunday afternoon (6 hours)
Stakeholders: "thank you!"
The best part? I now reuse the same 5 prompts for every batch of meetings. Last week, I had 6 meetings. I pasted the notes into Claude on Friday afternoon. By Friday evening, I had briefs and action items. Monday morning, I sent them to stakeholders. Total time: 3 hours. Before Claude, that would have been a full Monday. I got my evenings back.
What Didn't Work (Trial and Error)
The first time I tried this, I made mistakes. Here's what I learned:
- Don't paste all 40 pages at once. Claude free tier has a context limit. Paste one meeting at a time, or split into 5-10 page chunks.
- Don't trust the output without scanning. Claude sometimes hallucinates an owner if the notes say "someone should..." It will invent "Owner: Sarah" when Sarah never volunteered. I caught this twice. Always verify.
- Name the project in every prompt. If your notes cover multiple projects, Claude can get confused. I added "[Project: Mobile App Redesign]" to each prompt to keep things separate.
- Run Prompt #1 and #2 separately. I tried combining "extract decisions and action items" into one prompt. Claude mixed them up. Separate prompts = cleaner output.
How This Changed My Workflow Forever
Before Claude, I dreaded the "note cleanup" day. It was the worst part of being a PM. Now, I actually look forward to it — because I know it will take 1-2 hours instead of 8-10. More importantly, my stakeholders trust my notes now. When I send a project brief, they know it's accurate. When I assign action items, they know the owner actually agreed to it. The quality of our meetings has gone up because we spend less time rehashing old decisions and more time making new ones.
💡 The biggest unexpected benefit: My own memory improved. By forcing Claude to extract decisions and actions, I became more aware of what I was missing during meetings. Now I take better notes because I know what Claude needs. It's a virtuous cycle: better notes → better Claude output → better meetings → better notes.
Could Anyone Do This? Yes — Here's How to Start
If you've never used Claude (or ChatGPT) for note processing, here's the simplest possible starting point:
- Step 1: Take your messiest meeting notes from last week. Just copy-paste them into a text file.
- Step 2: Go to claude.ai (free). Create a new chat.
- Step 3: Paste your notes. Then paste Prompt #1 from above (extract decisions).
- Step 4: Look at the output. Is it useful? If yes, run Prompt #2. If no, add more context: "These notes are from a meeting about [topic] with [names of attendees]."
- Step 5: Copy the output into a Google Doc. Share it with your team. Ask: "Does this capture what we decided?"
You don't need to build a whole system. You don't need to process 40 pages at once. Just try it on one meeting. See what happens. For me, that first test took 15 minutes and saved me 2 hours of re-listening to a recording. I was hooked.
The One Resource That Made This Scalable
The 5-prompt system above is just the beginning. I learned how to write these prompts from a resource called AI Prompt Engineering for Profit. It taught me the formula for telling AI exactly what to extract, how to format it, and how to avoid hallucinations. Here's what's inside:
📘 AI Prompt Engineering for Profit
Your complete guide to using AI for business productivity — including meeting notes, client communication, project management, and more.
- ✅ 300 High-Income AI Prompts – including the 5 meeting note prompts above plus 50+ other business prompts
- ✅ 12 Profitable Side Hustles – including "AI note-taking for busy executives" as a service
- ✅ Prompt Formulas That Work – how to structure any request so AI understands exactly what you need
- ✅ Bonus Templates – project brief templates, action item trackers, meeting note templates
300 prompts · Meeting notes system included · 60-day refund
Try It on Your Next Meeting (Not Your Last One)
Don't wait until you're drowning in 40 pages of notes. Try this on your next meeting. Take notes normally (messy is fine). After the meeting, spend 15 minutes running the 5 prompts. See what comes out. If it works, great. If it doesn't, tweak the prompts. Add your own context. The system is free. The time you save is real. For me, that Sunday afternoon was the most productive 6 hours of my month. I went to bed on Sunday not dreading Monday. I had 5 clean documents ready to send. And when my boss asked "what's the status?" I had an answer. Not a messy notebook. Not a vague memory. A real, shareable, actionable project brief. That feeling? Worth every minute of setup.
~3,000 words · 5-prompt system · Turns messy notes into clean briefs · Free Claude tier · Used by 1 PM who got his evenings back
True story from May 2026 · Claude 3.5 Sonnet · Google Docs · Zero paid tools
Comments
Post a Comment