A page of meeting notes can contain five different things: ideas, questions, decisions, tasks and small talk. AI can help organise that mixture into something easier to review. The key is to ask it to sort what is there, and to leave gaps visible rather than completing the story for you.
Microsoft’s meeting-notes guidance describes AI-generated key topics and action items, and explicitly recommends verifying the results. The approach here works with your own typed notes, so you do not need to start by recording a meeting or buying a meeting assistant.
Source: Microsoft’s guide to generating meeting notes
Begin with notes you are allowed to share
For practice, invent a short meeting. For real work, use your organisation’s approved tool and follow its information-sharing rules. If you later use recording or transcription, tell participants and follow the applicable meeting policy before starting. Typed notes are enough for this exercise.
Here is a fictional example: “Community workshop. Agreed: limit the group to 12 people. Maia will ask the library about a room by Friday. Maybe print handouts. Need to check projector. Budget still undecided.” Notice how little of that is a confirmed task with both an owner and a deadline.
Ask for three separate sections
The group size belongs under Decisions. Asking the library belongs under Action items, with Maia as the owner and Friday as the stated deadline. “Maybe print handouts” remains a suggestion. The projector and budget need follow-up; the notes do not tell us who has accepted responsibility.
Why does that distinction matter?
A tidy list can quietly turn “we could” into “we will”. That is a substantive error, even if the wording sounds professional. The person reading your summary may assume someone agreed to do a job when nobody did. Keeping suggestions and decisions separate avoids false certainty.
Relative dates need attention too. If you intend to send the summary later, confirm which date “Friday” means. Do not let the assistant choose a calendar date when the meeting date or intended week is unclear.
Review before sharing
- Compare each decision with the original notes.
- Check that named owners really accepted their tasks.
- Confirm dates and any numbers or spending limits.
- Keep unresolved disagreements visible.
- Ask participants to correct the draft when the notes are incomplete.
If the AI cannot point to support for an item, remove it or label it as a proposed follow-up. You can ask, “Which entries depend on an assumption?” but that second AI answer also needs checking against your notes.
Does a task list actually create tasks?
A list written in a chat does not, by itself, create calendar events, reminders or tasks in another app. Transfer the approved actions yourself, or use an explicitly connected workflow and verify what it created. For a beginner, the simplest useful result is a short reviewed summary that everyone can understand.
Try the fictional example now. The goal is not a flawless transcript. It is a record that makes the next conversation easier: what was agreed, who is doing what, and what still needs a decision.

