When and how to disclose AI assistance
Goal: Disclose AI help in one calm ≤25-word line—neither more nor less than the truth.
Best for: Students, employees, indie publishers, and anyone shipping AI-shaped drafts.
Policies differ. Some classes ban AI; some require a footnote; some workplaces require internal tags. Default ethically: if a reader would reasonably want to know AI helped shape the words or analysis, disclose in proportion.
Disclosure is a trust habit, not a confession booth. Say what the AI did and what you checked—especially when the reader might think a human alone wrote every word.
Disclosure is not shame—it is calibration. Readers can trust you more when they know which parts a model drafted and which parts you verified.
Why beginners skip this
Skipping disclosure feels tidy—readers assume all human hands, and trust collapses later. Write the disclosure line first.
Step 1 — Quick decision
Use this table first; when unsure, disclose on the stricter row.
| Context | Usually |
|---|---|
| Graded work with ban/limits | Follow syllabus; when allowed, disclose method |
| Client deliverables | Ask; many want a note in process docs |
| Public essays / newsletters | Short footnote if AI drafted structure/prose |
| Private brainstorm only you see | Optional |
Draft a one-sentence disclosure for [context].
Facts: AI helped with [outline / wording / translation]; I verified [facts]; final edits by me.
No need to paste my prompts. Keep under 30 words.
Step 2 — Example footnotes
Example
Filled prompt
I used ChatGPT to polish a client proposal (structure only; all numbers mine).
Draft a one-line disclosure suitable for email footer AND a longer note if client asks.
No overclaiming "AI wrote this."
What good output looks like
- Opens as one calm sentence under ~25 words—no confession essay
- Names AI help for outline and that you rewrote every paragraph
- No ChatGPT/Claude brand parade or model-version dump
- Tone stays matter-of-fact—not defensive, cute, or oversharing
- Fits a blog footer without reading like a confession booth
Step 3 — Honesty > clever labels
“Inspired by AI” while the draft is mostly model prose is still misleading—say so plainly, or revise until the label matches reality.
Example
Filled prompt
Live artifact this week for: Know when transparency is required or wise—school, work, publishing—without oversharing pr
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.
What good output looks like
- One sentence; drops cousin name and multi-tool brand spam
- Keeps “not legal advice” as a separate boundary if the wiki needs it
- Still says AI helped with wording and that final edits are yours
- No private prompts, cousin jokes, or model-version dump
- Fits an internal wiki footnote without looking like a confession
Save this card
Card: Disclose in proportion: one calm line for what AI did and what you checked. Keep this beside the tool; read before you start.
Before you start
Put the scrub checklist on your desk. For “Know when transparency is required or wise—school, work, pub,” decide placeholders before the paste window opens Guide: safety-disclose-ai-assistance Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first
How to use this week
This week add a disclosure line to a real external draft: which parts used AI, what a human changed; no send without it.
Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).
Under 25 words
One calm sentence: what AI did + what you checked. No tool-brand dump.
Match the label to reality
“Inspired by AI” while most sentences are model prose is still misleading. Either rewrite until the label fits, or say AI drafted and you edited. Never put keys or PII inside a disclosure footnote.
Example
Filled prompt
AI outlined a proposal; numbers all mine.
Footer one-liner + longer answer if client asks. No "AI wrote this." overclaim.
≤25 words; what AI did + what you checked—no tool brands.
What good output looks like
- No raw PII/secrets in the paste for “Know when transparency is required or wise—school,”
- Placeholders used; scrub checklist visible
- Disclosure matches how much AI actually did
- Pass/fail: desk card updated today
Red flag
Silent AI on high-stakes outbound; disclosure missing where readers expect it—add one calm line.
Pitfalls
| Pitfall | Fix |
|---|---|
| Ignoring syllabus bans | Read policy first |
| Oversharing secrets in disclosure | No keys/PII in footnotes |
| Using disclosure to excuse fabrication | Never; verify anyway |
Example
Filled prompt
Temptation: skip the habit for safety-disclose-ai-assistance to save five minutes.
Job still: Know when transparency is required or
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.
What good output looks like
- Names the shortcut refused (specific to safety-disclose-ai-assistance)
- Still delivers checkable output for “When and how to disclose AI assistance”
- Unknowns labeled; draft-only
- Pass/fail: refuse-line dated (safety-disclose-ai-assistance #4)
Practice now
Policy link: if org policy exists, link it beside disclosure (Asia/Shanghai).
Audience variant: short vs long disclosure for two channels (Asia/Shanghai).
Where pasted: note which channel got the disclosure (Asia/Shanghai).
Channel fit: tailor disclosure length to email vs doc vs chat (Asia/Shanghai).
Paste-ready: disclosure line lives in a snippet tool, not only in memory (Asia/Shanghai).
Disclose drill: write the disclosure line you will actually paste; put it on Save (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight add one AI-assistance disclosure line to a real external draft before send.
Close the loop
Write one line: next time I send an external draft with no disclosure, I refuse.
One sentence takeaway
Disclosure line: which parts used AI, what a human changed; no send without it.
Next
Copyright & voice · Study honesty · Eval outputs · Secrets and pasting
何时以及如何披露 AI 协助
目标: 用一句冷静、不辩解的话(≤25 词)说明 AI 帮过什么:不多不少。
适合: 博客、内网 wiki、客户文档里需要诚实披露的人。
过度披露(工具名轰炸、还拉上表哥)和零披露一样伤信任。大众读者通常只需要:AI 协助过哪一步、人改过什么。
为什么新手跳过
不披露像省事;读者以为全是人手,信任会在事后崩。先写披露行。
步骤 1——快速判断
先用这张表判断要不要披露;场景对不上就按更严的一档写。
| 场景 | 通常 |
|---|---|
| 有禁止/限制的计分作业 | 遵守大纲;允许时披露方法 |
| 客户交付 | 先问;许多希望写在过程文档 |
| 公开文章 / 通讯 | 如果 AI 起草结构/行文,短脚注 |
| 只有你看见的私密头脑风暴 | 可选 |
为 [场景] 起草一句披露。
事实:AI 协助了 [提纲 / 措辞 / 翻译];我核实了 [事实];终稿由我修改。
不必粘贴我的提示词。30 词以内。
步骤 2——脚注例
实例
填好的提示词
为一篇博客起草一句披露(≤25 词):AI 帮我搭过提纲,每一段都是我重写的。读者:大众。语气冷静,不要辩解,不堆工具品牌。
边界:不编造;未知标 [?];发送前停下。
完成检查:一分钟内能判过/不过。
像样的输出大概长这样
- 页脚只留一句:提纲由 AI 协助生成,正文逐段经人工改写与事实核对
- 不堆模型品牌名,也不辩解、不卖惨、不自我表扬
- 大众读者五秒内看懂「谁做了什么」
- 格式可直接贴进博客页脚或内网 wiki 文末
- 语气冷静,像作者自己的工作笔记
步骤 3——诚实大于聪明标签
草稿大半是模型句子,却写「AI 灵感」仍具误导;如果大半句子来自 AI,就直说,或改到标签与现实一致。
实例
填好的提示词
把这段过度披露收成一句:「我用了 ChatGPT-5、Claude、三个插件和我表哥写这份法律备忘,我不是律师。」场景:内网 wiki,非正式法律意见。
边界:不编造;未知标 [?];发送前停下。
完成检查:一分钟内能判过/不过。
像样的输出大概长这样
- 法律向披露收成两行:AI 参与了哪些部分 + 「本文非正式法律意见」
- 删掉长表哥和工具清单轰炸,只留读者真正需要知道的
- 仍然诚实说明有 AI 协助,不装作全篇纯人工
- 适合对外 PDF 或客户可读材料的页脚
- 读起来像克制的作者声明,不像免责声明墙
保存这张卡
记下:今天收回的权限 / 打码习惯 / 披露句其中一项。标上日期。
开始前
为本会话选一件可衡量的安全动作(撤销、打码或披露)。
本周怎么用
本周给一份真对外稿加披露行:哪段用了 AI、人改了什么;缺披露不发出。
少于 25 字能说清更好
一句冷静话:AI 做了什么 + 你核对了什么。不堆工具品牌。
现实核对
把这篇指南放在真实任务旁边。说不出任务,就先挑一件再往下读。
标签要贴合现实
正文大半是模型写的,却标「受 AI 启发」,仍然误导。要么改到标签成立,要么写明 AI 起草、你修订。披露脚注里永不放密钥或 PII。
红旗
不披露,读者以为全是人手,信任会在事后崩;先写披露行。
常见坑
| 坑 | 改法 |
|---|---|
| 工具名轰炸 | 收成一句冷静披露 |
| 零披露 | 至少说明 AI 协助过哪一步 |
| 披露写成免责声明墙 | 大众读者一句够 |
现在就练一次
今晚就练:给一份真对外稿加披露行:哪段用了 AI、人改了什么;缺披露不发出。
闭环
写下一行:下次对外稿缺披露就发出,我拒绝。
一句话带走
披露行:哪段用了 AI、人改了什么;缺披露不发出。
下一步
← Back to home · Learn · Tools · Compare · Start