# Volunteer Debrief Lessons-Learned Register Prompt

> Turn volunteer debrief transcripts into a sourced lessons-learned table, separating observations from participant suggestions.

## Install

Copy the content below into your project:

# Volunteer Debrief Lessons-Learned Register Prompt

Turn volunteer debrief transcripts into a sourced lessons-learned table, separating observations from participant suggestions.

## Start here

Paste your raw volunteer event debrief transcript where the prompt says to. The prompt is plain text, so an ordinary AI chat that accepts text is enough. No terminal or API setup is needed.

## What this prompt does

It converts a messy debrief transcript into a Markdown table called "Lessons-Learned Register" with eight columns: Item ID, Topic, What Happened, Source, Suggested Change, Proposed By, Confidence, and Needs Human Follow-Up. It also adds a "Gaps and Ambiguities" section.

The core idea: observations and suggestions stay in separate columns and are never merged. Only changes a participant actually proposed are recorded; otherwise the cell reads "None stated." The prompt includes a fictional worked example and a pass/fail check for that example.

## How to use it

1. Copy the full prompt text (appended separately).
2. Paste it into an ordinary AI chat that accepts text.
3. Paste your transcript below the prompt, as the prompt instructs.
4. Send it and review the resulting table.

## How to check the output

- Every "What Happened" cell traces to a named speaker or identifiable comment in your transcript.
- No "Suggested Change" appears without a matching "Proposed By."
- No recommendations appear in the assistant's own voice.
- If the transcript is too short or disorganized to yield at least three distinct items, the prompt should say so and ask you for more context.

## Inputs, permissions and limits

- Input: one debrief transcript containing participant names or roles where possible. Missing names limit the Source and Proposed By columns.
- Permission: you are the one pasting the transcript, so you decide what to share. Transcripts may include personal names; remove anything you should not share before pasting.
- Limits: the prompt writes only a draft register for a human organizer to review. It does not browse, send, or schedule anything, and it does not give legal, safety, or financial advice. Such topics are logged for human follow-up.

Source reviewed; runtime not tested.

## FAQ

**What if my transcript has no speaker names?**
The Source and Proposed By columns may end up thin. The prompt asks you for additional context when it cannot extract enough distinct items.

**Does it invent recommendations?**
No. The rules forbid inferring a change that was not spoken or written; unstated changes are marked "None stated."

## Source and thanks

Original TokRepo prompt, CC BY 4.0. Reference: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>). External reference material retains its own rights.

## Complete reusable prompt

You are helping me turn a raw volunteer event debrief transcript into a lessons-learned register. I will paste the transcript below. Your job is to extract and organize the content that is actually present in the transcript — nothing more.

WHAT TO PRODUCE

Create a Markdown table called "Lessons-Learned Register" with these columns:

1. Item ID (L1, L2, L3...)
2. Topic (short label, e.g. check-in, supplies, parking)
3. What Happened (a factual statement grounded in the transcript — who observed what, where, and when if stated)
4. Source (the speaker's name or role as given in the transcript, plus a short quote fragment under 15 words)
5. Suggested Change (only if a participant actually proposed one; write "None stated" if not)
6. Proposed By (name/role of the person who suggested it; "—" if none)
7. Confidence (High / Medium / Low — based only on how clearly the transcript supports the 'What Happened' entry)
8. Needs Human Follow-Up (Yes/No, plus a one-line reason)

RULES FOR SEPARATING FACTS FROM SUGGESTIONS

- A "What Happened" entry must describe something that occurred during or around the event. Do not rephrase a suggestion as an observation.
- A "Suggested Change" entry must come from an identifiable participant in the transcript. Never invent, merge, or infer a recommendation that was not spoken or written.
- If a participant mixes observation and opinion in one sentence, split them into separate columns but keep the same Item ID.
- If the transcript contains vague statements ("it was fine," "people seemed happy"), record them as Low confidence and note in the follow-up column that specifics are missing.
- If a topic is raised but no clear outcome or change is stated, still log it with Suggested Change = "None stated" and Needs Human Follow-Up = Yes.

UNCERTAINTY AND MISSING INPUT HANDLING

- After the table, add a section "Gaps and Ambiguities" listing every place where the transcript was unclear, contradictory, or silent on an important point.
- List any speaker whose role or name could not be determined from the transcript.
- If the transcript is too short or too disorganized to extract at least three distinct items, say so and ask me what additional context I can supply.

REVIEW CHECKS BEFORE YOU FINISH

1. Verify every "What Happened" cell can be traced to at least one named source or identifiable comment in the transcript.
2. Verify no "Suggested Change" appears without a matching "Proposed By."
3. Verify no two Item IDs describe the same event from different angles unless you explicitly note the overlap in the follow-up column.
4. Confirm the register contains no recommendations written in your own voice.

BOUNDARIES

- Do not browse, send, or schedule anything. You are only producing a draft register for a human organizer to review.
- Do not give advice on legal, safety, or financial matters. If such topics arise, log them as items needing human follow-up.
- Do not add filler rows to reach a target count.

WORKED EXAMPLE (fictional, for shape only)

Input fragment: "Priya: The check-in table only had one person until 9:30, so the line got long. Tom: We should have two people from the start next time. Priya: Also the name badges ran out by 10."

Expected output row:
| L1 | Check-in staffing | Only one volunteer at the check-in table until 9:30, causing a long line | Priya, organizer ("line got long") | Have two people at check-in from the start | Tom | High | Yes — confirm actual arrival numbers |

A pass/fail check on this example: the row passes if "What Happened" contains only the staffing observation and the long line, while "Suggested Change" contains only Tom's proposal. The row fails if the suggested change is merged into the observation column, or if Tom's name is missing from Proposed By.

Now paste your transcript below. I will review the register and fill in any follow-up items myself.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 志愿者复盘经验教训登记表提示词

把志愿者复盘记录整理成有来源的经验教训表，区分观察到的情况与参与者提出的建议。

## 开始使用

把原始的志愿者活动复盘记录粘贴到提示词指明的位置。提示词是纯文本，任何能接受文字的普通 AI 对话界面都够用。无需终端或 API 配置。

## 这条提示词能做什么

它把零散的复盘记录整理成名为“Lessons-Learned Register”的 Markdown 表格，共八列：Item ID、Topic、What Happened、Source、Suggested Change、Proposed By、Confidence、Needs Human Follow-Up。此外还会加上“Gaps and Ambiguities”一节。

核心原则：观察与建议分列，绝不混在一起。只有参与者在记录中实际提出的改动才会被写入；否则该单元格写“None stated”。提示词内含一个虚构示例以及针对该示例的通过/不通过检查。

## 如何使用

1. 复制完整提示词文本（另行附上）。
2. 粘贴到能接受文字的普通 AI 对话界面。
3. 按提示词要求，把复盘记录粘贴在提示词下方。
4. 发送并检查生成的表格。

## 如何检查输出

- 每个“What Happened”单元格都能追溯到记录中具名的发言人或有明确出处的评论。
- 任何“Suggested Change”都有对应的“Proposed By”。
- 不会出现助手本人口吻的建议。
- 如果记录过短或过于零乱、无法提炼出至少三个不同条目，提示词应当说明并请你补充背景。

## 输入、权限与限制

- 输入：一份复盘记录，尽可能包含参与者姓名或角色。缺少姓名会削弱 Source 和 Proposed By 两列的内容。
- 权限：由你自己粘贴记录，因此分享什么由你决定。记录可能包含个人姓名，粘贴前请先移除不应分享的内容。
- 限制：提示词只生成供人工组织者审阅的草稿登记表，不会浏览、发送或安排任何事项，也不提供法律、安全或财务建议；此类话题只记为需人工跟进。

源码已审阅；未做运行测试。

## 常见问题

**如果记录里没有发言人姓名怎么办？**
Source 和 Proposed By 两列可能内容单薄。当无法提炼足够多的不同条目时，提示词会请你补充背景。

**它会编造建议吗？**
不会。规则禁止推断未说出口或未写下的改动；未提出的改动一律标为“None stated”。

## 来源与致谢

TokRepo 原创提示词，CC BY 4.0。参考：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。外部参考资料保留其各自权利。

## 完整可复制提示词

你正在帮我把一份原始的志愿者活动复盘记录整理成经验教训登记表。我会把记录粘贴在下方。你的任务是提取并整理记录中实际存在的内容——仅此而已。

需要产出什么

创建一张名为“Lessons-Learned Register”的 Markdown 表格，包含以下列：

1. Item ID（L1、L2、L3……）
2. Topic（简短标签，例如 check-in、supplies、parking）
3. What Happened（基于记录的事实陈述——谁观察到了什么、在哪里、以及记录中若有提及的时间）
4. Source（记录中给出的发言者姓名或角色，外加一段少于 15 词的简短引语片段）
5. Suggested Change（仅当参与者实际提出改动时才填写；若没有则写“None stated”）
6. Proposed By（提出建议者的姓名/角色；若无则填“—”）
7. Confidence（High / Medium / Low——仅依据记录对“What Happened”条目的支持清晰程度）
8. Needs Human Follow-Up（Yes/No，外加一行理由）

区分事实与建议的规则

- “What Happened”条目必须描述在活动期间或前后实际发生的事情。不要将建议改写为观察。
- “Suggested Change”条目必须来自记录中可识别的参与者。绝不编造、合并或推断未说出口或未写下的建议。
- 如果参与者在同一句话中混合了观察和意见，请将它们拆分到不同列，但保持相同的 Item ID。
- 如果记录中包含含糊的表述（“it was fine”、“people seemed happy”），请将其记为 Low confidence，并在跟进列中注明缺少具体细节。
- 如果某个话题被提出但没有明确的结果或改动，仍然要记录，Suggested Change = “None stated”，Needs Human Follow-Up = Yes。

不确定性与缺失输入的处理

- 在表格之后，添加一节“Gaps and Ambiguities”，列出记录中所有不清晰、自相矛盾或对重要问题保持沉默的地方。
- 列出所有无法从记录中确定角色或姓名的发言者。
- 如果记录过短或过于零乱、无法提炼出至少三个不同条目，请说明并询问我可以补充哪些背景信息。

完成前的复核检查

1. 核实每个“What Happened”单元格都能追溯到记录中至少一个具名来源或可识别的评论。
2. 核实任何“Suggested Change”都有对应的“Proposed By”。
3. 核实没有两个 Item ID 从不同角度描述同一事件，除非你在跟进列中明确注明重叠。
4. 确认登记表中没有以你自己口吻写成的建议。

边界

- 不要浏览、发送或安排任何事项。你只是在生成供人工组织者审阅的草稿登记表。
- 不要就法律、安全或财务事宜提供建议。此类话题若出现，请记为需要人工跟进的条目。
- 不要为凑够目标数量而添加填充行。

示例（虚构，仅示形状）

输入片段：“Priya: The check-in table only had one person until 9:30, so the line got long. Tom: We should have two people from the start next time. Priya: Also the name badges ran out by 10.”

预期输出行：
| L1 | Check-in staffing | Only one volunteer at the check-in table until 9:30, causing a long line | Priya, organizer ("line got long") | Have two people at check-in from the start | Tom | High | Yes — confirm actual arrival numbers |

针对该示例的通过/不通过检查：如果“What Happened”只包含人员配置观察和排长队的情况，而“Suggested Change”只包含 Tom 的提议，则该行通过。如果建议的改动被合并到观察列中，或者 Tom 的名字未出现在 Proposed By 中，则该行不通过。

现在把你的复盘记录粘贴到下方。我会自行审阅登记表并补充任何后续事项。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/volunteer-debrief-lessons-learned-register-prompt-12c084d7
Author: Prompt Lab