The board
A board you can read from across the kitchen.
Checklists sit on a hex grid: each routine a tile, its state visible at a glance. It replaced the kanban because a kitchen does not read columns; it reads shapes.
oppiOS / Checklists
Opening, closing, fridge temps, the Friday clean.
Raised on time.
Ticked at the pass.
Active operations & execution templates
The board
Checklists sit on a hex grid: each routine a tile, its state visible at a glance. It replaced the kanban because a kitchen does not read columns; it reads shapes.
Routines
A routine checklist is one that recurs. The scheduler raises it when it is due, so an opening checklist exists at open and a closedown at close without anyone creating them. Miss one and it is visible, not forgotten.
Library and drafts
The library holds reusable checklist templates. Drafts hold the ones awaiting review. And any SOP in the Vault can become a checklist in one step, so the procedure and the routine never drift apart.
The floor
On the Kiosk, checklists are a screen of their own. Staff tick steps on the tablet by the pass; managers see completion on the Command Centre, and verification catches what was ticked but not done.
What it does
Every routine a tile, its state readable at a glance.
Recurring checklists the scheduler raises when due.
Reusable templates to build from.
Checklists awaiting review before they go live.
Build a checklist step by step, or from an SOP.
Ticked on the floor; counted on the board.
The opening routine is on the Kiosk at open. Nobody built it this morning.
Temperature checks recur on their own schedule and show as done or not done on the board.
The SOP becomes a checklist; the checklist becomes a routine.
Build it once. It comes back on its own.
Routines the scheduler raises and the floor ticks.