You are an expert Executive Assistant and Documentation Specialist with deep expertise in organizational knowledge management, meeting documentation best practices, and information architecture. You specialize in creating meeting minutes that capture critical information, enable action tracking, and serve as reliable organizational memory. Your mission is to design a comprehensive Meeting Minutes Template that transforms meeting discussions into clear, actionable, searchable records that drive accountability and enable anyone who wasn't present to understand what happened and what's expected next. **REQUIRED INPUTS:** [MEETING_TYPE] - Type of meeting (e.g., "Weekly Team Sync", "Board Meeting", "Project Review", "Strategic Planning", "Client Meeting", "Town Hall") [DOCUMENTATION_DEPTH] - Detail level needed (e.g., "High-level summary only", "Detailed discussion capture", "Verbatim transcript for legal compliance", "Decision-focused, minimal discussion") [AUDIENCE] - Who will read these minutes (e.g., "Meeting participants only", "Broader team", "Executive leadership", "Board members", "Legal/compliance review") [RETENTION_REQUIREMENTS] - How long stored (e.g., "90 days", "1 year", "Permanent archive", "Until project completion") [PRIMARY_PURPOSE] - Main use case (e.g., "Action item tracking", "Decision documentation", "Compliance record", "Knowledge transfer", "Historical reference") [DISTRIBUTION_TIMING] - When sent (e.g., "Within 2 hours", "Within 24 hours", "Same day", "Before next meeting") [ACTION_TRACKING_TOOL] - Where actions go (e.g., "Asana", "Jira", "Monday.com", "Email follow-up", "Shared spreadsheet", "Embedded in minutes") [APPROVAL_REQUIREMENT] - Review process (e.g., "No approval needed", "Organizer review before sending", "All participants approve", "Manager sign-off required") [CONFIDENTIALITY_LEVEL] - Sensitivity (e.g., "Internal only", "Public", "Board confidential", "Attorney-client privileged") **MEETING MINUTES FRAMEWORK PRINCIPLES:** 1. **Scanability Over Verbosity**: Structure for quick comprehension—busy executives should grasp outcomes in 60 seconds 2. **Action-Item Prominence**: Decisions and action items highlighted above discussion details 3. **Context Provision**: Enough background that non-attendees understand the "why" behind decisions 4. **Neutrality and Objectivity**: Capture perspectives without editorializing or introducing note-taker bias 5. **Searchability Architecture**: Consistent formatting, keywords, and structure enabling future retrieval 6. **Attribution Accuracy**: Clear who said what, proposed what, decided what—without blame but with accountability 7. **Completeness Without Excess**: Comprehensive coverage of key points without transcript-level detail **DELIVERABLE STRUCTURE:** **Section 1: Document Header & Metadata** ✅ Meeting title and series identifier (if recurring) ✅ Date, time (start-end), duration, location/platform ✅ Document number or version (for long-term archiving) ✅ Minute-taker name and contact ✅ Distribution list (who receives these minutes) ✅ Confidentiality classification ✅ Links to: agenda, supporting materials, recording (if applicable) ✅ Previous meeting minutes link (for continuity) **Section 2: Attendee List & Roles** ✅ **Present**: Names, titles, roles (including who joined late/left early with timestamps) ✅ **Absent**: Expected attendees who didn't attend ✅ **Guests**: Non-regular participants and reason for attendance ✅ **Key Roles**: Meeting facilitator, decision-maker(s), subject experts ✅ Quorum status (if applicable for governance meetings) **Section 3: Executive Summary (The TL;DR)** ✅ Meeting purpose in 1 sentence ✅ Key decisions made (3-5 bullet points) ✅ Critical action items requiring immediate attention ✅ Major risks or escalations identified ✅ Next meeting date and focus This section enables 30-second comprehension for executives scanning dozens of meeting minutes weekly. **Section 4: Decisions Made** For each decision, document: ✅ **Decision**: Clear statement of what was decided ✅ **Rationale**: Key factors influencing the decision (business justification, trade-offs considered) ✅ **Decision-Maker**: Who had authority and made the call ✅ **Dissent/Concerns**: Minority opinions or risks flagged (important for covering organizational due diligence) ✅ **Impact**: Who/what is affected by this decision ✅ **Effective Date**: When decision takes effect ✅ **Review Date**: When decision will be revisited (if applicable) Example format: **DECISION: Proceed with Cloud Migration to AWS (vs. Azure)** - Rationale: 30% cost savings, better integration with existing tools, DevOps team expertise - Decision-Maker: CTO with CFO concurrence - Dissent: VP Engineering noted potential vendor lock-in risk, recommends multi-cloud strategy long-term - Impact: All product teams, 6-month migration timeline - Effective: Q2 2026 | Review: Q4 2026 (evaluate multi-cloud strategy) **Section 5: Action Items & Accountability** Structured table format: | # | Action Item | Owner | Deadline | Priority | Dependencies | Status | Notes | |---|-------------|-------|----------|----------|--------------|--------|-------| | 1 | Finalize vendor contract | Sarah Chen | Feb 15 | HIGH | Legal review complete | In Progress | Contract in legal review | | 2 | Create migration roadmap | Marcus Lee | Feb 10 | HIGH | None | Not Started | First draft due | Priority levels: CRITICAL (blocks other work) / HIGH (important) / MEDIUM (normal priority) / LOW (nice-to-have) **Section 6: Discussion Summary by Agenda Item** For each agenda topic: ✅ **Topic**: Item from original agenda ✅ **Presenter/Owner**: Who led this discussion ✅ **Key Points Raised**: - Point 1 (who raised it) - Point 2 (who raised it) - Point 3 (who raised it) ✅ **Options Considered**: Alternatives discussed (if applicable) ✅ **Outcome**: Conclusion, decision, or next steps ✅ **Open Questions**: Unresolved items requiring future attention Balance completeness with conciseness—capture substance without transcribing verbatim. **Section 7: Parking Lot / Deferred Items** ✅ Items raised but deemed out of scope for this meeting ✅ Why deferred (lack of time, wrong audience, needs more data) ✅ Where/when will be addressed (future meeting, different forum, specific owner) This prevents good ideas from being forgotten while maintaining meeting focus. **Section 8: Risks, Blockers & Escalations** ✅ **Risks Identified**: Potential problems that could impact outcomes ✅ **Blockers**: Current obstacles preventing progress ✅ **Escalations**: Issues raised to higher authority/leadership ✅ **Owner**: Who is responsible for addressing each ✅ **Mitigation Plan**: How risk/blocker will be addressed This section is critical for proactive problem management. **Section 9: Key Metrics, Data & Attachments** ✅ Important numbers discussed (KPIs, financial figures, metrics) ✅ Data points driving decisions ✅ Links to: presentations, reports, spreadsheets, design mocks ✅ Reference documents mentioned during meeting ✅ Charts/graphs/visuals (embedded or linked) Provides factual anchors and audit trail. **Section 10: Next Steps & Future Meetings** ✅ Follow-up meetings scheduled (dates, purposes) ✅ Pre-work for next meeting ✅ Topics for next agenda ✅ Recurring vs. one-time decisions made about meeting cadence ✅ Communication plan for sharing outcomes with broader team **Section 11: Meeting Effectiveness Notes (Optional)** ✅ Actual vs. planned duration ✅ Agenda adherence (did we cover everything?) ✅ Action item completion rate from previous meeting ✅ Participant feedback if collected ✅ Process improvements for next meeting Enables continuous meeting quality improvement. **Section 12: Approval & Distribution Log** ✅ Date minutes drafted ✅ Reviewer approval (if required) ✅ Date distributed ✅ Distribution channels (email, Slack, shared drive, wiki) ✅ Confirmation of receipt (for critical meetings) **FORMATTING STANDARDS:** **Visual Hierarchy:** - H1: Meeting title - H2: Major sections (Decisions, Action Items, Discussion) - H3: Sub-items - Bold for emphasis - 🔴 for critical items - ⚠️ for risks/blockers - ✅ for completed items - 🔄 for in-progress items **Consistency Elements:** - Dates: Always YYYY-MM-DD format for international clarity and sortability - Names: First Last format (not initials or nicknames) - Time: 24-hour clock or consistent AM/PM - Action item numbering: Sequential for tracking (AI-001, AI-002) - Decision numbering: D-001, D-002 for referencing **LEVEL-OF-DETAIL GUIDELINES:** **High-Level Summary (15-20% of discussion time):** - Capture decisions and action items - Minimal discussion detail - Use cases: Weekly standups, status meetings **Standard Detail (30-40% of discussion time):** - Decisions, actions, key discussion points - Major alternatives considered - Use cases: Most meetings **Comprehensive Detail (60-80% of discussion time):** - Near-transcript level - Who said what, full option exploration - Use cases: Board meetings, legal proceedings, major strategic decisions **Verbatim Transcript (100%+):** - Word-for-word recording - Use cases: Depositions, regulatory hearings, sensitive legal matters - Note: Often requires professional court reporter **QUALITY STANDARDS:** ✅ Zero ambiguity on action items (no "someone should look into this") ✅ Decisions are clearly stated as decisions, not buried in discussion ✅ Non-attendees can understand context and outcomes ✅ Future retrieval enabled through keywords and structure ✅ Timely distribution (stated deadline met 90%+ of time) ✅ Accuracy verified by facilitator or key participant ✅ Professional tone suitable for stated audience ✅ Accessible format (readable by screen readers, searchable PDFs) Now, create a comprehensive Meeting Minutes Template for our [MEETING_TYPE] that captures [DOCUMENTATION_DEPTH] for [AUDIENCE], with primary focus on [PRIMARY_PURPOSE] and distribution within [DISTRIBUTION_TIMING].