Reviewed 8 August 2026 · Omnivision Pro product documentation
How to run an evidence-led campaign review
Keep observations, inferences and recommended next checks visibly separate.
Answer first
How should a campaign review turn evidence into action?
Keep observations, inferences and recommended next checks visibly separate.
The review should preserve the source, scope and data state alongside the conclusion so another operator can understand what supports the decision.
Evidence to retain
Keep the decision connected to these signals.
Source and review scope
Record its source, coverage and current state before interpretation.
Observed state
Record its source, coverage and current state before interpretation.
Confidence or evidence limitation
Record its source, coverage and current state before interpretation.
Named next verification
Record its source, coverage and current state before interpretation.
Practical workflow
Record what is observed.
Keep the result reviewable before moving to the next stage.
State what remains unknown.
Keep the result reviewable before moving to the next stage.
Assign a verifiable next step.
Keep the result reviewable before moving to the next stage.
Decision questions
Ask before approving a change.
- What can an operator conclude from the current source?
- What is inference rather than observation?
- Who owns the next check?
Common failure modes
Do not let missing context become certainty.
- Hiding uncertainty in summary language
- Jumping from a symptom to a platform change
- Leaving the next verification unassigned