Lunch service: coordinating the floor and the kitchen better

Service usually gets harder at one specific point: passing information along. A change stays on the floor, a dish waits at the pass, a table is asking about an order no one can find. Everyone is working, but the team no longer shares the same picture.

To set up a smoother lunch service, start by making three things visible: what was ordered, what is being prepared, and what is ready to go out.

Before opening: a briefing that helps people act

Gather whoever is on shift for a short check-in. The goal is to circulate the information that will change decisions during service.

Go over the special reservations, the groups you're expecting, the dishes that are unavailable, limited quantities, and who is working each station. End with one question: "If we fall behind, who tells whom?"

A sample briefing: "We have a group at 12:30. The daily special is limited. One person owns the call-outs at the pass, and the floor warns the tables involved as soon as a timing changes." Adapt the roles to your headcount, even if one person wears several hats.

Give the order's stages the same meaning

The words have to point to precise situations. "Received," "in prep," "ready," and "served" are not interchangeable.

For each stage, define an owner and an expected action. A received order has to be acknowledged. A ready dish has to be signalled to the floor. A served dish must be distinguishable from one still sitting at the pass.

You can apply this rule with paper tickets or a kitchen display. The tool should support a method everyone understands.

Make orders readable from the start

A usable order lets you find the table, the dishes, their quantities, and the confirmed changes. Choose shared wording for the usual options rather than several personal shorthands.

Special requests must be confirmed with the people who can handle them. If a request involves an allergy, follow your dedicated procedure and make sure it is explicitly understood: a note on a ticket is not enough to guarantee it's handled.

To change an order that's already been sent, decide who records the change and who confirms the kitchen received it. Information shouted in passing is easy to lose.

Make the pass a point of coordination

Before a plate leaves, check its destination and what should go out with it. If several dishes for one table are expected together, the floor and the kitchen have to share that intention.

During a busy stretch, name one person to centralize the exchanges at the pass. That keeps several colleagues from asking separately about the same table.

When a delay comes up, give the floor something usable. "This table is still waiting on two dishes; we'll check before quoting a time" beats a promise made on the spot.

Prepare for the moment the pace changes

A quiet service and a rush don't call for the same division of work. Decide in advance how the team reorganizes: who helps clear tables, who tracks ready dishes, and who keeps an eye on the waiting tables.

Keep a fallback too, in case your digital tool becomes unavailable. What matters is keeping one reference order and avoiding duplicates when things get back to normal.

After service: pick one improvement

Take a few minutes to look at one specific situation. At which stage did the information break down? Was it a wording problem, an ownership problem, or a follow-up problem?

Note, for example, the orders corrected after they were sent, the dishes returned for an error, and the tables that asked for updates more than once. Then compare similar services and keep the context: number of covers, headcount, and group sizes.

Your coordination checklist

• Availability announced before opening.
• Roles and a point person at the pass identified.
• Order stages defined.
• Change procedure known.
• Waiting tables kept informed.
• One concrete thing to improve next service.

To get started: clarify your order stages with the team at the next briefing. Discover RiseResto to think through a shared way of working between the floor and the kitchen.