Three things change for the pass. This round asks about the routing rewrite underneath them and the ticket that shows it:
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 redesigned ticket match the routing flow (Placed -> In prep -> Ready -> Served) we discussed?
AnsweredThis decides whether the ticket ships as drawn. A tweak here changes the display only; the routing rewrite underneath it ships either way.
Which stations get the redesigned ticket?
AnsweredPick as many as apply.
Background: average ticket time today is 31 seconds across the three prep stations (grill, salad, expo).
Anything else the kitchen team should flag before we ship?
AnsweredRank these three palettes for the status chips (In prep / Rush / Ready for pickup) by legibility under kitchen pass lighting, most legible first.
AnsweredDrag them into order, most important first.
Which ticket-card layout reads faster at a glance?
Answered