Today demand analysis

Stage 2 · Analysis

The operator jobs behind Today

Organise current work by time and urgency while preserving the authority of every child capability.

  1. 1

    Prepare for the next service

    See due Mise, expected Receiving, stock exceptions and required Food Safety checks in one time-bound view.

    Today may order and link these records, but it does not copy or complete them.

    Owners: Mise · Receiving · Inventory · Food Safety

  2. 2

    Run the current service

    See active Orders, Station workload, unavailable items and operational exceptions that need attention now.

    Every status and action remains authoritative in its child capability.

    Owners: Orders & Service · Stations · Menus · Inventory

  3. 3

    Close and hand over

    See incomplete work, Waste records, Food Safety exceptions and the bounded Sales result for the completed period.

    Today can expose gaps and route follow-up; it cannot infer completion, causes, cost or compliance.

    Owners: Mise · Waste · Food Safety · Sales · Team

Required record questions

  • Which selected Kitchen, local date, service and timezone define today?
  • Which child capability owns each displayed record and action?
  • Which items are due, late, blocked, exceptional or awaiting approval?
  • Which status is current source evidence and which is an AI deduction?
  • Can an operator open the owning capability directly from every item?
  • Which child records are unavailable or incomplete rather than safely empty?
  • Which actions require approval, and where will that approval be recorded?
Analysis conclusion
Today is the Kitchen Workspace daily coordination surface. It becomes useful incrementally as child capabilities produce time-bound evidence; it never becomes a second operational authority.
Review coordination boundary