Performance demand analysis
Stage 2 · Analysis
The operator jobs behind Performance searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Understand service timing
Measure complete Order lifecycle durations such as accepted-to-ready or fired-to-completed using explicit transition timestamps.
The start and end event definitions must be named. FireUX Orders do not yet retain the complete transition history required for authoritative ticket-time reporting.
Evidence: kitchen ticket time report · kitchen speed of service report
- 2
Locate evidenced Station bottlenecks
Compare ticket volume and timing by the Station that actually received and completed work.
Stable Station routing plus Station-specific work timestamps are required. A device, assignee or current mapping cannot reconstruct historical routing.
Evidence: kitchen station performance report · KDS station ticket time
- 3
Review prep completion and blockers
Compare planned Mise work with recorded starts, completions, lateness and blocked outcomes.
Task counts and duration are operational measures. They do not prove human productivity, labour efficiency or individual performance.
Evidence: restaurant prep completion report · mise en place completion dashboard
- 4
Review time-bound readiness
Understand whether required Station and Food Safety checks were completed before the relevant service.
Configuration is not completion evidence. Each readiness result needs requirement version, service context, actor and time.
Evidence: kitchen readiness report · kitchen operations dashboard
- 5
Compare like periods and definitions
Compare supported measures across equivalent Kitchen-local services or periods with workload context.
Volume, item mix and missing records remain visible. A change does not by itself establish cause, quality, staffing need or profit impact.
Evidence: restaurant operational performance report · compare kitchen performance periods
Record map
Evidence the capability owns, references, or derives
kitchen.performance.operational-evidence
Operational performance evidence
Owner: Orders, Mise, Stations, Waste, Inventory and Sales
Performance reads bounded events from their owners and never stores a copied operational history.
- Order timestamps and transitions
- Mise completion evidence
- Station routing
- Waste and Inventory observations
- KitchenSales
kitchen.performance.review
Performance review
Owner: Performance
A review is a source-linked comparison with coverage and uncertainty, not a stored causal or personnel judgement.
- scope and period
- measure definitions
- source links and coverage
- observations, uncertainty and exclusions
Required record questions
What must Performance make knowable?
- Which Kitchen, owner-local service or period and measure definition apply?
- Which explicit lifecycle event starts and ends each duration?
- Does every included Order or work item contain both authoritative timestamps?
- Which Station mapping applied when the work occurred?
- Which volume, item count, order type, channel or complexity context accompanies timing?
- Which Mise tasks were planned, started, completed, blocked or late under the same definitions?
- Which readiness requirement version and service context produced each check result?
- Which missing, anomalous or excluded records affect coverage?
- Are percentiles, averages and on-time measures calculated over the same eligible population?
- Which observation is a supported measure rather than a claim about people, quality, cause or profit?