Who approves menu changes? Clear roles for small teams
Define who prepares, verifies and publishes menu changes, with a sample responsibility table and a practical urgent-update process for small restaurant teams.
A menu mistake does not always come from carelessness. The person preparing the draft may think a price has been approved, while the manager expects only the product name to change. Making publication clear does not require a large corporate structure. A useful starting point is to decide who supplies information, who checks it and who closes the task for each kind of change.
Contents
Do not put every edit through the same approval queue
Correcting a typo and changing every coffee price do not need the same review. Start by listing your common changes: prices, product information, photos, category order and availability. Then assign an information owner and a publishing owner to each. Reducing unnecessary decisions does not remove checks; it ensures the right person reviews the right information.
For example, the chef can verify an accompaniment in a product description but may not be authorized to decide the price alone. A social media manager can prepare a photo but should ask the kitchen whether the pictured presentation is actually used today. Writing down these distinctions means the menu editor does not have to guess every business decision. Consider the user permissions available in your current tool in light of these responsibilities.
Create a one-page responsibility table
Listing roles before names makes shift changes easier. In a small team, one person can hold two roles, with the person assigned that day recorded separately. Approval records should include the old value, the new value and the time it takes effect. A message saying only fine or done does not identify the approved version when several changes are being discussed at once.
Do not build this table on the assumption that Orvunai has an automatic approval engine. Design a working arrangement that can also be managed through your existing communication tool or a shared note. Menu permissions may help separate responsibilities, but kitchen verification and records of commercial decisions remain part of the business's own process. A simple example could look like this.
| Change | Information verifier | Post-publication check |
|---|---|---|
| Price | Business manager | Shift supervisor opening the menu |
| Product description | Kitchen supervisor | A member of the service team |
| Photo | Team member familiar with the presentation | Person checking the phone view |
Keep an urgent route short and traceable
A long approval chain is unhelpful when a product sells out during service. Designate an authorized person for these situations in advance, along with a backup if that person cannot be reached. Keep the urgent route narrow: availability changes or clear typos, for example. Quietly using the same route for decisions that change pricing policy creates uncertainty within the team.
The record completed after an urgent edit should also be brief. The product, reason, information source and publication time may be enough. The next shift can read it and check whether the temporary change should continue. This lets you work quickly without leaving behind a menu change that accidentally becomes permanent the following day.
Separate approval from correct publication
Approval does not prove that a change was published correctly. As a final step, a different team member should open the guest link where possible and compare the changed fields with the approval record. State the scope of that check: someone verifying a product price should not be assumed to have checked every menu translation too. A record of what was reviewed makes later checks more reliable.
During the first two weeks, watch where the process waits. If every small edit accumulates with one manager, clarify authority for some low-impact tasks. If errors usually come from missing product information, improve the request form instead of adding another approval layer. A good publishing process aims to complete the right information at the right time, rather than gather the largest possible number of signatures.
Explore the relevant Orvunai product guide to put these steps into practice with your own menu.
Explore QR code menus for restaurants and cafés