Using the kitchen display

The kitchen display is a dark, glanceable screen built for the wall above the pass. It shows every party currently in service as a card, sorted into columns by where they are in their meal, and it updates live as the floor moves — no one has to refresh it.

The layout

The screen is laid out in columns, left to right, following your venue's own service flow from Seated onward. The kitchen doesn't bus tables, so the final Departed stage isn't shown — a party drops off the screen once it leaves.

Each column header shows the stage name and a count of how many parties are sitting in it. If your venue has turned certain course steps off, those columns simply don't appear.

Reading a ticket card

Every live party is a card in its current column. Each card shows:

• The table(s) the party is on — joined with a + when a large party spans more than one table (or "No table" if none is assigned).
• Party size as a small badge.
• Elapsed time in minutes since they were seated, so the pass can see who's been waiting longest. Within a column, the oldest party sorts to the top.

Cards are ordered so the party that has been in that stage longest is easiest to find.

Allergies are shown in red

If anyone in the party has a recorded allergy, it appears as a red badge right on the ticket card — pulled from the guest book. Allergies are structured, safety-critical data, so they ride along with the party everywhere the kitchen and floor can see them. Duplicate allergens across a party are shown once. This is a core hospitality-and-safety feature; it is never hidden to save space.

Advancing a ticket

To move a party to their next course, tap the advance button at the bottom of their card. It's labelled with the next stage in your venue's flow (for example, "→ First course"), and one tap moves the party there. The change broadcasts instantly: the floor sees it, and this screen sees anything the floor does, so the two stay in lockstep.

The button only appears when there's a next stage to move to — a party at the last kitchen-relevant stage has no advance button, and neither does one that's about to depart (bussing happens on the floor, not here).

When the POS controls the course

If your venue runs an external POS that's set to be authoritative over course and payment states, the POS drives those stages — so the manual advance button is hidden for the steps it owns. Parties still move across the columns; they're just moving because the till reported it, not because someone tapped the screen. Under the advisory policy, staff keep the button and the POS may still update alongside them.

Live updates

The screen listens for floor changes and re-draws itself whenever a visit changes, and it also refreshes on a short timer as a safety net. In practice this means you can leave it running on a dedicated monitor and trust it to reflect the room.

What this affects

• Advancing a ticket moves the party through its service lifecycle, which broadcasts to the floor.

What affects this

• Your venue's course sequence decides which columns appear.
• A connected POS and its conflict policy decide whether staff can advance manually.
• Allergies come from each guest's record in the guest book.

Reading a card

Each card is one live party: the bold text is the table (or tables) it sits at, the badge with the people icon is the party size, and the number on the right is minutes since seated — it turns amber as the party nears your expected turn time and red past it. Column headers count parties and covers per course. The kitchen view now fills the whole screen edge to edge: the app navigation tucks itself away (the ☰ button in the header brings it back).