Turn Guest Questions into Better Menu Descriptions

Listen for the same uncertainty

Guest questions can reveal where a menu leaves an important detail unstated. “Does that come with rice?” points to a different problem from “Where are the drinks?” The first may need an item-description change; the second may need a clearer category label. Start by capturing the question before deciding on a solution.

Use this as a lightweight editorial routine, not a reason to record every conversation. A brief note of the item, the question, and the service context is enough for a wording review. Guest names, contact details, and personal stories are not needed to understand whether a dish description is unclear.

Keep a short question log

Ask staff to write down repeated points of confusion after service while the details are fresh. Preserve the substance of the question in plain language. “Guests confused” gives an editor little to work with, while “Asked whether the small plate includes two or four pieces” identifies a specific missing detail.

Group similar questions before editing. Several versions of a portion-size question may call for one consistent serving-unit convention across a category. Keep one-off preferences separate from facts that the menu should explain, and confirm the underlying answer with the kitchen or service lead.

Fix the smallest useful piece of text

Choose one recurring question and edit the relevant name, description, or heading. If the issue is portion size, add the portion rather than expanding the whole dish into a story. If the issue is an ambiguous category, try a familiar label before reorganizing the entire menu.

For example, “House dumplings” might become “House dumplings · six pieces” when that quantity is confirmed. This sample illustrates a writing choice, not a standard portion. Check that the new text still fits beside the correct price and does not contradict a size option elsewhere on the page.

W3C’s writing guidance recommends clear headings, meaningful link text, and concise instructions. Apply those principles to the menu so its labels and next steps describe what guests can actually find or do.

• W3C: Writing for Web Accessibility ↗

Review the change wherever the item appears

Compare the proposed wording with the approved recipe and service offer. Then check other copies of the dish, such as lunch, dinner, and takeaway menus. Some differences may be intentional, but they should be explicit enough for the next editor to understand.

If the restaurant publishes translations, have the changed wording reviewed in those versions too. A new quantity or included side should not remain only in the original language. Publish the approved update and open the guest-facing page to check the actual result, including long names on a smaller screen.

Ask whether the question became easier to answer

After several comparable services, ask staff whether the same uncertainty still comes up and whether they can point guests to a clear answer on the menu. Treat their observations as local feedback. A quiet shift alone cannot establish that a wording change improved ordering or sales.

Keep a brief note of what changed and why. If the question persists, inspect the placement and category context before adding more text. Work through the next issue with the same routine: listen, verify the answer, edit, publish, and review. Small corrections can keep the menu aligned with the questions your own guests actually ask.

1. Record the recurring question without guest details.
2. Confirm the answer with the responsible team.
3. Edit the relevant text and review translated copies.
4. Publish and check the public page.
5. Review the same question after comparable services.

• Write descriptions that help guests decide
• Review multilingual menus