Meeting write-ups are the most reliable first win in almost every job. The input is messy, the output is predictable, and nobody minds if the first attempt needs a pass from you.
The shape of a good write-up
Three sections, always the same:
- Decisions made — what is now settled, in one line each.
- Actions — what, who, by when. One owner per action, never "the team".
- Needs confirmation — anything the notes imply but do not state.
That third section is what makes the output trustworthy. Without it, models fill gaps by guessing, and a guessed owner is worse than a blank one.
The prompt
You are turning raw meeting notes into an internal write-up. Task: produce three sections — Decisions made, Actions, and Needs confirmation. For Actions, give what, a single named owner, and a date. Constraints: use only what is in the notes; if an owner or date is not stated, put the item under Needs confirmation instead of guessing; do not soften anything that sounds like a problem.
>
Notes: [paste]
Make it repeatable
Save that prompt where you will find it again — a note, a snippet, a saved chat. The value is not the single good output; it is that next Tuesday costs you two minutes instead of twenty. Once you have run it a few times without edits, it is a candidate for a fixed automation: recording lands, prompt runs, draft appears where you will see it.
Try this today
Run your last set of meeting notes through the prompt above and count how many items land in "Needs confirmation". That number is how much guessing you were previously doing by hand.