Skip to content
ProductivityBeginner

Meeting Notes to Summary and Action Items

Turn messy meeting notes or a transcript into a clean summary with decisions, action items, owners, and open questions.

Share on X (opens in a new tab)Share on LinkedIn (opens in a new tab)

Make it yours

Fill in each variable and watch the prompt update. Anything still in {{braces}} needs your input before you use it.

Fill in the blanks

0 of 3 filled

Who'll read the summary.

Name or topic of the meeting.

Raw notes or transcript.

Live previewUnfilled
Turn the meeting notes below into a clear summary for {{audience}}.

Meeting: {{meeting_name}}

Format:
**Summary** — 2–3 sentences on what the meeting was about and the main outcome.
**Decisions made** — bullet list.
**Action items** — a table with columns: Task | Owner | Due date. Only include owners and dates actually stated in the notes; otherwise write "unassigned" or "no date."
**Open questions** — anything raised but not resolved.

Rules: Don't invent decisions, owners, or deadlines. Keep it skimmable — under 200 words total.

Notes:
"""
{{meeting_notes}}
"""
Open in Playground

Example

Example input

Filled prompt
Turn the meeting notes below into a clear summary for team members who missed the meeting.

Meeting: Spring newsletter planning

Format:
**Summary** — 2–3 sentences on what the meeting was about and the main outcome.
**Decisions made** — bullet list.
**Action items** — a table with columns: Task | Owner | Due date. Only include owners and dates actually stated in the notes; otherwise write "unassigned" or "no date."
**Open questions** — anything raised but not resolved.

Rules: Don't invent decisions, owners, or deadlines. Keep it skimmable — under 200 words total.

Notes:
"""
- talked about spring newsletter, send date April 10?? everyone ok w/ that -> yes
- Mei: feature the new volunteer program as the lead story
- Carlos to write the lead story, draft by Apr 3
- need photos - who? nobody volunteered
- Jo asked if we should add a donation button - discuss w/ finance first
- Mei will update the mailing list
- decided to drop the events calendar section this time (too few events)
"""

Example output

Illustrative example response — written by Promptly, not generated live

Summary The team planned the spring newsletter, confirmed an April 10 send date, and chose the new volunteer program as the lead story.

Decisions made

  • Send date: April 10.
  • Lead story: the new volunteer program.
  • The events calendar section is dropped for this issue (too few events).

Action items

TaskOwnerDue date
Write the lead story draftCarlosApril 3
Update the mailing listMeino date
Source photosunassignedno date

Open questions

  • Should we add a donation button? (Needs discussion with finance first.)
  • Who will handle photos?

Why it works

A fixed structure (summary, decisions, actions, open questions) is what makes meeting notes useful later — people mostly need "what did we decide and who's doing what."

The "don't invent owners or deadlines" rule is crucial: models tend to fill gaps to look complete, and a made-up owner or date can cause real confusion. Flagging "unassigned" items also surfaces work that might otherwise fall through the cracks.

Techniques used