Overview

You're heading into a meeting with your VP, your finance director, and two vendor representatives. You have scattered notes: some Slack messages about problems they've been experiencing, a spreadsheet with performance metrics from last month, an email from your team about issues discovered in testing. You're pulling these together in the car before the meeting. You walk in unprepared, fumble through a few points, and the vendor asks something you should have anticipated. Everyone leaves confused about next steps.

Then the follow-up: "Can you send a summary of what we discussed?" You spend 30 minutes reconstructing conversation from notes. You guess at action items. You send it out, and someone says "that's not what we decided."

This is the meeting preparation and follow-up tax that operations leaders pay multiple times every week. AI can eliminate most of this. For any meeting with defined input (here's the context, here's who's coming, here's what we need to accomplish), AI can generate: a briefing document, an agenda, meeting notes from a transcript, and a clean action items list.

Pre-Meeting Briefing Documents

Before a meeting, you usually need context. Where are we on the project? What's the status? What are the key issues? Instead of assembling this manually, ask AI to generate it:

PRE-MEETING BRIEFING PROMPT

I have a meeting coming up. Generate a one-page briefing document that covers:

Meeting: [Who and when]
Attendees: [Names and titles/roles]
Purpose: [What are we deciding/discussing?]
Key decisions needed: [What needs to be decided?]

Background:
[Paste recent Slack conversations, email chains, project updates, performance reports]

For the briefing document, provide:

1. EXECUTIVE SUMMARY (2-3 sentences)
   Quick recap of where we are and what's at stake
2. CONTEXT & HISTORY
   How did we get here? What's the background someone joining late needs to know?
3. CURRENT STATUS
   Where are we now on this issue/project?
4. KNOWN ISSUES OR CONCERNS
   What's broken or uncertain?
5. DECISION POINTS
   What decisions do we need to make in this meeting?
6. KEY QUESTIONS TO RAISE
   What should I ask to move the conversation forward?
7. RECOMMENDED OUTCOMES
   What should we leave this meeting with?
8. VENDOR/PARTICIPANT-SPECIFIC TALKING POINTS
   What should I emphasize with each participant to get buy-in?

You paste your scattered notes, and you get back a crisp one-page briefing. Read it in 10 minutes before the meeting. Walk in prepared. You know what matters, what questions to ask, and what outcome you want.

Meeting Agenda Generation

A good meeting agenda saves time because everyone knows what's being discussed and roughly how long each topic will take:

MEETING AGENDA PROMPT

Generate an agenda for this meeting. The agenda should:
- Be time-boxed (total [X] minutes)
- Start with decision points
- Allow for questions/discussion
- End with clear next steps
- Include discussion time (not just presentations)

Meeting: [Title]
Duration: [X minutes]
Attendees: [Who]
Purpose: [Why are we meeting?]
Topics to cover:
- [Topic 1]
- [Topic 2]
- [Topic 3]

Key decisions that need to be made:
- [Decision 1]
- [Decision 2]

Constraints:
- [Anyone who needs to leave early?]
- [Any topics that must be first?]

Create an agenda that fits the topics into the time block, with time allocations for each. Start with critical decisions, leave time for discussion. Assume 2-3 minutes per topic for logistics (transitions, clarifications).

You get back an agenda like:

AGENDA - Vendor Performance Review (60 minutes)

1. Welcome & context setting (2 min)
   - Recap: This is annual vendor review. We're evaluating Q1-Q3 performance.
2. Q1-Q3 performance scorecard review (8 min)
   - Share vendor scorecard (quality metrics, delivery metrics, cost performance)
   - Vendor responds to data
3. Issues & concerns discussion (10 min)
   - Our concerns: Late deliveries in Q2, Quality issues in August shipment
   - Vendor response: What went wrong, how they're fixing it
4. Pricing & contract discussion (10 min)
   - Current contract rates vs market rates
   - Opportunity for rate negotiation for next year
   - Any contract changes needed?
5. Improvement plan (10 min)
   - If we continue relationship: What improvements will we see?
   - If we're discontinuing: What's the transition plan?
6. Decision: Continue/Renegotiate/Replace? (10 min)
   - Clear decision on contract going forward
   - If renegotiating: What are we asking for?
7. Next steps & timeline (5 min)
   - Who does what next?
   - When do we reconvene?
   - What's the decision deadline?

Time allocation: Critical decisions get the time. Admin stuff is brief.

PRO TIP: If vendor is presenting, send them the agenda 24 hours early so they can prep. Everyone shows up more ready.

Share this agenda with attendees 24 hours before the meeting. Everyone shows up prepared and knowing what to expect.

Try This Now: Meeting Notes and Action Items Extraction

Scenario: You just finished a 90-minute meeting with your operations team, a vendor, and your CEO about a major process change. You have rough notes and a Zoom recording. You need to send a summary email with what was discussed and who's doing what next.

Step 1: Capture Meeting Notes

Meeting: Process Optimization Initiative (Invoice Processing)
Date: March 10, 2026
Attendees: You (Ops Director), Tom (Team Lead), Sarah (Ops Manager), Jennifer (Finance), CEO, Vendor Rep

Meeting notes (rough):

Topic: Invoice processing cycle time reduction
- Current: 5 days average (too slow)
- Goal: 3 days (industry standard)
- Tom said we're losing 2 days to manual reconciliation
- Sarah said there's a tool (Invoice IQ) that can automate this
- Cost is $15K upfront + $500/month
- Needs 3-week implementation
- Jennifer will get budget approval
- Tom will evaluate the tool with his team
- Decision: try pilot in one region for 4 weeks starting next month

Finance involvement:
- Jennifer said finance wants visibility into the process
- Concern: How does this affect their month-end close?
- Sarah will set up a call with finance to align

Training/change management:
- Need to train team on new process
- Need to update the handbook
- Sarah will create training materials
- Tom will roll out training in selected region

Timeline:
- Tom: evaluate tool, send recommendation by Friday (March 14)
- Jennifer: get budget approval by March 21
- Sarah: coordinate finance alignment call by March 15
- You (me): approve implementation plan by March 21
- Pilot starts: April 1
- Pilot ends & decision on rollout: May 1

CEO input:
- CEO supports initiative
- Wants evidence that this improves quality/accuracy (not just speed)
- Wants to see results before full rollout

Concerns/risks:
- What if tool doesn't work as advertised?
- How do we handle exceptions/edge cases?
- What if new process breaks something?
- Plan: Use pilot as test; rollback if needed

Next steps:
- Tom: evaluate tool, send recommendation by Friday
- Jennifer: get budget approval
- Sarah: set up finance alignment, create training
- You: approve implementation plan
- Vendor rep will send implementation timeline by EOD today

Step 2: Create the Extraction Prompt

MEETING SUMMARY & ACTION ITEMS PROMPT

Here are rough notes from a meeting. Generate a clean summary with:

1. EXECUTIVE SUMMARY (2-3 sentences)
   - What was discussed?
   - What's the main outcome/decision?
2. DISCUSSION SUMMARY (by topic)
   - Topic 1: What was discussed? What are the key points?
   - Topic 2: ...etc
   - Any disagreements or concerns raised?
3. DECISIONS MADE
   - What decisions did we make?
   - What are we committing to?
   - What's NOT yet decided?
4. ACTION ITEMS
   - Who is doing what?
   - By when?
   - What's the success criteria?
   - Who depends on what?
5. OPEN QUESTIONS
   - What didn't we decide?
   - What do we need more information on?
   - What's still ambiguous?
6. RISKS & MITIGATION
   - What concerns were raised?
   - How are we managing them?
7. NEXT MEETING/CHECKPOINT
   - When do we reconvene?
   - What should we have completed by then?
   - Who needs to send update before then?

Meeting notes:
[PASTE ROUGH NOTES ABOVE]

Assume the reader is someone who wasn't in the meeting. Make it clear enough they understand what happened and what's expected of them. Also: assume readers are busy, so be concise.

Step 3: AI Generates the Summary

MEETING SUMMARY - Process Optimization Initiative: Invoice Processing

EXECUTIVE SUMMARY:
We approved moving forward with an automation tool (Invoice IQ) to reduce invoice processing time from 5 days to 3 days. We're running a 4-week pilot in one region starting April 1, with full rollout decision on May 1. Tool costs $15K upfront + $500/month. Finance is involved to ensure month-end close isn't affected.

DISCUSSION SUMMARY:

Invoice Processing Challenge
Current process: 5 days average, primarily due to 2 days of manual reconciliation. Goal: 3 days (industry standard). This affects cash flow and ties up team time.

Automation Solution
Vendor presented Invoice IQ tool: automates reconciliation, integrates with our accounting system, requires 3-week implementation. Cost: $15K + $500/month. Expected benefit: 2-day reduction in cycle time.

Finance Alignment
Jennifer (Finance) raised concern: How does this affect month-end close timing? Answer: Month-end closes on days 1-3 of next month; tool won't affect that, but Finance wants visibility into new process. Sarah will schedule alignment call with Finance Director to review.

Implementation Approach
Decision: Pilot in one region (to test before full rollout). Tom will lead evaluation; Sarah will manage training. CEO wants evidence that tool improves quality (accuracy) not just speed. We'll use pilot to validate both speed and quality improvements.

DECISIONS MADE:
1. Proceed with Invoice IQ tool pilot (4 weeks, one region, starting April 1)
2. Involve Finance in process design (Sarah to schedule alignment call)
3. Create training program for new process (Sarah will develop)
4. Measure both speed AND quality in pilot (Tom will track)
5. Make full rollout decision on May 1 based on pilot results
6. If pilot successful: full rollout by Q2 end; if not: we discontinue tool and pursue alternatives

NOT YET DECIDED:
- Which region for pilot (Jennifer to choose)
- What "success metrics" look like for the May 1 decision
- How to handle exceptions/edge cases in new process (Tom to document during pilot)

ACTION ITEMS:

Tom (Team Lead) - Due Friday, March 14
- Evaluate Invoice IQ tool with his team
- Run requirements review (does it meet our needs?)
- Send recommendation: proceed with pilot or not?
- Success criteria: Tool meets requirements, 3-week implementation is realistic

Jennifer (Finance) - Due March 21
- Secure budget approval for pilot ($15K + $500/month)
- Identify which region for pilot testing
- Success criteria: Budget approved, region selected

Sarah (Ops Manager) - Due March 15 (call), March 21 (training plan)
- Schedule meeting with Finance Director (alignment call)
- Agenda: explain new process, understand Finance concerns/requirements
- Develop training materials for new process
- Create implementation plan with Tom
- Success criteria: Finance agrees with approach; training materials ready

You (Ops Director) - Due March 21
- Review Tom's evaluation
- Approve implementation plan
- Review training materials
- Approve April 1 pilot start date
- Success criteria: Plan is realistic, team is ready, risks are identified

Vendor Rep
- Send detailed implementation timeline by EOD today (March 10)
- Confirm support availability during 3-week implementation
- Confirm support during 4-week pilot

OPEN QUESTIONS:
1. Which region is best for pilot? (Jennifer to determine)
2. What qualifies as "successful" for May 1 rollout decision? (Need to define metrics)
3. How do we handle invoice exceptions or edge cases in new process? (Tom to assess during eval)
4. What's the rollback plan if tool doesn't work? (Tom to document)

RISKS & MITIGATION:
1. Tool doesn't work as advertised
- Mitigation: 4-week pilot tests it before full rollout; rollback plan ready

1. Implementation takes longer than 3 weeks
   - Mitigation: Start April 1; if not done by April 21, pilot delay (not critical)
2. Team resistance to change
   - Mitigation: Training program (Sarah developing); address concerns early
3. Finance month-end close is disrupted
   - Mitigation: Pilot doesn't touch month-end; Finance alignment call to clarify
4. Quality issues if speed increases without automation for all steps
   - Mitigation: CEO requires quality metrics; we're tracking both speed and accuracy

NEXT CHECKPOINT:
April 1: Pilot launches (should have Tom's eval, budget approval, training complete)
May 1: Pilot review & full rollout decision (do we roll out company-wide or kill the initiative?)

DELIVERABLES BEFORE APRIL 1:
- Tom's tool evaluation (done by March 14)
- Budget approval (done by March 21)
- Training materials (done by March 21)
- Implementation plan (done by March 21)
- Finance alignment completed (done by March 15)

Step 4: Send the Summary

Copy this into an email. Send it to everyone who was at the meeting. They confirm: "Yes, that's what we decided." You now have a clear record that everyone agrees on.

Meeting preparation for different meeting types

Different meetings need different preparation. A status update meeting needs different prep than a decision meeting. A vendor meeting is different from an exec update. Use the right template for each type so you're not over-preparing or under-preparing.

Meeting Preparation for Different Scenarios

For a status update meeting (weekly standup with your manager): Generate a briefing with current metrics, recent changes, anything that needs escalation. Keep it brief (5 min read time). Organize by: what's on track, what's at-risk, what needs decision.

For a decision meeting (we need to pick a vendor, or pick a process, or approve spend): Generate a briefing with options, pros/cons of each, your recommendation, and risk assessment. Organize by: decision criteria, options evaluated, why you're recommending option X.

For a vendor meeting (quarterly business review): Generate a briefing with vendor performance data (metrics, issues, recent interactions), what you want to accomplish in the meeting (negotiate better terms, address issues, plan for next quarter), and your BATNA (best alternative to negotiated agreement, what happens if vendor underperforms?).

For an executive/board update: Generate a briefing with high-level summary, key metrics, strategic highlights, any asks from the team, and risks/opportunities to be aware of. Keep it executive-focused (big picture, not details).

For a cross-functional or all-hands meeting: Generate an agenda that includes decision items AND time for team discussion. Make sure decision-making process is clear. Not everyone needs to decide, but everyone should understand how decisions are made.

Use different prompts for different meeting types. After three or four meetings, you'll have prompt templates you reuse.

Follow-Up Email Drafting

After the meeting, you often need to send follow-up emails to specific people. AI can draft these:

FOLLOW-UP EMAIL PROMPT

Draft a follow-up email based on this meeting. The email is to [recipient name], who has this action item:

[Action item description]

The email should:
- Thank them for attending
- Recap their specific action item
- Give context (why this matters, who else is involved)
- Set a clear deadline
- Explain what comes next
- Ask for confirmation they can deliver
- Include any specific requirements or acceptance criteria

Meeting context:
[Brief recap of what was discussed]

Tone: Professional but warm, collaborative not commanding

Also include: What do they need from others to complete this? Any blockers we should address now?

You get an email like:

Subject: Follow-up: Invoice Processing Tool Evaluation - Due Friday

Hi Tom,

Thanks for your thoughtful input in yesterday's process optimization meeting. We're excited about the potential to cut our invoice processing time from 5 days to 3 days, and your evaluation of the Invoice IQ tool is critical to deciding whether we move forward.

Here's what we need from you by Friday, March 14:

Evaluate the Invoice IQ tool with your team. Specifically, we need your assessment of:
1. Does it meet our requirements? (Can it handle our exception cases? Does it integrate with our system?)
2. Can we realistically implement in 3 weeks? (What would block us?)
3. Are there any gaps or concerns?

Your evaluation will inform Jennifer's budget request (she needs it by March 21) and our decision to pilot in April. If we decide to proceed with the pilot, your team will own the implementation and training, so your honest assessment now is essential.

I know you're busy. Here's what I can provide to help:
- Vendor contact info for technical questions
- Our current invoice processing documentation (so they understand our complexity)
- List of exception cases we handle

What other information do you need to complete this evaluation? Let me know if there are blockers.

Appreciate the quick turnaround.

Thanks,
[Your name]

Professional, clear, and written in 5 minutes instead of 20 minutes of crafting.

Building a Meeting Workflow

Once you've done this a few times, build it into your calendar:

• 24 hours before meeting: Generate briefing document and agenda. Review/refine. Send to attendees.
  - 1 hour before meeting: Read briefing. Prepare key questions. Make sure you know what outcome you want.
  - During meeting: Take rough notes. Record if possible (Zoom/Teams does this automatically). Focus on listening and asking good questions.
  - Immediately after meeting: Paste notes (or transcript) into summary prompt. Generate clean summary and action items.
  - Same day (ideally within 2 hours): Send summary email to attendees. Ask for corrections: "Here's what I understood we decided. Does this match your understanding?"
  - 1 day later: If attendees confirmed, send individual follow-up emails to action item owners (using the follow-up email prompt).

This process takes: 20 minutes for briefing/agenda, 10 minutes during meeting for notes, 5 minutes for summary generation, 10 minutes for follow-up emails. Total: 45 minutes per meeting. Without AI, this was easily 60+ minutes of meeting prep and follow-up.

Pro tip: If your meeting is recorded (Zoom, Teams, or you record on your phone), you can paste the transcript directly into the summary prompt and AI will generate the summary from the transcript. No manual note-taking needed. Just listen, engage, and let AI turn the recording into a summary. This is incredibly powerful for 60+ minute meetings where manual notes get sloppy.

What to Do Monday Morning

• Pick your next important meeting. Ideally something with multiple attendees and decisions to make, or a complex vendor/partner discussion.
  - Generate a pre-meeting briefing document. Use the prompt above. Review it. Send it to attendees 24 hours before.
  - Create an agenda based on the briefing. Time-box each topic. Send with briefing.
  - Record the meeting or take detailed notes.
  - Use the summary prompt to extract action items. Send to attendees within 2 hours for confirmation.
  - Follow up with individuals on their action items. Use the follow-up email prompt. Personalize slightly if needed.
  - Track action items through completion. Weekly standup: "Where are we on last week's action items?"

Key Takeaways

• Pre-meeting preparation prevents wasting time. A briefing document and agenda means everyone walks in knowing what to discuss. You spend less time on context-setting, more time on decisions.
  - Post-meeting summaries prevent confusion about what was decided. AI-generated summaries from notes or transcripts are usually better than hand-written notes because AI can structure them clearly.
  - Action item tracking prevents things from falling through the cracks. Clear action items, owners, and deadlines in writing. Follow up weekly on status.
  - Different meeting types need different prep. Status meetings, decision meetings, vendor meetings. Use different prompts and structures for each.
  - Recorded meetings can be automatically summarized. If your meeting is recorded, paste the transcript and skip the note-taking. Huge time savings.
  - Follow-up emails are the difference between decisions made and decisions implemented. A clear follow-up email that recaps action items and deadlines matters. People execute when they know what's expected.
  - Everyone should leave a meeting knowing: what was decided, who's doing what, and when it's due. If anyone is confused, the meeting wasn't successful. Your summary should make it crystal clear.

Frequently Asked Questions

Q: Should I share the briefing document with all attendees?

A: Yes. If attendees know what to expect, they come prepared. You have better meetings. Send it 24 hours early so people have time to review.

Q: What if the meeting takes a different direction than the agenda?

A: That's fine. The agenda is a guide, not a straitjacket. Use it to stay roughly on track, but allow for important conversations that emerge. If the conversation goes somewhere valuable, follow it. Just make sure you still cover the critical decisions before time runs out.

Q: Can I use AI-generated summaries as the official meeting record?

A: For informal meetings, yes. For official decisions or regulated processes, you might want a human review and sign-off. But for most operational meetings, AI-generated summaries are reliable and sufficient.

Q: How do I know if action items from the summary are accurate?

A: Send the summary to attendees for confirmation within 2 hours. "Here's what I understood we decided. Does this match your understanding?" Get explicit confirmation before it's official. This takes 5 minutes and prevents confusion.

Q: Should I let people know that I'm using AI to generate summaries and follow-ups?

A: No need. The summary is accurate and useful regardless of how it was generated. How you created it is irrelevant to the reader. What matters is that action items are clear and accurate.

Q: What if someone doesn't agree with the action item assigned to them?

A: That's a sign of miscommunication in the meeting. Address it immediately. Send follow-up: "I understood you were taking on X. Is that correct, or do we need to reassign?" Better to clarify in the moment than have work not get done.

Q: How long should a meeting summary be?

A: One page for most meetings. 2-3 pages for complex decisions or long meetings. If your summary is more than that, either: (1) the meeting was too long, or (2) you're including too much detail. Summaries should be scannable.