Meeting notes capture what was discussed. An action list captures what somebody agreed to do next. Turning one into the other requires judgment: do not transform every suggestion into a commitment.
Read the fictional notes
The original teaching example says: “Morgan will check the room by 18 November. We may need more pens; no owner yet. Riley can print after the room is confirmed.” No real meeting or client is represented.
Mark the first sentence as a committed action, the second as an unresolved question, and the third as a conditional capability that still needs an explicit assignment. Keep the original note so you can check whether your summary changed its meaning.
Extract four fields
| Action | Owner | Timing | Status or dependency |
|---|---|---|---|
| Check room availability | Morgan | By 2026-11-18 | Agreed action; no result yet |
| Do we need more pens? | Not assigned | Not agreed | Open question; no action agreed |
| Printing may be possible | Riley named as capable, not assigned | Only after room is confirmed; no deadline | Proposal/condition; ask who will print and what |
“Will check” commits Morgan to checking, not to obtaining a confirmed room. “May need” does not agree to count or buy pens. “Can print” states capability under a condition, not Riley’s commitment to print handouts. Keep proposals and open questions out of the committed-action list until the participants agree. The table preserves that distinction; it does not invent a quantity, item, owner, result, or deadline.
Distinguish a decision from a task
“We chose the Cedar room” is a decision if the meeting actually settled it. “Ask whether Cedar is available” is an action. A decision can generate a task, but the two should remain distinct when confirmation is still needed.
Use a short verb and a visible result for each action. Replace “handouts” with “Print twelve checked handouts after room confirmation,” provided the quantity was actually agreed. If it was not, record the quantity as a question.
Confirm the interpretation
Share the concise action list through your authorized meeting workflow and ask the relevant people to confirm ambiguous ownership or timing. Do not claim that a model’s summary counts as a participant’s agreement.
Microsoft’s Teams documentation distinguishes notes and follow-up tasks, but this method also works in a plain text file or document. It does not require creating a Teams meeting or sending anything from this website.
Review the result
Compare every row with the original note. Can you point to the wording that supports its owner and date? Can someone see which item is blocked? Keep unresolved items visible until the actual participants decide them.
The action list is useful when it supports the next conversation without rewriting the previous one. An attractive table with invented commitments is worse than a short list with explicit unknowns.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Take meeting notes in Microsoft Teams
Meeting notes can distinguish agenda, notes, and follow-up tasks; the example workflow here is independent.