What exactly is wrong?
Copy the smallest claim that requires correction, together with the complete answer, question, timestamp, language and interface. Preserve context: a statement about a former office can be accurate historically and wrong when presented as today's headquarters. Give every claim its own row so one resolved detail cannot hide another unresolved issue.
Ask the accountable internal owner to establish the current fact and its effective date. Leadership changes need approved corporate information; product availability needs a product owner; support hours need the service team. Record a public evidence URL where one exists. When evidence is still being confirmed, mark it under review and avoid publishing a guess.
Can you establish a source relationship?
Inspect available citations and the specific passages on those pages. Mark each relationship: the page repeats the error, gives the correct fact, discusses a different period, or fails to support the claim. Save the page's observed date as well as any publication date. A page may change after the answer was generated.
A source match provides a correction target. It does not prove the complete origin of the generated claim. The citation verifiability study treats support for assertions as a separate evaluation. Keep “source not found” as a valid finding. Unsupported generation, entity confusion and incomplete citation evidence remain possible explanations.
Who can correct which record?
For a controlled page, assign the change to its editor and verify the live result. For a third-party page, prepare a concise request containing the URL, exact disputed wording, proposed correction and public supporting record. Use the publisher's corrections channel and disclose your company relationship. Record the request status without assuming acceptance.
If the AI service provides relevant feedback or reporting, submit the specific answer and evidence under its current instructions. Treat this separately from correcting a website. A submitted report, an accepted source edit and a changed AI answer are three different milestones.
What should the correction say?
An illustrative statement is: “Example Company moved its customer support office to River Street on 1 September 2026. The current contact page lists the address and opening hours.” Replace fictional details with verified facts. Keep historical information dated where readers still need it, and put current contact information where people use it.
Avoid reproducing a sensational false claim in every title and social post. Give people accurate information at the point of need, with enough context to understand the change. Escalate serious misstatements according to impact even if you have seen them only once.
When is the case resolved?
Choose a follow-up schedule appropriate to urgency. Repeat the same question and settings and retain every completed answer. Mark source status and answer status separately. A correct later response is evidence from that check; it cannot certify every future answer. Close the editorial task when approved changes are verified, while retaining an owner for recurring errors.
Steps to follow
Create a claim record
Preserve exact wording and context in one row per factual issue.
Approve the correct fact
Attach a public record, effective date and accountable reviewer.
Complete source and platform actions
Log controlled edits, correction requests and feedback separately.
Verify subsequent answers
Repeat the saved question and record correct, incorrect or unresolved outcomes.
A company fact correction register
A blank CSV worksheet for your own evidence and decisions.
Download worksheet (CSV)Sources
Put the guide to work
A company fact correction register
Explore the public playbooks ↗