How Better Food Knowledge Cuts Comps and Remakes
Hey Team!
Saturday night at Fat Tommy's, maybe eight months ago. Table of four, peak service, every seat in the house full. Server puts in an order for the braised short rib. Guest gets it, takes two bites, flags the server. Says it's too rich, too heavy, not what she expected. She thought it was going to eat more like a grilled steak. Comp the dish, fire a chicken breast, hold the table for an extra twenty minutes while the kitchen scrambles.
Nobody did anything wrong, exactly. The server wasn't lying. The guest wasn't unreasonable. The short rib was the short rib. But somewhere between the menu description and the table, the picture in the guest's head and the plate in front of her didn't match. That's the whole story. That's where comps are born.
I've been doing this for thirty years. Opened more than twenty concepts. And the single most underrated cost in a full-service restaurant isn't food waste, isn't over-scheduling, isn't even theft. It's the comp that didn't have to happen. The remake that fired because a server described a dish wrong, or not at all, or just said "it's really good, you'll love it" and left the guest to fill in the blanks herself.
Here's what that actually costs you. A comp on a $28 entree isn't $28. It's the food you already sent out, the food you're sending again, the labor on both fires, and the table that's now running 25 minutes longer than it should be on a Saturday at 8pm. Meanwhile the guests behind them are waiting for that table. The guests in front of them are getting slower service because your kitchen is now in the weeds on a remake. One bad description ripples through the whole floor.
Multiply that by how often it happens. If you've got 15 servers and even three or four of them are fuzzy on what's actually in the plates, you're probably eating two or three comps a week that you didn't have to eat. Run that math over a year and you're not talking about rounding errors. You're talking about real margin.
The fix isn't complicated but it does require honesty about why servers don't know the food. Most of the time it's not laziness. It's that nobody ever actually taught them. They shadowed someone for two shifts, got a menu PDF they may or may not have read, took a 10-question quiz someone built in 2019, and got cut loose. The menu has changed four times since then and the quiz hasn't.
At Black Barrel Tavern, we added a walnut cream sauce to one of our pasta dishes. House-made, really good, but obviously a major allergen issue and a flavor profile that not every guest is going to expect in that dish. If a server describes it as "a pasta with a light cream sauce" and doesn't mention the walnut, two things can happen. One, a guest with a tree nut allergy eats something they shouldn't have. Two, a guest who doesn't love walnut gets a dish that surprises them in a way they didn't sign up for. Both of those situations end badly. One ends badly in a way that can shut you down.
The answer is that servers have to know the plate. Not sort of know it. Actually know it. Know the protein, the sauce, the starch, the garnish, the major allergens, and how it eats. Is it rich? Is it light? Is it spicy or does it just have a little heat on the finish? When a guest asks "what's the difference between the short rib and the strip," your server needs an answer that actually helps the guest order the right thing for themselves. That's the job.
When servers can do that, something interesting happens. Guests who would have ordered the wrong thing don't. The expectations they bring to the table match what the kitchen sends out. They're happier before they even take the first bite because the picture they built in their head was accurate. That's not a guest experience tactic, that's just honest communication. And it costs you nothing except the time to actually train it.
The training has to be current. That's the part most operators skip. You update the menu, you pull the old item, you add the new one, and the training doesn't change to match. Three months later half your staff is still describing the old preparation because that's the one they learned. The walnut sauce situation at Black Barrel was caught fast because we had a way to push updated questions to the staff's phones the same week the dish changed. But I've been in situations before where a menu change sat in a manager's head for two weeks before it made it into any kind of training material. That's a two-week window where your guests are getting bad information.
The platform I built, ShiftTrained, handles the update problem by generating new questions directly from the menu, so when the menu changes, the training changes. But even if you're doing this manually, the principle is the same. Your training has to reflect your current menu, not the one from six months ago.
Know your food. Describe it honestly. Set the right expectation before the plate lands. That's it. That's the whole comp-reduction strategy. It sounds simple because it is simple. The hard part is building a staff that actually knows the food well enough to do it consistently, every night, every server, not just the veterans who've been there long enough to learn by accident.
Every comp you write off is money you earned and gave back. Some of those comps are unavoidable. A kitchen mistake, a bad ingredient, a guest who's just having a rough night. But the ones that come from a server who didn't know what was in the plate? Those are on us as operators. We can fix those.
Have a great day! — Terry Psaltakis
Your AI Restaurant Guy
