You have been handed a menu with forty dishes and no time, and one of them is going to come back to a table you served. Describing a dish in one clear sentence is the single most useful menu skill there is, and it is a skill rather than a memory feat: a formula plus five minutes per section.
Why the menu’s own description is not enough
Menu copy is written to sell, which makes it the wrong length and the wrong shape for a spoken answer.
It is too long. A guest asking “what is the barramundi like?” wants ten seconds, not the paragraph on the card in front of them.
It is often vague on purpose. “Locally sourced, seasonal accompaniments” tells the guest nothing about what will arrive on the plate, and reading it back to them is worse than useless because they already read it.
And it leaves out what people actually ask: how big is it, how spicy, does it come with anything, can it be made without the cream.
So your job is not to recite. It is to translate the dish into a sentence a hungry person can act on.
The one-sentence formula
Protein or main element, cooking method, the one thing that defines its flavour, and what it comes with. In that order, in one breath.
“Barramundi, pan fried, with a lemon caper butter, on greens.”
“Beef short rib, slow cooked for eight hours, quite rich, with mash.”
“Chickpea and squash curry, medium heat, comes with rice and a flatbread.”
Notice what is missing: adjectives that mean nothing, the chef’s name, the provenance story. Those can follow if the guest is interested, and they should never come first.
Four elements is not an arbitrary cap: short-term memory holds only a small number of items, and a spoken description that exceeds it stops being retained. Notice also that the sentence answers the follow-up questions before they are asked. Size, richness and accompaniment are the three things guests ask about most, and two of them are already in there.
| Element | Example | Why it is in the sentence |
|---|---|---|
| Main element | Barramundi | What they are actually choosing |
| Method | Pan fried | Sets the expectation for texture |
| Defining flavour | Lemon caper butter | The reason to pick it over the others |
| What it comes with | On greens | Prevents the disappointed moment |
Adding the two optional clauses
Two more clauses turn a good description into a useful one, and you add them only when they matter.
Size, when the dish is unusually large or small relative to the rest of the menu. “It is one of the bigger plates” or “it is a starter portion, most people have two”.
A flag, when there is one worth volunteering. Very spicy, quite rich, contains a common allergen, takes twenty-five minutes. Guests appreciate this enormously and almost nobody offers it unprompted.
Both clauses are short and both prevent a specific bad outcome later in the meal, which is why they earn their place while the provenance story does not.
Describing dishes you have not tasted
You can describe accurately without having eaten it, which is what most servers are doing most of the time and rarely admit, and what to say about a dish you have never tasted covers that case in full.
Everything in the formula is factual: what is in it, how it is cooked, what defines it, what it comes with, how big it is. None of that requires personal experience, and all of it is checkable with the kitchen.
Where you need care is evaluation. “It is delicious” from someone who has not tried it is a small lie that guests occasionally catch. “It is our most popular fish” or “the kitchen is proud of that one” are true and do the same work.
If a guest asks directly whether you have had it, say so. Then describe it well, which is the thing they actually needed.
Building your sentences before the shift
This is a twenty-minute exercise once, then five minutes when the menu changes.
Take the menu section by section. For each dish, write the four-part sentence, in your own words, as you would say it out loud. Not the menu description reworded: your sentence.
Say each one aloud once. Sentences that work on paper and fail out loud are common, and the failure is usually length. Repeat the exercise across several days rather than in one sitting, since spaced practice retains far better.
Mark the dishes that need a size or flag clause. Usually a handful per menu.
Then test yourself: cover the menu, name a dish, and say your sentence. That last step is the one that makes it available under pressure, because retrieving an answer beats reviewing it, and it is exactly what a flashcard deck is for. MenuFlashcards turns a photo of the menu into cards, and putting your own one-sentence description on the back is what turns a memorisation aid into a speaking aid.
| Step | Time | Output |
|---|---|---|
| Write a sentence per dish | 15 minutes | Your words, not the menu’s |
| Say each aloud once | 5 minutes | Catches the ones that are too long |
| Mark size and flag clauses | 2 minutes | The handful that need them |
| Self-test with the menu covered | 5 minutes | Available under pressure |
Common mistakes in dish descriptions
Leading with provenance. The farm, the region, the fisherman. All lovely, all after the guest knows what the dish is.
Using kitchen language. Confit, emulsion, gastrique, sous vide. Some guests know these and most do not, and a description that needs explaining has failed at its job. If a term is on the menu, translate it rather than repeating it.
Listing every ingredient. Four elements is the limit for a spoken sentence; beyond that nobody retains any of them.
Evaluating before describing. “It is amazing” tells the guest about you rather than the dish.
And describing the wrong dish. Under pressure, servers reach for the description of a similar item, which is why the self-test with the menu covered matters more than reading the menu again.
What changes with the type of restaurant
Fine dining wants more precision and slightly more length, because the guest is paying for detail and the dishes are more unusual. The formula holds; the flavour clause gets more specific.
Casual and high volume wants shorter still. Three elements, not four, and lead with what the plate looks like when it lands.
Multi-course and tasting menus need a different unit: describe the arc rather than each dish, then a sentence per course as it arrives.
Bars and drinks flip the order: spirit, style, then how it drinks. “Rye, stirred, on the drier side.”
Across all of them the underlying skill is the same, which is having a prepared sentence rather than improvising while a table waits.
Handling the follow-up questions
A good sentence produces a follow-up, which is the point: the guest is now engaged rather than scanning. Four follow-ups cover nearly all of them, and each has a short answer.
“Is it spicy?” Answer on a scale the guest can use rather than your own tolerance. “There is chilli in it, it is warm rather than hot” beats “not really”, which is the answer that produces complaints.
“Is it enough?” Compare rather than assert. “It is about the same size as the risotto” is more useful than “yes”, because the guest has a reference on the same menu.
“Can I have it without the X?” Know which dishes can be modified and which cannot, since a wrong yes here becomes a kitchen problem and a delay. When unsure, say you will check, and check.
“What is in the sauce?” This is often an allergy question in disguise. Answer it precisely or go and find out, and never guess. In the UK, food businesses have a legal duty to provide allergen information, and the allergens every server should know is the practical version of that list.
Describing dishes for guests with restrictions
The one-sentence formula changes shape when the guest has told you about an allergy or a diet, and the change is worth rehearsing separately.
Lead with the restriction rather than the dish. “That one has cream in the sauce, but the sea bass next to it does not” is more useful than a description they then have to rule out.
Be specific about what you do and do not know. “It is made without gluten-containing ingredients, and I should tell you the kitchen is not a separate space” is the honest version, and guests who need it genuinely need it.
And do not improvise substitutions. A dish you think can be made dairy-free is a guess until the kitchen confirms, and the consequence of being wrong here is different in kind from being wrong about portion size.
Keeping descriptions accurate when the menu changes
Menus move: specials rotate, suppliers change, a garnish gets dropped. Descriptions that were accurate last month quietly become wrong, and nobody tells the floor.
Two habits fix most of it. Check the specials board against your own sentences before every shift, since that is where change concentrates. And when a plate looks different from your description as it goes past you, ask, because you have just found a stale card.
The failure mode to avoid is the description that outlives the dish by weeks. Guests notice when what arrives does not match what they were told, and it reads as carelessness rather than as a menu change.
A deck you can edit in seconds helps here more than a printed sheet, which is the practical case for keeping your descriptions somewhere you actually update.
Why this skill transfers
Servers who can describe a dish in one sentence tend to be better at the rest of the job, and it is not a coincidence.
The same compression works on wine, on specials, on explaining a delay, and on handing over a table. The underlying habit is deciding what matters before you open your mouth, which is most of what separates a smooth shift from a scrambling one.
It is also the skill that survives moving restaurants. The menu changes completely and the formula does not, so the second job takes days to learn rather than weeks.
Frequently asked questions
How do you describe a dish to a customer?
Use one sentence with four parts: the main element, the cooking method, the one flavour that defines it, and what it comes with. “Barramundi, pan fried, with a lemon caper butter, on greens.” Add a size or a flag clause only when the dish is unusually large, small, spicy, rich or slow. Skip the provenance story unless the guest asks.
What if I have not tasted the dish?
Describe rather than evaluate. Everything in the formula is factual and checkable with the kitchen, so you can describe a dish accurately without having eaten it. Avoid “it is delicious” from personal experience you do not have; “the kitchen is proud of that one” or “it is our most popular fish” is true and does the same job.
How long should a dish description be?
One breath. Guests asking about a dish want roughly ten seconds, and anything longer stops being useful because they cannot hold it. Four elements is the practical limit for a spoken description, which is why the formula caps at four and treats size and flags as optional extras.
How do I remember descriptions for a large menu?
Write your own sentence for each dish once, say it aloud, then self-test with the menu covered. Writing them is quick; the self-test is what makes them available under pressure. A flashcard deck with your sentence on the back, which MenuFlashcards can build from a photo of the menu, turns this into a five-minute daily drill.
Should I use the chef’s terminology?
Only if it is on the menu and you translate it. Terms like confit, gastrique or emulsion mean nothing to most guests, and a description that needs explaining has failed. Say what the technique produces instead: slow cooked in its own fat, a sharp sauce, a light foam.
