A confident answer still needs a fact check.

Fluent writing can make an answer feel complete before you have checked it. Treat generated text as a proposed result. Your review should focus on the details that could change the meaning or lead someone to act on incorrect information.

Identify the claims

Highlight names, dates, numbers, quotations and statements about what a tool can do. Separate facts from suggestions or interpretation. A general writing idea needs a different check from a claim about a current product feature.

Go to the source

Open the source and find the passage that supports the claim. Prefer an original announcement, official documentation or a primary record where available. A link in an answer is not proof that the linked page says what the answer claims.

Check time and context

Look at when the information was published and whether it applies to the same product version or situation. Preserve conditions and limitations. A result from one example should not become a claim about every case.

Review before sharing

• Can you support each material claim?
• Are names, dates and numbers accurate?
• Have quotations kept their original meaning?
• Is uncertainty visible where the evidence is incomplete?
• Have you removed information that does not need to be shared?

Keep the checked sources with the draft. If you cannot verify a detail, leave it out or explain the uncertainty. The review step belongs in the workflow from the beginning.