A late main course and a table that has noticed

The starters were cleared twenty-five minutes ago. The table of four has stopped talking. One guest is looking towards the kitchen door, another has picked up their phone, and the wine glasses are empty. A late main course has become something the table has noticed, and the evening is quietly turning. What happens in the next two minutes decides whether this becomes a story about a lovely dinner with a short wait or a story about a long wait.

Most of the damage from a late main course comes not from the wait itself but from the silence around it. Guests can accept a delay they understand. What frustrates them is not knowing: whether their order was forgotten, how long it will be, whether anyone has noticed. A server who goes to the table first, with an honest update and something in their hands, can turn the moment around.

This guide covers when a main course counts as late, what to tell the table and who should tell them, what to put in their hands, the kitchen signal that should reach the floor before the table notices and how to stop it happening as often. Every venue and figure in it is an example.

A main course is late when it takes longer than the guest expects. That depends on the venue: a busy bistro's guests may expect mains within fifteen minutes of their starters being cleared, while a tasting menu's guests expect a slower pace. The expectation is set by the venue's own rhythm, what the server said and what the guests can see happening around them.

Know your normal. If mains usually reach the table about fifteen to twenty minutes after starters are cleared, then twenty-five minutes is late, and thirty is a problem. Writing that rhythm down, and sharing it with the team, gives everyone the same sense of when to act.

Tables notice a delay before they say anything. The conversation slows. Guests look around, try to catch a server's eye, check the time or glance at other tables that were seated later and are already eating. Glasses run empty, and nobody refills them.

Train the team to read those signs. A table that has noticed is a table whose patience is running down, and every minute without contact makes the eventual conversation harder. The moment to act is when the signs appear, not when a guest finally waves someone over.

In many venues, a sensible point to go to the table is around twenty-five minutes after the starters were cleared, if the mains have not arrived. Before that, most guests are still relaxed. After it, many are wondering whether something has gone wrong.

The exact number is yours to set, based on your menu and your guests. What matters is having one. A shared mark means a server does not have to decide alone whether a wait is long enough to mention, and the floor manager can see at a glance which tables have passed it.

The single most effective thing a server can do is go to the table before the guests ask. A guest who has to wave for attention has already started to feel neglected. A guest who is approached with an update before they ask feels looked after, even though the food is just as late.

It takes courage, because nobody likes delivering bad news. But a short, honest update, given early, almost always goes better than waiting and hoping the food arrives. Make it the expectation for every server: if a table has passed the mark, you go.

Before going to the table, find out what is happening. Ask the pass or the kitchen how long the mains will be and why. A server who goes to the table without knowing can only offer vague reassurance, which guests see through quickly.

Never guess, and never say "it is just coming" unless it is. A guest told "two minutes" who waits another ten feels misled, and the second wait is worse than the first. An honest "about eight minutes" that turns out to be six is a pleasant surprise.

Keep it honest, specific and short. "I am so sorry for the wait. Your mains are about eight minutes away; the kitchen is catching up after a large party. Can I bring you some bread and top up your drinks while you wait?" That covers the apology, the time, a brief reason and an offer.

Avoid blaming anyone. "The kitchen is a mess tonight" or "we are short-staffed" makes the guest worry about the whole evening. Avoid long explanations, too. Guests want to know how long and that someone cares, not the details of what went wrong behind the scenes.

Usually the table's own server should go first, because they know the table and the guests know them. If the wait becomes long, the table is clearly upset or it is a second update, the floor manager should go, because a visit from a manager signals that the venue is taking it seriously.

Occasionally a chef going to the table can transform the moment: a brief apology from the person cooking the food, with an assurance that the dishes are being finished properly, is often appreciated. It suits some venues more than others, and it works best when it is genuine rather than staged.

A wait is easier with something to do. Bread, a small taste from the kitchen, a bowl of olives or a fresh round of drinks gives the table something to enjoy and shows that the venue is doing more than apologising.

Choose something the kitchen can send quickly without slowing the mains further. A taste of a dish that is already prepared, or something from the bar, is better than asking the struggling station to make something extra. The aim is to fill the wait, not to add to it.

Sometimes the second estimate is wrong too. If the mains still have not arrived when promised, the next update should come from the manager, with a more significant gesture and a clear new time. Do not let a table wait through a second delay in silence.

This is also the moment to offer options. If one dish is the problem, could the guest have something quicker? Would the table prefer to start while the last dish follows? Giving guests a choice restores some control to them, which matters a great deal when they have been waiting.

In a well-run service, the floor knows about a late main course before the table does. The kitchen can see that a ticket has been on the board too long, or that a station is behind, well before a guest looks at the time. The signal should travel from the pass to the floor at once.

Traditionally, the person running the pass, sometimes called the aboyeur in the brigade de cuisine, calls tickets and keeps the timing of every table in view. Whatever you call the role, agree a simple habit: when a ticket passes the mark, the pass tells the table's server, with an honest estimate. That turns a surprise into a plan.

The time each ticket has been in the kitchen is the most useful early warning a venue has. A ticket that is running well past the kitchen's usual time is a late main course in the making, and the earlier it is spotted, the more options there are.

Watching ticket times during service lets the pass act before the floor has to. Looking at them after service shows which dishes, stations and times of night are prone to delays. Our guide to ticket times: the only kitchen metric that moves covers how to use them.

Mains run late for a handful of reasons. One station is overloaded, often the grill on a busy night. A large table was fired at the same time as several smaller ones. A dish had to be remade. An ingredient ran out mid-service. A new cook is still finding their pace.

Most of these are kitchen bottlenecks: one part of the kitchen that cannot keep up with the rest. They tend to repeat, on the same nights and with the same dishes. Our guide to kitchen bottlenecks: finding the station that stalls covers how to find and fix them.

Many late main courses start at the door. When five tables are seated within ten minutes, they order within ten minutes, and their mains hit the kitchen together. However good the kitchen, some of those tables will wait.

Pace the room. Stagger booking times, especially for larger tables, and seat walk-ins with an eye on what the kitchen is already handling. A host who holds a table for five minutes at the door, with a drink at the bar, can save that table from a twenty-minute wait for its mains.

Mains should be fired when the starters are nearly finished, so they arrive soon after the plates are cleared. Fire too early and the dishes wait at the pass, going cold, or the table feels rushed. Fire too late and the table waits.

Servers who tell the kitchen when a table is ready for its mains, and a kitchen that fires on that signal, keep the timing right. Dishes with long cooking times need firing earlier, which is something the kitchen and floor should agree in advance rather than on the night.

When a dish is sent back, dropped or made wrongly, the remake starts from scratch, and the whole table may be waiting for it. A re-fire is one of the most common reasons a main course becomes very late.

Treat remakes as urgent. The kitchen should prioritise them, and the server should tell the table at once how long it will be. Offer the others at the table the choice of starting or waiting, and consider a gesture for the guest whose dish is being remade, especially if the original mistake was the venue's.

Tables usually want their mains together, so one late dish can hold up four guests. When that happens, ask the table what they would prefer: to wait for everyone's food together, or to start while the last dish follows.

Do not decide for them. Some tables would rather eat together; others would rather not let three meals go cold for one. Asking is respectful, and either choice is better than four guests watching three plates cool while nobody explains.

Once the mains arrive, the service recovery is not over. Check back soon to make sure the food is right, and acknowledge the wait again briefly. A gesture that fits the fault, such as a round of drinks or desserts on the house for a long wait, often closes the evening well.

Match the gesture to how long the wait was and how much it affected the table. A short wait handled well may need only the apology and the bread. A long one that strained the evening deserves more. Our guide to putting it right: the gesture that fits the fault covers how to choose.

Some phrases make a late main course worse. "It is coming now" when it is not. "The kitchen is really busy" when the guest can see the room is half full. "We are short-staffed tonight", which invites the guest to worry about everything else. "Nobody told me", which tells the guest that the team does not talk to each other.

Stick to what helps the guest: an apology, an honest time, a brief reason if it is useful and something to make the wait easier. Everything else is about the venue, and guests waiting for their dinner are not interested in the venue's problems.

What counts as a long wait depends on the guest. A couple on a relaxed anniversary dinner may not mind fifteen extra minutes. A business lunch with a meeting at two, or a family with tired children, may find the same wait unbearable.

Know which tables are on a clock. Ask when they order whether they have somewhere to be, and note it on the ticket so the kitchen knows. A server who knows a table needs to leave at nine can warn them early if the kitchen is behind, and suggest dishes that will come quickly.

For guests in a hurry, prevention matters most. If a table says they need to leave by a certain time, recommend dishes the kitchen can produce quickly, tell the kitchen and check the timing as the meal goes on.

If the kitchen is already behind when they order, say so honestly: "We are running about ten minutes behind on mains tonight. If you need to be away by eight, the risotto and the salad will be quickest." Guests appreciate the honesty, and it prevents a late main course from becoming a missed train.

Use the pre-shift briefing to prepare for delays. Which large tables are booked and when? Which dishes take longest? Which station is likely to be under pressure tonight? Who is watching ticket times at the pass?

A team that knows where the pressure will be can pace the room, warn tables early and respond quickly when a ticket runs long. A team that discovers the pressure at the same moment as the guests can only apologise.

After service, look back at the late tables. Which dishes were late, which station were they from and what time of night was it? Was it one large table, a remake, a missing ingredient or simply too many tables seated together?

Write it down, and look at the pattern over a few weeks. Most late main courses come from a small number of repeated causes. Fix those, and the number of tables that notice a wait falls, which is better for the guests, the team and the kitchen.

An invented bistro gets frequent complaints about slow mains on Friday nights. It sets a simple rule: if mains have not arrived twenty-five minutes after starters are cleared, the server goes to the table with an honest time and something to eat, and the pass tells servers as soon as a ticket runs long.

Looking at the late tickets over a month, it finds that most came from the grill, when several large tables ordered steaks at once. It staggers large bookings on Fridays, adds a second cook to the grill at the peak and gives servers a short list of quicker dishes for guests in a hurry. Complaints about slow mains fall sharply, and the tables that do wait are told before they ask.

In servearound, each kitchen station has its own board, tickets arrive oldest first and each ticket shows its age, counting up, with the guest's allergies at its head. Dishes can be held and fired from the POS, including "Fire N held" for every held dish at a table, or fired from the board with a second tap, so mains go when the starters are cleared. A dish sent back can be re-fired as a remake, with a reason, and arrives at its station marked Re-fire.

servearound does not warn the floor when a ticket runs long, so the signal in this guide is a habit between the pass and the servers. The Orders page sorts orders into pending, preparing and ready. Kitchen analytics show ticket times, median and P90, by station and by day and hour, the on-time rate against one fixed fifteen-minute mark, where the minutes go between queue, prep and pass, and the slowest tickets with their lines, so the review after service has its evidence. See point of sale and kitchen and the guests module.

When it takes longer than the guest expects. Set a mark for your venue, such as twenty-five minutes after starters are cleared.

An apology, an honest time, a brief reason if it helps and an offer of something while they wait.

The table's server first; the manager for a long wait, an upset table or a second update.

Something to fill the wait, such as bread or a drink, and a gesture afterwards that fits how long the wait was.

Agree a habit: when a ticket passes the mark, the pass tells the table's server with an honest estimate.

Usually an overloaded station, several tables fired at once, a remake or a missing ingredient.

Ask the table whether they would rather wait together or start while the last dish follows.

Pace the room, fire at the right time, watch ticket times and fix the causes that repeat.

A late main course does most of its damage through silence. Set a mark for your venue, such as twenty-five minutes after starters are cleared, and go to the table before the guests ask, with an honest time, an apology, a brief reason and something to fill the wait. Find out from the kitchen before you go, never guess and never blame anyone in front of the guests.

Better still, let the kitchen's signal reach the floor first: when a ticket runs long, the pass tells the server. Pace the room so mains do not all hit the kitchen at once, fire at the right time, treat remakes as urgent, ask tables in a hurry when they need to leave and look back after service at which dishes and stations ran late, so the same delay happens less often.