From meeting notes to a checked action list
Copy the prompt, keep each item tied to its source, and confirm missing details before assigning work.
Ask AI to separate confirmed commitments, unassigned needs, and suggestions—not just summarize the meeting. Require a quote from your notes for every item, and leave missing owners and deadlines marked “not stated.” Then check the result before sharing it.
“Priya will send the copy by October 14” and “maybe we should try a video” belong in different lists. The first records a commitment; the second records an idea. A fluent summary can hide that difference. An evidence column makes it easier to see where a draft goes beyond the notes.
This guide is for the person turning a team or client meeting into a follow-up. You will leave with a source-checked task list, a reusable format, and a message for confirming gaps. Start with written notes you are permitted to share.
1. Prepare the notes you can actually share
Use an AI tool permitted for the information in your notes. Remove confidential details before pasting, and number each note so you can find its source again. Keep words such as “suggested,” “agreed,” and “will”: they help distinguish proposals from commitments.
Write dates as they appear in the record. If a note says “before launch,” keep that wording rather than supplying a calendar date. If the notes are unclear about who agreed to do something, ask the attendees; a chatbot cannot recover a decision nobody recorded.
2. Copy this prompt
Use only the numbered meeting notes below. Do not add outside facts.
Sort the notes into three lists:
A. CONFIRMED COMMITMENTS
Tasks that someone explicitly agreed to carry out. For each item, give:
- Task
- Owner, exactly as recorded
- Due date or timing, exactly as recorded; otherwise "not stated"
- Evidence: note number and an exact quote supporting these details
B. UNASSIGNED NEEDS
Work the notes explicitly say is needed, with no person committed to it.
Give the needed work, owner: "not stated", any recorded timing, and an
exact supporting quote. Missing timing must stay "not stated".
C. SUGGESTIONS
Ideas or possibilities with no approval recorded. Quote the source and
keep these outside the task list. Do not assign an owner or deadline.
If a line is ambiguous, put it under "Questions to confirm" instead.
Do not invent a task, agreement, owner, or date. A missing due date does
not make an explicitly accepted task an unassigned need.
Meeting notes:
[PASTE NUMBERED NOTES HERE]3. Compare the output with this fictional example
These notes and the output below are written illustrations, not a record of a real meeting or a measured AI response.
- Priya will send the revised pricing page copy to Marcus by October 14.
- The FAQ needs an update, but we did not assign an owner or deadline.
- Marcus suggested trying a short customer video on the homepage; no decision was made.
| Category | Item | Owner / timing |
|---|---|---|
| Confirmed | Send revised pricing page copy to Marcus | Priya / October 14 |
| Unassigned | Update the FAQ | Not stated / not stated |
| Suggested | Try a short customer video on the homepage | No assignment or approval recorded |
Check the evidence for each row:
- Confirmed — Note 1: “Priya will send the revised pricing page copy to Marcus by October 14.”
- Unassigned — Note 2: “The FAQ needs an update, but we did not assign an owner or deadline.”
- Suggested — Note 3: “Marcus suggested trying a short customer video on the homepage; no decision was made.”
The FAQ does not acquire a made-up “by Friday.” Marcus is not assigned the video just because he mentioned it. If a draft makes either change, correct it against the notes.
Want to explore the book behind this workflow? Read the first chapter of Stop Typing, Start Asking free before deciding whether to buy.
4. Check before you send
Match every quote to the original notes. Check names, dates, and the words that establish a commitment. Ask attendees to resolve missing owners or unclear decisions, and keep proposed work separate until it is approved.
A useful follow-up is: “Review your draft against the notes. List any owner, deadline, or decision that is not explicitly supported. Correct those entries without filling the gaps.” Recheck that revision yourself; asking AI to review its answer is not independent verification.
Do not paste restricted client, HR, legal, health, or proprietary information into an unapproved chatbot. Replace identifiers locally only when your organization’s rules permit sharing the remaining content. Otherwise, organize the notes in a permitted system.
5. Reuse the format and send a confirmation
Keep the checked output with its source notes. Use this blank format for your next meeting; replace brackets with recorded facts and leave gaps visible.
Meeting: [title] | Notes: [source link or file]
Confirmed: [task] | [owner] | [timing or not stated] | [note + quote]
Unassigned: [needed work] | owner: not stated | [timing] | [note + quote]
Suggested: [idea] | no approval recorded | [note + quote]
Questions to confirm: [missing information]For the fictional example above, your follow-up could be:
Subject: Pricing page follow-up — please confirm open items
Priya: the notes record the revised copy going to Marcus by October 14.
Please correct this if the notes do not match your commitment.
The FAQ update still needs an owner and timing. Who can take it,
and what date can we agree on?
The homepage video remains a suggestion; no work is assigned yet.After the people involved confirm corrections, put agreed work in your team’s task tracker and link the source notes. Keep the FAQ pending until someone accepts it; record any newly agreed date as a follow-up decision.
Common questions
Can I use rough notes instead of a transcript?
Yes. The prompt works on the numbered text you provide. It cannot recover an unrecorded agreement. Keep unclear lines as questions for the participants.
What if someone accepted a task but no deadline was recorded?
Keep it as a confirmed commitment with timing marked “not stated.” Ask the owner to agree a date; do not let AI supply one.
Try the book’s method before buying
This article adapts Recipe 7.3 and Chapter 9 of Stop Typing, Start Asking: turning meeting or lecture material into an actionable brief, then checking the result against its source. The prompt above is a blog-specific adaptation, not a quotation from the book.
Read the free first chapter to judge the book’s approach. If you want the full collection of everyday administrative recipes, the English ebook is $9.99 USD before tax, with PDF and EPUB editions. This article’s prompt is free to use without buying the book.
If this workflow suits you, preview the book before deciding whether to buy. It is a collection of everyday AI recipes, rather than a meeting recorder or an automated task-management service.
Start with the free first chapter
Preview the writing and approach. The complete English ebook is $9.99 USD before tax, in PDF and EPUB.
See what is included · Buy the English ebook — $9.99 USD before tax
One-time purchase. Applicable tax is shown at checkout. Payment and delivery are handled by Lemon Squeezy.
More practical AI guides and free tool demonstrations.
▶ Subscribe to Avalon Company