Turn Messy Meeting Notes into Minutes with Decisions, Owners and Deadlines

Get clean meeting minutes that separate decisions from discussion, list action items with owners and dates, and flag every gap instead of guessing.

You getHeader, decisions and action Items

Prompt

Prompt
Act as an experienced operations manager who writes meeting minutes that people actually act on.

I will paste my raw meeting notes right after this message. They may be messy, partial or out of order. Turn them into clean minutes.

Rules:
1. Keep decisions separate from discussion. A decision is something the group clearly agreed to do or not do. Everything else is discussion.
2. Start every action item with a verb. Give it an owner and a due date exactly as stated in the notes.
3. If an owner or date is missing or vague (for example "soon", "the team", "next sprint" with no date), write MISSING in that cell and list it under Gaps. Never guess a name or a date.
4. Summarize each discussion topic in one or two sentences. Add no opinions or recommendations.
5. Use only what is in the notes. If a line is unclear, quote it under Open Questions.

Output format:
- Header: meeting title, date, attendees (only if stated in the notes)
- Decisions: numbered list
- Action Items: table with columns #, Action, Owner, Due Date, Status (Clear / Needs Owner / Needs Date)
- Discussion Summary: one bullet per topic
- Open Questions and Gaps: bullets, each saying what is missing and who could confirm it

End with one line listing anything in the notes you could not interpret.

Example output

At a glanceWhat the minutes captured from the product syncWeekly Product Sync, Tuesday 14 May
Decisions recorded
3
Billing redesign moved to June, among others
Action items
5
3 clear, 2 flagged
Action items missing owner or date
2
Action 2 needs a date, action 5 needs an owner
Open questions and gaps
3
Plus one line that could not be interpreted

Example for: rough notes from a weekly product sync at a small SaaS company, pasted as bullet fragments.

Header

  • Meeting: Weekly Product Sync
  • Date: Tuesday, 14 May
  • Attendees: Priya (PM), Marcus (Eng Lead), Dana (Design), Leo (Support)

Decisions

  1. Move the billing page redesign to the June release instead of May.
  2. Drop the CSV export for Free plan users. It stays on paid plans only.
  3. Hold the customer feedback call every two weeks, not weekly.

Action Items

#ActionOwnerDue DateStatus
1Update the release roadmap to show billing redesign in JunePriyaFri 17 MayClear
2Write the help-center notice about CSV export changesLeoMISSINGNeeds Date
3Fix the login timeout bug reported by 3 enterprise accountsMarcusMon 20 MayClear
4Share final mockups for the onboarding checklistDanaThu 16 MayClear
5Contact the payments vendor about failed renewal emailsMISSINGMISSINGNeeds Owner

Discussion Summary

  • Billing redesign: Engineering capacity is tied up with the login bug, so the team agreed a May launch was not realistic.
  • CSV export: Usage data showed few Free users export. Support expects some complaints.
  • Onboarding checklist: Dana presented two layouts. The group preferred the step-by-step version.
  • Failed renewal emails: Leo reported 11 tickets this week. The cause is unclear and may be on the vendor side.

Open Questions and Gaps

  • Action 2: No due date given for the help-center notice. Priya could confirm if it must go out before the June release.
  • Action 5: Notes say "someone should ping the vendor" with no name or date. Marcus or Priya could assign it.
  • Unclear line: "revisit pricing thing w/ Sam?" It is not clear who Sam is or whether this is an action item. Priya could clarify.

Could not interpret: "DT ok for Q3 — see last wk" (the abbreviation "DT" is not defined in the notes).

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Defining a decision versus discussion stops the model from mixing agreed outcomes with things people only talked about.
  • Writing MISSING instead of guessing makes ownership gaps visible so they get fixed before tasks slip.
  • The Status column and Gaps list give you a ready follow-up checklist to send after the meeting.

Use right after a meeting while it is fresh. Paste your raw notes, chat log or transcript into ChatGPT, Claude or Gemini after the prompt. Include names and dates if you have them.

Common edits

  • Ask for a short email version of the minutes to send to attendees and absent stakeholders.
  • Add a column for priority or project name if you track work across several teams.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business