A menu description should help a guest decide what to order without asking them to decode a kitchen shorthand or trust an unverified claim. Start with the dish, add only facts the restaurant can confirm, and keep every other decision in a field that clearly names what it changes.
This is narrower than a full restaurant digital menu audit, which checks the whole public route. It is also different from the digital menu modifier guide, which explains choices attached to an item. Here, the task is the sentence that tells a guest what the item itself is.
Write for the decision the guest must make
An item description does not need to tell the dish’s whole story. It needs to give a guest enough accurate context to decide whether the item is relevant to them before service begins.
| Guest question | A useful description can say | A description should not assume |
|---|---|---|
| What is this? | The dish name and the main prepared item | That a photo or internal shorthand explains it |
| What am I getting? | Confirmed ingredients, preparation, or serving cues | An ingredient, garnish, or method the kitchen did not confirm |
| Is this the version I want? | A clear distinction from a similarly named dish | That an option, side, or substitution is included without saying so |
| Can I have it now? | A current, confirmed service or availability condition | That an old menu, message, or memory is still current |
For example, “charred chicken with lemon rice and herb sauce” tells a guest more than “house favourite.” The first phrase can be checked against the approved item source. The second asks the guest to infer a promise that may mean something different to the kitchen, server, and guest.
Draft from one approved source, not from memory
Choose the source before anyone edits the public menu. It may be a chef-approved menu, a current recipe brief, or a named kitchen lead who confirms the published facts. The source does not need to become public; it needs to give the team one answer when a description is questioned.
Use this short drafting card for every new or revised item:
- Write the approved item name as the guest will see it.
- List the confirmed ingredients and preparation details that affect the choice.
- Mark the service period, location, or condition only when it changes what is available.
- Name the person who resolves a question the description cannot answer.
- Open the public page after publishing and compare it with the approved source.
The digital menu launch checklist turns that last step into a repeatable pre-service release. The mini-site content checklist helps when the item sits beside hours, location, or a waitlist action on the same public route.
Keep descriptions, choices, and changes in separate places
One long sentence often becomes unclear because it is trying to do several jobs at once. Keep the item description focused on the item, then give each different decision a visible home.
| Information | Put it where a guest can find it | Do not hide it as |
|---|---|---|
| What the dish is | Item name and description | A photo caption or internal category name |
| What changes the item | A clearly named option or modifier | A vague phrase such as “customize” |
| What changes a published amount | The relevant current price field | An unexplained adjective in the description |
| What is unavailable | A clear current availability note | A faded image, old chat, or staff guess |
| What needs kitchen confirmation | An explicit escalation path | A blanket assurance in the copy |
If a guest needs to choose a side, size, add-on, or exclusion, use the digital menu modifier guide to make that choice understandable before the guest asks. If the item cannot be served, move it through the restaurant’s current unavailable-item process rather than leaving a description that suggests it is still available.
Remove language the team cannot verify
Words such as “local,” “house-made,” “signature,” “allergen-safe,” or “best” can be meaningful, but only when the restaurant has decided what the phrase means and can support it for the published item. A guest-facing menu is not the place to turn a rough kitchen note into a claim.
The FTC’s advertising and marketing guidance is an official starting point for reviewing public claims in the United States. This is an operating guide, not legal advice. Use the rules that apply to the restaurant and ask qualified advice before adopting a legal or marketing policy.
When a detail is uncertain, choose one of three actions: confirm it with the owner, remove it until it is confirmed, or state the boundary plainly. “Please ask the service team to confirm today’s preparation” is more useful than an unverified ingredient list presented as final.
Make the description readable on the guest’s route
A correct description is still hard to use if it depends on tiny text, colour alone, a cryptic icon, or a link that makes no sense away from its surrounding paragraph. Read the item on an ordinary phone, from the same QR code or link a guest uses, before the service begins.
The W3C writing tips recommend clear headings, short sentences, and links that make sense on their own. Apply that standard to menu names and notes as well. The digital menu accessibility guide covers the broader guest path, including a route that does not depend on scanning a QR code.
Ask a simple test question: can a guest explain what the item is, what changes it, and where to get a confirmed answer without relying on staff memory? If not, rewrite the public copy before asking the floor to compensate for it.
Give the next shift one current answer
Record the item, what changed, the approved source, the reviewer, and the public page that was checked. Do not put a guest’s name, contact details, or order history into a menu-content note. The goal is an accurate public description, not a record of a guest interaction.
According to StoveOps’ public product reference, a restaurant’s public mini-site can carry a digital menu alongside a waitlist form, and the software works beside the restaurant’s existing POS or checkout stack. The restaurant still owns the content decision. Review the public route on the restaurant digital menu software page before making it part of the next service.
Five checks before publishing an item description
- The name tells the guest what the dish is before a decorative phrase does.
- Every ingredient and preparation detail comes from a current approved source.
- Options, amounts, availability, and escalation paths are visible in their own fields.
- A guest can read the item and understand the next step on a phone.
- The next shift knows who can confirm a disputed detail.
The best description is not the longest one. It is the one the kitchen, floor, and guest can read the same way when the restaurant is busy.