Running out of a dish at half past eight

At half past eight, the last portion of the braised short rib goes out. It is the most popular main on the menu, and the dining room is still filling. Over the next ten minutes, three servers sell it to four tables. The kitchen sends word back to each one, the servers return to the tables to apologise, and four groups of guests choose again, a little less happy than before.

Running out of a dish is part of restaurant life. Fresh food, limited prep and unpredictable demand mean it will happen. What separates a good venue from a frustrating one is what happens in the minutes after: who finds out, how quickly, what guests are offered and what changes so it happens less often.

This guide covers the order in which people need to know, how to tell guests who have already ordered, what to offer instead, and the prep change that stops the same dish running out next week. Every venue and figure in it is an example.

Dishes run out for a few common reasons. The kitchen prepared too few portions, because the prep was based on a guess or on an ordinary night. A dish sold far better than usual, because of the weather, a large booking or a mention online. A delivery was short or late. Or a batch went wrong and had to be thrown away.

Some running out is unavoidable, and some is even a good sign: a dish that sells out every night is a dish guests love. But running out of a dish at half past eight, every Friday, is a prep problem, not bad luck.

Knowing why each dish ran out is the first step towards running out less.

The best time to deal with running out of a dish is before the last portion goes. A kitchen that knows it has five portions left can warn the floor, slow recommendations and plan what to offer instead.

Build a simple habit for limited dishes: specials, dishes made in batches and anything with a fixed number of portions. The station that cooks them keeps a count during service and calls a warning at the pass when it reaches a set number, such as five.

That warning gives the floor time to stop recommending the dish, and gives the kitchen time to decide whether to make more or let it run out.

Running out is a test of kitchen communication. The message must travel from the station that has run out to the pass, from the pass to the floor and the system, and from the floor to the guests, in minutes. Each handover is a chance for delay.

Agree in advance who says what. The station tells the pass the moment the last portion goes. The pass 86s the dish and says it aloud. The manager or a senior server makes sure every server and the bar have heard. Practised once or twice, it takes under a minute.

The host often hears about a shortage last, and yet the host is the one seating guests who may have come for that dish. A guest who booked for the short rib and is told at the door is disappointed; one told after ordering is more so.

Tell the host when a popular dish runs out, so they can mention it gently to arriving guests who ask, and so the waiting list is not built on a promise the kitchen cannot keep.

When a dish runs out, several people need to know, and the order matters. First, everyone who can sell it: every server, the bar, the host and every menu guests order from, including any guests ordering from their phones. Second, the kitchen stations that cook it or its sides, so they stop preparing parts of it. Third, the manager, who may need to decide what to offer instead.

The first group matters most, because every minute they do not know is a minute in which the dish can be sold. A dish that runs out at half past eight and is still being sold at twenty to nine leaves several tables disappointed.

The fastest way to tell everyone is to 86 an item in the system the moment it runs out, so it comes off every till and every guest menu at once. A dish marked sold out cannot be ordered, so nobody has to remember to stop selling it.

Word of mouth is slower and less reliable. A shout from the pass reaches the servers nearby but not the one on the terrace, the bartender or the guest scrolling the menu on their phone. Our guide to 86 an item so nobody orders it at five past covers the routine.

Decide who is allowed to 86 a dish. Usually anyone at the pass or on the till can, because speed matters more than permission.

Running out of a dish affects more than the station that cooks it. A main that has run out may have a side that another station was preparing, or a garnish being portioned. Tell those stations too, so they stop preparing parts of a dish that will not be ordered.

Good kitchen communication makes this automatic: the person who calls the 86 says it at the pass, loudly enough for every station to hear, and the screens or tickets stop showing new orders for it.

The hardest part is the guests who have ordered the dish but not yet received it. Tell them quickly, in person, as soon as the kitchen confirms it cannot be made. A guest who hears straight away can choose again calmly; one who hears after twenty minutes of waiting has a reason to be annoyed.

The server should go to the table, apologise sincerely, explain briefly and offer alternatives. Avoid blaming the kitchen. "I'm so sorry, we've just run out of the short rib" is enough.

Running out is harder when the dish is part of a set menu or a pre-ordered party menu. The table may have chosen the venue for that menu, and a substitute changes the meal they agreed to.

Have a substitute agreed for every dish on a set menu before the night, of the same value and style. Tell the table's host or organiser first, before the guests, and let them decide how to tell their party.

Have alternatives ready before you need them. For each limited dish, the kitchen should know which dish is the best substitute: similar in style, similar in price, ready in similar time. The server can then suggest it with confidence.

Make the change easy for the guest. Offer the alternative, explain why it is a good choice, and let the guest decide. If the alternative costs more, consider charging the original price; if the guest's table now has to wait longer for one dish, make sure the rest of the table's food is timed to match.

Most guests accept that a dish can run out, especially if they are told quickly and kindly. Service recovery matters more when the guest has waited, when the dish was the reason they came, or when it happens to several guests at one table.

Fit the gesture to the disappointment. A sincere apology and a good alternative is usually enough. A guest who came specially for the dish, or who waited a long time before being told, may deserve more: a drink, a dessert or a note on their record so the dish is saved for them next time. Our guide to service recovery: putting a bad night right covers the approach.

Drinks run out too: a particular wine, a beer on draught, a spirit for a signature cocktail. The same principles apply: 86 it at once, tell the bar and the floor, have an alternative ready and record it.

Wine is the most delicate. A guest who chose a bottle from the list and is told it has gone should be offered a similar bottle at a similar price, or a slightly better one at the same price. Bar stock that runs out often is a sign the ordering needs adjusting.

When guests order from their phones, running out has to reach the digital menu at once. A dish still showing as available on the phone can be ordered, sent and then declined, which feels worse to the guest than being told by a server.

Make sure the 86 reaches the digital menu the moment it is made, and that a dish already in a guest's basket cannot be sent once it has run out. Our guide to updating a QR menu in the middle of service covers it.

Sometimes the kitchen can make more of a dish during service: a quick dish with ingredients on hand, or a batch that can be finished in time. Sometimes it cannot: a braise that takes four hours, or an ingredient that has run out.

Decide quickly, at the pass, and tell the floor the answer. A dish that will be back in twenty minutes can be offered with a wait; one that is gone for the night should come off every menu until tomorrow.

Some dishes are the reason guests choose your venue: a signature dish, a dish praised in a review, a seasonal special people have travelled for. Running out of those costs more than a single sale.

For signature dishes, prep generously, especially on busy nights, and consider holding a few portions back for guests who booked specially, if they told you. If one does run out, the apology and the gesture should be larger than for an ordinary dish.

If the dish comes back during service, put it back on the menu at once, and tell the floor. If it is gone for the night, make sure it comes back for the next service: a dish 86'd on Friday and forgotten can be missing from Saturday's lunch.

Check what is 86'd at the end of each service, and decide what should return for the next one. A line in the closing routine prevents the next morning's surprise.

Record every dish that runs out, with the time and the reason. A simple note at the pass is enough: "short rib, 8.32, sold more than expected". Over a few weeks, the notes show patterns: which dishes run out, on which days, at what time.

Those patterns are the evidence for changing prep. Without them, the kitchen guesses again next week; with them, it plans.

Once a week, read the record of what ran out. Look for the dishes that run out most often, the days they run out and the times. A dish that ran out three Fridays in a row at about the same time tells you exactly how much more to prepare.

Look at waste too. A dish that never runs out but is often thrown away is prepared in too large a quantity. The aim is to balance the two: rarely running out, rarely throwing away.

Most running out comes from prep based on yesterday, or on an ordinary night. A kitchen that prepares the same amount of short rib every day will run out on busy nights and waste it on quiet ones.

Prep from forecast instead. Look at what the dish sold on the same day last week and the week before, at today's bookings and at anything unusual, such as a large party or a holiday. The idea is the same as any demand forecasting: use what you know about the past and the day ahead to plan the quantity. Our guide to prep from forecast, not from yesterday's prep covers how.

Once you know which dishes run out, and when, change the prep. If the short rib runs out at half past eight every Friday, prepare more for Fridays, or prepare a second batch that can be finished by eight. If a special runs out on the first night, prepare more on the second.

Balance the change against waste. A dish that runs out at ten to ten may be prepared about right; one that runs out at half past eight is clearly short. The aim is to run out close to the end of service, not in the middle of it.

Some venues choose to run out. A dish made in a small batch each day, sold until it is gone, can create a sense of occasion and reduce waste. "When it's gone, it's gone" can be part of the menu's appeal.

If you choose to run out, tell guests. Mark the dish on the menu as limited, let servers mention it early in the evening, and make sure the 86 is quick when the last portion goes. Running out by design feels very different to guests from running out by accident.

Some running out starts with a delivery: an order that arrives short, late or not at all. Check deliveries on arrival, and tell the kitchen at once if anything is missing, so the prep can be adjusted and the floor warned before service.

Build a relationship with suppliers so a late delivery can be chased or replaced quickly. For key ingredients, know a second supplier who can step in at short notice.

An invented bistro runs out of its braised short rib most Fridays at around half past eight. The news travels by word of mouth from the pass, so servers keep selling it for ten minutes or more. Several tables a night have to choose again after waiting.

The bistro makes three changes. The grill calls a warning at five portions left and 86s the dish on the till the moment the last one goes, so it disappears from every menu at once. Servers are briefed on the best alternative for each limited dish. And the head chef looks at four weeks of Friday sales and prepares a second batch of short rib on Fridays.

Within a month, the short rib runs out on Fridays at about a quarter to ten rather than half past eight, and on the nights it does run out, no table orders it after it has gone.

In servearound, anyone on the till can 86 a dish from a search of the menu, with a confirmation that it comes off the digital menu straight away and no one can order it until it is put back, and "Back on" restores it from the same screen. It shows as sold out on every guest menu at once, including on the phones of guests who already have the menu open, and the team is told. In the menu library, a dish marked sold out can be set to come back by itself tomorrow, or to stay sold out until someone turns it back on.

For the prep change, the menu report shows the units sold of every dish over any range of dates, so last Friday's and the Friday before's sales are there to plan from. See Order Fulfillment and the menus module.

86 it in the system at once, tell the kitchen's other stations, tell guests who have already ordered, and offer a ready alternative.

Everyone who can sell it: servers, the bar, the host and every guest menu.

Quickly and in person, with a sincere apology and a good alternative, without blaming the kitchen.

Fit it to the disappointment. An apology and a good alternative is usually enough; a long wait may deserve more.

Keep a count of limited dishes during service and call a warning at a set number of portions.

Record what ran out and when, and prep from a forecast based on past sales and today's bookings.

It can be, by design: a limited dish, marked as such, sold until it is gone.

The 86 must reach the digital menu at once, so the dish cannot be ordered and then declined.

Running out of a dish will happen. What matters is how quickly everyone finds out and what guests are offered. See it coming with a count and a warning, 86 the dish in the system the moment it runs out so it disappears from every till and menu, tell the kitchen's other stations, tell guests who ordered it quickly and kindly, and have a ready alternative.

Then fix the cause: record what ran out and when, prep from a forecast rather than from yesterday, aim to run out near the end of service rather than the middle, and if you choose to run out on purpose, tell guests the dish is limited.