Meeting Summary Prompt Generator

Why this meeting summary prompt works

The biggest risk with AI meeting summaries is not bad writing; it is confident invention. If notes say "Lena to fix the bug" without a date, a loosely prompted model may happily write "Lena will fix the bug by Friday." That small invention can cause real confusion.

This prompt is built around accuracy. It puts your notes between triple quotes so the model knows exactly which text is the source, and it tells the model to use only that text. Missing owners or dates must be written as "not specified" instead of guessed. It also asks the model to keep decisions separate from topics that were only discussed, which is the distinction people most often need when they read a summary later.

The reader field changes the emphasis. Attendees need a reminder of commitments; people who missed the meeting need context; senior management usually wants outcomes and risks in a few lines. Leading with the one to three most important outcomes means even a skim-reader gets the point.

Worked example

Say you took rough notes in a planning meeting and need to update colleagues who could not attend. These are the inputs:

Meeting

weekly product planning meeting

Attendees

Priya (product), Tom (design), Lena (engineering)

Who is the summary for?

people who missed the meeting

Length

Short (100-250 words)

Format

headed sections with bullet points

Include action items with owners and due dates

Yes

Meeting notes or transcript

Release of search filters moved from 3 June to 10 June because of the API bug.; Tom will share the new filter designs by Thursday.; Discussed whether to drop the old export feature - no decision, needs usage data.; Lena to fix API pagination bug.

The builder turns these inputs into the following prompt. Load it into the form above with the Planning notes example chip and change anything you like.

You are an experienced executive assistant who writes accurate, concise meeting summaries.

## Task
Summarise the weekly product planning meeting using only the notes between the triple quotes below.
Attendees: Priya (product), Tom (design), Lena (engineering).
The summary is for: people who missed the meeting.

## Requirements
- Length: Short (100-250 words)
- Format: headed sections with bullet points
- Start with the 1-3 most important outcomes.
- List decisions that were actually made, separately from topics that were only discussed.
- List action items as: owner - task - due date. If an owner or date is not in the notes, write "not specified" instead of guessing.
- List open questions or unresolved issues.
- Do not add information, names or numbers that are not in the notes. If something is unclear, say so.

## Meeting notes
"""
Release of search filters moved from 3 June to 10 June because of the API bug.
Tom will share the new filter designs by Thursday.
Discussed whether to drop the old export feature - no decision, needs usage data.
Lena to fix API pagination bug.
"""

This page shows only the prompt. The answer depends on the AI tool you paste it into, so always review the result before you use it.

Tips to improve your results

• Raw notes are fine. You do not need to tidy them before pasting.
• If you use a transcript, keep the speaker names so the AI can assign owners correctly.
• Check every action item against your notes before you send the summary.
• Follow your company's rules on what may be pasted into AI tools; remove confidential details if needed.
• For recurring meetings, keep the same format so readers know where to look.