An illustrated fox compares an AI answer with reference documents using a magnifying glass.

AI & Tools · Guides

How to Fact-Check an AI Answer in 5 Steps

A practical guide by Curio Tangent

An AI answer can give you a useful starting point and still contain a wrong number, an outdated detail, or a citation that does not support its conclusion. Before you copy a claim into an email, report, or decision, follow the evidence back to something you can inspect.

This guide gives you five checks, a worked example you can reproduce, and a worksheet to keep beside your next AI-assisted task.

The five checks at a glance

  1. Pick the exact claim you need to verify.
  2. Open the source and find the supporting passage.
  3. Check the date, scope, and units.
  4. Look for independent support or reproduce the calculation.
  5. Record what is supported, contradicted, or still unresolved.

NIST’s Generative AI Profile describes how generative AI can produce confidently presented false information, including misleading reasoning and citations. Check the evidence behind an answer even when the explanation reads smoothly.

1. Pick one checkable claim

Start with the sentence that matters to your task. Underline the name, date, number, quotation, or instruction you plan to use. Split a sentence if it contains more than one factual assertion.

“This app is the best choice for small teams” combines a judgment with assumptions about price, features, and your team’s needs. Turn it into smaller questions: What does the plan cost? How many people can use it? Which feature do we actually need?

Save the original wording before you investigate. That prevents a claim from quietly changing as you search.

Try this: Write “I need to verify whether…” and finish the sentence with a specific fact. If you cannot tell what evidence would settle it, make the claim narrower.

2. Open the source and find the passage

Follow the citation to the actual page. Look for the paragraph, table, document section, or dataset that supports the claim. A working link and a relevant headline do not tell you whether the page supports that particular sentence.

Use the source closest to the fact: a product’s documentation for a feature, a published study for its reported findings, or an agency’s data page for a measurement. Check who produced it and what they are in a position to know. A company’s own page may establish its current price; it cannot, by itself, establish that its product is better than every competitor.

For an unfamiliar publisher, investigate it in another tab. The Digital Inquiry Group describes this approach as lateral reading: looking beyond the original page to learn who is behind the information.

Try this: Keep a short evidence note: page title, publisher, link, and the section you checked. If you cannot find the cited item, search its title and author separately. Mark it unresolved if the source remains unavailable.

3. Check the date, scope, and units

A source can be genuine while answering a different question. Compare its wording with the claim you saved.

  • Date: Is this the current price, rule, release, or dataset? Check the effective date as well as the page’s update date.
  • Scope: Does the statement apply to your country, product plan, version, population, or use case?
  • Units: Are you comparing kilometers with kilometers, monthly prices with monthly prices, and one-way travel with one-way travel?
  • Qualification: Did the answer drop words such as “average,” “estimated,” “up to,” or “in this study”?

Treat a missing qualification as something to fix. If a source reports an average, preserve that word when you use the number.

Try this: Finish the sentence “This is supported for ___, as of ___, under ___.” A blank may show where you need more evidence.

4. Look for independent support

For an important claim, look for another suitable source with its own evidence. Follow its references: two articles that repeat the same press release give you one underlying account. For a disputed claim, look for relevant evidence that could challenge it, too.

Another AI answer can suggest a place to look, but agreement between two tools does not establish a fact. Open their sources and compare the evidence behind the answers.

When a conclusion depends on arithmetic, reproduce the calculation with documented inputs. Check the units before entering numbers. The example below shows how this can expose an error even when some of the surrounding facts are correct.

Try this: Ask what would change your conclusion. Then look specifically for that evidence, rather than collecting more pages that repeat the same wording.

Worked example: how long does light take to reach Earth from the Moon?

Suppose an AI answer says:

The Moon is about 384,400 kilometers from Earth, and light travels at about 300,000 kilometers per second. A light signal from the Moon takes about eight minutes to reach Earth.

This is a deliberately constructed example for this guide, not a transcript of a tested chatbot response. It contains two useful approximate inputs and a conclusion we need to check.

Check the distance. NASA’s Moon Facts, “Size and Distance” section gives an average Earth–Moon distance of 384,400 kilometers. Keep the word “average.”

Check the speed and units. NIST’s Meet the Constants gives the speed of light in a vacuum as 299,792,458 meters per second. Dividing by 1,000 converts that to 299,792.458 kilometers per second.

Reproduce the calculation. For a rough one-way estimate, divide the average distance by the speed:

Time = distance / speed
384,400 km / 299,792.458 km per second
= approximately 1.282 seconds

The evidence supports about 1.3 seconds one way using the average separation. Eight minutes is contradicted by this calculation. This is an estimate from documented inputs, not a measurement of a particular signal or the exact travel time on a particular date.

Notice what the check accomplished: it preserved the useful inputs, corrected the conclusion, and stated the limits of the result. You can use the same habit for a subscription total, a percentage change, or an estimated journey time.

5. Record the result and keep the uncertainty

Choose a status for each claim you checked:

  • Supported: The inspected evidence supports this wording within the stated scope.
  • Contradicted: Relevant evidence conflicts with the claim; correct it before using it.
  • Unresolved: You could not obtain enough suitable evidence to decide.

These are working labels for this guide, not a score for an entire answer. Checking one sentence leaves the rest unchecked. Correcting one error also does not verify the revised answer automatically.

Save the source link, the passage or section you inspected, the date you checked it, and any limits. That makes the result easier for you or a colleague to revisit.

Try this: Rewrite the original sentence so it says exactly what the evidence supports. Leave out an unresolved detail if your task does not require it; investigate further if your decision depends on it.

A prompt to organize your next check

Use this to prepare a claim list. The output is a research aid that still needs source inspection.

Review the answer below for factual claims.

List the claims I would need to verify before using it.
Separate facts, assumptions, and recommendations.
For each factual claim, suggest the kind of original
source that could support or contradict it.

Only provide a source URL if you actually accessed it.
Otherwise say "source not accessed" and suggest a search.
Flag missing dates, scope, units, and qualifications.
Do not label a claim verified without inspected evidence.

Answer to review:
[Paste the answer here.]

Keep this verification checklist

  • I saved the exact claim I intend to use.
  • I opened the source and found the relevant passage or data.
  • I checked the publisher, date, scope, units, and qualifications.
  • I sought suitable independent support or reproduced the calculation where needed.
  • I recorded a status and kept unresolved points visible.

Copy the verification worksheet for your next task. Explore more practical topics in AI & Tools and Guides.

Sources and how this guide was prepared

Research checked October 24, 2026. This guide was prepared with AI assistance; the source checks and worked calculation are documented. The fox illustration was generated with AI and is conceptual, rather than evidence of a real test. The five-step sequence, example, and worksheet are Curio Tangent’s practical presentation of the checking process.

Similar Posts