These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Retail Analytics
- Features
- Review and evidence
Review and evidence
Record an independent decision against the exact measurement revision.
OverviewReview decision inbox×
Retail Analytics · Review and evidence
New
Review decision inbox
Action waits for the independent reviewer
| Id | Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|---|
| IDD-674 | RS-38091 | 160 | Pending | ER-168 | ||
| IDD-705 | RS-97944 | 640 | Pending | ER-934 | ||
| IDD-324 | RS-32077 | 430 | Pending | ER-140 | ||
| IDD-666 | RS-99979 | 950 | Pending | ER-156 | ||
| IDD-398 | RS-91623 | 950 | Pending | ER-137 |
6 of 6 records
IDD-674Review decisions · RD-79080
PendingSourceRS-38091
Source revision160
Evidence referenceER-168
What you can do
Give a reviewer the same case the analyst saw
A review decision belongs to a retail snapshot and carries its source revision, reviewer, decision, time, reason and evidence reference. That revision matters. A decision on an earlier calculation should not be read as approval of a later corrected snapshot. The Independent Reviewer examines the snapshot, accepted basket facts and source context, then records a decision that the Measurement Owner can act on.
Evidence documents hold an attachment or external reference, document date, verification state and verifying person. They let the reviewer explain what supported the decision without putting every source detail into a status field. State history keeps the separate record of lifecycle moves, actor and reason. Together, those records show both what was decided and what happened after the decision.
How the work is organized
- Evidence. Supporting documents remain linked to the measured snapshot and verifying person.
- Decision. Pending, approved, returned and rejected outcomes describe the reviewer’s recorded choice.
- History. State transitions retain actor, revision, operation key and reason.
What to agree during setup
Agree which evidence is required for a normal measurement and for a correction. Define how the reviewer checks the consent basis and source coverage. The reviewer should be separate from the person preparing the measurement. If a decision is returned, its reason should tell the owner what needs correction. If rejected, the record should still be available for later audit.
The review also needs a precise moment of handoff. The owner should present a specific snapshot revision, and any subsequent change should require a fresh decision. This keeps an earlier approval from silently covering new facts or a new metric value.
Check the handoff on an actual case
An analyst finishes collecting facts for a dated store snapshot. The reviewer opens the pending decision, checks the source window, reads the evidence documents and confirms the snapshot revision. One document has not been verified, so the reviewer returns the case with a reason. The owner resolves the evidence issue and records the current revision for a new decision. The reviewer approves that revision and records the evidence reference and decision time.
After publication, compare the decision with state history. The history should identify the actor who changed the lifecycle state and the revision used. If a later correction is made, the prior decision stays understandable as a decision on its original revision.
What your team sees
- Review decision inbox — Find pending decisions and inspect revision and evidence reference.
- Evidence to verify — See supporting documents awaiting verification.
- Snapshot lifecycle — Check the reviewed measurement’s current state.
Follow the work through
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Evidence documents
- Supporting source evidence documents and verification state.
- Retail snapshots
- Measured web properties with lifecycle status and observed outcome fields.
- Basket facts
- Consented observation-level session and conversion event facts.
- State history
- Immutable lifecycle transition history for each source.
- People
- Analysts, owners and reviewers belonging to an organization.
Who uses it
Permissions- Independent Reviewer
- , Measurement Owner, Retail Analyst
Set up Retail Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.