Know where one brand fragments into different public answers.
Verify Presence separates central facts from local facts, then shows where answers and sources disagree.
How the workflow works
The scope stays bounded from observation through remeasurement.
- Define central and local evidence ownership.
- Run a comparable core prompt set by location.
- Identify wrong-branch facts and stale records.
- Prioritise shared fixes before local exceptions.
What the customer receives
Every output remains attributable to its source and period.
- Location evidence matrix
- Comparable branch scorecards
- Consistency backlog
- Central and local approval queue
Human-review boundary
Configured tools can support collection, comparison and drafting; controlled launch may use disclosed human assistance. Material facts, external publication and insufficiently evidenced changes remain human decisions.
- Confirm evidence before it informs diagnosis.
- Approve an exact version, not a moving draft.
- Revoke access or sharing when the authority ends.
Measurement limit
Results cannot be collapsed into one national rank without losing their location and prompt boundaries.
- Small prompt sets are directional.
- AI answers can vary between runs.
- No ranking, recommendation or revenue guarantee.
What to know before you begin
What is fixed for comparison?
The prompt wording, target scope, measurement date, provider/model context and classification method are recorded. Material scope changes create a new version.
How is routine work delivered?
Configured tools can support scheduled collection, evidence matching, drafting and comparable remeasurement within configured permissions. Controlled launch may use disclosed human assistance, and sensitive changes retain human approval.
Does a better result prove the intervention caused it?
No. A measured difference is recorded with its limitations and does not automatically establish causation.