# Plain-Language Workshop Participant Agreement Prompt > A reusable prompt that turns rough workshop ground rules into a short, readable participant agreement with space for questions and host decisions. ## Install Copy the content below into your project: # Plain-Language Workshop Participant Agreement Prompt A reusable prompt that turns rough workshop ground rules into a short, readable participant agreement with space for questions and host decisions. ## Start here **What to paste:** three things after the instruction block — your current **ground rules**, the **context** (who attends, topic, length, in person or online, anything the host must personally approve), and any **terms you must keep word for word**. **Where to paste:** the full prompt (with those three parts) into any ordinary AI chat that accepts text. No terminal, account setup or plugin is needed. **How to check the output:** confirm every original rule appears somewhere, that kept terms survive word for word, that missing examples are labelled "needs an example", that `[TO CONFIRM: your question]` markers are listed in Checks, and that no invented penalties, dates or contacts were added. ## What this prompt does It restates an existing rule list in plain language under short headings, adds a blank "Questions and exceptions" area, a "Needs host decision" list drawn only from your context, and a note on what the agreement leaves vague. It never invents rules and never claims anyone was contacted or enrolled. ## Inputs and permissions - You supply the three required parts; if any is missing or thin, the prompt stops and asks for it. - Host must approve decisions such as refunds, recordings, accessibility needs, guests or leaving early. - The draft is for you to review and share yourself; it carries no legal, compliance or safeguarding advice. - The prompt is a plain-text instruction, not an executable skill and not a one-click install. ## Inputs you must have ready | Part | What to include | |------|-----------------| | Ground rules | Your current list, however rough | | Context | Participants, topic, length, setting, host-only decisions | | Terms to keep | Wording, obligations or limits that cannot be softened | ## FAQ **Can it finalise the agreement for me?** No. It produces a draft; you fill every `[TO CONFIRM: ...]` marker and decide what to send. **What if my rule list is messy?** The prompt restates it under short headings such as Respect, Participation, Time and Sharing, and uses one heading if no grouping fits, saying so. ## Privacy and limits Paste only rule lists and context you are comfortable putting into a chat service. Do not include participant names, medical details or other personal data the agreement does not need. The prompt does not contact anyone and does not present the draft as approved or binding; you remain responsible for reviewing it and filling every marker. > Source reviewed; runtime not tested. Source: original TokRepo prompt, CC BY 4.0. Reference context: [ChatGPT release notes](). ## Complete reusable prompt You are helping me turn my existing workshop ground rules into a plain-language participant agreement that a first-time attendee can read in about a minute. WHAT I WILL PASTE I will paste three things after this instruction block: 1. GROUND RULES — my current list, however rough, formal or legalistic it is. 2. CONTEXT — who the participants are, the workshop topic, its length, the setting (in person or online), and any decision the host must approve personally (for example refunds, recordings, accessibility needs, guests, leaving early). 3. TERMS I MUST KEEP — any wording, obligations or limits that cannot be softened, such as a code of conduct clause or a safety rule. If any of these three is missing or too thin to work with, stop and tell me exactly what to supply. Do not invent rules, penalties, deadlines or promises that are not in my material. Never state or imply that I have contacted, enrolled, scheduled or messaged anyone — this is only a draft for me to review and share myself. WHAT TO PRODUCE A participant agreement in this order: - A one-sentence summary of what agreeing to this means. - The rules restated in plain language, grouped under short headings such as Respect, Participation, Time, and Sharing. If my list has no natural grouping, use one heading and say so. - For each rule, one plain sentence on what it looks like in practice, drawn only from my material. If my material does not support a practical example, write "needs an example" instead of inventing one. - A clearly labelled "Questions and exceptions" section with blank space for the participant to write, plus a short neutral line explaining how to raise an exception with the host. - A clearly labelled "Needs host decision" list of anything in my rules that a participant cannot resolve alone, based only on the CONTEXT I supplied. - A short "What this agreement does not cover" note listing anything I left vague. STYLE RULES Short sentences. Everyday words. Address the participant as "you". No legalese, no threats, no guilt, no exclamation marks. Keep every date, obligation and limit that appears in TERMS I MUST KEEP, even if the wording is less friendly. Do not add rules, consequences or encouragement that are not in my material. OUTPUT FORMAT Markdown with the headings above, followed by a "Checks" section listing: every rule from my original list and where it appears in the draft; every term I asked you to keep and its exact surviving wording; and every item you marked "needs an example" or left out. UNCERTAINTY HANDLING Where my input is ambiguous, insert [TO CONFIRM: your question] instead of guessing, and list all such markers in Checks. BOUNDARIES Do not give legal, accessibility-compliance or safeguarding advice, and do not present this draft as approved or binding. I remain responsible for reviewing it, filling every marker, and deciding what to send. WORKED EXAMPLE Fictional input: GROUND RULES — attendees must arrive on time, phones silent, no recording without consent, one person speaks at a time. CONTEXT — 90-minute in-person neighbourhood gardening workshop, twelve adults, host approves recordings and accessibility requests. TERMS I MUST KEEP — "no recording without consent". Illustrative output shape: summary sentence; headings Respect, Participation, Time, Sharing; under Sharing, a plain sentence that recording needs everyone's agreement, plus [TO CONFIRM: who a participant asks about recording], since the host-approval detail can sit in Needs host decision; a blank Questions and exceptions area; and Checks flagging the "needs an example" placement for punctuality if my list gave no reason. SELF-CHECK BEFORE FINALIZING Pass or fail each: (1) Does every rule in my list appear somewhere, or is its absence named in Checks? (2) Does "no recording without consent" survive word for word? (3) Is every marker listed in Checks? (4) Is the draft free of invented penalties, dates or contacts? Now wait for my paste. Do not produce the agreement until I have supplied all three parts. ## 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. --- # 把工作坊规则改写为通俗参与者协议 一个可复用的提示词,把粗糙的工作坊基本规则改写为简短易读的参与者协议,并留出提问与主办方决定的空间。 ## 开始使用 **粘贴什么:** 在指令块之后粘贴三项内容——你现有的**基本规则**、**背景信息**(参与者是谁、主题、时长、线上或线下、任何必须由主办方亲自批准的事项),以及任何**必须逐字保留的条款**。 **粘贴到哪里:** 把完整提示词(连同这三项)粘贴进任何接受文本的普通 AI 对话。无需终端、账号设置或插件。 **如何检查输出:** 确认每条原始规则都出现在某处、需保留条款逐字不变、缺少示例处标注为“needs an example”、`[TO CONFIRM: your question]` 标记都列入 Checks,并且没有虚构惩罚、日期或联系人。 ## 这个提示词做什么 它把现有规则列表用通俗语言改写,归入简短标题下,并加入空白的“Questions and exceptions”区域、仅依据你所提供背景生成的“Needs host decision”清单,以及一份说明协议尚未涵盖内容的小注。它绝不虚构规则,也绝不声称已联系或招收了任何人。 ## 输入与权限 - 你提供三项必需内容;若任一项缺失或过于单薄,提示词会停下并索要。 - 退款、录音、无障碍需求、访客或提前离开等事项须由主办方批准。 - 草稿供你自己审阅和分享;它不提供法律、合规或安全保障建议。 - 该提示词是纯文本指令,不是可执行技能,也不是一键安装。 ## 你必须准备的输入 | 部分 | 应包含的内容 | |------|-----------------| | 基本规则 | 你现有的清单,无论多粗糙 | | 背景信息 | 参与者、主题、时长、场景、仅限主办方的决定 | | 需保留条款 | 不能软化的措辞、义务或限制 | ## 常见问题 **它能替我定稿协议吗?** 不能。它生成草稿;你需填写每个 `[TO CONFIRM: ...]` 标记并决定发送内容。 **如果我的规则列表很乱怎么办?** 提示词会将其归入 Respect、Participation、Time、Sharing 等简短标题下;若无法自然分组,则使用单一标题并说明。 ## 隐私与限制 只粘贴你愿意放进对话服务的规则清单和背景信息。不要包含参与者姓名、医疗细节或协议并不需要的其他个人数据。该提示词不会联系任何人,也不会把草稿呈现为已批准或有约束力;你仍负责审阅并填写每个标记。 > 已审阅来源;未做运行时测试。 来源:TokRepo 原创提示词,CC BY 4.0。参考背景:[ChatGPT release notes]()。 ## 完整可复制提示词 你正在帮助我把现有的工作坊基本规则改写成一份通俗易懂的参与者协议,让第一次参加的人大约一分钟就能读完。 我会粘贴什么 我会在此指令块之后粘贴三项内容: 1. 基本规则——我当前的清单,无论它多么粗糙、正式或法律化。 2. 背景信息——参与者是谁、工作坊主题、时长、场景(线下或线上),以及任何必须由主办方亲自批准的决定(例如退款、录音、无障碍需求、访客、提前离开)。 3. 我必须保留的条款——任何不能软化的措辞、义务或限制,例如行为准则条款或安全规则。 如果这三项中任何一项缺失或过于单薄而无法处理,请停下并明确告诉我需要提供什么。不要虚构我的材料中没有的规则、惩罚、截止日期或承诺。绝不要声明或暗示我已联系、招收、安排或通知任何人——这只是一份供我自己审阅和分享的草稿。 应产出什么 一份按以下顺序排列的参与者协议: - 一句话总结同意本协议意味着什么。 - 用通俗语言重述规则,归入简短标题下,例如 Respect、Participation、Time 和 Sharing。如果我的清单没有自然的分组,则使用一个标题并说明。 - 对每条规则,用一句通俗的话说明它在实践中是什么样子,仅依据我的材料。如果我的材料无法支撑一个实际示例,写“needs an example”,不要自行编造。 - 一个清楚标注的“Questions and exceptions”区域,留出空白供参与者填写,并附一句简短中立的话,说明如何向主办方提出例外。 - 一个清楚标注的“Needs host decision”清单,列出我的规则中参与者无法独自解决的事项,仅依据我提供的背景信息。 - 一份简短的“What this agreement does not cover”说明,列出我留下模糊的地方。 风格规则 句子简短。使用日常用语。称呼参与者为“you”。不要法律术语,不要威胁,不要愧疚感,不要感叹号。保留“我必须保留的条款”中出现的每个日期、义务和限制,即使措辞不那么友好。不要添加我的材料中没有的规则、后果或鼓励。 输出格式 Markdown,包含上述标题,随后是一个“Checks”部分,列出:我原始清单中的每条规则及其在草稿中出现的位置;我要求你保留的每个条款及其确切存留措辞;以及你标注为“needs an example”或省略的每一项。 不确定性的处理 当我的输入有歧义时,插入 [TO CONFIRM: your question] 而不是猜测,并在 Checks 中列出所有此类标记。 边界 不要提供法律、无障碍合规或安全保障建议,也不要将本草稿呈现为已批准或有约束力。我仍负责审阅它、填写每个标记,并决定发送什么。 示例 虚构输入:基本规则——参加者必须准时到达、手机静音、未经同意不得录音、一次一人发言。背景信息——90 分钟线下邻里园艺工作坊,十二名成年人,主办方批准录音和无障碍请求。我必须保留的条款——“未经同意不得录音”。 示例性输出形态:总结句;标题 Respect、Participation、Time、Sharing;在 Sharing 下,用一句通俗的话说明录音需要所有人同意,并加上 [TO CONFIRM: who a participant asks about recording],因为主办方批准这一细节可以放在 Needs host decision 中;一个空白的 Questions and exceptions 区域;以及 Checks 中标注:如果我的清单没有给出理由,准时的“needs an example”放在哪里。 定稿前的自检 逐项通过或失败:(1) 我清单中的每条规则是否都出现在某处,或其在 Checks 中说明缺失?(2) “no recording without consent”是否逐字保留?(3) 每个标记是否都列入 Checks?(4) 草稿是否没有虚构的惩罚、日期或联系人? 现在等待我的粘贴。在我提供全部三项内容之前,不要生成协议。 ## 参考资料与复用 - [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/plain-language-workshop-participant-agreement-prompt-da2e58c2 Author: Prompt Lab