Meeting Notes Summary Prompt (Decisions + Actions)
Splits meeting notes into three clean parts: decisions, actions with owners, and what stayed open.
You are a chief of staff turning raw meeting notes into something a team can act on. NOTES [PASTE NOTES OR TRANSCRIPT] MEETING: [NAME, DATE, ATTENDEES] OUTPUT 1) DECISIONS — what was decided, by whom, effective when. Only actual decisions, not discussions. 2) ACTIONS — table: action | owner | due date | dependency. Every action needs a named owner; "the team" is not an owner. 3) OPEN QUESTIONS — what was raised but not resolved, with who needs to answer it. 4) RISKS RAISED — anything flagged as a concern, with the mitigation mentioned (or "no mitigation discussed"). 5) NOT DISCUSSED BUT EXPECTED — agenda items that never came up. RULES - Do not invent owners or dates. If missing, write [OWNER?] or [DATE?]. - Do not summarise the discussion. Nobody needs the conversation, only the outcome. - Keep it under 250 words. - If the notes contradict themselves, flag it instead of choosing one version.
A meeting without a named owner per action did not decide anything.
02 — Variables
Fill in the brackets
The highlighted fields are the places where your own details go. You do not have to fill all of them; anything left empty is completed by the model's own assumption.
[PASTE NOTES OR TRANSCRIPT]
[NAME, DATE, ATTENDEES]
Field to fill in the prompt
[OWNER?]
Field to fill in the prompt
[DATE?]
Field to fill in the prompt
03 — How to use
How to use it, step by step
- 01
Paste the raw transcript rather than your own summary — the model extracts decisions you already forgot.
- 02
Fill [OWNER?] before sending the follow-up; unowned actions do not happen.
- 03
Send the output as the follow-up email body; it is already the right shape.
04 — Variations
Same prompt, different result
One prompt does not solve every case. These variations ask for the same job in a different tone, length or format — pick the one that fits.
Standup
Same structure for a daily standup: done, next, blocked. Max one line per person.
Client call
Same structure for a client call: what we promised, what they promised, what needs a quote or approval.
05 — Tips
Notes that take the result up a level
- The value is in the action table, not the summary. If nobody is named, nothing happens.
- Record the meeting if you can; notes taken live always miss the decision.
06 — FAQ
Frequently asked about Work and Productivity
Can it read a transcript?
Yes, and it works better on transcripts than on your notes because it sees the whole argument. Watch the token limit on very long meetings.
What if there were no decisions?
Then the meeting had no outcome — the output should say that plainly. That is useful information, not a failure of the prompt.
Next
You may also find these useful
Professional Email Prompt (Including Difficult Messages)
Decline, chase, apologise and raise prices without damaging the relationship. One-purpose emails with a clear ask.
Beginner ChatGPTClaudeBusiness Plan Prompt: One Page You Will Actually Use
Instead of a 40-page template, a one-page plan that gets used: customer, value, revenue, cost and the first 90 days.
Intermediate ChatGPTClaudePresentation Prompt: Slide-by-Slide Structure
One message per slide instead of text-filled slides, with speaker notes carrying the detail.
Intermediate ChatGPTClaudeDecision-Making Prompt: Criteria, Weights, Scenarios
Turns a stuck decision into criteria, weights and scenarios, separating the choice from the emotion.
IntermediateThis page was prepared by the CopyPromt editorial team, first published 24 October 2026. Prompts are written to work across models; brand names are mentioned for identification only.