September 16, 2026How to Keep Lunch and Dinner Menus in Sync
Build a practical service-change routine for lunch and dinner menus, with clear hours, shared dishes, and a final public-page check.
Start with the difference between services
A lunch and dinner menu can share a kitchen while making different promises to guests. A sandwich might include a side at lunch, appear alone in the evening, or disappear entirely after the afternoon break. Before editing either menu, write down what actually changes: dishes, portions, included extras, prices, and serving times.
Use that list as the starting point for a service review. Two menus with similar names are easy to confuse when staff are preparing for a busy shift. Give each a plain, recognizable title, then ask the floor team to explain which one a guest should read at each part of the day.
Make service times specific
Put the applicable days and hours where guests can find them before choosing a dish. For example, an illustrative lunch heading might read “Lunch · Monday–Friday · 11:30–14:30.” Use your actual kitchen schedule and confirm whether the end time refers to the last order or the end of service.
Check the awkward moments as well as the ordinary ones. What can someone order at 14:25? Does a weekend service use the weekday lunch menu? If a holiday changes the schedule, assign a person to update the wording and remove that exception afterward. Avoid leaving a temporary note on a permanent menu.
Review shared dishes as a pair
When a dish appears in both menus, compare the two entries side by side. A name change or corrected description may belong in both places, while a lunch-only price should stay with lunch. Do not assume that editing one copy updates the other unless you have checked that behavior in your menu tool.
Keep the review small enough to use during real preparation. A short comparison sheet can show the dish, lunch details, dinner details, and whether the difference is intentional. The reviewer should be able to distinguish a genuine service variation from an accidental mismatch.
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.
| Detail | Question to resolve |
|---|---|
| Portion | Is the serving size the same at lunch and dinner? |
| Included sides | Does each description name what comes with the dish? |
| Price | Is each service price approved? |
| Availability | Can the kitchen serve the dish throughout both periods? |
Give the changeover an owner
Assign the service lead to confirm which menu should be visible or clearly labeled at the changeover. If your setup requires manual publishing, include that step explicitly in the handover. If it supports scheduling, check the configured time zone and test the result before relying on it during service.
Brief staff about changes that affect a conversation at the table. A guest who started reading lunch before the cutoff may still have that page open. Agree on how the team will explain the transition, then make sure the published wording matches that approach.
Check the menu from the dining room
Open the guest-facing link after the change, using the same QR card a guest would scan. Confirm the menu title, service note, one shared dish, and one service-only dish. If multiple menus remain available, make sure their labels let a guest choose without guessing.
After the first few changeovers, review any repeated questions with the team. Correct the specific point of confusion rather than adding a long introduction to every menu. Keep the checklist alongside the shift notes so the next service starts with the same understanding.
- Confirm service hours and the changeover owner.
- Compare shared dishes and intentional price differences.
- Publish the approved menu changes.
- Scan a dining-room QR card and check the public result.