You order the tasting menu on a Tuesday, the place is half empty, and the dish arrives with a smear of brown on the plate and a name you don't recognise. It tastes like nothing. Not bad — nothing. That's the moment a menu stops being a list of options and becomes a document you can read for clues, and it's the skill I picked up slowly, badly, and mostly by wasting money.
Because there is a way to read a restaurant menu like a food critic. It has nothing to do with knowing what beurre blanc means. It's about spotting what a kitchen is hiding, what it's proud of, and what someone in the office decided to put there for reasons that have nothing to do with flavour. I'll show you the exact habits I use now, including the one that made me stop ordering the steak, and the failures that taught me to.
Key takeaways
- Read the menu as a system, not a list: sections, price spread, and repetition of ingredients tell you more than any single dish description.
- The 30/30/30 rule is a rough spread for ordering (30% starters, 30% mains, 30% desserts — I'll explain why I bend it) and, in a separate sense, a benchmark for how a menu's price and margin structure sits.
- Critics don't rate dishes in isolation. They score execution, seasoning, balance, technique, value, and consistency — and consistency is the one that separates a good kitchen from a lucky one.
- You can memorise a whole carte in about 90 seconds by learning its architecture first.
- Anything described with two adjectives and no technique is probably the worst-value item on the page.
How to read a restaurant menu without getting played
Start with the shape of the thing. Before you read a single dish, count the sections. Twelve starters and four mains is a warning: a kitchen set up for small plates and volume, which usually means prep-heavy, à la minute-light cooking. Four starters and twelve mains is the opposite, and usually a good sign for the mains.
Now look at the price spread. If every main sits between £18 and £22, the menu has been engineered to remove decisions — a technique that works on you whether you notice it or not. A menu where prices jump from £14 to £38 is telling you something honest: this kitchen has a cheap dish it can execute blind, and an expensive one it actually cares about.
What to read before you read the dishes
The small print at the bottom. "Please inform staff of allergies" is boilerplate. "Vegetarian and vegan options available on request" means the vegetarian dish is a negotiation, not a recipe. And a service charge printed at 15% for parties of two is a menu telling you what it thinks of you.
The description test
Here's my rule, and I'll defend it stubbornly: a dish described with technique is cooked; a dish described with adjectives is bought. "Slow-cooked beef short rib, bone marrow crumb, pickled walnut" tells you someone stood at a pass for six hours. "Succulent, tender, premium beef" tells you the marketing department wrote it.
- "Confit", "cured", "fermented", "charred", "braised", "hanging" — verbs that cost labour.
- "Succulent", "premium", "artisan", "fresh", "local" — words that cost nothing.
- A dish with four named components is usually a dish with a point of view.
- A dish with one component and two adjectives is usually a reheated profit centre.
- Unspecified "seasonal vegetables" — ask which ones. If the server can't answer, that's your answer.
I once ordered a "hand-dived scallop" at a place in Bristol that charged £17 for one piece of shellfish. It arrived grey. I asked the server when they'd last had the diver in, joking. She didn't laugh. That was £17 for a very clear lesson: the more precisely a menu names its sourcing, the more you're allowed to interrogate it.
What is the 30/30/30 rule for restaurants?
Honestly, I went looking for a formal version of this and couldn't find one that held up. What I can tell you is how it's actually used in the trade, in two distinct senses that get muddled together.
The ordering interpretation
Roughly: spend your order 30% on starters, 30% on mains, 30% on dessert and drinks, keeping 10% as slack for the thing you didn't plan. The logic is that a kitchen signals its ambition in the first course, its competence in the main, and its pastry section at the end. Skip the starters and you miss the part where a chef shows off. Skip dessert and you miss the only section where you can tell whether the kitchen has a dedicated pastry chef or buys in.
Where I break it: if a menu has eight starters and three mains, invert it. Small-plates kitchens are built around the top of the page. Ordering a main in that kind of restaurant is like asking a fishmonger for a steak.
The margin interpretation
In menu engineering, the same numbers show up in a different sense — the rough split of a restaurant's sales and margin across starter, main, and dessert-plus-drinks. Desserts and drinks carry the highest margin by a comfortable distance. Starters sit in the middle. Mains are the expensive, low-margin, high-effort part of the evening.
That single fact explains almost every strange thing about a menu. It's why the steak is on there even though nobody in the kitchen seems to enjoy cooking it. It's why the dessert list is written in a more lyrical style than the mains. It's why you're asked about sides. The menu is a profit document with recipes attached.
How do food critics rate restaurants?
The star hides a grid. When I write up a meal, I'm not scoring "did I enjoy it" — I'm scoring six things independently, then weighing them.
| Criterion | What I'm actually checking | Weight in my notes |
|---|---|---|
| Technique | Is the cooking method appropriate and controlled? Is a sauce reduced or thickened? | 25% |
| Seasoning | Under, over, or right. Can I taste salt and acid in balance? | 20% |
| Balance | Does the plate need something removed, not added? | 15% |
| Consistency | Would this dish taste the same at 9pm on a Saturday? | 20% |
| Value | Does the price map to the labour on the plate? | 10% |
| Menu coherence | Does the carte agree with itself, and with the season? | 10% |
Consistency carries a fifth of the score, and that surprises people. A single brilliant plate is easy. A restaurant that produces it forty times a night, on a Friday, with a new commis on the section — that's the hard part. When I return to a place I praised and the dish has drifted, the score drops hard, because the first visit was luck slightly more than skill.
Value is only 10% for me, which is a deliberate choice and one a lot of readers disagree with. I'd rather eat a £9 dish that punches above its price than a £40 dish that's merely correct. But I've also scored places down heavily for a £14 side of chips that arrived cold.
What is the best way to memorise a restaurant menu?
Don't memorise dishes. Memorise the architecture. You can hold an entire carte in your head for a dinner if you store it as a structure rather than a list, and it takes about a minute and a half.
- Count sections, left to right. Snacks, starters, mains, sides, desserts. Five chunks.
- Find the outlier in each section. The one dish that doesn't fit the price band or the ingredient pattern. That's the anchor — everything else is a variation on it.
- Note the repeated ingredient. If celeriac appears three times, the kitchen bought a lot of celeriac. That's a freshness signal and a creativity constraint.
- Read the desserts first, then the mains. Backwards reading breaks the marketing spell; you'll notice the mains are thinner than you thought.
- Close it. If you can't recall three dishes without looking, you haven't read it — you've scanned it. That's fine, but be honest about it.
I'll admit the first time I tried this, I forgot everything the moment the bread arrived. It took maybe a dozen meals before the structure stuck. Now I can usually reorder the whole menu in my head a day later, which is a party trick of almost no social value and enormous practical value when someone asks me where to eat.
The trick I still use
I read the menu before I sit down. Most restaurants post it online now, and reading it in a quiet room with no waiter hovering is worth more than any amount of live scanning. It also means I can look up the two ingredients I don't recognise instead of nodding along.
The signals that are wrong (and why I stopped trusting them)
For a few years I followed the classic advice to the letter. Soup as a signal: order it, because no one puts soup on a menu unless they believe in it. Specials board as a signal: always order from it, because that's where the chef is cooking what they actually want to cook.
Both are half-true and I've been burned by both. I once ordered a soup that turned out to be yesterday's roast blended with stock. Excellent, actually — but a signal of resourcefulness, not of ambition. And I've ordered from specials boards that existed purely to move produce bought too cheaply on a Monday.
The reliable signals, in my experience:
- Fewer than 25 dishes total. Anything above that and the kitchen is a logistics operation.
- Bread. Bought-in bread is the single most common tell in mid-range restaurants. If it arrives cold or in a plastic basket, lower your expectations for the rest.
- A sauce mentioned by name. "Sauce grenobloise" is a chef talking to other chefs. "House sauce" is a vat.
- Ask the server one specific question. "How's the hake cooked?" If they answer without hesitation and with detail, they've been briefed, which means the kitchen cares. If they go and ask, that's not a failure — but if they come back with a shrug, order the vegetarian.
And the thing nobody warns you about: a menu that's been laminated and reprinted weekly is often better than a beautiful letterpress one, because someone is paying attention to what's actually in the fridge.
What reading a menu properly actually changes
The point isn't to become insufferable at dinner. It's to stop paying for the wrong things. Since I started reading menus this way I order fewer dishes, spend roughly the same, and eat considerably better — and the strikes have dropped to something like one in fifteen meals, down from a stretch where I'd get two bad dinners in a month.
But the thing that stays with me isn't the hit rate. It's how much more visible a kitchen becomes once you know where to look. A menu is one of the few documents a restaurant writes honestly, whether it wants to or not: the price spread, the ingredient repetition, the adjectives where a technique should be. You can read all of it in two minutes at the table. The only question left is whether you want to know before or after the plate arrives.
