Stations demand analysis
Stage 2 · Analysis
The operator jobs behind Stations searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Define the Kitchen’s production destinations
Name each Station, its role, order and operational purpose.
A Station is a stable Kitchen-owned destination such as grill, fry, cold, pastry, bar or pass—not a screen, person or current task.
Evidence: restaurant kitchen station setup · kitchen station management
- 2
Connect Dishes and work to Stations
Define which Station prepares each Dish or stage so live routing can be deterministic.
Stations own the mapping configuration; Orders and Mise own each resulting live work projection.
Evidence: KDS item routing · restaurant kitchen station routing
- 3
Bind operational equipment
Associate displays, printers or other endpoints with the production destination they serve.
A device may serve one or more Stations but must not become the Station identity.
Evidence: KDS station setup · prep station KDS
- 4
Define and record readiness
Make required ingredients, tools, safety checks and setup visible before service.
Stations define checklist requirements; completed checks are time-bound operational evidence.
Evidence: restaurant station checklist · kitchen station readiness checklist
- 5
Make responsibility and competency explicit
Describe the competencies required to run a Station and who is assigned for a service.
Station requirements do not grant Team roles or certify a person; Team retains membership and competency evidence.
Evidence: line cook station competencies · chef station responsibilities
Record map
Evidence the capability owns, references, or derives
kitchen.stations.station
Kitchen Station
Owner: Stations
Station owns the stable named production destination and its lifecycle and display order.
- Station identity and name
- status and display order
- audit stamps
kitchen.stations.configuration
Station configuration
Owner: Stations
Routing, readiness requirements and competency requirements are versioned configuration, not live Mise or Team evidence.
- Dish or stage routing
- readiness requirements
- competency requirements
- effective version and approval
Required record questions
What must Stations make knowable?
- What is the Station called and what production role does it represent?
- Which Dishes, preparation stages or work types route there?
- Does work route in parallel or through an ordered Station sequence?
- Which screens, printers or endpoints serve the Station without defining it?
- Which readiness requirements apply before a service?
- Which competencies are required and which Team evidence supports an assignment?
- When is a Station active, unavailable or retired, and what downstream mappings depend on it?