AI Meeting Notes: Merge Multiple Attendees' Notes into Decisions, Action Items, and TBD Items
When creating AI meeting notes, instead of polishing only one person's notes, practice combining records from multiple attendees and organizing decisions, action items, TBD items, and differences between records together with source tags. Using fictional Team Haneul meeting notes from 2026-10-20, this guide shows how to create a draft for team sharing without forcing different wording into a single version.
Content checked 2026.09.22Copyable prompts
Show contents
Who this is forNon-developer teams that want to merge meeting notes from multiple attendees into one document without losing the original sources or unresolved items
What you need
A general AI chat tool that accepts text input
Prepare each attendee's notes for the same meeting separately
Use fictional or de-identified data instead of real confidential information, customer information, or contact details
Have someone compare the AI-organized version against the original notes
01Preserve sources when merging multiple notes
After a meeting, each attendee's notes emphasize different things. One person may record only decisions, while another leaves their own action items or wording that has not yet been confirmed. In AI meeting notes, the important point is not to make the sentences flow smoothly, but to preserve traceability so the team can see which note each item came from.
This article uses a fictional Team Haneul meeting held on 2026-10-20. The purpose of the meeting notes is not to invent decisions that are absent from the input, but to separate commonly confirmed facts, assigned tasks, TBD items, and differences between records so the team can review them again.
02Enter each attendee's notes with item numbers
Attach the attendee's name and an item number to the input material. Even when two notes appear to describe the same thing, keep different wording as written. This example includes one note that records the promotional-material deadline as an exact date and another that uses a relative expression.
Sample input
Meeting: Team Haneul workshop preparation meeting
Meeting date: 2026-10-20
Team members: Minseo (team lead / overall schedule), Junho (venue / supplies), Seoyeon (promotion / registration), Doyun (program / instructor outreach)
Event: Neighborhood Digital Basics Workshop
Event date: 2026-11-14
Event time: 14:00–16:00
Capacity: 30 people
Audience: local residents
Participation fee: none
Venue candidate Option A: Civic Center 3rd-floor seminar room, capacity 32 people, projector available, elevator available, booking availability confirmed
Venue candidate Option B: district library auditorium, capacity 60 people, booking availability not confirmed
Shared schedule: venue confirmation 2026-10-24 / final promotional material 2026-10-28 / instructor confirmation 2026-10-30
Shared registration status: as of 2026-10-23, 22 people
Minseo notes
[Note-Minseo-1] Reconfirmed the plan for event date 2026-11-14, time 14:00–16:00, and capacity 30 people.
[Note-Minseo-2] Confirm the venue by 2026-10-24. Junho will organize and share the confirmation status of Option A and Option B.
[Note-Minseo-3] Final promotional material deadline is 2026-10-28. Seoyeon will prepare the final version reflecting the confirmed venue.
[Note-Minseo-4] Instructor confirmation deadline is 2026-10-30. Doyun will organize the outreach progress status.
Junho notes
[Note-Junho-1] Option A: Civic Center 3rd-floor seminar room has capacity 32 people, projector / elevator available, and booking availability confirmed.
[Note-Junho-2] Heard that the promotional material would be finished 'sometime next week.'
[Note-Junho-3] Option B: district library auditorium has capacity 60 people. Booking availability has not yet been confirmed.
Seoyeon notes
[Note-Seoyeon-1] Recorded that the final promotional material should be ready by 2026-10-28.
[Note-Seoyeon-2] Once the venue is confirmed, the venue wording in the promotional material must be updated.
[Note-Seoyeon-3] Registration is still ongoing, and the registration count was not separately recorded in the meeting notes.
The shared registration status is listed separately to keep the series background consistent, but the 2026-10-20 meeting notes themselves do not pull in a later registration count as though it were a decision made at the meeting. Distinguishing the time scope of inputs is also an important part of reviewing meeting notes.
03Ask to separate decisions, action items, TBD items, and record differences
In the prompt, specify classification criteria rather than asking only for a summary. In particular, when records differ, do not have AI choose the more plausible sentence and treat it as confirmed; require both sources to remain. Also ask that owners and deadlines be left as 'TBD' or 'Needs confirmation' when the input does not support them.
Prompt
Organize the attendee-by-attendee meeting notes above into one draft of AI meeting notes for team sharing.
Categories:
- Decisions or reconfirmed facts
- Action items: show an owner and deadline only when they appear in the input
- TBD or Needs confirmation
- Different records or wording differences
- Draft team-sharing message
Rules:
- Keep the original source tag that supports each item at the end of the item.
- Do not arbitrarily delete one of two different records or treat one as confirmed.
- Use the shared schedule and attendee notes as distinct sources.
- Do not invent owners, deadlines, or completion status that are not in the input.
- Do not present information from after the meeting as though it were a decision made during the meeting.
- Do not add real contact details or personal information.
04Review a team-shareable draft that preserves source tags
Example result
[Example result · not an actual AI output]
Decisions / Reconfirmed
- Reconfirmed the plan for event date 2026-11-14, time 14:00–16:00, and capacity 30 people. [Note-Minseo-1]
Action items
- Junho: organize and share the confirmation status of Option A and Option B. Venue confirmation deadline 2026-10-24. [Note-Minseo-2] [Note-Junho-1] [Note-Junho-3]
- Seoyeon: prepare the final promotional material reflecting the confirmed venue. The date in the shared schedule and in Minseo / Seoyeon notes is 2026-10-28. [Note-Minseo-3] [Note-Seoyeon-1] [Note-Seoyeon-2]
- Doyun: organize instructor-outreach progress. Instructor confirmation deadline 2026-10-30. [Note-Minseo-4]
TBD / Needs confirmation
- The final venue is still TBD. Booking availability for Option B needs confirmation. [Note-Junho-3]
Record differences
- Junho recorded the promotional-material completion timing as 'sometime next week,' while Seoyeon recorded 2026-10-28. The shared schedule also lists 2026-10-28, but the wording difference between the meeting records should remain visible and be checked when sharing with the team. [Note-Junho-2] [Note-Seoyeon-1]
Draft team-sharing message
- Team Haneul meeting notes have been merged. The venue is scheduled to be confirmed by 2026-10-24, and Junho will organize the candidate status. Seoyeon's final promotional material deadline is recorded as 2026-10-28, and Doyun's instructor confirmation deadline as 2026-10-30. The final venue and booking availability for Option B need confirmation. The promotional-material deadline is worded differently across notes, so please check the original source tags as well.
Category
Content
Owner
Deadline
Source
Reconfirmed
Keep event schedule / capacity plan
Minseo
No confirmation needed
[Note-Minseo-1]
Action item
Share confirmation status of venue candidates
Junho
2026-10-24
[Note-Minseo-2] [Note-Junho-1] [Note-Junho-3]
Action item
Prepare final promotional material reflecting the confirmed venue
Seoyeon
2026-10-28
[Note-Minseo-3] [Note-Seoyeon-1] [Note-Seoyeon-2]
Action item
Organize instructor-outreach progress status
Doyun
2026-10-30
[Note-Minseo-4]
TBD
Final venue and booking availability for Option B
Junho
2026-10-24
[Note-Minseo-2] [Note-Junho-3]
Record difference
Wording for promotional-material completion timing
Seoyeon
2026-10-28 / sometime next week
[Note-Junho-2] [Note-Seoyeon-1]
A good merged version is not a document that chooses the most plausible note. It is a document that lines up the points the team needs to verify again. In particular, relative expressions such as 'sometime next week' should not be converted arbitrarily into a date; preserve the original wording. Even if the shared schedule contains an exact date, the wording difference between meeting notes can still be preserved as a record.
05Fix meeting notes that erase TBD items and record differences
Flawed result
[Common flawed result · not an actual AI output]
All venue discussions have been resolved, and the promotional-material schedule was agreed without disagreement. Each owner can proceed according to the existing plan, and there is nothing else to confirm.
This example removes the TBD status and record differences that remain in the input. The final venue has not yet been decided, and booking availability for Option B has not been confirmed. In addition, Junho's 'sometime next week' record and Seoyeon's exact-date record use different wording. Removing this difference makes it difficult to trace later who understood the schedule based on which evidence. To fix it, restore the TBD / Needs confirmation items and both source tags.
06Before sharing, have people verify the source text, timing, and owners
Before team sharing, having only one attendee read the organized version may not be enough. Check that no source items were omitted, that owners and deadlines actually appear in the notes, and that information created after the meeting has not been mixed in as though it were a decision made during the meeting. Important decisions are confirmed through the team's approval process, not by the wording of the meeting notes alone.
Checklist
Pre-share review checklist
- Are decisions, action items, TBD items, and record differences clearly separated?
- Does each key item retain its original note tag?
- Are owners and deadlines actually present in the input?
- Were different records kept separate rather than arbitrarily merged into one?
- Was post-meeting status kept from being presented as a decision made during the meeting?
- Are real confidential information, customer information, and contact details excluded?
The next step after merging notes from multiple people is to collect multiple people's progress updates under the same criteria. The next article, “AI Weekly Report: Roll Up Multiple Team Members' Progress into One Report” shows how to combine completed work, work in progress, delays, dependencies, help requests, and items needing confirmation in one report.
What to check yourself
Fictional input and edited examples · no actual AI execution · name, date, and number consistency check
Check that every code block has a role and that it is one of input / prompt / output / bad_output / checklist
Compare names, YYYY-MM-DD dates, HH:MM times, and numbers in output against the input in the same article
Check that the timing of the 2026-10-20 meeting notes is not confused with the registration status as of 2026-10-23
Check that 2026-11-14, 14:00–16:00, capacity 30 people, and key deadlines match the shared fictional case
Check that source tags remain on record differences and TBD items
Check that every table row has the same number of columns as the header and that no effect metrics are expressed
Verification limits
This is an edited example based on fictional notes, not meeting notes generated by an actual AI tool. In real meetings, people must compare each attendee's original notes with the latest status and separately follow the team's decision and approval process.
When introducing team collaboration AI for the first time, it is easier to manage if you compare tasks where multiple people repeatedly collect and verify information rather than starting with eye-catching features. Using 6 fictional tasks from Team Haneul, this guide describes expected benefits qualitatively, checks review burden and sensitive-information risk, and then narrows down the first use case. AI organizes the candidates, but the team makes the final choice.
Practice using AI to collect weekly updates in different formats from each team member and reorganize them into completed work, work in progress, delays, dependencies, help needed, and items needing confirmation. Using Team Haneul reports from the same period, this guide creates an AI weekly report example that preserves both reference times and sources when numbers differ instead of deleting one value.
This guide explains how to reorganize scattered notes into background, current status, material locations, next actions, cautions, and TBD items so someone else can continue the work immediately when the owner is absent. Using a fictional case in which Seoyeon's promotion and registration work is handed over to Junho, it creates both an AI work handover document and questions the recipient should verify.
Practice comparing confirmed facts, evidence, opposing views, and unverified assumptions in one framework without letting AI make the conclusion when team members disagree. Using Team Haneul’s Venue Option A and Option B for the workshop, we identify the decision owner and deadline clearly and leave items for the team to verify before making the final judgment.
Practice turning a short work request from a team lead into a draft request the team can agree on again, separating confirmed requirements from missing conditions instead of letting AI fill in the gaps arbitrarily. Using Team Haneul’s request, 'Please prepare some workshop materials,' we leave completion criteria, included and excluded scope, and submission conditions as clarifying questions.
Learn how to turn team collaboration AI into a team asset that is reviewed and revised together rather than a set of individual prompts. We follow Team Haneul as it improves an AI meeting-notes prompt from v1.0 to v1.1 and checks it again with the same test input.
Learn how to check facts, omissions, sensitive information, owners, and approval status by role before sharing an AI weekly-report draft with the team. Separate the author, reviewer, and approver and record what evidence was checked so AI output is not mistaken for the team’s official conclusion.