The kitchen display one page back is the mockup. Three things change for the pass, and the routing rewrite underneath them is what this round is asking about:
The payload each station receives on a status transition:
{
"ticketId": 482,
"status": "ready_for_pickup",
"notifiedStations": ["grill", "expo"]
}| Station | Avg. ticket time (today) | Avg. ticket time (proposed) |
|---|---|---|
| Grill | 46s | 33s |
| Salad | 28s | 24s |
| Expo | 19s | 15s |
flowchart LR Placed[Order placed] --> Prepping[In prep] --> Ready[Ready for pickup] --> Served[Served]
function priorityScore(ticket) {
const waitMs = Date.now() - ticket.placedAt;
const rushBonus = ticket.rush ? 500 : 0;
return waitMs + rushBonus;
}
function priorityScore(ticket) {
const waitMs = Date.now() - ticket.placedAt;
const rushBonus = ticket.rush ? 500 : 0;
- return waitMs + rushBonus;
+ const recallBonus = ticket.recalled ? 1500 : 0;
+ return waitMs + rushBonus + recallBonus;
}
Does the kitchen display in round 1 match the routing flow (Placed -> In prep -> Ready -> Served) we discussed?
Background: average ticket time today is 31 seconds across the three prep stations (grill, salad, expo).
Which stations need their ticket displays updated to match the round 1 mockup?
Anything else the kitchen team should flag before we ship?
Rank these three palettes for the status chips (In prep / Rush / Ready for pickup) by legibility under kitchen pass lighting, most legible first. The display one page back uses the first of them.
Which ticket-card layout reads faster at a glance?