Every server spends their first weeks, and quite a lot of their later career, talking about food they have not eaten. Large menus, rotating specials, agency shifts, a kitchen that does not run staff tastings: the situation is normal rather than a failure of preparation. What is not normal is how badly most people handle it.
The two bad options are lying and freezing. There is a third one, and it works better than either.
Why bluffing is the worst available choice
The instinct is to say something positive and move on. “That one is great.” It takes a second, the guest is satisfied, and nothing appears to go wrong.
Things go wrong later. The guest asks a follow-up you cannot answer, and the bluff is now visible. Or the dish arrives and it is not what they expected, and the person who told them it was great is you. Or, worst, they had an allergy question folded into the taste question and your confident answer was a guess.
The reputational cost is quiet and real. Guests rarely complain about being misled, they just stop asking you things, which removes exactly the interaction that produces good service and better tips.
Freezing is not much better. “I have not tried it” and then nothing leaves the guest holding a question they still need answered, and it reads as unhelpfulness rather than honesty.
The third option: describe, attribute, offer
The working move has three parts and takes about eight seconds.
Describe what you know factually. What is in it, how it is cooked, how big it is, what it comes with. All of that is available from the menu and the kitchen, and none of it requires having tasted anything.
Attribute any evaluation to someone who has. The kitchen, the chef, other guests, the specials briefing. “The chef put that on this week and is pleased with it” is a real signal and an honest one.
Offer to find out. “I have not had it myself, I can ask the kitchen if you want the detail.” Most guests say no and appreciate the offer more than the answer.
Put together: “I have not tried it yet, and I can tell you it is the sea bream, pan roasted, with a salsa verde and it comes on its own. It has been going out all night. Do you want me to check anything with the kitchen?”
That answer is more useful than a bluff, and it is more useful than most confident answers, because it contains actual information.
| Situation | Weak answer | Working answer |
|---|---|---|
| Guest asks if a dish is good | ”It is great” (untasted) | Describe it, then attribute the praise |
| Guest asks about texture | Guess | ”I have not had it, the kitchen says it is very soft” |
| Guest asks about spice | ”Not too spicy" | "There is chilli in it, let me check the level” |
| Guest asks about an allergen | Any guess at all | ”I will confirm with the kitchen” and go |
| Guest asks what you would order | Naming an untasted dish | Name one you have had, or say which is selling |
What you can say without ever tasting a dish
More than most servers realise. The following are all factual and all obtainable in a two-minute conversation with the kitchen.
The composition: main ingredient, sauce, garnish, what it sits on. Compressing that into one spoken sentence is the skill this rests on.
The method: roasted, fried, braised, raw, smoked. This sets a texture expectation, which is a large part of what “is it good” means to a guest.
The size relative to the rest of the menu, which is the question behind roughly half of all dish questions.
The accompaniment, or the absence of one. Whether it arrives alone is the most complaint-preventing fact on any menu.
The flavour direction, which the kitchen will tell you in one word: rich, sharp, sweet, mild, smoky.
Allergens and whether modification is possible, which you must have exactly right and must never infer. The major food allergens the FDA requires to be declared make a reasonable memorisation target, and the allergens every server should know turns it into floor practice.
Preparation time, if it is unusual.
That is seven facts, none of which require personal experience, and together they answer nearly every question a table will ask. It is also, not coincidentally, what fits on the back of a card, and drilling those cards by recall rather than by re-reading is what research on the testing effect supports. MenuFlashcards builds a deck from a photo of the menu, and these are the fields worth adding when you cannot taste your way through the list.
How to get the information fast
The bottleneck is not memory, it is access. Kitchens are busy and new servers are reluctant to ask.
Ask in a batch rather than one dish at a time. Turning up with a list of six dishes at a quiet moment is welcome; interrupting six times during service is not.
Ask the right person. The chef de partie who actually plates the dish knows more about it than the head chef does at that moment, and is usually easier to reach.
Ask specific questions. “What is the salsa verde in the bream?” gets an answer. “What is the bream like?” gets a shrug.
Use the specials briefing properly. This is the one moment the kitchen has already committed to talking about the food, and most floors let it wash over them. One question each turns a two-minute briefing into something worth having.
Spread the asking across several shifts rather than cramming it into one, because distributed practice outperforms massed practice. And taste when you can. Ends of prep, staff meal, a plate that came back for a non-food reason. Servers who eat the food describe it better, and the difference is noticeable.
The situations where honesty is not optional
Most of this is about doing the job well. Two situations are different, because a wrong answer causes harm rather than disappointment.
Allergies and intolerances. Never estimate, never say “I think so”, never reason from the menu description. UK food businesses are legally required to provide allergen information, and in the EU Regulation 1169/2011 sets out which allergens must be declared, so this is a duty rather than a courtesy. If you have not been told by the kitchen for that specific dish today, the only correct answer is that you will find out. Recipes change, suppliers change, and a fryer is shared until someone tells you it is not.
Dietary and religious requirements. The same rule and the same reason. A guest who does not eat pork needs to know about the stock, and that is not a question you can answer by looking at the plate.
There is no version of these where a confident guess is acceptable, and no time pressure that makes it acceptable. Walking to the kitchen takes thirty seconds.
What to do about specials, which are the hardest case
Specials are where untasted description happens most, because they change daily and nobody tastes them in time.
Write them down at the briefing, in your own words, using the seven facts. Learning daily specials is its own small discipline. Not the poetic name, the actual composition.
Ask the one question the briefing skipped, which is almost always what it comes with or how big it is.
Look at the first one that goes out. Ten seconds of watching a plate leave the pass tells you more about size and appearance than any description.
And say “tonight” when you talk about it. “The special tonight is” signals freshness and quietly explains why your knowledge of it is thinner than of the main menu.
| Special-board habit | Why it pays |
|---|---|
| Write the composition, not the name | The name tells the guest nothing |
| Ask what it comes with | The single most-asked follow-up |
| Watch the first plate leave | Size and appearance, in ten seconds |
| Say “tonight” | Frames it as new for everyone |
Talking about a menu you have never seen
Agency shifts, covering another section, a first day with no training: sometimes you are describing a whole menu you met an hour ago.
Triage. Learn the five best-selling dishes properly and know that you do not know the rest. Five is achievable in twenty minutes and covers a surprising proportion of orders.
Be upfront with tables once, early. “It is my first shift here, so I will check anything I am not certain about” buys enormous goodwill and permission to be slow.
Carry the menu. Reading a description to a guest is weak; looking something up in front of them while telling them you want to get it right is fine.
And build the deck that night rather than the next week. The dishes you fumbled today are the ones to put on cards, which is the whole argument for a tool that turns a menu photo into cards in a couple of minutes rather than an evening.
The habit that removes the problem over time
Keep a running list of dishes you have described but not tasted, and work through it.
It is a short list on most menus, it shrinks quickly, and it converts the single weakest part of your service into your strongest. Servers who have eaten the menu sound different, and guests can hear it even when they could not say why.
Until then, describe accurately, attribute honestly, and go and ask when it matters. That is not a compromise, it is what good service looks like when the information is incomplete.
What managers can do about it
The floor-level version of this problem is mostly created upstairs, and it is cheap to fix.
Run a tasting when the menu changes, even a partial one, and run it in the format described in how to run a menu tasting staff remember. A single spoon of each sauce at the pass, five minutes before service, changes how the whole floor talks about the food for the next three months. Nothing on this list has a better return.
Write the specials down. Verbally announced specials produce a floor that half-remembers them, which is exactly the untasted-and-undescribed worst case.
Give new starters the seven facts in writing rather than the menu. The menu is marketing copy; the seven facts are what tables ask about, and handing them over on day one removes weeks of guessing.
Make it safe to say “I will check”. Floors where servers get visibly irritated for asking the kitchen a question are floors where servers guess about allergens, and that is a genuinely serious outcome rather than a service one.
A short script to keep in your pocket
Three sentences cover almost every version of this.
For a taste question: “I have not had it yet, and I can tell you what is in it.”
For an evaluation question: “The kitchen is pleased with that one, and it has been going out all evening.”
For anything that touches safety: “Let me confirm that with the kitchen rather than guess.”
Said calmly, none of these sound like an apology, which is the difference between honesty reading as competence and honesty reading as inexperience.
Frequently asked questions
What should I say if a guest asks about a dish I have not tried?
Describe it factually, attribute any evaluation to someone who has tasted it, and offer to check with the kitchen. “I have not had it myself, it is the sea bream with a salsa verde and it comes on its own, and it has been going out all night” is more useful than a confident guess, and guests trust it more.
Is it unprofessional to admit you have not tasted a dish?
No, and it reads as honest rather than unprepared when it comes with real information. Large menus, daily specials and agency shifts make untasted dishes normal. The unprofessional version is the bluff that falls apart at the follow-up question, or the flat “I do not know” with nothing after it.
What can I tell a guest without having eaten the dish?
Seven things: what is in it, how it is cooked, how big it is relative to other dishes, what it comes with, its flavour direction, allergen information from the kitchen, and preparation time if it is unusual. Together those answer nearly every question a table asks, and none of them need personal experience.
Can I guess at allergen information if I am fairly sure?
Never. If the kitchen has not confirmed it for that dish today, the only correct answer is that you will find out. Recipes and suppliers change without the floor being told, and a fryer is shared until someone says otherwise. Walking to the kitchen takes thirty seconds and removes the only real risk in this whole topic.
How do I learn a new menu quickly when I cannot taste everything?
Ask the kitchen in batches rather than one dish at a time, ask specific questions, use the specials briefing to ask one real question, and put the seven facts on cards so they are drilled rather than re-read. Then keep a list of dishes you have described but not tasted and work through it over the following weeks.
