Turn meeting notes into an action list: a worked example
By TechlyUp · Updated · Professionals and beginners
To turn meeting notes into a trustworthy action list, ask the AI to extract only explicit commitments, preserve missing owners or deadlines as unknown, and keep proposals separate from decisions. Check every row against the original notes before sharing it.
The scenario and source notes
This is a synthetic teaching example created for this guide. It is not a customer case study, testimonial, time-saving measurement or real meeting transcript. The aim is to show the review process so you can reproduce it.
Practice notes: “Maya will send the draft by Thursday. Arun will check the export bug; no deadline agreed. Someone suggested moving the launch to Monday, but the team did not decide. The support checklist needs an owner.”
Ask for evidence and explicit gaps
Keep the instruction focused on extraction. Asking the model to “make a complete project plan” would invite it to add information that is not present in these notes.
TASK: Extract actions from the supplied notes. FORMAT: A table with Action, Owner, Deadline, Evidence. Then a separate list of unresolved decisions. CONSTRAINTS: Do not assign an owner or date unless the notes do. Use “not specified” for missing values. Proposals are not approved decisions. NOTES: [paste the synthetic notes above]
An acceptable result to compare against
The following is an authored expected result, not a claim that a particular model produced it. Different wording is acceptable if it preserves the same facts.
Action | Owner | Deadline | Evidence Send the draft | Maya | Thursday (calendar date not specified) | “Maya will send the draft by Thursday” Check the export bug | Arun | Not specified | “Arun will check the export bug; no deadline agreed” Assign the support checklist | Not specified | Not specified | “The support checklist needs an owner” Unresolved: moving the launch to Monday was suggested, not decided.
Audit the output before sharing
An answer that says “launch moved to Monday” fails the exercise. An answer that assigns the checklist to Maya also fails, even if doing so would seem convenient. Check that Thursday has not silently become a guessed calendar date.
If the assistant combines decisions and suggestions, ask it to revise those rows while preserving supported facts. A person still needs to resolve the real owner and launch decisions.
Package the workflow for reuse
Save the prompt, input, expected-result rules and a reviewed example. Add a boundary: only notes approved for the chosen tool may be used. Before sharing a real output, verify that names, dates and commitments match the actual meeting record.
To measure usefulness later, record how long the full manual process takes and how long the AI-assisted process takes including review and corrections. Report real observations and sample size rather than assuming the draft-generation time is the total saving.
Try it yourself
Change the practice notes so Maya only proposes sending a draft. Rerun the extraction and check that a proposal does not become an assigned commitment. Keep both versions as a small regression set for your workflow.
Start the free AI prompting microcourseSources and further reading
Examples are authored practice material, not measured learner outcomes. Tool behavior can change. Found an error? Contact TechlyUp with the page URL and correction.