Meeting Summary and Progress Generator
Category: Executive Business Difficulty: Intermediate Estimated Tokens: 700-1000 Version: 1.0.0
Description
Create professional meeting summaries that can be shared with team members, clients, or stakeholders. This prompt transforms meeting discussions into clear progress reports and next steps.
The Prompt
Please create a professional meeting summary from this transcript that clearly communicates decisions, progress, and next steps.
MEETING TRANSCRIPT: [Paste your meeting transcript here]
Create a comprehensive summary in this format:
## MEETING OVERVIEW
- **Date**: [Meeting Date]
- **Participants**: [List attendees]
- **Duration**: [Meeting length]
- **Purpose**: [Main meeting objective]
## KEY DECISIONS MADE
Summarize important decisions reached:
1. [Decision topic] - [What was decided and why]
2. [Decision topic] - [What was decided and why]
3. [Decision topic] - [What was decided and why]
## PROJECT PROGRESS UPDATES
Current status of ongoing initiatives:
### [Project Name]
- **Status**: [On track/Behind/Ahead of schedule]
- **Progress**: [What has been completed]
- **Challenges**: [Any obstacles discussed]
- **Next Steps**: [Immediate next actions]
### [Project Name]
- **Status**: [On track/Behind/Ahead of schedule]
- **Progress**: [What has been completed]
- **Challenges**: [Any obstacles discussed]
- **Next Steps**: [Immediate next actions]
## ACTION ITEMS SUMMARY
High-level overview of commitments made:
- [Number] total action items assigned
- [Number] items due this week
- [Number] items due next week
- [Number] items requiring external coordination
## PRIORITY FOCUS AREAS
Most important items requiring attention:
1. [Priority item] - Why it's critical and who's responsible
2. [Priority item] - Why it's critical and who's responsible
3. [Priority item] - Why it's critical and who's responsible
## UPCOMING MILESTONES
Key dates and deliverables discussed:
- [Date]: [Milestone/Deadline] - [Owner]
- [Date]: [Milestone/Deadline] - [Owner]
- [Date]: [Milestone/Deadline] - [Owner]
## RESOURCES AND SUPPORT NEEDED
Support requirements identified:
- [Resource need]: [Details] - [Who will provide]
- [Resource need]: [Details] - [Who will provide]
## NEXT MEETING
- **Date**: [When scheduled or "TBD"]
- **Purpose**: [What will be covered]
- **Preparation Required**: [What team members should prepare]
Make this summary professional enough to share with clients or external stakeholders while being detailed enough for internal team accountability.
---
Prompt by BrassTranscripts (brasstranscripts.com) – Professional AI transcription with high-quality results.
---
Best Practices
Executive-ready formatting: Create summaries polished enough for senior leadership or client sharing.
Progress clarity: Focus on measurable progress and concrete deliverables over vague updates.
Stakeholder transparency: Include enough context for people who missed the meeting to understand decisions.
Action orientation: Emphasize next steps and accountability rather than just documenting discussion.
Use Cases
- Executive reporting - Keep leadership informed on project status and decisions
- Client communication - Share progress updates with external stakeholders
- Team alignment - Ensure all members understand current priorities and status
- Project documentation - Create searchable records of project evolution
- Stakeholder updates - Provide comprehensive progress reports for investors or partners
- Cross-team coordination - Share relevant updates with other departments
Example Output
Weekly Team Progress Meeting Summary
MEETING OVERVIEW
- Date: November 26, 2024
- Participants: Sarah (Marketing), Mike (Operations), Lisa (Development), John (Project Manager)
- Duration: 45 minutes
- Purpose: Weekly progress review and Q4 milestone planning
KEY DECISIONS MADE
- Product Launch Timeline - Moved launch date to December 15th to allow additional testing time
- Budget Allocation - Approved additional $5,000 for external QA testing services
- Marketing Strategy - Decided to focus launch campaign on educational content rather than feature comparisons
- Team Structure - Lisa will lead technical documentation efforts with Sarah providing content strategy support
PROJECT PROGRESS UPDATES
Product Development (Q4 Launch)
- Status: Behind schedule but recoverable
- Progress: Core features 85% complete, UI/UX finalized, initial testing begun
- Challenges: Integration testing revealed performance issues requiring optimization
- Next Steps: Complete performance optimization by December 1, begin user acceptance testing
Marketing Campaign (Launch Support)
- Status: On track
- Progress: Content strategy approved, 60% of educational materials created
- Challenges: Waiting for final product specifications to complete demo videos
- Next Steps: Finalize demo scripts, coordinate with development for product screenshots
ACTION ITEMS SUMMARY
- 12 total action items assigned
- 8 items due this week
- 3 items due next week
- 2 items requiring external vendor coordination
PRIORITY FOCUS AREAS
- Performance Optimization - Critical for launch timeline, Lisa responsible with Mike providing infrastructure support
- External QA Coordination - Must be scheduled immediately to meet December 1 deadline, John managing vendor relationships
- Demo Content Creation - Essential for marketing launch, Sarah leading with Lisa providing technical specifications
UPCOMING MILESTONES
- December 1: Performance optimization complete, external QA begins - Lisa
- December 8: Marketing materials finalized and approved - Sarah
- December 15: Official product launch - John (project coordination)
- December 20: Post-launch analysis and lessons learned session - All team
RESOURCES AND SUPPORT NEEDED
- External QA testing service: $5,000 budget approved - John will coordinate procurement
- Additional server capacity for load testing: Infrastructure team support - Mike will coordinate
- Legal review of marketing claims: Legal team consultation - Sarah will schedule
NEXT MEETING
- Date: December 3, 2024
- Purpose: Final pre-launch review and go/no-go decision
- Preparation Required: All teams prepare launch readiness reports, Lisa provides technical stability assessment
Advanced Techniques
Risk assessment integration: Include identified risks in summaries:
Additionally, document risk factors:
- High-risk items that could impact deadlines
- Dependencies on external parties
- Resource constraints that need attention
- Technical or process risks requiring mitigation
Stakeholder-specific versions: Create targeted summaries:
For each summary, consider creating versions for:
- Executive leadership (high-level decisions and risks)
- Project teams (detailed action items and dependencies)
- Clients (progress updates and milestone confirmation)
- Cross-functional teams (relevant updates and coordination needs)
Integration Tips
Meeting series tracking: Link summaries to show project progression over time.
Action item management: Extract action items for direct import into project management systems.
Documentation archives: Create searchable meeting summary libraries for historical reference.
Resources
- 📖 Detailed Guide: Small Business Meeting Minutes: AI Transcription for Team Accountability
- 🎯 All Prompts: BrassTranscripts AI Prompt Guide
- 🎤 Get Transcripts: Upload Your Audio
Created by BrassTranscripts - Professional AI transcription with high-quality results