What you will achieve
Complete a source-check record for one meaningful product statement in an AI answer. The record will preserve the answer context, inspect visible citations, compare the statement with current references and video evidence, and assign a proportionate action.
This is an investigation method, not a way to reconstruct a provider's hidden retrieval process. Use current AdCyte observations where available and an ordinary working document for the review.
Before you start
Choose a statement that affects product understanding or a buying decision. Gather the visible answer, source links, current product reference and relevant campaign assets. Identify an authorised reviewer for the disputed fact.
The example below concerns whether a cleaner's crevice tool is included in a bundle. It is an illustrative review scenario, not a recorded provider result.
1. Capture the exact statement and context
Record the user's question, provider, date, relevant settings and whether sources were supplied during the session. Preserve the exact wording of the statement you intend to check.
Keep a supplied-video analysis separate from an independent search observation. If you gave the system a file, record that fact. Otherwise a later reviewer may assume it found the campaign unaided.
Check: another person can understand the conditions of the observation without repeating it.
2. Break the answer into claims
Separate identity, feature, inclusion and recommendation statements. “This cleaner uses a crevice tool” and “the tool is included in the standard bundle” require different support.
Choose one claim for the first review. If several are materially important, give them separate rows rather than assigning one verdict to a whole paragraph.
Check: the claim is precise enough that evidence could support, contradict or leave it unresolved.
3. Inspect the visible sources
Open each relevant citation and find the passage that might support the claim. Record the page title, URL, access date, product identity and applicable context. Note any access limitation.
Do not treat a linked domain as sufficient evidence. Check whether the cited page describes the same model and bundle, and whether its wording supports the full sentence rather than just a nearby idea.
Check: the record distinguishes a displayed citation from a source that actually supports the claim.
4. Compare with current product references
Use the maintained approved reference for the exact configuration. Record its version or date where available. If the answer concerns a retailer-specific bundle, obtain the relevant bundle information rather than substituting a generic brand page.
Where references disagree, assign the discrepancy to the responsible product owner. Do not choose the source that happens to support the response you would prefer to publish.
Check: the comparison concerns the same item, conditions and time period.
5. Inspect the campaign evidence
Review the relevant advert in AdCyte and open the supporting moments. In the example, the film shows the crevice tool attached to the cleaner. That supports a description of the demonstration but does not establish bundle inclusion.
Record the observation separately from the approved product fact. This prevents the visual evidence from being asked to answer a question it cannot settle.
Check: the review states what the footage adds and what it leaves unresolved.
6. Complete the finding record
| Field | Illustrative completed entry |
|---|---|
| Statement under review | The crevice tool is included with the cleaner |
| Identity issue | Answer names the range without a specific bundle |
| Displayed source | Retailer listing for a particular bundle; actual URL required in a live review |
| Video evidence | Tool demonstrated; inclusion not stated |
| Approved reference | Inclusion must be checked for the exact bundle |
| Finding | Statement is too broad for the evidence currently available |
| Recommended action | Clarify bundle identity and check maintained inclusion information |
| Owner | Named product reviewer required |
| Public status | No correction published by this record |
In a live review, replace illustrative fields with actual observations. If the evidence supports a narrower claim, write it explicitly. If it remains insufficient, retain an unresolved finding.
Check: the conclusion follows from the recorded sources rather than an assumption about how the AI system works.
7. Prepare the appropriate action
The action may be to improve an owned explanation, clarify product identity, request an external correction through the proper process, or simply retain the observation. Assign the work and its dependencies.
Example clarification for review: “Check the current listing for your chosen bundle to confirm included accessories. The campaign demonstrates the crevice tool in use; that demonstration does not establish the contents of every package.”
This wording is suitable only where the underlying references and destination support it. Do not publish the example unchanged as a claim about an actual product.
Check: the proposed action addresses the customer uncertainty and has an authorised owner.
8. Record implementation and a later observation
After an approved change is implemented, inspect the actual destination and record its date. If the team repeats the AI question, preserve the new answer separately with comparable conditions where possible.
A changed answer does not prove that the update caused it. Record the visible result and any differences in provider settings, question wording or source availability.
Troubleshooting
| Problem | Response |
|---|---|
| Citation cannot be opened | Record the access limitation; do not invent its contents |
| Source concerns a different model | Classify the identity mismatch and find the relevant reference |
| Only part of a sentence is supported | Split the claims and assess them separately |
| Video shows a feature but no specification | Use it for the demonstration only |
| Two current references disagree | Escalate the fact question to the responsible owner |
| The next answer differs | Retain both observations and their contexts |
Completion checklist
- Exact statement and answer context captured.
- Claims separated where necessary.
- Visible sources inspected or access limits recorded.
- Product identity and current references checked.
- Video observation distinguished from broader facts.
- Finding and action supported by the record.
- Owner, implementation status and follow-up conditions recorded.
Investigate one useful question
Explore AI Visibility to inspect supported campaign observations. If you need to coordinate evidence and review across teams, book a workflow demo.
FAQs
Does this reveal the provider's internal sources?
No. It reviews the visible answer and inspectable evidence. Do not claim complete knowledge of hidden retrieval or training influences.
Can a finding remain unresolved?
Yes. Record the missing evidence and responsible owner. An honest unresolved result is more useful than an unsupported correction.
Should we repeat the question until it is correct?
Use a defined observation method and retain results. Repeating until a preferred answer appears does not establish reliable performance.

