AI meeting notes summary prompt

A productivity prompt that turns meeting notes into summaries, decision drafts, action items, follow-up lists, and review notes.

April 27, 2026

Ready prompt

You are a productivity editor who turns meeting notes into clear, organized, and follow-up-ready summaries. Using the general details below, organize the raw meeting notes into a summary, decision drafts, action items, and a follow-up list.

Meeting type: 
Raw meeting notes: 
Summary goal: 
Detail level: 
Follow-up style: 

Rules:
- Work with a general and safe meeting summary context.
- Rely only on the provided general notes without expanding private, confidential, or company-specific information.
- Do not add decisions, owners, dates, commitments, budgets, or approvals that were not provided as confirmed.
- Separate unclear points as items to review or clarify.
- Present decisions as drafts inferred from the notes, not as confirmed outcomes.
- Prepare the output as a reviewable and editable meeting summary.

Output format:
1. Short meeting summary
2. Main agenda items
3. Draft decisions that appear in the notes
4. Action items table
5. Owner or follow-up person field
6. Follow-up list if dates or timelines exist
7. Unclear or to-be-clarified points
8. Risks and open questions
9. Short executive summary
10. Post-meeting email draft
11. Final checklist

ChatGPT Claude Gemini

How to use this prompt

This section helps you understand when and how to use this prompt more clearly.

What is this prompt used for?

This prompt helps turn messy meeting notes into a clearer and more follow-up-ready format. It creates a short summary, agenda points, decision drafts, action items, open questions, and follow-up notes.

Who is it for?

It is useful for team leads, project managers, software teams, product teams, students, consultants, and anyone who wants to share meeting notes more clearly after a meeting.

When should you use it?

It can be used after a meeting when you want to organize raw notes, separate action items, clarify owners and follow-ups, or prepare a short summary for managers.

Example use case

After a project meeting, a user can provide short and messy notes to this prompt. The prompt can organize them into agenda points, decision drafts, action items, open questions, and a follow-up email.

Tips for better results

When sharing meeting notes, avoid including private customer data, access details, or confidential company information. If an owner, date, or decision is unclear, keep it as a review note instead of writing it as confirmed.

Additional usage questions

Can this prompt create meeting minutes?

Yes. It does not replace an official record, but it can create a meeting minutes draft, action list, and follow-up summary.

Is this prompt suitable for internal team meetings?

Yes. It can be adapted for weekly team meetings, project meetings, sprint reviews, or post-customer internal review notes.

Preview

Example output

This example shows how the prompt can turn raw meeting notes into a summary, action items, and a follow-up list.

Example variables

Meeting type: Weekly project meeting
Raw meeting notes: New screen design was reviewed. Some spacing issues on mobile. API test environment is ready. Content team will review text by Friday. Release date is not confirmed.
Summary goal: Internal follow-up and action list
Detail level: Medium detail, bullet points
Follow-up style: Action-focused, separate unclear points

Short meeting summary

The meeting covered the new screen design, mobile spacing issues, API test environment status, and content review timeline. The release date is still unclear and should be tracked as an open item.

Main agenda items

1. Review of the new screen design 2. Mobile spacing issues 3. API test environment status 4. Content review timeline 5. Release date clarification

Action items

Design team: Review spacing issues on mobile screens. API team: Share test environment readiness with the team. Content team: Review text by Friday. Project team: Follow up on release date clarification.

Unclear or to-be-clarified points

The release date is not confirmed. The exact mobile screens with spacing issues should be checked. It is not clear whether content review may require additional revisions.

Post-meeting email draft

Hello, Here are the key points from the weekly project meeting: - The new screen design was reviewed. - Mobile spacing issues will be checked again. - The API test environment is ready. - The content team will review the text by Friday. - The release date is not confirmed yet and will be followed up separately. Please review your action items before the next update.

This example is a meeting note draft. Owners, dates, decisions, and release details should be checked against the real team record before sharing.

Usage tips

1
Writing raw notes clearly helps produce a more understandable summary.
2
If owner or date information is unclear, it is safer to leave it as a point to clarify.
3
Before sharing the meeting summary, compare decisions, dates, owners, and action items with the real meeting record.