Putting it right: the gesture that fits the fault

A main course arrives cold. A table waits forty minutes between courses. A bottle of wine is opened that nobody ordered. Each needs putting right, and each needs something different. Putting it right well means matching the gesture to the fault: enough to show the venue cares, not so much that the guest feels bought off, and the same whichever manager is on.

Most venues leave this to instinct. One manager takes the whole bill off for a slow starter; another offers a coffee after a ruined anniversary. Guests notice the difference, and so do the accounts. A venue that agrees a simple scale of faults and gestures, sets limits for each role and records what it gives can respond quickly and fairly on the busiest night.

This guide covers how to judge a fault, the gestures available, how to match the two, who should decide, how to set a recovery budget and a refund policy, and how to learn from the gestures you give. Every venue and figure in it is an example.

Before choosing a gesture, understand the fault. What went wrong, how much did it affect the guest's evening and was it the venue's doing? A cold main course that is replaced quickly has affected ten minutes of the evening. A forty-minute wait that made a couple miss their theatre has affected the whole night.

Ask the guest, briefly and sincerely, and listen to the answer. The same fault can matter very differently to different guests: a slow dessert is a minor irritation for a relaxed table and a real problem for a table with a babysitter waiting. The gesture should fit the effect on this guest, not only the mistake itself.

The gesture is the smallest part of putting things right. What guests remember most is how they were treated: whether someone listened, apologised sincerely, took ownership and fixed the problem quickly. A free dessert offered without an apology feels like a transaction. An honest apology and a quick fix, with a small gesture, feels like care.

Handled well, a mistake can even leave a guest more loyal than if nothing had gone wrong, an effect known as the service recovery paradox. It does not happen every time, and it is no reason to make mistakes, but it shows how much the response matters. The gesture confirms the response; it does not replace it.

It helps to group faults into a few levels, so the team shares a language for them. Minor faults are small irritations: a drink that took too long, a missing side, a dirty glass. Moderate faults affect part of the meal: a wrong or badly cooked dish, a long wait for a main course, a booking that was not ready.

Serious faults affect the whole evening: a meal that failed from start to finish, rude or careless service, a ruined occasion, a large billing mistake. Critical faults are about safety: an allergy mistake, food that made a guest ill, an injury. Each level calls for a different kind of response, and critical faults are not about gestures at all.

The gestures available to a venue form a scale too. At the lightest, an apology and a quick fix. Then a small gesture: a round of drinks, a dessert, a coffee. Then a dish taken off the bill. Then a larger part of the bill, such as a course or the drinks. Then, rarely, the whole bill.

Alongside these sits the invitation back: a meal, a course or a bottle of wine on the house on a future visit. It is not a step on the scale so much as a different kind of gesture, one that brings the guest back to see the venue at its best.

Matching faults to gestures works best as a simple guide the team can remember:

The guide is a starting point, not a rule. A manager can go further for a regular, an occasion or a guest who was especially affected. But a shared starting point means guests are treated consistently, and staff do not have to invent a response under pressure.

Comped gestures feel generous when they are offered, not requested. A server who says, "I am so sorry about the wait, the desserts are on us tonight," before the guest asks, turns a complaint into a moment of care. The same dessert given after a guest has demanded compensation feels like a concession.

Be specific about what is being given and why. "We have taken the steak off the bill, because it was not cooked as you asked" is clear and honest. A vague "we have sorted the bill" leaves the guest unsure what happened, and may lead to an awkward moment when the bill arrives.

A round of drinks is one of the most useful gestures a venue has. It is immediate, it changes the mood of a table at once, and for most venues its cost is modest. It suits faults that affected the evening's pace rather than its food: a wait for a table, a slow kitchen, a mix-up with the booking.

It works especially well for groups, where a slow course affects everyone and a round of drinks restores the atmosphere for the whole table. Offer it early, while the wait is still happening, rather than at the end, when the evening has already been spoiled.

When a dish fails, taking it off the bill is usually the right response, whether or not the guest has eaten some of it. A guest who says their main course was overcooked, and who did not enjoy it, should not have to pay for it. Arguing over how much they ate turns a small fault into a large one.

Offer to replace the dish first, if the guest wants another, and take the original off the bill either way. If the replacement arrives quickly and is good, the evening is often saved. If the guest would rather not wait, removing the dish from the bill acknowledges that the venue let them down.

Taking off the whole bill is rare, and it should be. It suits evenings that failed completely: a series of mistakes, a very long wait, an occasion ruined, a guest treated badly by a member of staff. In those cases, charging anything would add insult to the original harm.

Even then, the bill is not the whole response. A guest whose evening failed wants to know someone cares and that it will not happen again. Combine the gesture with a sincere apology from the manager and, where it fits, an invitation back, so the venue has a chance to show what it is really like.

A gesture can be too generous. Taking the whole bill off for a slightly slow starter can leave a guest embarrassed, as if they had made a fuss. It also costs money the venue may need for faults that really deserve it, and it can teach a few guests that complaining pays.

Overshooting often comes from panic: a manager who wants a complaint to go away as quickly as possible. A clear scale of faults and gestures helps. It gives managers permission to respond proportionately, knowing that a sincere apology and a suitable gesture are enough.

Undershooting is just as damaging. A free coffee after a ruined anniversary dinner, or a dessert after an hour's wait for a main course, tells the guest that the venue does not understand what happened. It can turn a disappointed guest into an angry one, and an angry guest into a public review.

When in doubt, ask the guest what would put things right. Most guests ask for less than the venue would have offered. And when the answer is reasonable, giving it graciously costs far less than the guest's lost goodwill.

An invitation back can be a better gesture than a discount tonight. A guest who leaves with a promise of dinner on the house next time has a reason to return, and the venue has a chance to show them a good evening. A discount tonight is spent and forgotten.

Use it alongside an acknowledgement tonight, not instead of one. "We would love you to come back as our guests, so we can show you what we are really like" works when the evening's fault has also been addressed. Record the invitation on the guest's profile, so whoever is working on their return visit knows to look after them especially well.

A recovery budget is an amount managers can spend each month on putting things right, without asking permission each time. It sounds like a cost, but it is really a tool. It lets managers act quickly and generously when it matters, and it makes the cost of mistakes visible.

Set it from your own history: what the venue has given away in gestures over a few months, adjusted for what you think is right. Review it monthly. A budget that is always exhausted may point to too many faults, or too much generosity. One that is never used may mean guests are not being looked after when things go wrong.

Decide in advance who can give what. Servers might be able to offer a drink or a dessert on their own judgement, so they can respond at once. Supervisors might take a dish off the bill. Managers decide larger gestures and the whole bill.

Empowering the person who hears the complaint matters, because speed is part of the response. A server who has to find a manager before offering a drink loses the moment. A server who can say, "Let me get you a drink on us while the kitchen fixes this," keeps it. Our guide to POS permissions: who can void, who cannot covers how to set roles on the till.

Write the limits down and share them with the team: what each role can give, in what circumstances and how it should be recorded. Include them in training for new staff and review them at the pre-shift briefing from time to time.

Published limits protect everyone. Staff know what they are allowed to do and can act with confidence. Managers know their decisions will be consistent with their colleagues'. And the venue knows that a guest who complains on a Tuesday will be treated much like one who complains on a Saturday.

Sometimes the right response comes after the guest has paid: a guest who calls the next day, or a mistake discovered once the bill is settled. That needs a refund policy the floor can apply without guessing: when money goes back, who can approve it, how it is returned and how it is recorded.

Keep it simple. A manager can approve refunds up to a set amount; anything larger goes to the owner. Refunds go back the way the guest paid. Every refund is recorded with its reason. A clear policy means a guest who rings with a fair complaint is answered quickly, rather than passed between people.

Record every gesture: what was given, why, by whom and for which table. It takes a few seconds on the till, and it turns individual decisions into information the venue can learn from.

Review the record each week. It shows how much the venue gave away, which faults caused it and whether gestures were consistent between managers. It also protects staff: a gesture that is recorded with a reason is a decision, not a suspicion.

The most valuable thing about recording gestures is the patterns they reveal. If the same dish is taken off the bill three times in a week, the problem is the dish. If most gestures happen on one night, the problem may be staffing on that night. If one station causes most of the waits, the kitchen needs to look at it.

A gesture fixes tonight's fault. A pattern, acted upon, prevents next week's. Our guide to complaint patterns: the same thing four times covers how to count complaints by cause and act on what repeats.

An allergy mistake is not a fault to be matched with a gesture. It is a safety incident. The first priority is the guest's health: stop them eating, check how they are, call for help if needed and follow your venue's allergy procedure.

Gestures come later, if at all, and they are a matter for the manager or owner. What the guest needs most is care, honesty and assurance that the venue will find out what went wrong. Our guide to an allergy mistake: the next ten minutes covers what to do when it happens.

Occasionally a guest asks for more than the fault deserves, or more than the person serving them can give. Stay calm and courteous. Acknowledge the problem again, explain what you can do and, if the guest wants more, fetch the manager rather than bargaining at the table.

The manager can then decide, within the venue's policy. Most of the time, a sincere manager and a fair gesture are enough. Where a guest is plainly trying to take advantage, the manager can politely hold to what is reasonable. Bargaining in front of other tables helps nobody.

Sometimes a guest is unhappy about something that is not the venue's fault: a dish that was exactly as described but not to their taste, a quiet room they expected to be lively, a price that was on the menu. They still deserve to be heard.

Acknowledge their disappointment without accepting blame you do not owe. Offering something different, such as another dish they might prefer, is often enough. A small gesture of goodwill is your choice, not an obligation, and it can be worthwhile for a guest you would like to see again.

For serious faults, follow up after the visit. A short, personal note the next day, from the manager or owner, saying you are sorry the evening went wrong and what you have done about it, shows that the apology was meant.

Keep it personal and brief, and do not use it to sell. If you invited the guest back, remind them of the invitation and make it easy to book. Our guide to guest complaints: the first thing to say covers the words that matter most when a guest first complains.

An invented brasserie notices that its managers respond very differently to the same faults. It agrees a simple scale: an apology and a fix for minor faults, the dish or a round of drinks for moderate ones, a significant part of the bill and an invitation back for serious ones. Servers can offer a drink or a dessert themselves; supervisors can take a dish off; managers decide anything larger.

It sets a monthly recovery budget from its last six months of gestures and asks every gesture to be recorded with a reason. Within a few weeks, the weekly review shows that one dish accounts for a third of the gestures. The kitchen changes how it is cooked, gestures fall, and guests notice that problems are fixed quickly whoever is on.

In servearound, a gesture is recorded on the till as a comp, on one dish or on the whole check, with an optional reason, and the dish stays on the check at zero, so the bill shows what was given. A dish that has to be made again can be re-fired as a remake, with a reason: the guest is not charged again and the ticket reaches its station marked Re-fire. Anyone who can take orders can comp, void or re-fire, and there is no manager approval step, so the limits in this guide are a policy the team follows rather than a setting.

Each void, comp and re-fire raises a notification for the team, payment analytics show voids and comps by member of staff, and order analytics show the comp rate and the comped checks with their value, so the weekly review has its figures. A comp or a void on a check that already has a payment recorded is refused, because that would be a refund, and servearound has no refund screen for guest bills: refunds are made outside it, for example on the card terminal that took the payment. See the guests module and point of sale and kitchen.

Responding to a mistake with an apology, a fix and a gesture that fits the effect on the guest.

Judge the fault and its effect on this guest, then use a simple agreed scale as a starting point.

Yes, within limits. A server who can offer a drink or a dessert at once keeps the moment.

A monthly amount managers can spend on putting things right without asking each time.

Rarely: when the whole evening failed, together with a sincere apology and often an invitation back.

Often, because it brings the guest back to see the venue at its best. Use it alongside an acknowledgement tonight.

Stay calm, explain what you can do and let the manager decide within the venue's policy.

To see what mistakes cost and to spot the patterns behind them.

Putting it right means matching the gesture to the fault. Understand what went wrong and how much it affected the guest, then respond with a sincere apology, a quick fix and a gesture that fits: a word for a minor fault, a dish or a round of drinks for a moderate one, a large part of the bill for a serious one, and safety first for anything critical.

Agree the scale in advance, give each role clear limits, set a monthly recovery budget and a refund policy the floor can apply, and record every gesture with its reason. Review the record each week, because the patterns behind gestures show which faults to fix so that next week needs fewer of them.