Check the claims that affect your decision
To verify an AI answer, break it into specific claims, find independent evidence for each important one, and record what the evidence supports. Asking the same assistant “are you sure?” is a request for another answer, not independent verification.
OpenAI’s guidance warns that generated responses can include incorrect facts and invented references. The practical response is to make the evidence visible before relying on a conclusion.
Create a small claim ledger
Read the answer once for meaning, then a second time for checkable statements. Highlight numbers, dates, quotations, eligibility conditions, product capabilities, and absolute words such as “always.” Separate factual assertions from suggestions.
For a fictional answer about a community room booking, your ledger might look like this:
| Claim | Evidence needed | Current status |
|---|---|---|
| The room holds 40 people | Official room specification | Not checked |
| Booking requires seven days’ notice | Current booking policy | Not checked |
| Morning is a good time for volunteers | Team preference or discussion | Suggestion |
The distinction matters. A suggestion can be worth considering without being “verified” as a fact. A capacity limit needs actual evidence.
Follow a verification sequence
- Identify the intended use. A casual explanation and a published operational policy need different depth of review.
- Extract the claims that would change your action if false.
- Find the original source: official documentation, the underlying dataset, or the original paper.
- Read the relevant passage in context, including definitions and exceptions.
- Check whether the source applies to your date, location, version, and situation.
- Mark each claim supported, contradicted, or unresolved.
- Rewrite the conclusion so unresolved claims are not presented as facts.
Keep links and a short note about the relevant section. A bookmark alone may not remind you why a page was useful.
Copy a ledger you can actually maintain
Paste this tab-separated header into a blank spreadsheet or text file. Keep the exact claim and the decision separate so a later correction remains traceable.
Claim ID Exact claim Primary source URL Section or passage Source date/version Checked on Status Decision
C01 [one checkable claim] [URL or not found] [section] [date or unknown] [date] [supported/contradicted/unresolved] [keep/rewrite/omit]
For the fictional room example, the completed decisions should be:
| ID | Evidence found | Status | Publication decision |
|---|---|---|---|
| C01: room holds 40 people | Fictional official specification says seated capacity 32 | Contradicted | Rewrite to 32; preserve “seated” |
| C02: tomorrow is bookable | No booking lead-time evidence | Unresolved | Omit the promise and ask the venue |
| C03: morning is best | No team preference recorded | Unresolved suggestion | Present as an option, not a fact |
The venue and specification are illustrative; they are not real citations. For your own ledger, the URL must lead to a source you opened. A blank source date remains “unknown,” not today’s date. A source that merely mentions the topic leaves the claim unresolved.
Stop publication when an unresolved claim changes the reader’s action. Less consequential uncertainty can stay visible as an open question. This is a decision rule for your review, not an automated truth score.
Use AI to prepare the review
An assistant can help organize claims without serving as the evidence. Try this on an answer you are allowed to share:
Extract the checkable factual claims from the answer below.
Return a table with:
- exact claim
- what evidence would support it
- why being wrong would matter
Do not verify the claims from memory.
Do not invent sources or URLs.
Separate suggestions from factual statements.
Answer:
[PASTE THE ANSWER]
Check the extraction too. If the assistant omits a condition such as “only for members,” add it manually. An incomplete claim list can hide the most consequential part of the answer.
Open the source, not just the citation
A citation can fail in several ways: the page may not exist, it may discuss the topic without supporting the claim, or it may describe a different product version. Search for the claimed sentence or concept and read the surrounding paragraphs.
For a quotation, compare the exact words and attribution. For a research claim, distinguish what the study observed from what someone inferred. For a calculation, reproduce the arithmetic using known inputs rather than asking for a fresh verbal explanation.
A worked correction
Suppose the generated room-booking answer says, “The hall fits 40 people and can be booked tomorrow.” You find an official page stating a seated capacity of 32 but no booking lead time.
The corrected result is: “The published seated capacity is 32. The earliest booking date is not established by the source; confirm it with the venue.” Do not replace the unknown booking rule with another plausible number.
This example is fictional. Its purpose is to show how a supported correction and an unresolved detail can coexist in the same conclusion.
When sources disagree or are missing
Check whether the pages describe different dates, regions, or definitions. Prefer the source responsible for the relevant fact, while retaining uncertainty if the conflict remains. Several summaries repeating one original claim do not become several independent confirmations.
If you cannot find adequate evidence, omit the claim, label it unresolved, or delay the decision. For consequential professional decisions, bring the evidence to a qualified person instead of filling the gap with confident language.
Finish with an explicit decision
Write one sentence about what you can safely conclude and one about what still needs checking. Use our response checklist for a quick review, or read why AI gives wrong answers to understand the failure patterns behind the process.
Official sources
References checked October 23, 2026. Features and policies can change; follow the source for current details.
Examples are illustrative and use fictional data. Product performance was not benchmarked for this guide.