Turn Meeting Notes into an Action Plan
Recovers decisions, owners, deadlines, dependencies, and open questions from messy notes.
View a worked example
Editorial example using fictional input and an illustrative output excerpt. It is not a recorded model test.
Example input
Notes: On September 5, Lin says the login draft is due Tuesday, after Jay confirms the fields. Jay says Monday. No rollout date is agreed. People worry that existing users may fail to sign in.
Example output
Decision: confirm fields before drafting; rollout date remains open. Risk: existing-user login failures, unresolved. Before the next meeting: collect login test results; owner TBD.
| Task | Owner | Due | Dependency | Acceptance |
|---|---|---|---|---|
| Confirm fields | Jay | Monday, exact date TBD | None stated | Approved field list |
| Login draft | Lin | Tuesday, exact date TBD | Field confirmation | Reviewable draft |
Check the result
- Check every action against the notes; do not invent a rollout decision.
- Confirm the calendar dates for Monday and Tuesday.
- Acceptance criteria are proposed interpretations and need team confirmation.
Fill in the blanks0/1
Fill these in and the prompt updates as you type. Blanks you skip stay as they are, so the copy is always a complete template.
Prompt
Turn the following [meeting notes] into an action plan the team can execute immediately. Start with one paragraph explaining what the meeting ultimately achieved. Then provide an action-item table with task, owner, deadline, dependency, and definition of done. If the source does not name an owner or date, write 'to confirm' rather than assigning one. Then list decisions already made, issues that remain disputed, risks mentioned without a conclusion, and materials needed before the next meeting. Remove greetings and repetition, but retain constraints that could change a decision.
Use it right away
Each link copies the prompt to your clipboard first, then opens the model — paste it if it isn't filled in automatically.