A store plan moves through distinct phases, each supported by specific screens and interactions. Tracking activates from the point of publication onward.

1. Plan authoring - An HQ operations manager or regional manager creates a store plan that defines the plan type, tasks to be completed, store locations to assign, and a schedule (one-time or recurring). This phase exists entirely in the Store Plan Authoring capability released in March 2026. Execution Tracking does not begin here.
2. Plan publication and case generation - Once the plan is published, the system generates parent HQ cases and child store cases according to the schedule. Each store assignment produces one store case containing the relevant tasks. This is the moment execution tracking becomes relevant and plan authors now need to monitor what has been generated.
3. HQ case review - The parent HQ case aggregates the status of all store cases generated under a plan. HQ operations managers review the HQ case details on the store record page to understand the overall completion state and identify which stores are overdue. From here they can drill into individual store cases or escalate directly.
4. Store-level execution - Regional managers access the store case list for their region, drill into specific store cases, and review the tasks being worked. They can monitor task-level status, reassign work, or flag blockers. This is the primary execution layer — where stores actually complete the plan.
5. Task and case closure - Once store tasks are completed, HQ managers can view the state and close the HQ tasks and Store managers can view and close store tasks. The same playbook pattern is reused across both closure flows, creating a consistent interaction model. The HQ case closed state marks the end of the plan execution cycle for that store assignment.