Intro to Git — Snapshots, Branches & Sharing
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
AI hallucination training for teams: check a support reply, sales brief, policy summary and citations claim by claim, then build your team's checklist.

WorkshopyOfficial
78 lessons · used by 2 teachers
Sign in to copy it to your workspace. It’s free.
9 steps · 2 quizzes · open any step, or read it here
In this fact-checking workshop you practise spotting AI hallucinations: statements in an AI answer that sound sure but that no source supports. It is AI hallucination training for everyday work, so you check real-looking drafts (a support reply, a sales brief, a policy summary, a report's citations) one claim at a time.
Here is the whole idea in one draft. Watch the checker go through it claim by claim.
Interactive · One AI draft, checked claim by claim — try it in the lesson
In this lesson you'll:
It takes about an hour. No AI account is needed: every AI answer here is a written example.
Takeaway: a draft can be fluent from start to finish and still be wrong in the middle. Checking is done claim by claim.
A language model writes by predicting the next word, again and again. It picks words that are likely after the words so far. Nothing in that step looks the fact up.
When the model has seen a fact many times in its training text, the likely word and the true word are usually the same. When it has never seen the fact (your company's support hours, a client's revenue, last week's meeting), many words are about equally likely, and it still writes one of them, in the same confident sentence.
That is what people call a hallucination: not a glitch, but the normal way of writing, applied to something the model doesn't know.
Try it: pick each prompt and press Generate five times. Watch how many different answers you get, and how sure each one sounds.
Interactive · Generate the same sentence again and again — try it in the lesson
What changed between the two prompts: the bars, not the sentences. Both sentences read as facts. You can't hear the difference; you can only check.
Models trained to answer helpfully tend to answer rather than say "I don't know", and newer tools that search the web or read your files make fewer of these slips. Fewer is not none, so the habits in this lesson apply to every tool.
Takeaway: a model writes what is likely, and it sounds the same whether it knows or not. The facts it is least likely to know are your company's own.
Most of an AI answer is safe to read: greetings, structure, ordinary advice. The risky parts are short and specific: a number (45 days, $15), a name (a person, a product, a policy), a date, a quote, a link, a rule ("you can…", "we never…").
These are the parts a reader acts on, and they are the parts a model fills in when it doesn't know. So the first habit is to find them before you send anything.
Try it: this reply was drafted by an assistant for a support agent (it's invented). Tap each part a customer could act on. There are four.
Interactive · Mark the claims in a support reply — try it in the lesson
Notice what you didn't mark: the friendly opening and closing. Those are the parts people usually polish, and the parts that never need a source.
Takeaway: before you check anything, list what can be checked: names, numbers, dates, quotes, links and rules.
A paragraph is hard to check. A list of single claims is easy: each one is true or not, and each one has a place where you can look.
So the second habit is to split the answer. One claim per line, its kind, and where you would check it. Some lines turn out to be opinion or filler: nothing to check, but nothing to rely on either.
Try it: here is a sales brief an assistant wrote about a prospect (company and people invented). Press Split into claims, then open each card to see where you would check it.
Interactive · Split a sales brief into claims — try it in the lesson
A brief like this is where invented details do the most damage: a salesperson who opens a call with the wrong CEO's name or a quote nobody said loses the room in a sentence.
You don't have to do the split by hand every time. You can ask the assistant to "list every factual claim in this answer, one per line". Then you check the list, not the prose.
Takeaway: split an answer into single claims, note the kind of each, and name where you'd check it. Opinions have nothing to check and nothing to rely on.
Question 1. Why can a language model state something false in a fluent, confident sentence?
Question 2. An assistant drafts: "Thanks for asking. Our Premium plan includes 24/7 phone support and a 99.9% uptime guarantee." Which part most needs checking?
Question 3. An answer is detailed and sounds certain. What does that tell you about whether it's right?
Question 4. A brief says the prospect's CEO "said in a 2023 interview that fuel is our biggest cost". What is the best check?
Once you have a claim, you need a source that is not the AI: the policy itself, the price list, the contract, the database, the person who owns the fact.
Read the claim against the source and give it one of three verdicts:
The third verdict is the one people miss. A missing claim feels like a small extra, but it is exactly what a model adds when it fills a gap.
Try it: an assistant summarised a travel policy for new hires (both invented). Judge each line of the summary; the policy line it is about lights up when you answer.
Interactive · Judge a policy summary against the policy — try it in the lesson
Look at line 3. It had the right number and a wrong detail attached. Partly-true claims are the hardest to catch, because the part you check first is the part that's right. Read the whole source line, not just the number.
Takeaway: every claim gets a verdict against a source that isn't the AI. "Not in the source" means cut it or ask, never keep it.
A citation looks like proof, which is why invented ones are dangerous. A model can produce an author, a title, a year and a journal that fit together perfectly and don't exist.
This happened in a real court case. In Mata v. Avianca (New York, 2023), lawyers filed a brief citing court decisions that ChatGPT had made up. One lawyer had asked ChatGPT whether one of the cases was real; it said yes. In June 2023 the judge fined the lawyers and their firm 5,000 dollars, and wrote that using AI is not wrong in itself, but that the lawyers are responsible for what they file.
The lesson for any report: asking the same assistant "is this real?" is not a check. It writes a likely answer to that question too. Check outside it, three ways:
Try it: a report on remote work cites four sources (all invented for this exercise, including the catalog). For each, ask the AI and search the catalog, then give your verdict.
Interactive · Check the citations in a report — try it in the lesson
The "doesn't say that" kind is the most common in real reports, and the hardest: the source is real, so it passes a quick look. Only opening it catches the gap between what it found and what the sentence claims.
Takeaway: a citation is checked when you have found it outside the AI, opened it, and seen it say what the sentence says. "The AI says it's real" counts for nothing.
You can't stop a model from inventing, but you can ask in a way that makes inventions easier to catch:
None of these makes an answer true. A model can still misread the text, or quote a section that doesn't say what it claims. They make checking faster, because each claim now points at the place to check.
Try it: turn the three switches on one at a time and watch the prompt and the answer change. The policy is the travel policy from step 5.
Interactive · Turn a prompt into one you can check — try it in the lesson
Notice the taxi line. With the policy pasted, the answer got the numbers right but kept the taxi claim. Only the "allow it doesn't say" line turned it into an honest gap.
Takeaway: give the model the source, ask for the reference behind each point, and allow "it doesn't say". Then still open the references.
You can't check every word of every AI answer, and you don't need to. Two questions decide how much checking a piece of work needs:
No to both: read it once. Yes to one: check every fact in it against a source. Yes to both: check every claim, and a second person reads it before it goes out.
Try it: choose the level for each piece of work.
Interactive · How much checking does it need? — try it in the lesson
The rule is yours to change. A regulated team may put everything that touches a customer at the top level; a design team may put most drafts at the bottom. What matters is that the team agrees on it, so nobody has to guess.
Takeaway: two questions (does it leave the team, could a mistake cost) decide how much checking a piece of work gets.
Habits stick when they are written down where the work happens. Build a short checklist from what you practised: pick the checks your team needs, add one of your own, and keep it beside the tools you use.
Try it: tap checks to add them, add one of your own, then press Show as text to copy the list into your team's wiki or chat.
Interactive · Build your team's fact-checking checklist — try it in the lesson
A good team checklist is short (five to eight lines), uses your own words, and names your own sources: "prices come from the price list", "policy answers link to the policy page". Agree on it together, put it where people draft, and look at it again after the first mistake it didn't catch.
Takeaway: the checklist turns this lesson into a habit. Keep it short, in your words, next to the tools.
Question 1. An AI summary says "Receipts are due within 60 days". The policy says 30 days. What is the verdict?
Question 2. A summary says "Taxis to the airport are always covered". The policy doesn't mention taxis. What do you do?
Question 3. In Mata v. Avianca (2023), lawyers filed court decisions that ChatGPT had invented. What happened when one of them asked ChatGPT whether a case was real?
Question 4. Which of these show that a citation checks out? (pick all)
Question 5. Which piece of AI-assisted work needs the most checking?
Question 6. You paste the policy into the prompt and ask for the section behind each point. What is true?
Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.
Version 1Current
· First published
Copies are made from the current version. A copy you already have doesn’t change.
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
WorkshopyOfficial16 steps2 quizzes15 interactiveDiagram
workshopyproduct touronboarding
WorkshopyOfficial10 steps2 quizzes10 interactive
data-literacystatisticsmean and median
WorkshopyOfficial11 steps2 quizzes10 interactive
data-literacycorrelationcausation
WorkshopyOfficial9 steps2 quizzes7 interactive
pythonpandasdataframe
WorkshopyOfficial10 steps2 quizzes9 interactive
excelsumifcountif
Comments
No comments yet. Be the first to say how it went.