Create a Shared Team AI Prompt: Version-Control the Rules for Organizing Meeting Notes

01Make it a shared team standard, not an individual prompt

Even when organizing the same meeting notes, different instructions from each team member can produce different section names, source-labeling methods, and ways of handling TBD items. The goal here is not to create 'good wording.' It is to combine the input format, expected output, prohibited behavior, and review method the team will reuse into one document and record why it changes. Unlike keeping a personal prompt, other team members should be able to see who changed what.

The fictional Team Haneul is preparing the “Neighborhood Digital Basics Workshop” for local residents on 2026-11-14 from 14:00–16:00. Capacity is 30 people and there is no fee. The venue decision deadline is 2026-10-24, the final promotional material deadline is 2026-10-28, and the instructor confirmation deadline is 2026-10-30. Registrations as of 2026-10-23 are 22 people. These facts must not be changed arbitrarily even if the shared team prompt changes.

02Keep the same test input fixed for comparison

If you change the test input every time you revise a version, it becomes difficult to tell what caused the output to change. The data below contains fictional notes from three people about the 2026-10-20 meeting. Their wording differs, and one person uses a relative expression for the promotional-material schedule. We also include the version history and changer for the shared team prompt itself so the later output does not invent new information.

Team Haneul shared facts
- Event: Neighborhood Digital Basics Workshop
- Event date: 2026-11-14
- Event time: 14:00–16:00
- Capacity: 30 people
- Audience: local residents
- Fee: none
- Venue decision deadline: 2026-10-24
- Final promotional material deadline: 2026-10-28
- Instructor confirmation deadline: 2026-10-30
- Registration status as of 2026-10-23: 22 people

Team member roles
- Minseo: team lead · overall schedule
- Junho: venue · supplies
- Seoyeon: promotion · registration
- Doyun: program · instructor outreach

Test meeting: 2026-10-20

[Note-Minseo-1] Prioritize reviewing Option A: Civic Center 3rd-floor seminar room. Make the final decision by 2026-10-24.
[Note-Minseo-2] Prepare the final promotional material by 2026-10-28.
[Note-Junho-1] Option A: Civic Center 3rd-floor seminar room has a capacity of 32 people, a projector, an elevator, and confirmed booking availability.
[Note-Junho-2] Option B: district library auditorium has a capacity of 60 people, and booking availability has not yet been confirmed.
[Note-Seoyeon-1] The promotional material needs final revision after the venue is confirmed.
[Note-Junho-3] I heard the promotional material would be finished 'sometime next week.' I want to confirm the exact date again.
[Note-Doyun-1] The instructor confirmation deadline is 2026-10-30.

Shared prompt version history
- v1.0: 2026-10-22, changed by Minseo, initial shared draft created
- v1.1: 2026-10-23, changed by Seoyeon, revised to specify rules for preserving conflicts and labeling sources

This input contains no real organizational information or customer data. When creating a shared prompt in real work, do not paste confidential information, passwords, authentication information, or personally identifiable information as-is; check the organization’s information security policy first.

03Fix input, output, and prohibited behavior in one prompt

The point of v1.1 is not to make the prompt longer, but to state the decision rules. In particular, when records from different people conflict, it requires keeping both records and separating them as Needs confirmation instead of automatically choosing one. It also prohibits filling in plausible owners or dates that are not in the notes.

Organize the meeting notes from multiple people below for team sharing.

Input rules
- Use each note’s author and item number as the source.
- Distinguish shared facts from individual notes.

Output format
1) Decisions
2) Action items
3) TBD items
4) Records that conflict or use different wording
Attach the original source tag at the end of each item.

Prohibited behavior
- Do not invent owners, dates, times, numbers, or decisions that are not in the input.
- Do not convert relative date expressions into an arbitrary YYYY-MM-DD.
- Do not arbitrarily adopt one of the conflicting records.
- If confirmation status is unclear, write 'Needs confirmation'.

At the end, briefly list the items a person should compare with the source.

04A good result preserves evidence rather than looking like the single right answer

The following is an edited example created to review the prompt, not an actual AI output. The important point is that it does not invent new decisions and preserves differing records together with their source tags.

[Example result · not an actual AI output]
Shared prompt: v1.1
Change record: 2026-10-23, changed by Seoyeon

Decisions
- The event date is 2026-11-14, the time is 14:00–16:00, and the capacity is 30 people.
- The instructor confirmation deadline is 2026-10-30. [Note-Doyun-1]

Action items
- Prioritize reviewing Option A: Civic Center 3rd-floor seminar room and make the final decision by 2026-10-24. [Note-Minseo-1]
- The promotional material needs final revision after the venue is confirmed. [Note-Seoyeon-1]

TBD items
- Booking availability for Option B: district library auditorium Needs confirmation. [Note-Junho-2]

Records that conflict or use different wording
- Minseo recorded the final promotional material deadline as 2026-10-28. [Note-Minseo-2]
- Junho recorded that he heard the promotional material would be finished 'sometime next week' and wrote that he wanted to confirm the exact date again. [Note-Junho-3]
- Therefore, the wording of the promotional material deadline needs source verification, and neither record should be deleted arbitrarily.

Items for a person to compare
- Check Minseo’s and Junho’s records of the promotional material deadline together.
- Check whether any new confirmation result for Option B booking availability has appeared in Junho’s notes.

This format is not a mechanism for AI to decide the meeting conclusion; it is a mechanism for showing team members what they need to verify. In particular, when wording differs as in [Note-Minseo-2] and [Note-Junho-3], removing one side makes the issue that needs review disappear.

05Have the team record how the shared prompt fails as well

If the team treats a shared prompt as finished after writing it once, repeated errors can persist. It is better to record what flawed output appeared and what rule was added to prevent it as part of the reason for a version change.

[Common flawed result · not an actual AI output]
- The venue was confirmed as Option B.
- Junho will complete the promotional material.
- The promotional material deadline is 2026-10-27.
- Option B is available for booking.

This example invents a decision not present in the input, assigns new work to Junho even though he is not responsible for promotion, and confirms a date and Option B booking availability that were never provided. The fix is not to polish the wording, but to add rules such as 'no guessing,' 'preserve conflicts,' and 'keep source tags' to the prompt and test it again with the same input.

Shared prompt review checklist
- Does the input format retain the author and original item number?
- Are decisions, action items, TBD items, and conflicts separated?
- Does the prompt prohibit inventing owners, dates, times, or numbers not in the input?
- Does it avoid merging different records into one side?
- Can team members verify the changed version, date, changer, and reason?
- Was the organization’s information security policy checked before entering real work data?

06Re-review version changes with the same input

A shared team prompt is closer to a small operating rule than a finished product. When creating a new version, the person making the change should record the reason, and another team member should use the same test input to check the output format and omissions before sharing it. Keeping input and output rules in text rather than relying on settings in a specific AI product makes it easier to preserve the team’s review criteria even if tools change.

• The person who revised the prompt and the person reviewing it read together what changed.
• Keep the test input unchanged and check that the decision, action-item, TBD, and conflict categories are preserved.
• Check that source tags are not lost and unverified information is not turned into confirmed information in the new version.
• Clearly mark only the version the team has decided to use in the shared location.

The next article, “How to Review and Approve AI Output as a Team: Checks Before Sharing a Weekly Report”, explains how to separately verify facts, omissions, sensitive information, owners, and final approval status before sharing even when the output was created with a shared prompt.

What to check yourself

Fictional input data and edited examples · no actual AI execution · checks for matching names, dates, and numbers

• Check that every code block has a role of input, prompt, output, bad_output, or checklist
• Check that person names, YYYY-MM-DD dates, HH:MM times, and numbers in the output exist in the input of the same article
• Check that the v1.0 and v1.1 change records match the versions, dates, and changers in the input data
• Check that conflicting promotional material deadline records are not arbitrarily merged into one side in the output
• Check that the venue, event schedule, capacity, major deadlines, and registration status do not contradict the shared facts of the series
• Check that no effect metrics such as time-saving rates or productivity-improvement figures are used