How to review a restaurant

A good restaurant review is a small act of public service — it helps strangers decide where to spend their money and their evening, and it gives restaurants honest feedback they can act on. A bad review (vague, unfair, or written in a rage) helps no one and can do real damage to a small business. Whether you're posting on a review site or writing a proper food write-up, this guide shows you how to be useful, specific and fair. It's the natural companion to our how to choose a restaurant guide — the flip side of reading reviews well is writing them well.

Why good reviews matter

Reviews shape decisions and reputations. For diners, they're a key way to find good places and avoid bad ones. For restaurants — especially independents — they're influential feedback and a major driver of business. That dual impact is exactly why fairness matters: your words affect both the next customer and someone's livelihood. The goal isn't to be nice or harsh; it's to be accurate, specific and balanced.

The four pillars to assess

A complete review weighs four things, judged against what the restaurant is trying to be:

• Food — taste, quality, freshness, execution and portion. Name the dishes and describe them.
• Service — attentiveness, friendliness, accuracy, timing. Did staff make the meal better or worse?
• Atmosphere — comfort, noise, décor, and crucially cleanliness.
• Value — the price relative to what you actually got, for this kind of place.

Be specific, not vague

"It was nice" tells a reader nothing; "the slow-cooked lamb was meltingly tender, though the accompanying polenta was bland" tells them a great deal. Specificity is what makes a review trustworthy and useful:

• Name the dishes you ordered and describe how they tasted.
• Give concrete details — the bread was warm, the wait was 40 minutes, the room was loud.
• Explain your rating rather than just assigning stars.
• Mention standouts and disappointments by name so readers can order around them.

Be fair and balanced

Fairness is the difference between a review that helps and one that misleads:

• Mention both strengths and weaknesses. Almost no meal is all good or all bad; a balanced account is more credible.
• Separate facts from feelings. "The risotto was undercooked" is a fact; "worst meal ever" is an emotion. Lead with facts.
• Give context. A rammed Saturday night differs from a quiet Tuesday; a set lunch isn't the à la carte experience. Tell the reader when and what you visited.
• Note whether issues seemed representative. An off night happens to everyone; flag if something felt like a one-off.

Handling problems honestly

When something goes wrong, the fair and useful path has two steps. First, raise fixable problems at the time — a wrong or cold dish, slow service — politely with staff, giving the restaurant a chance to put it right. A good one usually will, and that's often the end of it. Our restaurant etiquette guide covers how to complain gracefully.

Second, if a genuine problem went unresolved, describe it calmly and factually in your review — what happened, whether you raised it, and how it was handled. That's far more helpful and credible than an angry blanket condemnation, and it respects that a single bad moment shouldn't necessarily erase an otherwise good place.

The etiquette of online reviews

• Review the food and service, not things outside the restaurant's control (the weather, a delivery app, your own mood).
• Don't review a place you didn't actually visit, and don't punish a restaurant for a delivery courier's mistakes.
• Update a review if a problem was later resolved or your next visit was better.
• Be honest but humane — there's a real person and often a small business on the other end.
• Skip the review if you can't be fair — if you went in already determined to dislike it, a review won't be useful.

Frequently asked questions

Mustafa Bilgic

Editor, Arsenal Rest

Mustafa Bilgic writes Arsenal Rest's guides to dining out, etiquette and food culture. Fact-checked against established culinary and public sources. Last reviewed 2026-06-13.