What is a comp, and who should approve it

A table's main course arrives cold after a long wait. The server apologises and takes the two mains off the bill. Across the room, another server gives a regular a free dessert because they are friends. At the bar, a bartender gives a round to a group who complained about the music. At the end of the month, the owner sees that comps came to more than the wine list's profit, and nobody can say which were deserved, which were kind and which were simply given away.

What is a comp? In a restaurant, a comp, short for complimentary, is an item served without charge: a dish, a drink or a whole bill given free, on purpose, for a reason. Comps are one of the most useful tools a venue has for putting a bad experience right and for looking after its best guests. They are also one of the easiest ways for margin to leak away, unless they are recorded, explained and approved properly.

This guide covers what a comp is, how it differs from a void and a discount, when comps are the right tool, who should approve them, how to set a recovery budget and how to review them. Every venue and figure in it is an example.

A comp is a deliberate decision not to charge a guest for something they received. The item was ordered, prepared and served; the venue chose to give it free. It may be a single dish, a drink, a course for the table or, rarely, the whole bill.

Comps are given for reasons: a mistake the venue made, a long wait, a regular's birthday, a guest the venue wants to welcome back. The reason is what turns a comp from a giveaway into a tool.

Comps and voids are often confused, but they are different. A void cancels an item that should not have been charged, usually because it was entered by mistake, never served or never made. A comp keeps the item on the record, because it was served, but charges nothing for it.

The difference matters for the records. A void says "this never happened"; a comp says "this happened, and we chose not to charge". Mixing them up makes it impossible to see how much the venue really gives away. Our guide to what a void is, and why it must be recorded covers the other side.

A discount reduces a price, often for a group of guests or a period: a percentage off, an offer, a set price for a promotion. A comp gives a specific item away for a specific reason. Discounts are part of pricing; comps are part of service.

Keep them separate in the records and in the team's minds. A server who uses comps as informal discounts for friends is changing the venue's prices without anyone deciding to.

Comps matter because they cost money and because they work. A well-judged comp, offered at the right moment, can turn an unhappy guest into a loyal one, and the cost of a dessert is far less than the cost of losing a regular or receiving a damaging review.

But comps add up. A few comps a night, every night, can cost as much as a member of staff. Knowing how much the venue comps, for what and by whom is the difference between a tool and a leak.

Service recovery is putting a guest's experience right after something has gone wrong. A comp is one way to do it, but not the only one, and not always the best. A sincere apology, a quick fix, a manager's visit to the table and an explanation often matter more to the guest than a free item.

Use a comp when the problem cost the guest something real: a long wait, a dish that was wrong or missing, a special occasion spoiled. Our guide to service recovery: putting a bad night right covers the whole process, and the idea of service recovery is well studied beyond restaurants.

A comp is the right tool when the venue was at fault and the guest has lost something: time, enjoyment or the meal they expected. It is also right for recognition: a regular's anniversary, a guest returning after a bad experience, a table celebrating something important.

It is the wrong tool when it replaces fixing the problem, when it is given to avoid a difficult conversation or when it is given to friends. A comp should always have a reason the manager would accept.

Match the comp to the problem. A short wait for a drink might deserve a sincere apology and the drink quickly; a main course that arrived cold after forty minutes might deserve the dish taken off the bill. A comp much larger than the problem looks like guilt; one much smaller looks like an insult.

Give the team guidance: the kinds of problems that usually call for a comp, and the usual size. Guidance makes the comps fair across the room, so one table is not treated more generously than another for the same problem.

Who should approve a comp depends on its size. Many venues let servers comp small items, such as a drink or a dessert, within a limit, and ask for a manager's approval for anything larger: a main course, a round of drinks for a table or a whole bill.

The approval is not about mistrust. It makes sure the comp fits the problem, that the manager knows what went wrong and can fix the cause, and that the guest receives an apology from someone with authority.

Manager approvals should be quick. A server waiting five minutes for a manager to approve a dessert while the guest waits too defeats the purpose. Agree how approvals are given on a busy night: a word at the pass, a quick sign on the till, a limit the server can use without asking.

Our guide to manager approvals that do not stall a service covers how to design them. The aim is control without delay.

A recovery budget is the amount the venue is prepared to spend on comps for service recovery and recognition each week or month. It turns comps from a surprise at the end of the month into a planned cost.

Set it from the venue's past comps and its goals: enough to put right the problems that will inevitably happen, not so much that it hides problems that should be fixed. Review spending against it each week.

Record every comp at the time, with the item, the value, the reason and the person who gave it. A comp not recorded is a free item the venue cannot explain, and the records are what make the review possible.

Make the reason a short note, not an essay: "main cold after long wait", "regular's anniversary", "missing side". Over a month, the reasons tell the venue where its service is failing.

Review comps every week: the total, the value against the recovery budget, the reasons and the comps by member of staff. Look for patterns: a reason that appears every night points to a problem to fix; a member of staff whose comps are far above everyone else's needs a conversation.

Most of the time, the review shows sensible comps given for good reasons. That is worth knowing too, and worth thanking the team for.

Comps are a signal of what is going wrong. A run of comps for cold mains points to the pass; comps for long waits point to the kitchen's pace or the booking times; comps for missing items point to the order process.

Fix the causes, and the comps fall. A venue that only counts its comps, without asking why they happened, will keep paying for the same problems.

The team's judgement is what makes comps work. A server who notices a problem early and offers the right comp quickly can save a table's evening; one who waits for the guest to complain has already lost part of it.

Train the team in when and how to comp, give them a clear limit and trust them to use it. Review their comps not to catch them out, but to learn from what they saw.

Comps for regulars are a form of recognition: a dessert on a birthday, a glass of wine for a long-standing guest, a taste of a new dish. They build loyalty, but they should be given deliberately, not by habit, or they become an expected discount.

Decide which regulars' occasions the venue recognises and how, and record those comps like any other. Our guide to what average spend is, and how to raise it shows why the guests who return matter so much to the figures.

The hardest comps to control are those given to friends and family: a free drink for a friend at the bar, a dessert for a cousin. They are rarely meant badly, but they are the comps most likely to go unrecorded and to grow.

Set a clear rule: staff do not comp their own friends and family without a manager's approval. Applied to everyone, including managers, the rule is fair and easy to follow.

Occasionally, comps hide dishonesty: items comped after the guest paid in cash, with the cash kept, or comps used to give away stock. These cases are rare, but the records are what reveal them.

Watch for patterns: comps made after a bill was paid, comps concentrated on one person's tables, or comps that rise sharply on particular shifts. Our guide to till fraud: the six patterns worth watching covers the signs.

When a comp is given, tell the guest, simply and sincerely: "We have taken the mains off the bill, because they should never have arrived like that." A comp the guest does not notice, buried in the bill, does little for the relationship.

Do not make a show of it, and never ask the guest to promise a good review in return. The comp is an apology, not a trade.

Bars comp drinks more often than kitchens comp food: a round for a regular, a drink for a guest who waited, a replacement for a spilled glass. Because drinks are quick to give and hard to trace, bar comps need the same recording as any other.

Ring every comped drink through the till with its reason. A bar where drinks are given without a record cannot tell its generosity from its shrinkage.

Some complaints arrive after the guest has left: an email the next morning, a message through the website, a review. The comp, if one is right, cannot be taken off a bill that is already paid.

Many venues offer an invitation to return instead: a table, a dish or a bottle on the house on their next visit. Record it like any comp, with the reason, and make sure the team knows when the guest arrives.

Never offer a comp in exchange for a good review, or ask a guest to change a review in return for one. It undermines the trust the comp was meant to rebuild, and review platforms do not allow rewards for reviews.

Offer the comp as an apology, with no conditions. A guest who feels genuinely looked after may update their review on their own; one who feels bought will not.

Guests often value a sincere apology and a quick fix more than a free item. A manager who comes to the table, apologises in plain words and explains what will happen next can do more than a comp.

Use the comp as part of the recovery, not as a substitute for it. A dessert left on the table without a word looks like an attempt to make the problem go away.

Teach the team to apologise well: acknowledge what went wrong, take responsibility without blaming the kitchen or a colleague, and say what will happen now. Practise it in training, because it is hard to do well under pressure.

A team that apologises well needs fewer comps, and the comps it gives carry more meaning.

Comps reduce the venue's sales, and the accountant needs to know how they are recorded. Ask how comps should appear in the figures, whether as a reduction of sales or a cost, and how they are treated for tax where you trade.

A comp recorded consistently, with its value, makes the accounts and the weekly review agree.

Many comps follow kitchen mistakes: a dish wrong, cold or late. The comp puts things right for the guest, but the kitchen needs to know too, so the cause can be fixed.

Share the comps with the head chef each week, with their reasons. A chef who sees five comps for the same dish in a week has a reason to look at the recipe, the station or the timing.

Comps also follow floor mistakes: an order entered wrongly, a drink forgotten, a dish delivered to the wrong table. These point to the order process, the training or the number of tables each server is looking after.

Look at floor comps by shift and by member of staff. A pattern on the busiest nights may mean too few servers for the room, rather than any one person's failing.

A comp means more when the team knows the guest. A regular who has a rare bad evening deserves a different response from a first-time guest, and both deserve a sincere apology.

Note significant comps on the guest's record, where the venue keeps one, so the team knows on the next visit that something went wrong last time. A guest welcomed back with that knowledge feels genuinely looked after.

Set the limits for comps clearly and write them down: what a server may give without asking, what a supervisor may give and what needs the manager. Review the limits every few months against the weekly figures.

Limits that are too low make the team wait for approval on every small problem; limits that are too high hide comps that should have been questioned.

An invented brasserie finds that comps came to more than its wine margin last month. It introduces a rule: servers may comp a drink or a dessert without asking, up to a small limit, and anything larger needs the manager's word at the pass. Every comp is recorded with a short reason, and the manager reviews them each Monday against a weekly recovery budget.

The first review shows a third of the comps were for cold mains on Fridays. The kitchen moves a cook to the pass on Friday evenings, and the Friday comps fall by half. The second review shows one server's comps far above the others, mostly to friends at the bar; a quiet conversation ends it. Within two months, comps are within the budget, and every one has a reason.

In servearound, a line or a whole check can be comped on the till, with an optional reason, and un-comped if it was a mistake. Anyone who can take orders can comp: there is no separate comp permission and no manager-approval step, so approvals are the venue's own rule, and each comp raises a notification to the team. A comp on a check that already has a payment recorded is refused.

Order analytics show the comp rate and the comped checks and their value, and payment analytics show voids and comps by member of staff, the weekly review in one place. See point of sale and kitchen.

An item served without charge, on purpose, for a reason.

A comp keeps the item on the record and charges nothing; a void cancels an item that should not have been charged.

When the venue was at fault and the guest lost something, or to recognise a regular's occasion.

Servers within a small limit; a manager for anything larger.

A planned amount for comps each week or month, reviewed against what was spent.

Yes, with the item, the value, the reason and the person.

Weekly, by reason and by member of staff, against the budget.

Occasionally. The records and the patterns in them are what reveal it.

What is a comp? It is an item given free, deliberately, for a reason: a tool for service recovery and recognition. Keep comps and voids separate, and both separate from discounts, so the records show how much the venue really gives away and why.

Let servers comp small items within a limit, design manager approvals that do not slow the service, set a recovery budget and record every comp with its reason. Review them weekly by reason and by member of staff, fix the problems they reveal and tell the guest sincerely when a comp is given.