Platform - course timing

Fire times, per table.

Course timing in Aplateful is not a ticket clock. Every table has its own tempo - built from pre-orders, party size, current pacing between courses, and how the kitchen is loaded right now.

How a fire time is decided

Table pacing
How long the table has spent between the previous two courses, weighted toward the most recent.
Kitchen load
Concurrent tickets on the same station, held against expected pass times.
Course profile
Prep window and hold tolerance for the specific dish - a soufflé is not a jus.
Sommelier cadence
Time reserved for the pour before the dish arrives at the table.

The result is a fire time that the pass and the floor share, not a ticket printer speculating on when a table might be ready.

Live during service

Table 8 - fish course firing

Live

7:20

Starter

Beetroot tartare, whipped chevre

fired

7:52

Fish

Turbot, beurre blanc, sea beans

firing

8:20

Main

Duck breast, cherry gastrique

scheduled

8:50

Dessert

Chocolate marquise, olive oil

scheduled

A worked example

One table, from seat to petit four.

What the engine did across the evening for Table 12 - a four-cover, six-course tasting.

Seated 7:00 PM

Table 12 - six-course tasting

Live