How to communicate prep times between kitchen and floor

Prep-time communication is where guest expectations meet kitchen reality. It works best when it is short, shared, and honest. A floor team does not need every detail of a station’s workload; it needs enough information to set an accurate next step for a table. A kitchen team does not need repeated interruptions asking “how long?” without order context.

The aim is not to make every preparation time perfectly predictable. It is to prevent silence, vague promises, and unnecessary back-and-forth when conditions change. Use this framework alongside a peak-hour service plan so timing is part of service coordination rather than an afterthought.

Agree on a small shared status vocabulary

Choose terms that mean the same thing to everyone. Software labels can help, but the team must decide what action each label represents in your operation. Avoid a long list of statuses that nobody can use during a rush.

Status	Shared meaning	What the floor can say
Received	Order is visible to the intended station	“The kitchen has received your order.”
In preparation	Work has started or the station has accepted it	“It is being prepared now.”
Waiting on constraint	A known dependency needs resolution	“We are confirming the next update with the kitchen.”
Ready to run	Food can be collected for delivery	“Your order is on its way to the table.”
Needs escalation	The planned timing has changed materially	“I am checking the revised timing for you.”

Only use a phrase with a guest when the team can support it. “Almost ready” becomes frustrating if it repeatedly means ten more minutes. If the kitchen cannot give a reliable estimate, the floor should say what is known and commit to the next check rather than invent a number.

Make each timing question actionable

When a server asks the kitchen for an update, include the order or table context, the relevant item, the current stage, and why the update is needed. “How long on table 12’s mains?” is more useful than “how long?” shouted across a pass.

Create one route for timing questions during peak periods. It might be an expediter, kitchen lead, or designated floor lead. This protects cooks from receiving conflicting interruptions and prevents five people from asking about the same ticket.

Information to include	Why it matters
Table or ticket identifier	Finds the right order quickly
Specific item or course	Avoids a broad queue search
Current guest impact	Helps prioritise meaningful updates
Requested action	Clarifies whether you need timing, a change, or a decision

The same discipline reduces order mistakes. Review how to reduce restaurant order errors when unclear notes are causing timing conversations that should have been avoided at entry.

Set expectation at the right time

Guests generally respond better to an early, honest update than to a late explanation. Train staff to share an expected wait only when the kitchen has a basis for it, such as a known preparation sequence or a confirmed queue condition. Do not turn an average into a promise.

For a dish with a naturally longer preparation, explain that before the guest orders if the menu and service approach support it. For an unexpected delay, acknowledge it as soon as the team identifies the material change. Use simple language: “The kitchen is working through a delay on that station. I am checking the revised timing now.”

Avoid putting detailed operational language in front of the guest. They do not need to hear about equipment, staffing, or internal blame. They need a respectful acknowledgement and a useful next step.

Escalate changes, not every ticket

An escalation is appropriate when the order will not meet the communicated expectation, an item has become unavailable, a quality issue requires a remake, or a guest has a time-sensitive need that the team should consider. Define who can decide what to offer, what to change, and what must be recorded according to your restaurant’s policies.

Situation	First escalation action
Longer-than-expected wait	Kitchen lead confirms realistic update to floor lead
Unavailable item	Kitchen confirms options before floor promises a substitute
Remake	Manager or authorised lead coordinates guest update
Large group timing	Floor and kitchen agree on course sequence
Repeated station delay	Log for post-shift operational review

The escalation path should be visible in a pre-shift brief. It is much easier to use a process the team has rehearsed than to decide it in front of a waiting table.

Review timing communication after service

Use a short end-of-shift discussion:

• Which status words were misunderstood or overused?
• Did timing questions include enough order context?
• Were guests updated early when a material delay was known?
• Did kitchen staff receive avoidable repeat interruptions?
• Which menu, prep, or handoff change would prevent the next delay?
• Is one scenario worth practising in tomorrow’s briefing?

Clear prep-time communication does not make a busy kitchen less busy. It makes the work visible enough for the floor to protect guest trust while the kitchen focuses on producing the food well.