1. Retail Analytics
  2. Process
  3. Exception to follow-up
Process · Exception to follow-up

Exception to follow-up

Give a measurement exception an assignee, due date and recorded resolution.

Step by step

  1. Find exception Operations Lead

    The Operations Lead inspects an overdue follow-up, invalid result, stale source or run that needs reconciliation. The source snapshot identifies the affected measurement.

    • Identify affected measurement
    • Updates Metric results, Operation runs, Retail snapshots
  2. Assign work Operations Lead

    The lead creates a follow-up action with an assigned person and due date. The title identifies the source issue and the next decision.

    • Set owner and due date
    • Updates Follow up actions, People
  3. Resolve source issue Data Steward

    The Data Steward or Retail Analyst checks the capture, mapping, observation, result and run that caused the exception. The assignee records what changed.

    • Explain correction and run context
    • Updates Source snapshots, Source mappings, Operation steps
  4. Review correction Operations Lead

    The Independent Reviewer decides the affected snapshot revision when its evidence or result changed. The action can then be closed with a resolution and completion date.

    • Decide revision and close action
    • Updates Review decisions, Follow up actions
    ApprovalA person approves before the work moves on.
Operations Lead
, Data Steward, Retail Analyst, Independent Reviewer, Measurement Owner.

Set up Retail Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started