Tie each deliverable to a check
Agree the fields, owner and due date for each artifact before work starts. In a visibility review, preserve the original answer and the URL actually cited.
| Deliverable | Record to inspect | Acceptance check |
|---|---|---|
| Buyer-question panel | Question ID, exact text, intent, product, market, language, sample version | A reviewer can explain why each question is in scope and rerun the same panel. |
| Baseline observations | Platform and mode, observed time, locale, run status, answer, sources, valid run count | A reviewer can open the sources, compare the answer with approved facts and reproduce the reported denominator. |
| Issue and change log | URL, evidence, proposed action, owner, approval, release date and published version | The release owner verifies the published change and records any discrepancy or deferred work. |
| Retest and outcome report | Matched question set, conditions, actual coverage, metrics and any changes in scope | The report distinguishes visibility, site referrals and qualified inquiries and records missing data. |
Keep the visibility and business records connected
For a mention or owned-site citation rate, show the numerator and number of valid observations for the stated platform, prompt panel and period. Report unavailable or failed runs separately. When the panel or observation conditions change, identify which periods are still comparable.
For referrals and qualified inquiries, document the analytics or CRM source, the comparison dates and the qualification rule. If attribution or a baseline is unavailable, label that gap in the result.
Agree handover ownership
Identify who will keep the raw answers, approved content and working records. Ask for exports in the format your team will use, and specify the next review date and the open items the next owner needs to check.