The Meeting Documentation Problem

Meetings are expensive. A one-hour meeting with six senior professionals costs your organisation $600-$1,200 in productive time. The follow-up — distributing decisions, assigning actions, sending minutes — adds another 30-60 minutes per attendee. For a company running 50 significant meetings per week, that's 25-50 hours of post-meeting documentation time. Every week.

Claude reduces that documentation time by 80-90%. The workflow is simple: paste the transcript or your notes, use the right prompt, and receive structured minutes in 30 seconds. Review, adjust if needed (typically 2-3 minutes), and send. Total time: under 5 minutes for a 60-minute meeting.

This guide covers the prompt templates for four meeting types: strategy and decision meetings, project status meetings, client and external meetings, and executive briefings. It also covers the automated workflow for teams that want zero-touch meeting documentation.

Want to automate this completely? Our implementation service connects Claude to your meeting platform (Zoom, Teams, Google Meet) so minutes are generated and distributed automatically within minutes of every meeting ending — no manual steps.

Request Free Assessment →

The Universal Meeting Minutes Prompt

This prompt works for 80% of meeting types. It produces a well-structured output that most teams can use immediately without modification.

Universal Meeting Minutes Prompt
You are a professional meeting facilitator producing structured minutes. From the following meeting notes or transcript, extract and format: 1. MEETING OVERVIEW: Date, attendees (if mentioned), purpose (1 sentence) 2. KEY DECISIONS: Numbered list of decisions made — each as a clear, standalone statement 3. ACTION ITEMS: Table with columns: Action | Owner | Deadline | Priority 4. OPEN QUESTIONS / PARKING LOT: Items raised but not resolved 5. NEXT STEPS: Next meeting or follow-up schedule if mentioned Rules: - Use only information present in the notes — do not infer or add - Each decision should be self-contained (readable without context) - Action items must have a named owner (use "TBD" if not specified) - Flag any action items with no deadline as [NO DEADLINE SET] Meeting notes/transcript: [PASTE HERE]

Meeting-Type Specific Templates

Strategy and Decision Meetings

Strategy meetings produce the most consequential decisions — and the most consequential documentation errors. The key for this meeting type is capturing the reasoning behind decisions, not just the decisions themselves, so the record is useful for anyone who wasn't in the room.

Strategy Meeting Minutes Prompt
Produce structured minutes for a strategy meeting. Format: MEETING PURPOSE: [one sentence] STRATEGIC CONTEXT: [2-3 sentences on what problem/opportunity was being addressed] OPTIONS CONSIDERED: [if multiple options were discussed, list them with brief pros/cons] DECISIONS MADE: [numbered — each with the decision AND the rationale in 1-2 sentences] REJECTED OPTIONS: [briefly — what was considered and why it was set aside] ACTION ITEMS: [owner / action / deadline / success measure] REVIEW DATE: [when will this decision be revisited?] OPEN QUESTIONS: [what needs further analysis or input] Notes: [PASTE]

Project Status Meetings

Project status meetings are typically the highest-frequency meeting type. The documentation requirement is consistent every week: what's done, what's at risk, what needs escalating. Claude handles this format perfectly with a consistent prompt.

Project Status Meeting Prompt
Produce a project status meeting summary. Format: PROJECT: [name] DATE: [date] ATTENDEES: [from notes] RAG STATUS: [Red / Amber / Green — infer from notes if not explicit] THIS WEEK: Completed items (bullet list) NEXT WEEK: Planned deliverables (bullet list) RISKS & BLOCKERS: Active risks with owner and mitigation status DECISIONS: Any decisions made in this meeting ESCALATIONS NEEDED: Items requiring senior intervention ACTION ITEMS: [owner / action / deadline] Notes: [PASTE]
Implementation playbook
Free White Paper

Enterprise Claude Implementation Playbook

Includes complete meeting documentation workflows — automated setup guides for Zoom, Teams, and Google Meet integrations.

Download Free →

Client and External Meetings

Client meeting documentation has a dual audience: your internal team (who need the full picture) and sometimes the client (who needs a clean summary of agreements). This prompt produces both.

Client Meeting Minutes Prompt
Produce client meeting minutes in two formats from these notes: FORMAT 1 — INTERNAL (full detail): - Client: [name / company] - Meeting purpose and context - Client concerns/needs expressed (verbatim where possible) - Our commitments (clear list — review carefully) - Client commitments (what they agreed to do) - Red flags / concerns from the meeting - Full action items with owners and deadlines - Intelligence / notes on relationship dynamics FORMAT 2 — CLIENT SUMMARY (to send to client): - Meeting recap (1 paragraph) - What we agreed to (numbered list) - What you agreed to (numbered list) - Next steps with dates - Tone: professional, collaborative Notes: [PASTE]

The Automated Meeting Documentation Workflow

Manual prompting works well for individual professionals. But at the enterprise level — when your organisation runs 50-200 significant meetings per week — manual documentation is still a significant overhead. The fully automated workflow eliminates it.

The Integration Architecture

The automated workflow connects three systems: your meeting platform (Zoom/Teams/Google Meet), a transcription service (built-in or Otter.ai/Fireflies), and Claude via the API. The sequence:

  • Meeting ends → transcription service generates transcript automatically
  • Transcript triggers API call to Claude with your meeting minutes prompt template
  • Claude generates structured minutes in ~30 seconds
  • Minutes automatically posted to Slack channel / Confluence / email — within 5 minutes of meeting end

Our implementation team sets this up using either the Claude API directly or via MCP integrations. For most enterprise setups, this takes 2-3 days to configure and test. Teams that implement this workflow report saving 3-5 hours per week per knowledge worker in documentation time.

Governing Automated Meeting Documentation

Automation raises a governance question: who reviews before distribution? Our recommendation depends on meeting type. For internal operational meetings (standups, project syncs), immediate automated distribution is appropriate. For client meetings or strategy sessions, a 15-minute review window before automatic distribution is advisable. For confidential or sensitive discussions, human review is mandatory — automate the draft, but not the send. See our governance service for the full framework.

Getting the Best Output Quality

The quality of Claude's meeting minutes depends significantly on the quality of the input. Three tips from our deployment experience:

1. Speaker Attribution Matters

A transcript that attributes statements to named speakers produces dramatically better output than an unattributed wall of text. If your transcription tool doesn't attribute speakers, spend 2 minutes adding "[NAME]:" markers to the most important exchanges before processing.

2. Pre-Process Your Own Notes First

If you're working from notes rather than a transcript, spend 30 seconds adding structure before pasting: use line breaks between topics, mark decisions with [DECISION:] and action items with [ACTION:]. This simple pre-processing improves Claude's output quality noticeably and requires almost no additional time.

3. The Two-Pass Method for Complex Meetings

For long, complex meetings (60+ minutes with multiple agenda items), use a two-pass approach: first ask Claude to extract all decisions and action items from the full transcript; then ask it to synthesise those into final minutes. This produces higher accuracy than a single-pass prompt on dense content.

Related workflows: Email Drafting Workflows · Research Synthesis · 100 Claude Workflows · Report Generation