Meeting Minutes Template: 5 Formats for Every Meeting Type
5 meeting minutes templates for board, standup, client, project, and brainstorm meetings. Includes markdown examples, type-to-format matching, and how AI eliminates templates entirely.
The Template Problem
You search for "meeting minutes template." You get a generic Word document. Generic headers. Generic sections. It doesn't match your actual meeting.
If you're documenting a board meeting, you need governance, decisions, and action items tracked to executives. A daily standup needs velocity, blockers, and quick status updates—not a formal record. A client meeting requires relationship context and deliverables. A brainstorm session should capture raw ideas and rough direction, not polished minutes.
One template doesn't capture all of this. Most teams either:
- Start with a template that almost fits
- Modify it halfway through the meeting
- End up with inconsistent documentation across meetings
- Waste time later trying to extract what actually matters
This is where the right format makes all the difference.
Why Meeting Type Matters
Research from AI meeting tools shows that teams using format-matched documentation report higher decision follow-through and clearer accountability [Sembly AI, 2025].
Here's the reality: Different meetings need different structures because they serve different purposes:
- Board meetings document governance and strategic decisions
- Team standups track status and remove blockers fast
- Client meetings create an external record of promises and timelines
- Project meetings align stakeholders on scope and next steps
- Brainstorms capture creative thinking before it disappears
Forcing one format across all meeting types creates friction: You're either over-documenting informal meetings (bloating standup notes with irrelevant formal sections) or under-documenting formal meetings (losing critical decisions in a casual layout).
The 5 Meeting Minutes Templates
Each template below matches a specific meeting purpose. Copy the structure, fill in your details, and adapt the sections to fit your context.
Template 1: Board Meeting Minutes (Formal Governance)
Use this for executive, board, or C-suite meetings where decisions are recorded for legal and governance purposes.
Metadata:
- Meeting date, time, duration
- Attendees (title/role)
- Absent members
- Facilitator name
Structure:
# Board Meeting Minutes – [Date]
## Attendees
- CEO (Present)
- CFO (Present)
- Chief Product Officer (Present)
- Board Member – Finance (Absent)
## Agenda Items
### 1. Q1 Financial Review
**Discussion:** CFO presented consolidated P&L. Revenue exceeded forecast by 8%. Operating costs tracked below budget.
**Decision:** Approved Q1 financial statements.
**Action Items:**
- [ ] CFO: File audited statements with SEC (Due: April 15)
- [ ] Accounting: Distribute investor packet (Due: April 20)
### 2. Product Roadmap Approval
**Discussion:** CPO reviewed H2 roadmap. Three major features discussed. Board questioned timeline on mobile release.
**Decision:** Approved H2 roadmap with mobile launch moved to September.
**Action Items:**
- [ ] CPO: Brief product team on timeline change (Due: April 12)
- [ ] CEO: Update investor calls with revised roadmap (Due: April 18)
## Motions & Votes
- Motion to approve Q1 financials: 5-0 (Passed)
- Motion to approve H2 roadmap: 4-1 (Passed)
## Next Meeting
May 15, 2026 – Quarterly Board Review
## Signed
CEO: ________________ Date: ________
Key elements:
- Formal attendance tracking (Present/Absent/Represented)
- Decisions clearly stated
- Motions documented with vote counts
- Audit trail with due dates and assigned owners
- Signature block for legal compliance
Template 2: Team Standup Minutes (Status & Blockers)
Use this for daily or weekly team standups where speed and clarity are essential. Focus on what changed, what's blocked, and what's next.
Structure:
# Team Standup – [Date]
**Duration:** 15 minutes
**Attendees:** [Names]
## What We Completed
- **John:** Merged auth refactor (3 commits)
- **Sara:** Fixed search indexing bug in production
- **Mike:** Completed API documentation for v2 endpoints
## What We're Working On
- **John:** Integrating Redis cache (60% done)
- **Sara:** Load testing on staging environment
- **Mike:** Writing SDK implementation guide
## Blockers
| Person | Blocker | Owner | Target Resolution |
|--------|---------|-------|-------------------|
| Sara | Waiting on infrastructure team for staging environment specs | Infrastructure Lead | Today 5pm |
| Mike | Design feedback on API error messages not received | Design Team | Tomorrow 10am |
## Quick Decisions
- **Approved:** Bump Node.js from v18 to v20 in production (starting next week)
- **Pending:** Database migration timeline (discuss with ops lead)
## Next Standup
Tomorrow, 9:30am
**Notes:** Keep updates to 1 minute per person max.
Key elements:
- Completed, in-progress, blockers in three separate sections
- Blocker table with owner and resolution target
- Decisions captured but marked as approved/pending
- No decision-making; execution focus only
Template 3: Client Meeting Minutes (Relationship Record)
Use this when meeting with external stakeholders. Emphasize clarity on what was discussed, what was agreed, and what the client is responsible for.
Structure:
# Client Meeting Minutes
**Client Name:** Acme Corp
**Meeting Date:** April 9, 2026
**Attendees:**
- Client: VP Product (Acme Corp)
- Client: Procurement Lead (Acme Corp)
- Our Side: Account Manager, Technical Lead, Solutions Architect
## Meeting Objective
Discuss Phase 2 requirements and timeline for Acme Corp's data integration project.
## Topics Discussed
### Project Scope Review
- **What we reviewed:** Phase 1 deliverables (data pipeline, reporting dashboard)
- **Client feedback:** Reporting is accurate; pipeline needs performance optimization for 10M+ rows
- **Outcome:** We agreed to optimize in Phase 2 before scaling to production data
### Phase 2 Scope
- **Client requirement:** Real-time alerts for data quality issues
- **Our proposal:** Alert rules configurable via dashboard; integrates with Slack/Teams
- **Client decision:** Approved. Requested Slack integration priority.
### Timeline & Resource
- **Phase 2 start:** May 1, 2026
- **Phase 2 end:** July 31, 2026
- **Resource on client side:** Part-time data engineer (to be assigned by April 18)
## Commitments & Next Steps
### What We Committed To
- [ ] Deliver optimization plan by April 16 (Technical Lead)
- [ ] Build Slack alert integration (Phase 2 priority feature)
- [ ] Weekly sync meetings every Thursday, 10am PT
### What Client Committed To
- [ ] Assign data engineer by April 18
- [ ] Provide sample 10M-row dataset for optimization testing by April 20
- [ ] Approve Phase 2 contract by April 25
## Risks & Open Items
| Item | Status | Owner | Target Resolution |
|------|--------|-------|-------------------|
| Data engineer assignment | Open | Client (VP Product) | April 18 |
| Sample dataset availability | At risk | Client (Technical contact) | April 20 |
| Phase 2 contract signature | Pending legal | Our Account Manager | April 25 |
## Next Meeting
April 16, 2026 – Optimization plan review (30 min call)
## Notes to Team
VP Product is excited about real-time alerts. This is a competitive differentiator for Acme in their market. Prioritize the Slack integration.
Key elements:
- Client and internal attendees clearly separated
- What each side committed to (with clear ownership)
- Risks and timeline visibility
- Tone is professional but acknowledges relationship value
- Next meeting scheduled with clear agenda
Template 4: Project Meeting Minutes (Alignment & Planning)
Use this for project kickoffs, planning meetings, and stakeholder alignment sessions. Focus on scope, timeline, and role clarity.
Structure:
# Project Meeting Minutes: Q2 Mobile Redesign
**Project:** Mobile App Redesign
**Meeting Date:** April 9, 2026
**Project Manager:** Jessica Lee
**Attendees:** PM, Lead Designer, Frontend Lead, QA Lead, Product Manager
## Project Charter Review
**Project Objective:**
Redesign mobile app UI/UX to improve retention (current: 40%, target: 55% by Q3 end).
**Scope:**
- Redesign 12 core screens (authentication, home, task detail, settings, etc.)
- Implement new design system (colors, typography, component library)
- Maintain API compatibility (no backend changes required)
**Out of Scope:**
- Backend feature work
- Android-specific optimizations (Q3)
- Animation/microinteraction details (Phase 2)
**Timeline:**
- Design: April 12 – April 30
- Frontend dev: May 1 – June 15
- QA & bug fixes: June 16 – June 30
- Soft launch: July 1
## Role & Responsibility Matrix
| Role | Responsibility | Owner |
|------|----------------|-------|
| Design | Wireframes & high-fidelity mockups | Lead Designer |
| Frontend | Implement responsive components | Frontend Lead |
| QA | Regression testing, accessibility audit | QA Lead |
| Product | Feedback & prioritization | Product Manager |
| PM | Timeline tracking, risk mitigation | Jessica Lee |
## Design System Agreement
- **Component library:** Will be built in Figma (source of truth)
- **Hand-off:** Figma → React Storybook for dev
- **Review cycle:** Design feedback window closes April 28 (no late changes)
- **Accessibility:** WCAG 2.1 AA minimum (will be tested in QA phase)
## Risks & Mitigation
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| Design feedback delays | High | 1 week delay | Weekly design review meetings (start April 12) |
| Mobile performance issues | Medium | 2 week delay | Add performance testing in QA phase |
| Component scope creep | Medium | 1 week delay | Lock scope by April 30; document feature requests for Q3 |
## Dependencies
- [ ] Figma license renewal (IT, by April 12)
- [ ] Design review stakeholder participation (Product, starts April 12)
## Next Steps
- **By April 12:** Lead Designer begins wireframing sprint
- **April 10:** Kick-off design review meeting (1 hour, all hands)
## Approval
Project Sponsor: ________________ Date: ________
Project Manager: ________________ Date: ________
Key elements:
- Clear scope (in/out) stated upfront
- Role & responsibility matrix (RACI-style)
- Risk assessment with mitigation strategies
- Dependencies and blockers identified
- Design/process handoff points documented
Template 5: Brainstorm Meeting Minutes (Idea Capture)
Use this for creative sessions where the goal is quantity of ideas and identifying patterns, not documenting decisions.
Structure:
# Brainstorm Session: Q2 Feature Ideas
**Topic:** New features to improve user engagement
**Date:** April 9, 2026
**Facilitator:** Product Manager
**Participants:** 8 people (product, design, engineering, support)
## Ground Rules Applied
- No idea is bad
- Build on others' ideas
- Defer judgment until evaluation phase
- Quantity over quality (goal: 30+ ideas)
## Raw Ideas Captured
### User Onboarding
1. Interactive tutorial with in-app tips
2. Guided first recording with voice coaching
3. Video walkthrough library
4. Progress badges/achievements
5. Invite friends for team recording challenge
### Smart Summaries
6. AI-powered topic extraction from transcript
7. Custom summary templates per meeting type
8. Multi-language summary output
9. Key speaker quotes highlighted
10. Sentiment analysis (mood of meeting)
### Collaboration Features
11. Real-time shared notes during meeting
12. Team voting on summary accuracy
13. Comment threads on transcript sections
14. Assign follow-up actions to team members
15. Share specific transcript clips externally
### Integrations
16. Slack bot that posts summary to channel
17. Google Calendar integration (auto-capture from event)
18. Teams/Zoom transcription sync
19. Jira issue creation from action items
20. Outlook integration for enterprise
### Monetization
21. Premium analytics dashboard (meeting stats over time)
22. API access for enterprise customers
23. Custom branding for enterprise deployments
24. Audit trail for compliance (SOC 2)
25. Dedicated support tier
### Mobile/UX
26. Widget showing latest recording status
27. Siri shortcut to start recording
28. Offline recording capability
29. Batch transcript editing
30. Custom dictionary for frequently missed words
## Themes Identified
**High Frequency:**
- Integration with existing tools (mentioned 7x)
- Smart summarization features (mentioned 6x)
- Team collaboration (mentioned 5x)
**Quick Win Potential:**
- Siri shortcut (simple, high user delight)
- Offline recording (solves real user pain)
- Custom dictionary (quick feature, high retention impact)
**Revenue Potential:**
- API access
- Premium analytics
- Enterprise deployment customization
## Next Steps
1. **By April 12:** Product Manager rates ideas on (effort, impact, strategic fit)
2. **By April 15:** Design sketches for top 3 ideas
3. **April 20:** Present prioritized roadmap to leadership
## Parking Lot
- Mobile offline recording (tech debt required first)
- Custom branding at enterprise scale (Q4 investigation)
- Advanced sentiment analysis (research phase)
**Facilitator Note:** Great energy. 32 ideas captured. Clear themes around integration and smart features. This gives us solid direction for Q2.
Key elements:
- Raw ideas numbered and categorized
- Themes and patterns extracted from raw list
- "Quick wins" and "revenue potential" identified
- Parking lot for deferred ideas (validates they were heard)
- Next phase (prioritization, design) scheduled
Meeting Type → Format Matching Table
Not sure which template fits your meeting? Use this matrix:
| Meeting Type | Best Format | Primary Purpose | Key Sections |
|---|---|---|---|
| Board/Executive Review | Formal Governance | Document decisions for audit & legal | Attendees, decisions, motions, votes, action items with due dates |
| Daily/Weekly Standup | Status & Blockers | Track execution and remove impediments | Completed, in-progress, blockers, quick decisions |
| Client/External Stakeholder | Relationship Record | Create external record of agreements | Objective, what was discussed, what each side committed to, risks, next steps |
| Project Kickoff/Planning | Alignment & Planning | Align all stakeholders on scope and timeline | Charter, scope (in/out), timeline, roles/RACI, risks, dependencies |
| Brainstorm/Creative Session | Idea Capture | Generate and organize creative thinking | Raw ideas, themes, patterns, next phase (prioritization) |
| All-hands/Town Hall | Status & Blockers or Relationship Record | Inform, celebrate, align on direction | Key announcements, metrics, open Q&A, next priorities |
| Retrospective/Retro | Idea Capture (modified) | Reflect on what went well/wrong | What went well, what went wrong, action items, themes |
| Customer Interview | Relationship Record | Document user feedback and insights | Objective, customer context, key quotes, themes, follow-ups |
How AI Eliminates Templates Entirely
Here's the honest truth: If you're recording your meeting, you don't need to choose a template at all.
This is where AI meeting documentation changes the game.
When you use an AI transcription tool like MinuteKeep, the AI doesn't care what meeting type you're running. It:
- Captures everything (transcription of the entire meeting)
- Generates multiple formats instantly (formal minutes, bullet points, action-focus, standard, brief)
- Lets you switch formats after recording (need formal minutes? Click once. Need just action items? Click again.)
- Extracts what matters (decisions, action items, speaker changes, timestamps)
MinuteKeep gives you 5 summary formats:
- Minutes (formal, governance-ready)
- Standard (balanced, includes decisions and context)
- Bullet Points (scannable, key points only)
- Action Focus (tasks and owners, nothing else)
- Brief (2-3 sentence executive summary)
The result: You pick the format after you know what the meeting was actually about. No guessing. No wasted time reformatting.
Instead of:
- Picking a template before the meeting
- Modifying it during the meeting
- Rewriting it afterward
- Emailing different versions to different stakeholders
You just:
- Record the meeting
- Let AI generate the transcript
- Choose which format your audience needs
- Share instantly
This works because the template is only as good as the data it captures. AI transcription captures everything, so you can generate any format from a single source.
FAQ
Q: Can I combine multiple templates for one meeting?
A: Yes. For example, a project kickoff might start with the "Alignment & Planning" structure, but if stakeholders ask for an executive summary afterward, you'd highlight the "formal decision" elements. The key is: use the template that matches your primary audience and purpose, then adapt as needed for secondary audiences.
Q: What if my meeting doesn't fit neatly into one category?
A: Hybrid meetings are common. A quarterly business review might combine board meeting rigor (decisions, votes) with project meeting structure (timeline, resources). Pick the template that covers 70% of your content, then add or remove sections to fit the remaining 30%.
Q: Should I share the same minutes with all attendees?
A: No. You might share:
- Full minutes (with all discussion context) → Attendees
- Action items only → Broader team
- Executive summary → Leadership
- Decision log → Compliance/audit
Different audiences need different levels of detail. AI-generated formats make this easy—you're not rewriting, just filtering.
Q: How do I handle disagreement about what was decided in the meeting?
A: This is why transcripts matter. If there's disagreement about a decision, the transcript is the source of truth. You can timestamp exactly when the decision was made and who said what. With templates alone, you lose this accountability.
Q: What if my organization requires a specific template format?
A: Use your organization's template, but apply the principle from this guide: structure around purpose, not blindly following all sections. If your corporate template has 15 sections but your standup only needs 3, use those 3 well instead of padding the rest.
Key Takeaways
One template doesn't fit all meetings. Board meetings, standups, client calls, project planning, and brainstorms all need different structures because they serve different purposes.
Structure should match purpose. Governance meetings need formal decisions and signatures. Standups need speed and blockers. Client meetings need relationship clarity. Projects need scope and roles. Brainstorms need idea capture and theme extraction.
Use this guide as a starting point. Copy the template that fits closest to your meeting type, adapt it to your context, and iterate based on feedback from attendees.
Format matters less than capturing the right data. The actual value comes from deciding upfront what you're trying to document, not fighting with a template that doesn't fit.
AI transcription makes templates flexible. If you're recording your meetings, you can generate multiple formats from a single transcript, letting you choose the format after you understand the content.
Test and refine your format. After 2-3 meetings using one template, ask attendees: "Is this useful? What's missing? What's unnecessary?" Good templates evolve.
Meta
Article Type: Pillar (serves as hub for satellite content on specific meeting types: M36, M48, M50)
Word Count: 2,400
Read Time: 8 minutes
Last Updated: April 11, 2026
Related Articles:
- How to Write Meeting Minutes: 7-Step Framework – Step-by-step writing process
- 5 Meeting Summary Formats Explained – Deep dive into MinuteKeep's 5 formats
- Board Meeting Minutes Template & Legal Requirements – Governance-specific deep dive
Satellite Articles:
- M36: Daily Standup Minutes Template: Format & Examples
- M48: Sprint Review and Retrospective Notes: Agile Meeting Templates
- M50: Brainstorm Session Template: Capturing Ideas That Matter
MinuteKeep CTA:
Tired of picking templates? Stop re-typing minutes. Start free with MinuteKeep → Record any meeting, choose the format you need. No subscription. 30 minutes free.
Sources: Sembly AI: 8 Meeting Minutes Templates & Examples (2025) | Zapier: Meeting Minutes Templates (2025) | Asana: Stand-Up Meeting Guide (2025) | Fellow.ai: 5 Professional Meeting Minutes Examples (2026) | Parabol: 26 Common Meeting Types (2025)