Meeting Notes Prompt Templates
AI prompt templates for meeting notes. Create clear summaries, action items, and follow-ups.
Overview
Meeting notes capture decisions, action items, and context that would otherwise be lost. But most meeting notes are either too detailed to be useful or too sparse to be actionable. Effective meeting notes prompts help you extract what matters, decisions made, tasks assigned, and context needed, in a format people will actually reference.
Best Practices
1
Structure notes around decisions and action items, not chronological discussion flow
2
Assign every action item to a specific person with a due date
3
Capture the 'why' behind decisions so future readers understand context
4
Send notes within 24 hours while the meeting is fresh
5
Use consistent formatting so recipients know where to find key information
Prompt Templates
1. Meeting Summary Generator
Summarize this meeting about [TOPIC] with [ATTENDEES]. Key points discussed: [DISCUSSION_POINTS]. Decisions made: [DECISIONS]. Action items: [ACTION_ITEMS]. Include: executive summary (2-3 sentences), decisions with rationale, action items with owners and dates, and any open questions for follow-up.
Topic: Q4 product roadmap prioritization, Attendees: Product team + Engineering leads, Discussion Points: feature requests from sales, technical debt backlog, resource constraints, Decisions: prioritize customer dashboard over mobile app, defer API v2 to Q1, Action Items: Sarah to create dashboard spec by Friday, Mike to estimate dashboard effort by next Tuesday
Meeting Summary: Q4 Product Roadmap Prioritization Date: October 15, 2024 | Attendees: Product + Engineering Leads --- Executive Summary We aligned on Q4 priorities, choosing to focus on the customer dashboard over mobile app development. API v2 is deferred to Q1 2025 to allow proper scoping. --- Decisions Made 1. **Customer dashboard is Q4 priority** - Rationale: 3 enterprise deals blocked on this feature; mobile app has no immediate revenue impact - Trade-off: Mobile app pushed to Q1 at earliest 2. **API v2 deferred to Q1 2025** - Rationale: Current scope is unclear; rushing would create technical debt - Next step: Discovery sprint in November to define scope 3. **Technical debt gets 20% of sprint capacity** - Rationale: Accumulating issues affecting velocity; need sustained investment --- Action Items | Action | Owner | Due Date | |--------|-------|----------| | Create dashboard product spec | Sarah | Oct 18 | | Estimate dashboard engineering effort | Mike | Oct 22 | | Draft API v2 discovery plan | James | Oct 25 | | Update sales team on timeline | Sarah | Oct 16 | --- Open Questions - Do we need a designer for dashboard, or can we use existing patterns? - Should we communicate mobile app delay to customers who requested it?
After any meeting where decisions were made or work was assigned
- •Send notes to all attendees plus anyone affected by decisions
- •Highlight action items for each person so they can quickly find their tasks
2. Action Item Extractor
Extract action items from these meeting notes or transcript: [MEETING_CONTENT]. For each action item, identify: the task, the owner, the due date (or suggest one if not stated), and any dependencies. Format as a clear checklist.
Meeting notes: We discussed the marketing campaign launch. John mentioned he'd get the landing page copy done soon. Maria said she needs the copy before she can finalize designs. Tom will coordinate with the ad agency but needs budget approval first. We should probably have everything ready for the Nov 1 launch.
Action Items Extracted Target launch date: November 1 --- | # | Task | Owner | Due Date | Dependencies | Status | |---|------|-------|----------|--------------|--------| | 1 | Complete landing page copy | John | Oct 21 | None | Pending | | 2 | Finalize landing page designs | Maria | Oct 25 | Needs #1 (copy) | Blocked | | 3 | Get budget approval for ad agency | [Unassigned] | Oct 18 | None | Pending | | 4 | Coordinate with ad agency | Tom | Oct 28 | Needs #3 (budget) | Blocked | --- Flags: ⚠️ Budget approval has no owner assigned, who needs to action this? ⚠️ "Soon" is vague, I've suggested Oct 21 for copy to allow time for design iteration ⚠️ Timeline is tight, only 2 weeks to launch with dependencies Recommended next step: Assign budget approval owner immediately (blocker for Tom)
When you have messy notes or a transcript and need to extract clear next steps
- •Flag any action items without clear owners, these fall through cracks
- •Surface dependencies so people understand what's blocking what
3. One-on-One Notes Template
Create notes for a 1:1 meeting between [MANAGER] and [DIRECT_REPORT]. Topics discussed: [TOPICS]. Updates shared: [UPDATES]. Feedback given: [FEEDBACK]. Career discussion: [CAREER_TOPICS]. Action items: [ACTIONS]. Format for the manager's records with follow-up reminders.
Manager: Lisa, Direct Report: David, Topics: project status, workload concerns, promotion timeline, Updates: API project on track, feeling overwhelmed with support tickets, Feedback: great job on client presentation but needs to delegate more, Career Topics: interested in tech lead role, wants more architecture exposure, Actions: Lisa to reassign some support tickets, David to shadow senior architect next sprint
1:1 Notes: Lisa ↔ David Date: October 15, 2024 --- Project Updates - API project: On track for Nov 15 delivery - No blockers, but David is stretched thin --- Workload Discussion - David is overwhelmed with support ticket volume (spending ~40% of time on support) - This is affecting his project work and energy - Agreed: Lisa will reassign some support tickets to reduce load to ~20% --- Feedback Given ✓ Positive: Client presentation last week was excellent, clear, confident, well-prepared △ Growth area: Needs to delegate more; tendency to take on too much personally - Specific example: Took 3 extra tickets last sprint instead of pushing back - Agreed approach: Practice saying "I can take this on if we deprioritize X, which do you prefer?" --- Career Development - Goal: Tech lead role (12-18 month horizon) - Interest: More architecture and system design exposure - Action: Shadow senior architect (James) during next sprint's design sessions - Lisa to discuss tech lead path with skip-level in next month --- Action Items | Action | Owner | Due | |--------|-------|-----| | Reassign 50% of David's support tickets | Lisa | Oct 18 | | Arrange shadowing with James | Lisa | Oct 20 | | Practice delegation language in next sprint | David | Ongoing | | Discuss tech lead path with VP Eng | Lisa | Nov 1:1 | --- Follow-up for Next 1:1 - Check in on workload after support reassignment - Debrief on architecture shadowing experience - Review delegation practice, any situations to discuss?
After 1:1 meetings to track ongoing development and commitments
- •Keep 1:1 notes in a running document so you can track themes over time
- •Reference previous action items at the start of each 1:1
4. Client Meeting Recap
Write a client meeting recap for [CLIENT_NAME] following our meeting about [TOPIC]. Attendees: [ATTENDEES]. Key discussion points: [DISCUSSION]. Client concerns or questions: [CONCERNS]. Commitments we made: [OUR_COMMITMENTS]. Commitments they made: [THEIR_COMMITMENTS]. Format as a professional email to send to the client.
Client: Acme Corp, Topic: implementation kickoff, Attendees: Their PM (Jennifer) and IT lead (Robert), our CS lead (Amanda) and solutions engineer (Chris), Discussion: timeline expectations, integration requirements, training needs, Concerns: worried about data migration complexity and user adoption, Our Commitments: provide migration plan by Friday, schedule training for week of Nov 4, Their Commitments: send us access credentials and sample data export by Wednesday
Subject: Acme Corp Implementation Kickoff - Recap & Next Steps Hi Jennifer and Robert, Thank you for taking the time to meet with us today to kick off your implementation. We're excited to partner with Acme Corp on this project. Here's a summary of what we covered and our agreed next steps: --- **Key Discussion Points** 1. **Timeline**: Targeting go-live by December 1, with a soft launch to pilot group on November 15 2. **Integration Requirements**: - Salesforce integration (bi-directional sync) - SSO via Okta - Data export to your existing BI tool 3. **Training Approach**: - Admin training for Robert's team (week of Nov 4) - End-user training sessions (week of Nov 11) - We'll provide recorded sessions for future reference --- **Your Questions & Our Responses** *Data migration complexity*: We'll provide a detailed migration plan by Friday that maps your current data structure to our system. Chris has done similar migrations for companies your size and will personally oversee this. *User adoption concerns*: We'll share our adoption playbook and can discuss specific tactics for your team during training planning. --- **Action Items** *From our team:* - [ ] Send data migration plan, Amanda, Friday, Oct 18 - [ ] Schedule admin training sessions, Amanda, By Oct 21 - [ ] Prepare integration specifications document, Chris, Oct 22 *From Acme:* - [ ] Provide sandbox access credentials, Robert, Wednesday, Oct 16 - [ ] Send sample data export, Robert, Wednesday, Oct 16 - [ ] Confirm training attendee list, Jennifer, Oct 21 --- Please let us know if we missed anything or if you have questions before our next check-in. Best regards, Amanda
After any significant client meeting to create a written record and confirm alignment
- •Send client recaps within 24 hours while details are fresh
- •Always include both what you committed to AND what they committed to
5. All-Hands Meeting Notes
Create notes for an all-hands meeting held on [DATE]. Presenter: [PRESENTER]. Topics covered: [TOPICS]. Key announcements: [ANNOUNCEMENTS]. Q&A highlights: [QA_SUMMARY]. Format for company-wide distribution with clear sections for quick scanning.
Date: October 15, 2024, Presenter: CEO Sarah, Topics: Q3 results, Q4 priorities, new hires, policy updates, Announcements: hit $10M ARR milestone, expanding to Europe in Q1, new VP of Sales starting Nov 1, remote work policy updated, Q&A: questions about Europe expansion timeline, concerns about workload during expansion, question about holiday schedule
All-Hands Meeting Notes October 15, 2024 --- 🎉 Key Announcements **1. We hit $10M ARR!** We crossed the $10M milestone last week, three months ahead of plan. This is a testament to everyone's work this year. Team celebration details coming soon. **2. European expansion launching Q1 2025** We're opening our first European office in London, with plans to expand to Germany by end of 2025. More details in the Q&A section below. **3. New VP of Sales joining November 1** Marcus Thompson joins us from [Previous Company]. He'll be spending his first two weeks meeting teams across the company. **4. Remote work policy update** Effective November 1: - Core collaboration hours: 10am-3pm local time - In-office expectation changing from 3 days to 2 days/week - Full policy document in the HR portal --- 📊 Q3 Results Snapshot | Metric | Target | Actual | |--------|--------|--------| | ARR | $9.5M | $10.2M | | Net Revenue Retention | 105% | 112% | | New Customers | 45 | 52 | | Employee NPS | 40 | 47 | --- 🎯 Q4 Priorities 1. **Product**: Ship customer dashboard (top customer request) 2. **Sales**: Close 60 new accounts to hit $12M ARR by year-end 3. **Operations**: Prepare infrastructure for European launch 4. **People**: Hire 15 roles across Sales, Engineering, and CS --- ❓ Q&A Highlights **Q: What's the timeline for Europe, and will there be relocation opportunities?** A: London office opens March 2025. We'll post relocation opportunities in November for those interested. Initial team will be 5-8 people. **Q: How do we manage workload during expansion while maintaining current customer experience?** A: We're hiring ahead of the expansion, not after. Q4 hiring is specifically to build capacity before Europe launches. **Q: What's the holiday schedule this year?** A: Company closed Dec 23 - Jan 1. Details in the HR portal by end of week. --- 📅 Upcoming Dates - Nov 1: New VP of Sales starts - Nov 1: Updated remote policy effective - Nov 15: Q4 hiring kickoff - Dec 15: Next all-hands meeting --- Recording available in [Company Portal]. Questions? Reach out to your manager or post in #ask-leadership.
After company-wide meetings to ensure everyone has access to the same information
- •Use emojis and clear headers to make long notes scannable
- •Include links to recordings and related documents for those who missed it
Common Mistakes to Avoid
•
Writing notes that are too detailed, no one will read a transcript; focus on decisions and actions
•
Forgetting to assign owners to action items, unowned tasks don't get done
•
Waiting too long to send notes, context fades quickly; send within 24 hours
Frequently Asked Questions
Meeting notes capture decisions, action items, and context that would otherwise be lost. But most meeting notes are either too detailed to be useful or too sparse to be actionable. Effective meeting notes prompts help you extract what matters, decisions made, tasks assigned, and context needed, in a format people will actually reference.
Related Templates
Sales Email Prompt Templates
AI prompt templates for sales emails. Create compelling cold outreach, follow-ups, and closing messages.
Business Proposal Prompt Templates
AI prompt templates for business proposals. Create persuasive proposals that win clients and projects.
Business Report Prompt Templates
AI prompt templates for business reports. Create clear, actionable reports for stakeholders.
Have your own prompt to optimize?