Meeting Notes & Action-Item Systems
Stop losing decisions and owners the moment a meeting ends
The real failure isn’t note-taking, it’s follow-through
Almost every agency takes some form of meeting notes. Almost none reliably convert those notes into owned, tracked action items. The notes sit in a doc, everyone nods along in the meeting, and two weeks later nobody remembers who was supposed to send the client the revised timeline. This is the exact bottleneck the workflow audit in Lesson 2 often surfaces — and it’s one of the fastest wins in this course to fix.
From raw notes or transcript to structured action items
Whether you’re working from a live transcript, a recording tool’s auto-transcript, or your own typed notes, the conversion prompt is the same shape: extract decisions and owners explicitly, don’t just summarize.
Turn these internal meeting notes into a structured action-item
list. For each item, capture: the task, who owns it (use names
from the notes - if unclear, mark [OWNER UNCLEAR]), and any
deadline mentioned or implied. Separate into "decisions made"
and "open questions still unresolved." Don't invent owners or
deadlines that weren't actually stated.
MEETING NOTES:
Weekly sync, Sept 9. Attendees: Priya, Marcus, Dana.
Discussed the Kepler account - Marcus flagged that the landing
page copy is still waiting on client feedback, been a week.
Priya said she'd follow up with the client directly today.
Decided to push the launch date to Sept 20 instead of Sept 16
since we're blocked. Dana raised that we're also behind on the
Foothill Dental report, needs to go out by Friday. Nobody
confirmed who's writing it. Also discussed whether to raise
Kepler's retainer at renewal - tabled, need more data on hours
logged before deciding.Notice “[OWNER UNCLEAR]” in the instructions. That flag is more valuable than a clean-looking list with a guessed owner — a guessed owner quietly becomes nobody’s job, exactly the failure mode this lesson is fixing.
What good output looks like
| Category | Example from the notes above |
|---|---|
| Decision made | Kepler launch date moved to Sept 20 |
| Action item, owned | Priya to follow up with Kepler client on landing page feedback — today |
| Action item, unclear owner | [OWNER UNCLEAR] Foothill Dental report — due Friday |
| Open question, not decided | Whether to raise Kepler’s retainer at renewal — needs hours-logged data first |
The unclear-owner flag isn’t a failure of the system — it’s the system working. It forces someone to actually assign the Foothill report in the next thirty seconds instead of letting it silently slip.
Route items into wherever your team actually works
A clean list in a doc that nobody reopens is only marginally better than no list. Ask Claude to format the output to match your actual task system — a Slack-postable summary, a CSV-style table you can paste into project management software, or a short client-facing recap for items that involve them.
Reformat the action items above into a short Slack message I can
post in our #team channel right after this meeting - use @Name
mentions for owners, bold the deadlines, keep it under 100 words.Key principle: An action item that isn’t in the system your team checks daily doesn’t exist. The conversion from notes to items is only half the job — routing it to the right surface is the other half.
Watch out: If your meetings involve client-confidential details, follow the redaction guardrails from Lesson 3 before pasting a transcript — recorded calls often capture more sensitive detail than typed notes would.
Try it: Take notes from your next internal meeting and run them through the action-item prompt above. Count how many items would have had an unclear or assumed owner if you’d written the list yourself.