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
- Follow-up actions
Follow-up actions
Assign and close dated work arising from a retail measurement exception.
OverviewMy follow-up actions×
Retail Analytics · Follow-up actions
New
My follow-up actions
Follow up actions
| Id | Title | Due date | Status | Assigned to | Source | |
|---|---|---|---|---|---|---|
| IDD-276 | Open fua-841 | 17 Oct | Open | RS-66576 | ||
| IDD-612 | In progress fua-238 | 15 Oct | In progress | RS-99394 | ||
| IDD-252 | Completed fua-121 | 17 Oct | Completed | RS-61310 | ||
| IDD-239 | Cancelled fua-856 | 04 Oct | Open | RS-87399 | ||
| IDD-302 | Open fua-461 | 17 Oct | In progress | RS-56064 |
6 of 6 records
IDD-276Follow up actions · FUA-13356
OpenTitleOpen fua-841
Due date17 Oct
SourceRS-66576
What you can do
Keep an exception with an owner
A follow-up action relates to a retail snapshot and names the person responsible. It carries a title, due date, status, completion time and resolution. The Operations Lead can use those fields to track an evidence gap, a source freshness problem or a result that needs reconciliation. The action stays attached to the measurement that raised it, so the person working it can see the relevant review and result context.
The Retail Overview page includes an overdue follow-up exception queue. It helps the lead identify which assignments need attention across snapshots. The action record then holds the detail: who owns the next step, when it is due and what was done. A completed action should have a resolution that another reviewer can understand.
How the work is organized
- Assignment. Each action names an assigned person and source snapshot.
- Timing. The due date and completion time show whether work was handled in the intended cycle.
- Outcome. Open, in-progress, completed and cancelled states distinguish current work from closed work.
What to agree during setup
Agree which exception types should become follow-up actions and who may close them. The team should write action titles that identify the issue rather than repeat a vague alert. A due date should reflect the next business decision. If a source capture needs replacing, the action should lead the Data Steward back to the capture record. If a metric result needs review, the analyst should reference the result and its run in the resolution.
Decide when cancellation is appropriate and who can make that decision. Cancellation should have a reason, especially when a result remains invalid or a reviewer has returned the snapshot. Keep the source snapshot link through closure so the action still explains a historical exception.
Check the handoff on an actual case
A reviewer finds a stale source capture behind a monthly conversion result. The Operations Lead assigns a follow-up action to the Data Steward with a due date. The steward checks the capture window and obtains a fresh source snapshot. The analyst examines the affected observation and result; the reviewer records the necessary decision for the snapshot revision. The assigned person closes the action with a resolution describing the source correction and its result.
At the next operating review, the lead opens the completed action from the snapshot. The due date, assignee and resolution should explain what changed. If the result was left invalid, the action should remain open or explain why it was cancelled. The status alone should not hide an unresolved measurement issue.
What your team sees
- Open follow-up queue — Review current actions by assignee and due date.
- My follow-up actions — Give each assigned person a focused work list.
- Retail Overview — Spot overdue exceptions across the retail measurement cycle.
Follow the work through
What it keeps track of
Data model- Follow up actions
- Assigned corrective and follow-up actions with due dates.
- Retail snapshots
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
- Source snapshots
- Sourced snapshot captures with coverage window and freshness status.
- Metric results
- Calculated metric results persisted once per approved definition and window.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
Who uses it
Permissions- Operations Lead
- , Data Steward, Retail Analyst, Measurement Owner
Set up Retail Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.