Restaurant Menu Change Checklist
5.0/5 with 1 votes
Table of Contents
Introduction
Use this checklist when adding dishes, changing prices or replacing a menu. Keep one approved source of truth and verify every place guests or staff see the menu.
Saving a product edit does not prove it reached every ordering channel. Plan the release, test the actual combinations and inspect the live result after the authorized change.
Have responsible food-service staff verify current recipes, ingredients and allergen information before release. Use approved test methods without an unauthorized live charge.
List is the default for work shared across kitchen, service and channel owners; Play is available for a guided pass. Dedicated answers capture the menu version, sites, effective time, approved sources and release decision. Editable POS, printed-menu, website and external-ordering checks each record the actual live result and evidence.
Prefer guided mode? Try Play - answer one question at a time in full screen view.
Establish a version that every team can use.
Use one approved version/reference for this change; keep the prior version available for the agreed recovery process.
Name the restaurants/sites included. Create separate channel checks where versions or timing differ.
State the operating timezone in run notes.
Name the person authorized to approve this exact version and handle restrictions or rollback.
Use a document/version ID or approved link containing the changed dishes, descriptions, prices, sizes and modifiers.
Compare every changed item, size, modifier and price against the commercial source record. Record approval and unresolved questions.
Have the responsible food-service person approve current information from recipes/suppliers. Keep the approved reference and prohibit guesses or unsupported claims.
Check required ingredients, supplier timing, preparation capacity, serviceware and station instructions. Record unavailable dishes or substitutions for decision.
Record who can restrict an affected item/channel and the approved route to restore the prior version. Do this before changing customer-visible menus.
Use the same approved version everywhere.
Explain the changed dishes, preparation/portion instructions, prices, modifiers and availability. Give staff the approved information and a question/escalation route.
Configure changes in the approved environment/process. Check item identities, variants/modifiers, availability and kitchen/bar destinations.
Compare changed menus and signs with the approved names, descriptions, prices and terms. Coordinate installation with the effective release time and identify the copies to retire.
Have the authorized owner update the restaurant’s website and other directly managed menu displays. Check the saved version and release timing; retain a channel-specific verification task.
STARTER CHANNEL: Rename to an actual ordering provider/site and duplicate for each independently managed external channel; remove if unused. Follow its actual sync, scheduling and publication requirements through the approved release process. Identify the owner and whether the update is prepared, scheduled or already authorized to go live. Use the matching live-verification starter below after release.
Test the customer choice and the operational result.
STARTER CASES: Tailor the four visible cases to actual changed dishes and approved expected prices. Rename, duplicate or remove irrelevant cases before use; record each actual case independently. Use only the permitted test process without an unauthorized live charge.
Rename to one actual changed dish/site/channel. Record the approved dish/version, expected base price, actual item description/total and permitted test-order evidence. Record a mismatch as its own correction task. Duplicate for independently tested changed dishes.
Rename to an actual dish and priced modifier, or remove if none changed. Record the selected modifier, approved price increment/total, actual displayed/charged test total and order evidence. Check that the option remains attached to the dish; verify kitchen/bar routing in the routing task.
Rename to an actual removed or unavailable dish and channel, or remove if not in scope. Record the expected visibility/order restriction and what the customer could actually select. Confirm no unintended order is accepted through the approved test route; capture evidence and any correction owner.
Optional starter: rename to an actual changed size/bundle and channel, or remove if unsupported/out of scope. Record included choices, approved price/total, actual order contents and permitted test evidence. Duplicate where combinations need independent results.
Check the actual ticket/display or approved test evidence. Confirm staff receive the correct dish, modifiers and relevant preparation notes.
Give the authorized owner the approved version, food-information checks, staff briefing and test evidence. Record approval or a hold for that exact version and effective time.
Record the actual decision-maker, decision time/timezone, approved version and conditions/reference. A completed decision observation does not publish the menu or resolve a hold.
STARTER CHANNELS: Rename, duplicate or remove the channel groups before use. Give each real channel/site a separate owner and result. Verify only after the authorized release. Record the version, time and evidence in each evidence task. Any mismatch gets a separate correction task; recording a failed observation does not close the correction.
STARTER EXAMPLE: Compare the actual sellable dishes, sizes, prices, modifiers and availability with the approved version. Check that the selected items route to the intended kitchen/bar destination through the approved test process.
Record the actual channel/site, version seen, check time and evidence/reference. State any mismatch and the separate correction owner/task; do not prefill a pass.
STARTER EXAMPLE: Check the actual installed menu/sign at the named site, including dish names, prices, terms and effective version. Confirm superseded copies have been removed through the approved process.
Record the actual channel/site, version seen, check time and evidence/reference. State any mismatch and the separate correction owner/task; do not prefill a pass.
STARTER EXAMPLE: Check the customer-facing website/menu URL on the supported view. Compare changed and removed dishes, prices, modifiers and availability; a saved admin edit is not live evidence.
Record the actual channel/site, version seen, check time and evidence/reference. State any mismatch and the separate correction owner/task; do not prefill a pass.
STARTER EXAMPLE: Rename to the actual provider and site or remove if unused. Check the customer-facing listing after its real sync/publication process. Record any platform-specific pricing or availability explicitly approved for this channel.
Record the actual channel/site, version seen, check time and evidence/reference. State any mismatch and the separate correction owner/task; do not prefill a pass.
Remove or archive outdated printed and digital menus through the approved process. Verify that staff and customer channels point to the current approved version; retain the prior version where the change record requires it.
Check initial real orders for the changed dishes, prices, modifiers and kitchen/bar routing without placing an unapproved live charge. Record mismatches, the responsible correction owner and any approved rollback or restriction.
Record the final channel register and staff briefing. Keep unresolved issues owned with next action and an approved correction/rollback decision where needed.
Download or Print this Restaurant Menu Change Checklist
Get a printable version of this checklist in your preferred format: PDF, Word, Excel, or print directly from your browser.
Presented by:
Checklist.com
Stats
Views
14
Views: 14
Uses
0
Uses: 0
Tasks
41
Tasks: 41
Details
Approve the food and commercial details first
The current dish record should identify name, description, price, portion, modifiers and availability. Ingredient, allergen and preparation information must be verified by the responsible food-service staff using current evidence. Do not infer it from a dish name.
Track each channel separately
POS, kitchen displays, printed menus, the website and third-party ordering channels can update differently. Keep a short channel register with the approved version, update owner, verification evidence and any limitation.
Test the order rather than only the menu page
Check selected options, charged price, unavailable-item behavior and the instructions that reach the kitchen or bar. Use the platform’s approved test process without an unauthorized live charge. Prepare a correction or rollback decision if critical information is wrong.
Saving a product edit does not prove it reached every ordering channel. Plan the release, test the actual combinations and inspect the live result after the authorized change.
Who it's for
A menu-change owner coordinates kitchen, service and ordering channels so guests can order the approved dishes at correct prices and staff can produce them reliably.
How to use
- Save a checklist for this release, or tailor a reusable template. Complete menu version, sites, effective time, release owner and approved source fields.
- In List, assign independent preparation work to the kitchen, service and channel owners. Open task details to enter an answer, or use Play for the guided sequence.
- Rename, duplicate or remove the four starter channel groups for every actual site/channel. Give independently verified channels separate owners and evidence.
- Obtain commercial and food-information approval, brief staff, and run permitted tests for changed dishes, modifiers, removed choices and kitchen/bar routing.
- Record the authorized release decision and its dated evidence. After the approved release, check what is actually live in each channel and record its version/time/evidence.
- Treat a mismatch or hold as an observation that creates separate correction work. Review initial orders and keep restrictions and corrections owned until the release owner closes the change.
Restaurant Menu Change Checklist Frequently Asked Questions
Who verifies ingredient and allergen information?
The responsible food-service person must verify it against current recipes and supplier information. This checklist does not generate or certify those facts.
Does saving the POS menu update online ordering?
Not necessarily. Check each platform’s actual sync and publishing process, then verify the customer-facing result in each channel.
What should be tested?
Representative dishes and modifiers, availability, charged totals, receipt descriptions and kitchen/bar routing. Include changed and removed items, not only new dishes.
How do I avoid different prices across channels?
Use one approved menu version and record every affected POS, printed menu, owned website and external ordering channel. Give each an owner and compare its customer-visible items, options and prices with that version. Keep a mismatch open until corrected or explicitly controlled by the release owner.
What if a problem appears after the menu goes live?
Record the affected dish, channel and order evidence, then contact the authorized release owner. Apply the agreed correction, restriction or rollback process and verify the result. Keep ingredient or allergen questions with the responsible food-service person.
Why does this open in List?
Kitchen, service and different menu-channel owners can prepare separate actions in parallel. List keeps those responsibilities visible, and Play provides a guided pass through the answer fields. The phases stay as section headings. Actual live channel checks are separate tasks so one website result cannot stand in for the POS or an external ordering platform.
Rate this Checklist
5 stars
Scores 5.00 with 1 vote