Why Meeting Follow-Up Is Your Best Delegation Opportunity
Meeting minutes are where good intentions go to die. You've just spent 60 minutes aligning stakeholders, making decisions, and assigning responsibilities—then you spend another 45 minutes manually extracting action items, assigning owners, and formatting updates. The cognitive load isn't in attending meetings; it's in translating conversation into executable tasks.
- Time saved: Reduces 45 minutes of post-meeting admin to under 5 minutes
- Consistency gain: Standardizes action item formatting across all team meetings (no more "who was supposed to do what?" confusion)
- Cognitive load: Frees mental bandwidth to focus on strategic follow-through instead of clerical note-taking
- Cost comparison: Eliminates the need for dedicated meeting coordinators for teams under 15 people
Why This Task Tests Your Delegation Skills
Converting meeting minutes to action items reveals whether you understand specification versus execution. A junior employee can't read your mind—they need clear criteria for what constitutes an "action item" versus a "discussion point," how to assign ownership when it's ambiguous, and what format makes tasks actually actionable.
This is delegation engineering, not prompt hacking. Just like training a new coordinator, you must define:
- Decision thresholds (when does "we should explore X" become a task?)
- Ownership rules (who gets assigned when multiple people contributed?)
- Quality standards (what makes a well-formed action item?)
Configuring Your AI for Meeting Minutes Processing
| 5C Component | Configuration Strategy | Why it Matters |
|---|---|---|
| Character | Executive assistant with 10+ years in corporate operations, trained in project management methodologies | Ensures AI understands business context (distinguishes FYI updates from commitments) and applies professional judgment to edge cases |
| Context | Meeting type (standup/planning/retrospective), team size, your organization's action item tracking system (Asana/Jira/Monday) | Different meetings have different output needs—a daily standup requires lightweight tasks; a quarterly review needs strategic initiatives with milestones |
| Command | Extract action items using SMART criteria, assign ownership based on explicit commitments, flag ambiguous responsibilities | Prevents vague outputs like "Team to review proposal" (not actionable) and ensures every item has a clear DRI (Directly Responsible Individual) |
| Constraints | Only extract items with explicit deadlines or decisions; ignore discussion/context; flag items missing owner or due date | Stops AI from inventing tasks that weren't agreed upon and surfaces gaps requiring your clarification before distribution |
| Content | Provide 2-3 examples of well-formed action items from past meetings in your format | Teaches AI your team's specific conventions (e.g., whether you use due dates vs. sprint assignments, how you phrase acceptance criteria) |
The Copy-Paste Delegation Template
<role>
You are an executive assistant with 10+ years supporting leadership teams in fast-paced environments. You specialize in meeting operations and project coordination, with expertise in translating conversations into trackable deliverables.
</role>
<context>
I need you to process meeting minutes and extract action items. My team uses [Asana/Monday/Jira/other] for task tracking. This was a [meeting type: team standup/planning session/client call/board meeting].
Our action item standards:
- Every item must have an owner (DRI - Directly Responsible Individual)
- Every item must have a due date or milestone
- Tasks should be specific and measurable (SMART framework)
- Distinguish between decisions made, action items assigned, and topics for future discussion
</context>
<instructions>
Follow this sequence:
1. **Read the entire transcript** to understand meeting context and identify distinct discussion threads.
2. **Extract action items** by identifying:
- Explicit commitments ("I'll draft the proposal by Friday")
- Assigned responsibilities ("Sarah, can you coordinate with legal?")
- Decisions requiring implementation ("We're moving forward with Option B—someone needs to notify vendors")
3. **Structure each action item** in this format:
- **Task:** [Verb-led, specific description - max 10 words]
- **Owner:** [Name mentioned or "UNASSIGNED" if ambiguous]
- **Due Date:** [Explicit date mentioned or "TBD" if not specified]
- **Context:** [One sentence explaining why this matters or dependencies]
- **Source:** [Quote the relevant sentence from minutes that triggered this item]
4. **Flag ambiguities** in a separate "Needs Clarification" section for items where:
- No clear owner was assigned
- Multiple people discussed it but no one committed
- Due date is implied but not stated
5. **Summarize key decisions** made during the meeting (non-task outcomes that provide context for these action items).
Output as a structured markdown document ready to paste into our project management tool.
</instructions>
<input>
Paste your meeting minutes, transcript, or notes below:
Example format:
"Team standup 1/23/26 - Sarah mentioned the Q1 report is delayed because legal hasn't reviewed the compliance section. John said he'd follow up with legal by EOW. Maria asked if we're still targeting Feb 5 launch—consensus was yes but we need final designs from the agency first. Tom volunteered to check in with them..."
[PASTE YOUR MEETING NOTES HERE]
</input>The Manager's Review Protocol
Before distributing AI-generated action items, apply these quality checks:
- Accuracy Check: Cross-reference each action item against your own meeting notes—did AI correctly interpret who committed to what? Verify names are spelled correctly and ownership assignments match what was actually said (not assumed).
- Hallucination Scan: Ensure AI didn't invent deadlines that weren't mentioned or combine separate discussion points into one action item. Check that "Context" field accurately reflects the meeting conversation, not AI's assumptions about why the task matters.
- Tone Alignment: Confirm task phrasing matches your team's communication style—some teams prefer direct commands ("Update client by Friday"), others use collaborative language ("Coordinate with client for Friday update"). Adjust to maintain team culture.
- Strategic Fitness: Review the "Needs Clarification" section critically—are these genuine ambiguities requiring your input, or did AI fail to use contextual clues? Strong delegation means knowing when AI appropriately escalated uncertainty versus when it should have inferred from context.
Build your SOP Library, one drop at a time.
We are constantly testing new ways to delegate complex work to AI. When we crack the code on a new "Job to be Done," we send the SOP directly to you, fresh from the lab.
Our Promise: High signal, low noise. We email you strictly once a week (max), and only when we have something worth your time.
When This SOP Isn't Enough
This SOP solves single-meeting processing, but managers typically face cross-meeting task management—tracking recurring action items, synthesizing decisions across multiple sessions, and building institutional memory. The full 5C methodology covers workflow chaining (connecting meeting outputs to project dashboards), custom role configuration (teaching AI your team's specific decision-making patterns), and systematic quality control (building review checklists for your specific business context).
For one-off meetings, this template works perfectly. For managing ongoing meeting cadences, product councils, or cross-functional initiatives, you'll need the advanced delegation frameworks taught in Sorai Academy.
For one-off meetings, this template works perfectly. For managing ongoing meeting cadences, product councils, or cross-functional initiatives, you'll need the advanced delegation frameworks taught in Sorai Academy.