Scenarios for tracking store plans

  • Release version: Australia
  • Updated April 15, 2026
  • 1 minute to read
  • Tracking can support several operational goals.

    HQ Manager:
    • Product recall oversight - When a product recall plan is published, the HQ manager needs to confirm that all assigned stores have acknowledged, actioned, and closed their recall tasks within the compliance window. This capability helps the manager can escalate directly rather than waiting for ad-hoc status emails from regional teams.
    • Promotional campaign rollout - A seasonal promotional campaign requires consistent merchandising setup across 200 stores by a fixed launch date. HQ uses the plan-level view to track store-by-store progress, filter by completion status, and identify stores at risk of missing the launch window before the campaign goes live.
    Regional Manager:
    • Store-level execution review - The regional manager is responsible for a cluster of stores within a region. The manager accesses the store case list to review which stores have open tasks, drills into an individual store case to understand what is blocking progress and reassign tasks as needed from within the case record.
    • Safety audit compliance - Safety audits require documented task completion at every store location. The regional manager uses tracking to verify that each store in the region has completed the required audit tasks before the compliance deadline and can confirm closure through the HQ case.

    HQ Manager and Regional Manager: Recurring operational plans - For plans scheduled on a recurring basis such as weekly stock counts, monthly safety checks. Both HQ and regional managers use the Track Plan view to monitor the current cycle's execution state and compare completion rates across cycles over time.