Snapshot workspace

A retail snapshot gives the team a dated record for one measurement. The Measurement Owner selects the organization and store definition, sets the store date, and records the source identity and consent basis. Those details let the Retail Analyst relate basket facts and observations to the right measurement rather than mixing periods or stores. The owner also has a clear place to see the current lifecycle state and revision.

The Retail Overview screen gives a broader operating picture: KPI health, reviewed results by unit, monthly snapshot counts, status mix, observed basket conversion trend and overdue follow-up exceptions. Use that overview to find a measurement that needs attention, then inspect the underlying snapshot before making a decision.

• Definition. The store definition and organization establish which measurement the snapshot represents.
• Collection. Basket facts and observations retain their source context under the dated snapshot.
• Review. A reviewer decision and state history identify which revision was examined before publication.

Agree how a source record identifies a store and reporting date. The source record ID should stay stable when collection is retried. Decide who owns the snapshot, which consent basis applies, and how the team checks a revised result. For a correction, record the changed revision and retain the earlier decision against its original revision. Keep store definitions effective dated so an older snapshot can still be read using the definition that applied then.

Agree which result needs an independent decision before the owner marks a snapshot published. The reviewer must see the supporting evidence and the exact revision. If a measurement is returned, record the reason and route the work back to the owner. This preserves the context behind a later correction.

Take a store measurement for a particular date. The owner creates the snapshot, links the store definition and records its source identity. The analyst collects consented basket facts and checks the observation window. A reviewer examines evidence and records a decision against the current revision. The owner then reads the result and confirms the published state. If collection is repeated with the same operation key, inspect the original run rather than accepting duplicate facts.

The review should also inspect state history for recorded transitions, actors and revisions. A returned decision keeps its reason beside the revision it covers. A dashboard count alone cannot answer those questions.

• Snapshot lifecycle — Find a measurement by date, owner and status, then open its source and review context.
• My retail snapshots — Keep each owner’s current measurements together.
• Retail Overview — See the status mix and overdue follow-up exceptions across measurements.

Follow collection and review or prepare the first cycle.