How to write a shorter, more useful restaurant menu

Start with the decisions guests make

Guests rarely read a menu as a detailed inventory. They scan for a familiar category, compare a handful of options and decide whether the price and description feel right. A clear structure respects that process.

Group dishes by how people order, not by how the kitchen stores ingredients. Familiar headings and an intentional order help diners navigate quickly without asking the server to translate the menu.

Describe what matters

A useful description should answer the most important questions: what is it, what does it taste like, and what makes it distinctive? Start with the main ingredient and technique. Add one or two details that help a guest imagine the dish.

Avoid overlong adjectives that make every dish sound identical. State allergens and dietary information accurately and give staff a consistent method for answering follow-up questions.

• Lead with the dish rather than a slogan
• Use the same naming style across categories
• Check descriptions against what is actually served

Edit with the kitchen in mind

A very broad menu creates extra prep, storage and training requirements. Look for ingredients shared across several dishes without making the menu repetitive. Removing a weak seller can create capacity for a better special.

Review guest feedback alongside food cost, prep time and waste. The best menu is not necessarily the one with the fewest dishes; it is the one the team can deliver consistently.

Keep the printed and digital versions aligned

Prices, available items and opening hours should match across the menu on the table and the information online. When a seasonal item changes, update every public version in the same workflow.

Use readable type, strong contrast and enough spacing. QR menus can be a useful option, but they should not be the only way guests can understand what is available.