Store Task Tracking Agent
Tracks head-office tasks sent to stores and chases the overdue ones.
- Industry
- Retail
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Store Operations Manager
- Code
- MGT-03
It checks the tasks head office sends to stores (price and markdown changes, planogram resets, recall pulls, promotion set-ups, stock counts) against their due dates and each store's completion, and chases the store manager with a short, specific reminder. Recall and pricing tasks that stay overdue go straight to the area manager, and each task's status and follow-up date is recorded in the store task tool.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the store task management tool: the open head-office tasks, their due dates and each store's completion and comments..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Store Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the store task management tool: it updates each task's status and follow-up date and sends the reminders and escalations. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The store task standards: task types and their deadlines, which tasks are legal or safety critical (recalls, price changes, age-restricted product moves), the area manager structure and the store opening hours.
Reads from
the store task management tool: the open head-office tasks, their due dates and each store's completion and comments.
Acts in
the store task management tool: it updates each task's status and follow-up date and sends the reminders and escalations.
Hands back
An object with overdue (a list, each with task_id, type, store_number, days_overdue and action remind, escalate or unblock), due_soon (a list of task_id), reminders (a list, each with store_number, to and text) and escalations (a list, each with task_id, to and reason).
Asks a person when
A recall pull or product safety task is past 4 hours, a price change is live at the till but not on the shelf, or an escalation would name a store manager to their area manager.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Due soon within (days) | 1 | Store tasks due within this many days get a heads-up to the store manager. |
| Recall pull deadline (hours) | 4 | A recall pull not confirmed within this many hours of issue is escalated to the area manager at once. |
| Escalate other tasks after (days overdue) | 2 | A non-critical task this many days overdue goes to the area manager. |
| Most reminders per task | 2 | After this many reminders the task is escalated instead of chased again. |
| Send reminders only between | 07:00-10:00 | Reminders reach stores before or at the start of trading, not mid-rush. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A recall pull or a product safety task not confirmed within 4 hours goes to the area manager and the Store Operations Manager at once, never into the reminder queue.
- A price change or markdown not done by its effective date is a pricing-law risk: escalate it the same day, because the shelf price must match the till.
- Remind a store manager when a task is due within 1 days or overdue, at most 2 times, then escalate.
- Escalate any other task 2 days overdue to the area manager.
- Send reminders only between 07:00-10:00 in the store's local time.
- A blocked task (missing stock, labels or fixtures) is routed to the team that can unblock it, not chased at the store.
See the Store Task Tracking Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.