To extract meeting action items with AI, ask for a separate record of each task, its owner, its deadline, and the words that support it. Keep suggestions and decisions outside the action list unless the notes also contain an assignment or commitment. An empty owner field is more useful than a plausible name that nobody agreed to.
This guide uses fictional meeting notes and an editorially checked example. It is not a transcript of a real meeting or a test of a particular AI product. For a broad overview of a document, use our document summary workflow. Here, the deliverable is a traceable action register that participants can confirm.
1. Preserve speakers, corrections, and uncertainty
Keep the meeting date, note version, speaker names, and source order. Add stable labels such as S1 and S2 so every extracted item can point back to a passage. If the input is an automatic transcript, review unclear names and dates against the recording or the participant before treating them as reliable evidence.
Use only notes you are permitted to share with your chosen tool. Remove unnecessary personal details while keeping consistent speaker labels. A role such as “designer” can replace a name, but do not merge two different speakers under one label.
Keep phrases such as “if approved,” “possibly,” and “I can check” intact. They change what was promised. Preserve relative deadlines such as “next Friday” until the meeting date and intended meaning are confirmed. Converting an ambiguous phrase into a precise calendar date does not resolve the ambiguity.
2. Read the fictional meeting notes
Source: onboarding pilot review, 10 September 2026, notes version 1. These six entries were written for this guide.
- S1 — Maya: “I will send the revised onboarding checklist by 15 September 2026.”
- S2 — Noah: “Could Leo record a welcome video? It might help.” No response from Leo is recorded on this proposal.
- S3 — Leo: “I will finish the browser QA report by 16 September 2026. Correction: make that 18 September 2026.”
- S4 — Meeting decision: “Keep the pilot limited to 20 volunteers. The wider launch date is undecided.”
- S5 — Meeting note: “The support FAQ needs an update before the pilot. No owner or calendar deadline was assigned.”
- S6 — Maya: “If the revised checklist is approved, I will email it to the volunteers. I am not committing to a send date yet.”
The notes contain two unconditional personal commitments, one conditional commitment, and one identified task without an owner. They also contain a proposal and a decision. Those categories should remain visible in the result.
3. Use a prompt that requires evidence for each field
Extract an action register from the meeting notes below. Use only these notes. For each action, return: - Task and source label. - Owner explicitly assigned or committed in the source; otherwise “unassigned.” - Deadline exactly as stated; otherwise “not stated.” - Any condition or dependency. - Classification: explicit commitment, conditional commitment, or unassigned task. - A short exact excerpt supporting the task, owner, and deadline. Use separate excerpts if needed. Put proposals, decisions, and unresolved questions in separate lists. Do not turn a suggestion, a question, or a decision into an assigned task. Apply an explicit correction to the same commitment and retain the correction in the evidence. Flag conflicting statements that do not explicitly replace one another. Do not infer owners from who spoke or from job titles. Do not convert relative dates without enough context. Do not mark work complete or send reminders. End with the missing information participants need to confirm. Meeting date and note version: [insert] Labeled notes: [paste here]
The evidence requirement makes the output easier to inspect; it does not guarantee correctness. Anthropic’s guidance on reducing unsupported answers recommends allowing uncertainty and checking claims against source passages, while noting that such techniques do not eliminate errors. Compare the returned excerpts with your original notes.
4. Compare the result with this checked action register
This is an editorial reference answer for the six entries above. “Explicit commitment” describes what the notes record; it does not mean the task has been completed or independently reconfirmed.
| Task and evidence | Owner and timing | Classification and condition |
|---|---|---|
| A1. Send the revised onboarding checklist. S1: “I will send the revised onboarding checklist by 15 September 2026.” | Maya 15 September 2026 | Explicit commitment. No condition stated. |
| A2. Finish the browser QA report. S3: “I will finish the browser QA report” and “Correction: make that 18 September 2026.” | Leo 18 September 2026 | Explicit commitment. The explicit correction replaces 16 September. |
| A3. Update the support FAQ. S5: “The support FAQ needs an update before the pilot.” | Unassigned Before the pilot; calendar deadline not assigned | Unassigned task. Owner and usable calendar deadline need confirmation. |
| A4. Email the revised checklist to the volunteers. S6: “If the revised checklist is approved, I will email it to the volunteers.” | Maya Not stated | Conditional commitment. Requires checklist approval; no send date committed. |
Keep the following outside the action register:
- Proposal — S2: ask whether Leo will record a welcome video. Leo has not accepted the task in the notes.
- Decision — S4: limit the pilot to 20 volunteers. This does not assign someone to recruit them.
- Open questions: who owns the FAQ update, what date does “before the pilot” mean, who will approve the checklist, and when should the conditional email be sent? The wider launch date is also undecided.
5. Catch five common extraction errors
Assigning the welcome video to Leo. S2 names him in a question. A named person is not automatically an owner. Keep the proposal pending until an assignment or acceptance is recorded.
Keeping the first QA deadline. S3 explicitly corrects the same commitment from 16 to 18 September. Preserve both the final date and the evidence of the correction. If two notes merely disagree, flag the conflict instead of assuming that the later line wins.
Borrowing the checklist deadline for the email. A1 and A4 concern the same document but are separate tasks. The 15 September deadline belongs to sending the revised checklist in S1. S6 gives neither a send date nor approval completion, so the email cannot inherit that deadline.
Assigning the FAQ to the most likely person. S5 explicitly leaves ownership open. Even if a participant manages support, that job title is not evidence of an assignment in these notes.
Turning a participant limit into a recruitment task. S4 records a constraint. “Recruit 20 volunteers” would introduce an action, an implied goal, and possibly an owner that the source does not provide.
6. Confirm the list before using it to manage work
Read the register alongside the notes, checking one field at a time: task, owner, timing, condition, and evidence. Also read every source entry once to catch omissions. A list can contain no invented tasks and still miss a real commitment.
Ask participants to resolve missing ownership and ambiguous timing. Record their replies as a new source version rather than rewriting the original meeting notes without a trace. Give each task a stable identifier, and keep a separate status field for later updates such as “in progress” or “completed.” An extracted promise alone is not evidence for either status.
For a follow-up message, use the AI email rewriting guide to present the checked list clearly and ask targeted questions. Once owners and deadlines are confirmed, the daily scheduling workflow can help fit the work into available time. Keep the unassigned and conditional items visible so they do not silently become scheduled commitments.
Browse more practical prompts and worked examples in the AI guides by task.
Need a tool to capture the source conversation? Our Otter, Fireflies, and Notion comparison covers spoken-language support, audio capture, plan limits, and a short test before using an AI notetaker in regular meetings.