Meeting Minute Summarization AI Prompts for EAs

You have been there. Another two-hour leadership meeting ends, and you are sitting with 45 minutes of transcript that needs to become a clear, actionable summary before the executive sees it tomorrow morning. You know the key points were discussed, but extracting them while capturing the nuances and action items feels like a second full-time job.

Most executive assistants spend two to three hours per meeting on documentation alone. The actual work of synthesizing insights, identifying patterns, and surfacing strategic implications gets lost in the time spent simply transcribing what was said.

AI changes this by taking raw transcript and turning it into structured, actionable summaries in a fraction of the time. It can identify decisions made, actions assigned, topics discussed, and questions raised. You bring the context; AI brings the speed.

AI Unpacker provides prompts designed to help executive assistants summarize meeting minutes with clarity, depth, and actionability.

TL;DR

• AI can cut meeting documentation time by 70-80%.
• Structured summaries outperform chronological transcripts.
• Action items need owners, deadlines, and context.
• Decision documentation requires capturing both outcome and reasoning.
• Follow-up tracking turns meeting insights into results.
• AI cannot replace your judgment about what matters most.

Introduction

Meeting minutes serve two purposes: record-keeping and accountability. The problem is that most meeting documentation fails at both. Transcripts are too long to be useful. Summaries are too vague to be actionable. The result is meetings that end without clear decisions, action items without owners, and follow-ups that fall through the cracks.

The best executive assistants know that meeting minutes are not about capturing everything. They are about capturing what matters. And what matters depends on context: the participants, the topics, the decisions, and the follow-up needs.

AI cannot know what your executive cares about most. But it can help you structure the raw material of a meeting transcript into formats that serve different purposes: quick reference, detailed documentation, action tracking, and strategic analysis.

1. Meeting Summary Framework

Before summarizing, you need a framework for what makes meeting minutes useful. The framework determines structure, depth, and prioritization.

Prompt for Meeting Summary Framework

Develop meeting minute summarization framework.

Meeting context:
- Weekly leadership team meeting
- Attendees: CEO, CTO, CFO, VP Sales, VP Marketing, 2 Executive Assistants
- Duration: 90 minutes
- Frequency: Weekly recurring

Meeting summary principles:

Principle 1: Different summaries for different audiences
- Executive summary: 1 page, key decisions and actions
- Detailed notes: Full context for record-keeping
- Action tracker: Standalone list for follow-up

Principle 2: Structure over chronology
- Decisions first (what was decided)
- Actions second (who does what by when)
- Discussions third (key points, context)
- Open items fourth (parking lot, unresolved)

Principle 3: Capture the why, not just the what
- Document the reasoning behind decisions
- Note alternatives considered
- Record concerns raised
- Track consensus or disagreement

Standard meeting summary structure:

Section 1: Decision Log
- [Decision made]
- [Date effective]
- [Rationale summary]
- [Owner]

Section 2: Action Items
- [Action] | [Owner] | [Deadline] | [Priority]
- Format for easy tracking and follow-up

Section 3: Key Discussions
- [Topic 1]: Summary of discussion, key points, decision or open
- [Topic 2]: ...
- Keep to 2-3 sentences per topic

Section 4: Open Items / Parking Lot
- Items that need follow-up but were not resolved
- Owner and deadline if assigned

Section 5: Next Meeting Preparation
- Topics to prepare for next meeting
- Information to gather in advance

Summary length guidelines:
- Executive summary: 1 page maximum
- Full meeting notes: 3-5 pages
- Action tracker: 1 page or less
- Decision log: Ongoing additions

Quality checklist:
- [ ] All action items have owners and deadlines
- [ ] All decisions have context and rationale
- [ ] Open items are flagged for follow-up
- [ ] Next steps for next meeting are identified
- [ ] Format matches executive's preferences

Tasks:
1. Create standard template for meeting type
2. Define structure for different summary types
3. Build quality checklist
4. Set up distribution workflow

Generate meeting summary framework with templates and structure.

2. Transcript to Summary Prompts

The core challenge is transforming raw transcript into structured summary. AI can help you do this consistently and quickly.

Prompt for Transcript Summarization

Develop transcript summarization process.

Raw transcript context:
- Sales pipeline review meeting
- Duration: 60 minutes
- Attendees: VP Sales, 5 Account Executives, Sales Operations
- Topic: Q4 pipeline review and deal troubleshooting

Summarization principles:

Principle 1: Extract, do not paraphrase
- Identify the actual words that capture meaning
- Do not rephrase unless clarity requires it
- Quote key statements when they add value

Principle 2: Group by topic, not speaker
- Organize by subject matter
- Track topics across speakers
- Note where opinions diverge

Principle 3: Prioritize by impact
- Decisions matter most
- Actions matter second
- Discussions matter third
- Background context matters least

Step-by-step summarization:

Step 1: Initial scan
- Read through transcript quickly
- Identify major topics (5-7)
- Note approximate time markers
- Flag decision or action language

Step 2: Decision extraction
- What was decided?
- Who decided?
- What reasoning was given?
- When does it take effect?
- Any dissenting opinions?

Step 3: Action item extraction
- What tasks were assigned?
- Who is the owner?
- What is the deadline?
- What is the priority?
- Any dependencies?

Step 4: Discussion synthesis
- For each major topic:
  - What was the issue?
  - What perspectives were shared?
  - What was the outcome?
  - Any open questions?

Step 5: Quality review
- Check all actions have owners
- Check all decisions have context
- Verify timeline accuracy
- Ensure summary is scannable

AI prompt for structured extraction:

Prompt: "Analyze this meeting transcript and extract:
1. Decisions made (with context and rationale)
2. Action items (with owner, deadline, priority)
3. Key discussion points (with summary and outcome)
4. Open items (with owner if assigned)

Format output as structured markdown for easy reference."

Output structure:
- Use clear headings and bullet points
- Bold action item owners
- Include dates and deadlines
- Add [COMPLETED], [IN PROGRESS], [BLOCKED] status markers

Tasks:
1. Define summarization process for meeting type
2. Create extraction prompt
3. Build review checklist
4. Set up distribution format

Generate transcript summarization process with prompts.

3. Action Item Extraction

Action items are the most important output of any meeting. Getting them right requires precision in capturing what was asked, who is responsible, and when it is due.

Prompt for Action Item Extraction

Develop action item extraction process.

Meeting context:
- Cross-functional project planning meeting
- Participants: PM, Engineering Lead, Design Lead, Marketing Lead
- Topic: Q1 product launch planning

Action item extraction principles:

Principle 1: Be specific about the task
- "Follow up" is not an action item
- "Contact vendor about timeline extension by Thursday" is
- Capture exactly what needs to happen

Principle 2: Identify the owner clearly
- One owner per action item
- If multiple people involved, note primary owner
- Role or name both acceptable (match meeting context)

Principle 3: Set clear deadlines
- Specific date if possible
- "End of week" only if date is clear from context
- Note if deadline is hard or soft

Principle 4: Capture priority and dependencies
- Critical path items flagged
- Dependencies on other actions noted
- Priority level if discussed

Action item format:

Standard format:
[Action description] | [Owner] | [Deadline] | [Priority]

Priority levels:
- P1: Critical, must complete
- P2: Important, should complete
- P3: Nice to have, complete if time allows

Example action item extraction:

Original: "We should probably get marketing to do some kind of campaign around the launch. Maybe reach out to them?"

Extracted action:
"Schedule kick-off meeting with marketing to discuss Q1 launch campaign scope and timeline" | [PM name] | [1 week] | [P2]

Original: "Engineering needs to give us a timeline for the API changes"

Extracted action:
"Provide technical timeline for API changes required for Q1 launch" | [Engineering Lead] | [3 days] | [P1]

Decision vs Action distinction:

Decision: "We will use vendor X for this project"
Action: "Confirm vendor X contract by [date]" or "Onboard vendor X for [specific work]"

Decisions are not action items, but they often spawn action items. Note the connection.

Status tracking:
- [ ] Not started
- [ ] In progress
- [ ] Blocked
- [ ] Complete

Review process:
- Read each action item back to confirm understanding
- Ask: "Is this what you meant?"
- Confirm owner accepts responsibility
- Note any dependencies

Tasks:
1. Define action item format for your organization
2. Create extraction criteria
3. Build review and confirmation process
4. Set up tracking system

Generate action item extraction process with templates.

4. Decision Documentation

Decisions are the output of meetings, but they are often poorly documented. Good decision documentation captures not just what was decided, but why.

Prompt for Decision Documentation

Develop decision documentation process.

Decision context:
- Strategic planning meeting
- Topic: Go-to-market approach for new product line
- Participants: CEO, VP Sales, VP Marketing, VP Product

Decision documentation principles:

Principle 1: Capture outcome and reasoning
- What was decided?
- Why was this decision made?
- What alternatives were considered?
- What information informed the decision?

Principle 2: Note the decision-making process
- Who was involved in the decision?
- Was it consensus, vote, or executive decision?
- Any dissenting opinions recorded?
- Any conditions or contingencies?

Principle 3: Include relevant context
- What problem is this decision solving?
- What constraints were considered?
- What are the success criteria?
- What happens if the decision proves wrong?

Decision documentation template:

---
## Decision: [Title]

**Date**: [When decided]
**Meeting**: [What meeting]
**Participants**: [Who was involved]

**Decision**:
[Clear statement of what was decided]

**Context**:
[What problem or opportunity this addresses]

**Alternatives considered**:
- [Option 1] - [why not chosen]
- [Option 2] - [why not chosen]
- [Option 3] - [why not chosen]

**Information considered**:
- [Data or analysis that informed decision]
- [Stakeholder input]
- [External factors]

**Rationale**:
[Explanation of why this was the right decision]

**Conditions**:
- [Any conditions that must be met]
- [Any assumptions this decision is based on]

**Follow-up**:
- [Any monitoring or review planned]
- [When decision will be revisited]

**Owner**: [Who owns this decision]
---

Documentation best practices:
1. Document immediately while context is fresh
2. Review with key stakeholders for accuracy
3. Store in accessible, searchable location
4. Link related decisions together

Decision vs discussion distinction:
- Discussion: "We talked about the problem of X"
- Decision: "We decided to do Y because of Z"

If no explicit decision was made, note that:
"Discussion only - no decision made. Topic to be revisited at [meeting]."

Tasks:
1. Create decision documentation template
2. Define decision-making process markers
3. Build searchable storage system
4. Set up review cadence

Generate decision documentation process with templates.

5. Follow-Up and Tracking

Meeting insights are only valuable if they lead to action. A follow-up system turns meeting outputs into outcomes.

Prompt for Meeting Follow-Up Tracking

Develop meeting follow-up tracking system.

Meeting context:
- Weekly leadership meeting
- Output: 8 action items, 3 decisions, 2 open topics

Follow-up principles:

Principle 1: Immediate confirmation
- Send summary within 24 hours
- Confirm action items with owners
- Verify deadlines are realistic

Principle 2: Progress tracking
- Weekly check on all open items
- Update status as progress is made
- Escalate blocked items promptly

Principle 3: Closure confirmation
- Confirm when actions are complete
- Document any changes to deadlines
- Note any decisions that were reversed or modified

Follow-up workflow:

Day 1: Summary distribution
- Send summary to all participants
- Confirm action item owners
- Note any immediate deadlines

Day 3-7: Progress check
- Follow up on any items with approaching deadlines
- Check for blockers
- Update status in tracking system

Day 14: Mid-cycle review
- Review all open action items
- Check in with owners
- Note any timeline changes

Day 30 or next meeting: Full review
- Status report on all items
- Decisions that have been implemented
- Open items still pending

Tracking system elements:
1. Action item list (sorted by deadline)
2. Status per item (not started, in progress, blocked, complete)
3. Owner contact info
4. Link to meeting notes
5. Link to related decisions

Status update format:

**Action Item Update - [Date]**

| Item | Owner | Status | Notes |
|------|-------|--------|-------|
| [Action 1] | [Name] | [Status] | [Update] |
| [Action 2] | [Name] | [Status] | [Update] |

Escalation triggers:
- Deadline passed without completion
- Item blocked for more than 3 days
- Scope or priority change requested

Escalation process:
1. Check in with owner directly
2. Raise to executive if no resolution
3. Document reason for delay
4. Adjust timeline if necessary

Tasks:
1. Create tracking template
2. Define review cadence
3. Build escalation process
4. Set up distribution list

Generate meeting follow-up tracking system with workflows.

FAQ

How do I handle meetings where I am also a participant?

Focus on capturing what matters for follow-up. If you are actively participating, designate someone else to take notes if possible. If not, prioritize your note-taking during less active moments and fill in details immediately after the meeting.

Should I send meeting summaries to everyone or only to relevant parties?

Send to all participants as a default. Others may have context you do not realize they need. For sensitive discussions, send only to participants. When in doubt, ask the meeting leader.

How do I handle meetings that run over time and go off track?

Document what actually happened, not what was supposed to happen. Note the actual topics discussed and decisions made. If significant time was spent on non-agenda items, note that in the summary. This is often as important as the planned content.

What should I do if action items are unclear from the meeting?

Follow up immediately. Message the relevant person for clarification before documenting. It is better to ask right away than to document something incorrectly. Note in the summary that clarification was sought and provided.

How do I track recurring action items across multiple meetings?

Create a running project list separate from individual meeting notes. Update status at each meeting. Note any recurring deadlines (weekly reports, monthly reviews) separately so they are not lost in meeting-by-meeting tracking.

Conclusion

Meeting minutes are not administrative burden — they are strategic infrastructure. Well-documented meetings enable follow-up, track accountability, and preserve institutional memory.

AI Unpacker gives you prompts to structure summaries, extract actions, document decisions, and track follow-ups. But the judgment about what matters most, the relationships that help you clarify ambiguities, and the discipline to follow up consistently — those come from you.

The goal is not comprehensive documentation. The goal is meetings that lead to outcomes.