The meeting notes problem nobody talks about
Most project managers I know are good at running meetings.
They come prepared, they keep things on track, and they know what came out of the room. The problem isn't the meeting. It's what happens after.
Manual meeting cleanup — turning raw notes into a structured record with decisions, action items, owners, and risks — takes 20 to 45 minutes per meeting. For a PM running five meetings a week, that's two to four hours every week doing something that is entirely administrative.
Over a six-month project, that's up to 100 hours. Spent on formatting.
This week's workflow removes that work.
The Workflow: Meeting Notes to Structured Record in 10 Minutes
What it does: Takes your raw meeting notes — however messy, partial, or stream-of-consciousness — and produces a clean, structured record: decisions made, action items with owners and due dates, risks flagged in passing, and open questions.
What you need: Claude or ChatGPT. Free tier works. No API access. No special setup.
How long it takes: 2 minutes to run the prompt. 5-10 minutes to review the output. Done.
The Prompt
Copy this exactly. Paste it into Claude or ChatGPT, then paste your raw notes below it.
You are a project management assistant. I'm going to give you raw meeting notes. Your job is to extract and structure the following:
DECISIONS: Any decisions made or confirmed during the meeting. Be specific — include what was decided, not just that a decision was made.
ACTION ITEMS: Tasks assigned or agreed to. For each one: the action, who owns it, and any due date mentioned. If an owner wasn't named explicitly, note it as "TBD."
RISKS & ISSUES: Any concerns, blockers, dependencies, or risks flagged — including ones mentioned in passing or embedded in how someone phrased something.
OPEN QUESTIONS: Things that were raised but not resolved.
NEXT STEPS: The agreed next meeting, check-in, or follow-up, if any.
Format each section with a header and a numbered list. If a section has no items, write "None identified."
Here are the notes:
[PASTE YOUR NOTES HERE]
That's it. Run it, review the output, make any corrections. Your meeting record is done.
Tips from real use
If your notes are truly messy (sentence fragments, typos, shorthand), add this line before your notes: "These notes are informal and may contain shorthand, typos, and incomplete sentences — extract meaning, not exact wording."
If someone's name isn't in the notes, the AI will flag action items as "TBD" on owner. Fill those in during your review — takes 30 seconds.
If you use Granola or another meeting tool, paste the transcript or auto-summary instead of handwritten notes. The prompt handles both.
The weekly rollup (bonus)
Once you've run this prompt after each meeting, you can consolidate a full week into a single status update:
I'm going to give you structured meeting records from [X] meetings this week. Produce a weekly rollup that includes: top decisions made, all open action items with owners, top risks and issues, and any unresolved open questions. Keep it concise — this is for a weekly status update, not a full record.
[PASTE YOUR STRUCTURED MEETING RECORDS HERE]
Five meetings becomes one status update in 3 minutes.
What's coming next week
Next week: the RAID log. Specifically, how to stop manually hunting through meeting notes for risks and dependencies — and let the AI catch everything, including the items that get mentioned in passing and usually disappear.
If that's a pain point for you, you'll want that one.
The Output is published weekly by OutputKit.
Questions or feedback? Reply to this email.
newsletter.outputkit.com