Guests browsing a menu need to know what a dish is, its main ingredients, how it is prepared, and what comes with it. Add portion context when it helps them choose, and give them a clear way to ask about ingredients and allergies. A good description answers the obvious questions without making the guest read a recipe.
Start with the dish as the kitchen actually serves it. Then check that the name, description, and photo tell the same story. The goal is to help someone who has never visited your restaurant decide whether the dish fits their appetite and preferences.
Start with the dish and its portion
Ask the person responsible for the recipe to identify the main component, preparation method, prominent ingredients, sauce, and included sides. A line cook or kitchen manager can explain what is normally on the plate; the person who manages the menu can turn that information into guest-friendly words.
Include details that change a guest’s expectations. “Grilled chicken with rice” gives a starting point. “Grilled chicken over rice with roasted peppers and lemon sauce” explains more of the meal. If the sauce is spicy, creamy, or served separately, say so when that detail matters to the dish.
Portion context does not have to mean a weight. A description can say that a dish is served as a bowl, a sandwich, or a plate with two sides. For a shareable item, explain what is included rather than promising that it feeds a particular number of people. Appetites vary.
Be specific about included components. “Served with fries” tells a guest more than “with sides.” If a dish comes with a choice, describe the choice only if it is part of the actual offer. The ordering screen should then make any required selection clear; the description should not substitute for it.
A practical description template
Dish name: A recognizable name, with a distinguishing word if needed.
Description: Main ingredient or dish + preparation + notable ingredients or sauce + what is included + useful portion context.
Use the parts that help a guest choose. A simple side of rice may need only a few words; a house specialty with an unfamiliar name may need more explanation. Leave out an ingredient or preparation claim if staff cannot confirm it for the version currently served.
Choose names and details guests can understand
Put the familiar name first when a house name does not explain the food. “Market Bowl” might mean almost anything to a new guest. “Roasted vegetable rice bowl” gives them a category before the description supplies the details. You can still keep a distinctive house name alongside the plain-language name.
Use the same terms across your menu. If the kitchen calls a sauce “lemon yogurt sauce,” avoid calling it “white sauce” on one dish and “house dressing” on another unless those are genuinely different preparations. Consistent wording helps guests compare dishes and gives staff fewer discrepancies to explain.
Choose descriptive words over vague praise. “Crispy,” “smoky,” and “tangy” can be useful when they accurately describe the food. “Delicious” and “amazing” do not tell a guest what to expect. Likewise, explain an unfamiliar preparation in a few everyday words rather than removing the name that gives the dish its identity.
The following is a hypothetical example for a restaurant reviewing a vegetable bowl. Assume the kitchen confirms every component shown in the revised copy.
| Version | Menu copy | What a guest learns |
|---|---|---|
| Before | Garden Bowl: A delicious house favorite. | Very little about the food or portion. |
| After | Roasted Vegetable Rice Bowl: Roasted carrots and peppers over rice, finished with lemon yogurt sauce. | The main ingredients, preparation, format, and sauce. |
The revised version is longer, but each detail does a job. It does not claim the bowl is suitable for a particular diet, promise a serving size, or list optional additions as included. If the restaurant also serves it with a side, that should be added after staff confirm it.
Read descriptions on a phone as well as a large screen. A guest should be able to scan the name and identify the dish without opening several pages. Keep important facts near the beginning, especially when the menu display might shorten longer text. Check the actual display rather than assuming every device shows the same amount.
Review ingredient and allergy statements with staff
Descriptions are useful summaries, not complete ingredient records. A sauce, marinade, garnish, or purchased component can contain ingredients that are not obvious from its name. Before making an ingredient or dietary statement, ask the kitchen lead to check the current recipe and relevant supplier information.
Set a clear route for questions. For example, include a brief note near the menu asking guests with allergies to contact the restaurant before ordering. Make sure the team knows who should answer and how to find current information. Staff should not guess when they are unsure; they can check with the kitchen or explain that they cannot confirm an answer.
Be especially careful with broad labels such as “dairy-free” or “gluten-free.” Ask what ingredients and preparation practices the statement covers, and who can verify it. If the team cannot support the wording, use an accurate description of the dish and invite the guest to ask. A short menu description cannot account for every guest’s needs or every preparation circumstance.
Use a simulated question during a staff review: “Does the sauce on the vegetable bowl contain dairy?” In the hypothetical bowl above, the description identifies yogurt sauce, so staff should recognize that the question needs attention. The exercise checks whether the team knows where to look and whom to ask; it does not verify the current recipe or establish that the dish is safe for a particular guest.
Do this as an internal practice conversation. Do not send a guest message or place a real order for the exercise. Separately, confirm that the contact details on the live menu reach the right team and that someone is responsible for keeping them current.
Keep the menu accurate as recipes change
A description can become wrong even when the dish name stays the same. A new supplier, a different sauce, a missing garnish, or a change from a side included to a side sold separately can alter what the guest expects. Give one person responsibility for publishing menu changes, and make the kitchen responsible for supplying the details.
Before a changed dish goes live, compare the recipe, the description, the price, any photo, and the ordering choices. Check both the browsing menu and the ordering page if they are maintained separately. A guest should not see one set of included sides on your restaurant website and another after opening online ordering.
For a temporary substitution, decide whether you can update the description promptly or whether the dish should be unavailable until the listed version returns. Tell front-of-house and order-handling staff what changed so they can answer questions consistently. When the regular recipe returns, update the copy again rather than assuming someone will remember.
Menu description review checklist
- Name: Can a new guest recognize the dish or understand it from the description?
- Food: Are the main ingredients, preparation, sauce, and included sides accurate?
- Portion context: Does the copy explain the format or included items without making unsupported serving promises?
- Consistency: Do the description, photo, price, and ordering choices match the current offer?
- Ingredient questions: Does staff know where to find current recipe and supplier details, and whom to ask?
- Display: Is the important information readable on a phone and wherever guests browse the menu?
- Ownership: Does someone know who approves changes and who publishes them?
Use the checklist on a handful of dishes first, including a simple item and one with a sauce or several components. Ask a staff member who did not write the copy to explain what each dish includes. Their questions can reveal gaps before you apply the same review to the rest of the menu.
Next, check whether your current setup lets the right person make timely menu edits. If you are considering a change, use the restaurant website builder comparison to frame your questions, then ask Fleksa about its website setup and verified US availability.
Frequently asked questions
How long should a menu description be?
Make it long enough to explain the dish and short enough to scan. One sentence is often sufficient, but an unfamiliar preparation or several included components may need more detail.
Should every ingredient appear in the description?
Not necessarily. List the main and notable ingredients, and make it easy for guests to ask about others. Keep current recipe and supplier information available to staff rather than treating the description as a complete ingredient record.
What should I do when a dish changes temporarily?
Update the menu and tell staff when practical. If you cannot accurately present the temporary version, consider making the dish unavailable until the listed version returns. Check the description again when the regular preparation is back.
