Turn meeting notes into an action list with owners, due dates, and done criteria

01Result to complete: a checkable action list

If a meeting ends with only “review this” or “improve that,” it becomes unclear what to confirm with whom. An action list records the task, the responsible role, the due date, the deliverable that shows completion, and the supporting note together. The goal is not to fill in unagreed items so there are no blanks. Showing where the undecided items are is what makes the next check possible.

02Separate decisions, tasks, and suggestions

The person who spoke is not necessarily the owner. An opinion like “it would be good to improve this” is also different from a commitment to do it. If responsibility or schedule is unclear, leave it as an item to confirm with the facilitator and the person involved.

03Order for turning notes into an action list

1. Write the meeting date and give the note sentences evidence numbers such as N01 and N02.
2. Mark tasks that were explicitly agreed, and put in each row one task whose completion can be judged.
3. Record the role or person who will do it. If it is not in the original, leave it as undecided.
4. Write the due date as YYYY-MM-DD. If the range is vague, such as “sometime next week,” keep the original wording and mark it as needing confirmation.
5. In the done criteria, write the deliverable, quantity, and check criteria. If “reviewed” alone makes it hard to judge completion, decide on a result file or other evidence of the check.
6. Add the checker and evidence number, and collect unconfirmed items separately.
7. Share after the owners and the facilitator have checked the original, schedule, and done criteria. Do not record that AI stood in for agreement or confirmation at this stage.

04Extract two tasks from synthetic meeting notes

회의 메모 — 설명용 합성 자료
회의일: 2026-09-19. 실제 회의·인물·회사와 무관합니다.
[N01] 편집 담당이 2026-09-23까지 안내문 제목 후보 3개와 각 후보의 선택 이유 한 문장씩을 작성한다.
[N02] 디자인 담당이 2026-09-24까지 휴대폰 폭 360 px와 데스크톱 폭 1280 px의 화면 예시를 각 1장 만든다. 회의 진행자가 두 파일과 잘린 글자 여부를 확인한다.
[N03] 문의 문구를 바꾸자는 제안이 나왔다. 누가 언제 할지는 정하지 않았다. 적용 여부도 다음 검토 때 정한다.
[N04] 배포일은 제목과 화면 검토가 끝난 뒤 정한다. 이번 회의에서는 날짜를 확정하지 않았다.

Changing the inquiry wording in N03 is undecided in whether to apply it, who owns it, and when, so it goes in the follow-up list. The release date in N04 is also not automatically set to September 24. The due date for the design files and the release date are different facts. A01 was agreed as a task, but it has no checker yet, so that status is kept as it is.

05An AI request with less sensitive information

다음 합성 회의 메모를 실행 목록으로 정리해 주세요. 실제 개인정보와 내부 기밀은 없습니다.
목적: 합의된 일과 추가 확인이 필요한 제안을 구분해 담당자가 확인할 수 있게 합니다.
입력: 아래 [N01]처럼 번호가 있는 메모입니다. 입력에 없는 담당자·기한·완료조건·승인을 만들지 마세요.
출력 1: 실행 목록. 열은 ID, 할 일, 담당 역할, 기한, 완료조건, 확인자, 근거 메모 ID, 확정 상태입니다.
출력 2: 추가 확인 목록. 미정인 담당·기한·적용 여부·의존 조건을 따로 적으세요.
규칙:
- 명시적으로 합의된 수행 항목만 실행 목록에 넣습니다.
- 제안·논의·미확정 일정은 확정 작업으로 바꾸지 않습니다.
- 상대 날짜는 회의일과 문맥이 명확할 때만 풀어 쓰며, 모호하면 원문과 확인 필요를 남깁니다.
- 확인자가 원문에 없으면 미정으로 표시합니다. 발언자를 자동으로 담당자나 승인자로 지정하지 않습니다.
- 완료조건은 원문에 있는 결과물·수량·검사 기준을 유지합니다. 추가 기준은 별도의 제안으로만 표시합니다.
- 책임을 지시하거나 초대·메일·메신저 전송을 실행하지 않습니다. 표만 작성합니다.
- 실명·연락처·고객 정보·계약 금액은 출력하지 않습니다. 실제 자료를 쓰게 되면 승인된 최소 발췌문만 사용합니다.
- 사람이 원문과 대조해야 하는 항목을 마지막에 짧게 적습니다.
이 요청은 실제 실행이나 합의 확인을 대신하지 않습니다.

[회의 메모]
회의 메모 — 설명용 합성 자료
회의일: 2026-09-19. 실제 회의·인물·회사와 무관합니다.
[N01] 편집 담당이 2026-09-23까지 안내문 제목 후보 3개와 각 후보의 선택 이유 한 문장씩을 작성한다.
[N02] 디자인 담당이 2026-09-24까지 휴대폰 폭 360 px와 데스크톱 폭 1280 px의 화면 예시를 각 1장 만든다. 회의 진행자가 두 파일과 잘린 글자 여부를 확인한다.
[N03] 문의 문구를 바꾸자는 제안이 나왔다. 누가 언제 할지는 정하지 않았다. 적용 여부도 다음 검토 때 정한다.
[N04] 배포일은 제목과 화면 검토가 끝난 뒤 정한다. 이번 회의에서는 날짜를 확정하지 않았다.

If you use real meeting notes, first confirm the approved environment and the scope of data. Replace unnecessary real names with role names, and delete customer or contract information that does not need to be shared externally. Replacing names with roles does not remove every identification risk, so also consider whether unusual events or numbers are needed. NIST's guidance treats generative AI errors and privacy risks separately. Here, AI was asked only to serve as a tool for organizing a draft.

06Check before sharing the list

• Check that the 2 action items correspond to N01 and N02, respectively.
• Check that N03 was not turned into an agreed task and that no arbitrary date was put in N04.
• Check that the conditions stated in the original, 3 candidates and 2 screen examples, were kept as they are.
• Check that the undecided checker was not hidden.
• Limit what you send to each owner to the deliverable and the evidence needed. No messages were sent in the example.
• When changing to done, record the deliverable location, the checker, and the check date. Do not write that it passed review just because a file exists.

07Common errors

08Downloads and scope of checks

The download includes README.txt, meeting-notes.txt, expected-actions.json, open-questions.txt, ai-request.txt, and action-checklist.txt. The JSON structure, evidence numbers, and the dates and quantities of the two tasks were checked locally. No AI service was called, no real owner's agreement was confirmed, and no messages were sent.

This procedure is not a way to assign new responsibilities or create an approval record with legal meaning. It is a way to organize what was agreed in a meeting so it can be checked again. If your organization has approval or security standards, follow those procedures. The official references were checked on September 19, 2026.

Execution and verification record

Windows local Python; official sources checked 2026-09-19

• Checked the article JSON schema and 8 sections
• Checked the links between synthetic evidence N01/N02 and action items A01/A02
• Compared the owner roles, dates, 3 candidates, 2 screen examples, and undecided items with the original

Site-wide writing and verification principles

References

The explanations and examples were written for this site. See the official sources below for the related behavior and concepts.

• NIST AI 600-1, Generative AI Profile · Information errors and privacy risks ↗ (New tab)