Verify an AI summary in 5 minutes (5 gates)
Updated: 2 November 2026
Goal: Catch fluent-but-wrong summary errors before they leave your desk—using a phone timer and five short gates against the original.
Page type: Hands-on checklist (about 5 minutes with a timer).
Key rule: The original document decides. The summary is on trial. A confident tone is not evidence. Mark anything you did not check as Unverified—do not “assume it is fine.”
If you are on the first 7-day path, this Guide turns Day 3 (compare and fix) and Day 4 (catch a wrong detail) into a repeatable habit. New here? Start with Lesson 1: your first useful AI email, then come back.
Start the timer
Open the original and the AI summary side by side. Set a 5-minute timer. You are not rewriting the whole document—you are only hunting for mismatches.
- Minutes 0–1: Gates 1–2 (scope + hard facts)
- Minutes 2–3: Gates 3–4 (names + additions)
- Minute 4: Gate 5 (certainty) + mark Unverified
- Minute 5: Fix with one follow-up prompt, or refuse to share
If the original is long, pick the section the summary claims to cover. Do not “skim the vibe.”
The five gates
| # | Gate | Ask against the original | Fail looks like |
|---|---|---|---|
| 1 | Scope | Same event / document / audience? | Wrong day of week, wrong meeting, mixed two notices |
| 2 | Hard facts | Dates, times, places, amounts, IDs match one by one? | Room D instead of Room B; noon became “Friday” |
| 3 | Names & labels | People, rooms, products, URLs spelled as in the source? | Bay 3 vs Bay 2; renamed a team or tool |
| 4 | Additions | Anything in the summary that is not in the original? | Invented reason, extra tip, fake promise, new deadline |
| 5 | Certainty | Where the original was optional / a question / unknown, is it still that way? | “Thursday is confirmed” when it was only a suggestion |
Pass all five, or do not paste the summary into Slack, email, class notes, or a shared doc. Related habit for whole answers (not just summaries): spot a bad AI answer in under a minute. For fluent-wrong tone: when AI sounds sure but wrong.
Mini lesson (Given → Prompt → Example → Check)
Practice with fictional material only. Remove names, contact details and anything private before you try this on real work. The example reply is illustrative—your AI may word it differently as long as the facts stay the same.
Given input
Original notice (fictional):
Harbor Co-op weekend shift
Date: Saturday, 8 November
Hours: 9:00–13:00
Meet: Loading bay 2
Bring: your own gloves (required)
Confirm by: Thursday, 6 November, noon
Bad AI summary (fictional):
"Harbor Co-op weekend shift is Sunday 8 November from 9–1 at Loading bay 3.
Bring gloves if you have them. Confirm by Friday."Prompt (copy this)
Compare the summary with the original using five gates: Scope · Hard facts · Names & labels · Additions · Certainty.
For each gate: Pass / Fail · one short note · quote the mismatch if Fail.
Then write a corrected one-paragraph summary using only the original. If something is missing, write Unknown—do not invent.
Mark every claim you could not check as Unverified.
Original:
Harbor Co-op weekend shift. Date: Saturday, 8 November. Hours: 9:00–13:00. Meet: Loading bay 2. Bring: your own gloves (required). Confirm by: Thursday, 6 November, noon.
Summary:
"Harbor Co-op weekend shift is Sunday 8 November from 9–1 at Loading bay 3. Bring gloves if you have them. Confirm by Friday."A good answer (open after you try)
Gate 1 Scope — Fail: summary says Sunday; original is Saturday.
Gate 2 Hard facts — Fail: confirm-by became Friday; original is Thursday noon.
Gate 3 Names & labels — Fail: Loading bay 3 vs Loading bay 2.
Gate 4 Additions — Fail: “if you have them” softens required gloves; Friday is not in the notice.
Gate 5 Certainty — Fail: required gear treated as optional.
Corrected summary:
Harbor Co-op weekend shift is Saturday, 8 November, 9:00–13:00, at Loading bay 2. Bring your own gloves (required). Confirm by Thursday, 6 November, noon.Your wording can differ. It fails if Sunday, bay 3, Friday, or optional gloves remain.
A bad summary that “sounds fine”—and the fix
Fluent wrong answers often pass a skim. This one keeps the date number (8 November) but swaps the weekday, moves the bay, softens a requirement, and invents a Friday deadline. Send:
Rewrite using only the original. Keep Saturday (not Sunday), Loading bay 2, gloves required, and Thursday noon. Remove Friday and any optional wording for gloves.Check
- You found at least the Sunday / bay 3 / Friday / optional-gloves mismatches yourself (AI help is optional; the original decides).
- The corrected summary contains only facts from the notice.
- Nothing optional was upgraded to a promise, and nothing required was softened.
When the timer ends
- All gates Pass → you may use the summary; keep the original link or file next to it.
- Any Fail → one follow-up prompt (like the fix above), then re-run only the failed gates.
- Out of time → mark Unverified and do not share yet. Five more minutes tomorrow beats a wrong Room / Bay in a team channel.
Save this card
Timer 5 · Scope · Hard facts · Names · Additions · Certainty · Unverified if unchecked · original decides.
Track the habit on the free pack: templates checklist (no download). Path days that practise the same muscle: Day 3 · Day 4.
Practise on Day 4 of the path → ← All guides
More
Lesson 1 — first useful AI email · Spot a bad AI answer · Sounds sure but wrong · Free templates
5 分钟核实 AI 摘要（五道关）
更新：2026 年 11 月 2 日
目标： 在摘要离开你的桌面之前，用手机计时器和五道短关卡，对照原文抓住「读起来顺、其实错了」的错误。
页面类型： 实操检查表（配合计时器约 5 分钟）。
关键规则： 以原文为准，摘要接受审查。语气笃定不是证据。没查过的标成未核实——不要默认「应该没问题」。
若你在走 前 7 天路径，本指南把 第 3 天（对照并修正） 和 第 4 天（找出错误细节） 收成可重复的习惯。刚开始？先做 第 1 课：写出第一封有用的 AI 邮件，再回来。
先开计时器
原文和 AI 摘要左右对照。设 5 分钟 计时。你不是在重写全文——只抓不一致之处。
- 第 0–1 分钟： 关卡 1–2（范围 + 硬事实）
- 第 2–3 分钟： 关卡 3–4（名称 + 增添）
- 第 4 分钟： 关卡 5（确定性）并标未核实
- 第 5 分钟： 用一条跟进提示词修正，或拒绝转发
原文很长时，只核摘要声称覆盖的那一段。不要「凭感觉扫一眼」。
五道关
| # | 关卡 | 对照原文问 | 不合格的样子 |
|---|---|---|---|
| 1 | 范围 | 同一事件 / 同一文档 / 同一读者？ | 搞错星期、搞错会议、两份通知混在一起 |
| 2 | 硬事实 | 日期、时间、地点、金额、编号是否逐项一致？ | Room D 写成 Room B；中午变成「周五」 |
| 3 | 名称与标签 | 人名、房间、产品、链接是否与原文一致？ | 装卸区 3 对装卸区 2；改了团队或工具名 |
| 4 | 增添 | 摘要里有没有原文没有的内容？ | 编造理由、额外建议、假承诺、新截止日期 |
| 5 | 确定性 | 原文是可选 / 疑问 / 未知的地方，是否仍保持原状？ | 原本只是建议的「周四」被写成已确认 |
五关都过，才把摘要贴进 Slack、邮件、课堂笔记或共享文档。整段回答（不只是摘要）的相关习惯：一分钟内看出糟糕的 AI 回答。针对「说得笃定却错了」：AI 说得笃定却错了。
小课（给定 → 提示词 → 示例 → 检查）
先用虚构材料练习。用到真实工作前，先去掉姓名、联系方式和任何隐私。示例回复仅供示意——你的 AI 用词可以不同，只要事实一致。
给定材料
原文通知（虚构）：
Harbor 合作社周末班次
日期：11 月 8 日（周六）
时间：9:00–13:00
集合：装卸区 2
自备：手套（必须）
确认截止：11 月 6 日（周四）中午
糟糕的 AI 摘要（虚构）：
「Harbor 合作社周末班次是 11 月 8 日周日 9–1，在装卸区 3。
有手套的话就带上。周五前确认。」提示词（可复制）
用五道关对照原文检查摘要：范围 · 硬事实 · 名称与标签 · 增添 · 确定性。
每一关写：通过 / 不通过 · 一句短说明 · 若不通过请引用不一致处。
然后只用原文写一段修正后的摘要。缺的信息写「未知」——不要编造。
没能核对的主张标为「未核实」。
原文：
Harbor 合作社周末班次。日期：11 月 8 日（周六）。时间：9:00–13:00。集合：装卸区 2。自备：手套（必须）。确认截止：11 月 6 日（周四）中午。
摘要：
「Harbor 合作社周末班次是 11 月 8 日周日 9–1，在装卸区 3。有手套的话就带上。周五前确认。」合格的回答（先自己试再打开）
关卡 1 范围 — 不通过：摘要写周日；原文是周六。
关卡 2 硬事实 — 不通过：确认日变成周五；原文是周四中午。
关卡 3 名称与标签 — 不通过：装卸区 3 对装卸区 2。
关卡 4 增添 — 不通过：「有的话就带」弱化了必须带手套；周五不在通知里。
关卡 5 确定性 — 不通过：必须装备被写成可选。
修正摘要：
Harbor 合作社周末班次为 11 月 8 日（周六）9:00–13:00，在装卸区 2。请自备手套（必须）。请于 11 月 6 日（周四）中午前确认。措辞可以不同。若仍保留周日、装卸区 3、周五或「可选手套」，即不合格。
读起来「挺顺」的坏摘要——以及修正
流畅的错误常能骗过扫读。这份摘要保留了日期数字（8 日），却换了星期、挪了装卸区、弱化了要求，还编造了周五截止。发送：
只用原文重写。保留周六（不是周日）、装卸区 2、手套必须、周四中午。删掉周五，以及任何把手套写成可选的措辞。检查
- 你自己至少找出了「周日 / 装卸区 3 / 周五 / 可选手套」这些不一致（可请 AI 帮忙；以原文为准）。
- 修正后的摘要只含通知中的事实。
- 没有把可选升级成承诺，也没有把必须弱化成可选。
计时结束时
- 五关都通过 → 可以使用摘要；旁边保留原文链接或文件。
- 任一关不通过 → 发一条跟进提示词（如上），然后只重跑未通过的关。
- 时间不够 → 标未核实，先不转发。明天再花五分钟，好过在团队频道里写错房间 / 装卸区。
存这张卡
计时 5 · 范围 · 硬事实 · 名称 · 增添 · 确定性 · 未查过就标未核实 · 以原文为准。
用免费模板包打卡：模板清单（无需下载）。练同一块肌肉的路径日：第 3 天 · 第 4 天。
更多
← Back to home · Learn · Tools · Compare · Account & safety