Operating guide · Weekly accountability
Turn weekly numbers into owned action.
Validate the district workbook, generate deterministic exception questions, collect one response at a time, and close the period with weighted reports.
01 / Calendar
Open the authoritative week
An Administrator defines the reporting period, local timezone, delivery time, and open week from KPI Reviews. The open week determines the exact Week N sheet and required week-ending date.
02 / District intake
Validate before processing
District Managers upload a maximum 20 MB .xlsx. Stores match by CJR/store code. The original is private and versioned. Transactions, Ticket Average, and OLO are ignored and never stored.
03 / Exceptions
Ask only when the data requires it
Versioned deterministic rules generate questions for allowed KPI exceptions. District and Market leaders may preview and assign current-week one-time questions within their scope. Credential and safe-code requests are blocked.
04 / GM workflow
One question per screen
Responses autosave and resume. Submission requires current key holders and the exact safe code. The code is encrypted before persistence and never included in the District Manager email.
05 / First Tuesday
Previous-period evidence
General Managers receive store week-by-week results. District Managers receive weighted combined KPIs and store coverage. Reports are immutable, versioned, scoped, and delivered through the retrying outbox.
06 / Controls
Scope is enforced twice
The interface hides unavailable actions, while database policies and RPC checks independently enforce store, district, and market boundaries. Safe-code access is a separate Administrator permission, requires a reason, and is audit logged.
Open KPI Reviews →