A hallucination is a confident AI answer that is incorrect, invented, or unsupported by the evidence available to the model. The word can sound dramatic, but the everyday version is usually quiet: a date that was not in the source, a link that looks real but does not work, a made-up quote, or a recommendation that skips over uncertainty.
The problem is not that AI systems are useless. The problem is that fluent output can make weak evidence feel finished. Verification is the habit that slows that down.
Why Hallucinations Happen
Large language models generate likely continuations of text. They are good at completing patterns: summaries, explanations, lists, emails, outlines, and code-shaped answers. When the prompt lacks the facts needed for the task, the model may still produce an answer that matches the expected shape.
That is why hallucinations often feel plausible. The answer has the rhythm of truth, even when the details are not grounded.
Common causes include:
- missing source material
- vague prompts that ask for facts the model was not given
- pressure to produce a complete answer
- outdated or partial context
- requests for exact numbers, links, quotes, or citations without sources
- long conversations where earlier constraints fade
Grounding reduces the risk by giving the model source material. Verification decides whether the draft is ready to trust.
Common Hallucination Patterns
Look for these patterns before using AI output.
Fabricated Citations Or Links
The model may invent an article title, policy name, author, URL, or citation format that looks credible.
Red flag: the citation is specific, but the prompt did not provide a source.
Verification action: open the link, search the title, or remove the citation until it is proven.
Confident Wrong Facts
The model may state a date, number, definition, owner, version, or rule as if it is settled.
Red flag: the detail would matter if wrong, but the answer does not show where it came from.
Verification action: check the source of truth, or label the claim as unverified.
False Quotes
The model may produce a sentence in quotation marks even when no quoted source was provided.
Red flag: the answer quotes a person, document, law, policy, or article without source text.
Verification action: remove the quote or replace it with a paraphrase labeled as a draft.
Invented Tools Or Steps
For technical or process questions, the model may invent a button, menu, command, method, API, or workflow step that sounds realistic.
Red flag: the step is precise, but you have not tested it or checked documentation.
Verification action: test the step in a safe environment or route it to someone who owns the tool.
Smooth Missing Context
The model may summarize missing information as if it was present.
Red flag: the answer fills in owners, due dates, decisions, or causes that were not in the source.
Verification action: change those parts to “not stated,” “needs owner,” or “needs verification.”
Red Flags In The Wording
Some words and shapes deserve extra attention:
- exact percentages without a source
- “as of” claims about recent information
- named laws, policies, standards, or product features
- quotes that were not provided
- “always,” “never,” “guaranteed,” or “proven”
- confident advice in legal, medical, financial, security, HR, or compliance contexts
- instructions for tools you have not used
- links, package names, commands, or file paths that were not in the prompt
None of these automatically means the answer is wrong. They mean the answer needs a check before it becomes trusted work.
The Verification Depth Ladder
Match review effort to the stakes.
No Check
Use no-check only for private, low-risk brainstorming where mistakes do not matter.
Example: asking for ten possible workshop titles.
Label: draft ideas only.
Light Check
Use a light check when the draft is internal, reversible, and not relied on for decisions.
Actions:
- read for fit
- remove obvious unsupported claims
- mark anything uncertain
Example: a first-pass meeting outline for your own planning.
Label: spot-checked draft.
Source Check
Use a source check when someone else may rely on the output.
Actions:
- mark names, dates, numbers, links, quotes, owners, recommendations, and required steps
- compare each important claim to source material
- remove or label anything unsupported
Example: a summary of policy notes for a team.
Label: checked against source, with gaps listed.
Expert Check
Use expert review when the output affects risk, policy, money, security, safety, people, or public communication.
Actions:
- route the draft to a qualified owner
- keep AI output in draft mode
- record what was and was not verified
Example: guidance about a compliance requirement or a public-facing commitment.
Label: requires qualified review before use.
Confidence Labels
Before sharing AI-assisted work, label its state.
Use simple labels:
- Verified: important claims were checked against source material or an accountable owner.
- Partially verified: some claims were checked, but specific gaps remain.
- Unverified: the output may be useful, but important claims were not checked.
- Escalated: the output needs expert or owner review before use.
These labels are not bureaucracy. They prevent the next person from mistaking a fluent draft for a finished answer.
Worked Example: Public Article Summary
Suppose AI summarizes a public article and writes:
The article says 64% of teams adopted AI assistants by March 2026, and the author recommends replacing weekly planning meetings with automated task summaries.
Verification pass:
- “64%” needs source check.
- “March 2026” needs source check.
- “the author recommends” needs source check.
- “replacing weekly planning meetings” may be too strong if the article only suggests a trial.
That revision is less flashy. It is also more honest.
Worked Example: Technical Step
Suppose AI writes:
Use
Spreadsheet.summarizeRows()to generate the summary column automatically.
Verification pass:
- Does that method exist?
- Is it part of the tool or library being used?
- Was it tested in a safe environment?
- Is there official documentation?
Technical hallucinations are especially dangerous because they can look precise. Precision is not proof.
When To Escalate
Stop and escalate when:
- the output affects a person, commitment, policy, system, or public message
- you cannot find the source for an important claim
- the topic requires expertise you do not have
- the answer includes sensitive or regulated information
- a wrong answer would create financial, legal, safety, security, or trust risk
- the draft is being used to decide rather than brainstorm
The best AI users are not the ones who never see hallucinations. They are the ones who know when a polished answer still needs evidence.
Compact Exercise
Take an AI answer you recently received. Mark five claims. For each one, choose a verification depth: no check, light check, source check, or expert check. Then label the whole output as verified, partially verified, unverified, or escalated.
Check Your Understanding
Question: Why can a hallucination be hard to spot?
Answer: It often looks polished and specific, even when the detail is invented, unsupported, or not grounded in the available evidence.
Question: How should verification depth be chosen?
Answer: Match the review effort to the consequence of being wrong. Low-risk drafts may need only a light check, while decisions involving policy, money, security, people, or public communication need source or expert review.
Question: Why label confidence before handoff?
Answer: It tells the next person whether the output is verified, partially verified, unverified, or escalated so they do not mistake a fluent draft for finished work.
Question: When should an AI-assisted draft be escalated?
Answer: Escalate when the output affects risk, policy, money, security, safety, people, public communication, or another high-stakes area, and route it to the qualified owner before use.
Reference Links
These public references are useful starting points for deeper study. They are linked for attribution and further reading; the lesson above is synthesized as original LIW training guidance.
- NIST AI Risk Management Framework - useful for thinking about risk, measurement, and oversight.
- People + AI Guidebook - useful for product and user trust patterns around AI systems.
- Hallucination in artificial intelligence - useful as a neutral definitional pointer.