Turn Messy Meeting Notes into Clear Action Plans

Summarize the following meeting notes into a concise executive summary.
Meeting type: [e.g., quarterly business review / product sprint review / client kickoff]
Attendees: [list names and roles]
Date: [date]
Raw notes: [paste your raw notes here]

Format the summary as:
1. Meeting Purpose (1 sentence)
2. Key Decisions Made (bullet list)
3. Critical Issues Raised (bullet list)
4. Next Steps (bullet list with owner and due date)
5. Items Tabled for Next Meeting

Keep the total summary under 300 words. Use plain language — no jargon.

Extract all action items from the following meeting transcript or notes.
[Paste meeting notes or transcript here]

For each action item, output a structured table with these columns:
- Action Item (clear, verb-first description)
- Owner (name/role)
- Due Date (if mentioned; otherwise flag as "No deadline set")
- Priority (High / Medium / Low based on context)
- Dependencies (what needs to happen first, if any)

After the table, list any implied tasks that were discussed but not explicitly assigned — flag these as "Unassigned Action Items."

Create a formal decision log from the following meeting notes.
Meeting: [meeting name or project]
Date: [date]
Raw notes: [paste notes here]

For each decision made in the meeting, capture:
- Decision: (what was decided)
- Context: (why this decision was made — 1-2 sentences)
- Alternatives Considered: (what other options were discussed)
- Decision Maker(s): (who made or approved the decision)
- Impact: (what this decision affects)
- Reversibility: (Easy to reverse / Difficult to reverse / Irreversible)

Format as a numbered list of decisions. If no clear decisions were made, note "No formal decisions recorded — items are still open for discussion."

Write a professional follow-up email based on these meeting notes.
Meeting type: [e.g., sales discovery call / team standup / client update / board meeting]
My name: [your name]
Recipients: [names and roles]
Meeting date: [date]
Key outcomes from my notes: [paste 5-10 bullet points from your notes]

The email should:
- Have a subject line in the format: "Follow-Up: [Meeting Name] — [Date]"
- Open with a brief thank-you (1 sentence)
- Include a "What We Decided" section
- Include a "Next Steps" section with owners and deadlines
- Close with the next scheduled touchpoint or a request to confirm the recap is accurate

Keep the email professional but warm. Under 250 words.

Create a structured meeting agenda for an upcoming [meeting type, e.g., quarterly planning / client review / product roadmap discussion].
Meeting goal: [what we need to achieve by the end of this meeting]
Duration: [e.g., 60 minutes]
Attendees: [names and roles]
Key topics to cover: [list 3-5 topics]
Decisions that need to be made: [list decisions]
Pre-work participants should complete: [any prep required]

Format the agenda with:
- A one-sentence goal at the top
- Time-boxed sections for each topic (allocate minutes)
- A 5-minute buffer before the end for "Open Issues / Parking Lot"
- A designated facilitator and note-taker
- Pre-read links or materials section

Write a client-facing meeting recap email from these internal notes.
Client name / company: [client name]
Meeting purpose: [e.g., monthly check-in / project kickoff / problem-solving session]
My role: [your role]
Internal notes: [paste raw notes — can include internal commentary]

IMPORTANT: The output should be professional and external-facing. Strip out any internal commentary, pricing discussions, or team frustrations. Focus on:
1. What was accomplished
2. What the client agreed to provide or do
3. What we agreed to provide or do
4. Timeline and next meeting date

Tone: warm, professional, client-service oriented. Sign off with my name and direct contact info placeholder.

Synthesize the following async standup updates from my team into a single daily summary report.
Team members and their updates:
[Name 1]: [their update]
[Name 2]: [their update]
[Name 3]: [their update]
[Name 4]: [their update]

Create a summary that includes:
1. Overall Team Progress (2-3 sentences on collective momentum)
2. Blockers & Risks (anything flagged that needs management attention)
3. Key Completions from Yesterday
4. Focus Areas for Today
5. Team Members Who Need Support (anyone mentioning blockers or delays)

Keep the report under 200 words. Format for easy scanning with short bullet points.

Convert the following raw meeting notes into formal meeting minutes.
Organization/Project: [name]
Meeting title: [title]
Date and time: [date/time]
Location/Platform: [e.g., Zoom / Conference Room A]
Facilitator: [name]
Note-taker: [name]
Attendees: [list]
Apologies/Absences: [if any]
Raw notes: [paste here]

Format the minutes in this formal structure:
1. Call to Order
2. Approval of Previous Minutes (if applicable)
3. Agenda Items Discussed (one section per topic with discussion summary)
4. Resolutions Passed (if any formal votes or agreements)
5. Action Items (with owner and deadline)
6. Next Meeting Date
7. Adjournment

Use formal language. Use past tense throughout (e.g., "The team discussed..." not "The team will discuss...").

Summarize the following sprint retrospective or project retrospective meeting notes.
Project/Sprint: [name]
Team: [list members]
Retrospective format used: [e.g., Start/Stop/Continue / What Went Well/What Didn't / 4Ls]
Raw notes: [paste notes here]

Structure the summary as:
1. What Went Well (keep doing these)
2. What Didn't Work (stop or fix these)
3. Experiments to Try (new things to start)
4. Patterns Noticed (recurring themes across multiple items)
5. Top 3 Action Items for Next Sprint (specific, measurable, owned)
6. Team Sentiment Score (based on tone of comments: Positive / Neutral / Needs Attention)

Highlight any recurring issues that have appeared in previous retrospectives (I'll flag those in my notes with an asterisk *).

Convert my one-on-one meeting notes into a structured update I can share with my manager or keep in my personal record.
Meeting with: [manager's name / direct report's name]
Date: [date]
My raw notes: [paste notes here]

Organize the output into:
1. Topics Discussed (brief recap of each)
2. Feedback Received (specific feedback given to me or by me)
3. My Commitments (what I agreed to do)
4. Their Commitments (what they agreed to do or follow up on)
5. Career Development Notes (anything discussed about growth, skills, or goals)
6. Open Questions (things that need clarification or follow-up)

Tone: First-person from my perspective. Professional but not stiff.