Good service is also a physics problem: heat, time and hand-offs. Timing decides whether the fries land crisp and the meat on point in front of the guest. A terminal that orders firing, holding and hand-off – for table, pickup and delivery with their own clocks – holds quality in the rush. What you measure is the flow: ticket age, remake rate, hand-off time.
Great service has a problem people rarely talk about: physics. Heat is lost, time runs on, and every hand-off is a chance for a plate to go cold or a course to be ready too early. Whether the fries land crisp and the meat on point in front of the guest isn't down to the recipe alone — it's down to the timing: when what is fired, how long something may wait, and in what order the pass brings the plates together.
When that timing drifts, it shows: cold fries, dishes made twice, servers pacing the pass like a traffic cop. A terminal with good timing logic prevents exactly that — it respects the physics of service instead of treating orders as isolated tickets.
Fire, hold, hand off
The core of timing logic is three relationships the guest never sees but always tastes: when something is fired, how long it may be held and in what order it's handed off. A course at the table needs different timing than a pickup; a plate that's ready too early waits under the lamp and loses. Good software makes these rules editable without rebuilding the whole system — and it documents the exceptions: replate the allergy dish, pace the VIP table differently, "fire on arrival".
Pickup and delivery tick differently
Pickup and delivery add a second clock to the timing. A bag still sitting at the pickup spot two minutes after "ready" is the same mistake as a plate under a dying heat lamp — only here nobody notices until the guest is disappointed. For these channels the terminal should speak the same language as the time promise the guest saw when ordering: if a pickup is promised for 7:10, the kitchen has to time towards that, not towards "as fast as possible".
The pass as command station
At the pass, all the stations come together — and that's exactly where the right signals are needed: a clear alert when a dish waits too long, and a sign when two stations finish at the same time for the same table. That turns the pass from a bottleneck into a command station that orders the hand-off, instead of leaving it to chance and the loudest shout.
Measure the flow, not the show
Whether the timing is right doesn't show in pretty numbers, but in the flow: how old are the tickets on average, how often does a dish have to be remade, how long does the hand-off between stations take? And the warning signs of a wrong timing model are concrete: a rising number of dishes given away over temperature, servers forcing a re-fire through an extra order, pickup bags reopened at the window.
The 7 most common mistakes
- Firing everything at once, without balancing firing and holding.
- Courses at the table come out jumbled instead of in sequence.
- Pickup and delivery without their own clock — the bag goes cold.
- Timing to "as fast as possible" instead of the promised window.
- No signal at the pass when a dish waits too long.
- Exceptions not documented — allergy, VIP, "fire on arrival".
- Measuring show numbers instead of ticket age, remake rate and hand-off time.
How to get the timing right
Common questions
Isn't timing logic a matter for experienced chefs, not software?+
Why do pickup and delivery need different timing?+
How do I notice my timing model is off?+
Which numbers should I track?+
When everything shares the same time
Timing works best when kitchen, pass and counter don't work against each other but sit on the same line — and when web, table and delivery respond to the same demand the guest has already triggered. Then the timing rules aren't theory, but the quiet order that makes sure every plate reaches the guest the way the kitchen meant it.
