Menu Change Communication & Launch Checklist

Welcome

This checklist helps kitchen, front-of-house, purchasing and marketing teams coordinate menu changes so food quality, service, and profitability stay steady. Use the timeline and role matrix to assign clear owners, adapt timing to your operation size, and record decisions in one shared place.

Quick start

Choose a launch type: Soft pilot (select items, limited hours) or Full rollout (entire menu live). For a first-time or larger change, pilot before full rollout. Communicate decisions 2–8 weeks in advance depending on scale.

Who owns what (roles & responsibilities)

• General Manager (GM) — overall owner, approves launch date, staff schedule, guest communications.
• Executive Chef / Kitchen Manager — final recipe, PLTs, portioning, supplier lead, training for cooks.
• FOH Manager — tasting events, server training, menu knowledge, guest Q&A, upsell scripts.
• Purchasing — supplier orders, lead times, cost changes, substitutions.
• POS Admin — menu item setup, modifiers, routing to printers, pricing, reporting flags.
• Marketing — digital assets, website, social, loyalty messaging, in-house signage.
• Shift Leads / Trainers — run shift-level briefings, coach during service, collect feedback.

Timeline checklist (adapt to your operation)

1. 6–8 weeks before — final concept and costs; supplier availability check; tentative launch window.
2. 4 weeks before — recipe cards completed; costing & target margins reviewed; choose pilot locations or days.
3. 2–3 weeks before — run pilot service or internal tasting; collect feedback; finalize POS codes; begin marketing creative.
4. 1 week before — staff training scheduled; digital assets drafted; supplier orders placed; menu proofs ready.
5. 3 days before — POS changes staged in test environment; printed menus ordered; staff pre-brief; pre-launch inventory check.
6. Launch day — morning huddle; final POS publish; FOH tasting for servers; monitor first service closely.
7. 1–7 days post-launch — daily quick reviews (sales, comps, waste, guest feedback); adjust as needed.
8. 30 days post-launch — full performance review and decision on permanent items.

Training agenda template (1–2 hour session)

• Welcome & launch goals (5 min)
• Menu story and hero items (10 min)
• Recipe walk-through & portion demo (20–30 min) — cooks practice portions and plating
• FOH tasting & selling points (20 min) — servers taste, note allergens, and rehearse upsell lines
• POS navigation & modifier training (15 min)
• Service scenarios & common guest questions (15 min)
• Day-of roles, communication channels, and escalation (10 min)
• Quick quiz or checklist sign-off (optional) — confirm each staff member reviewed key points

FOH tasting script & quick cheat-sheet

Provide each server with a one-page card containing:

• Item name & short description (20–30 words)
• Key allergens & dietary notes
• Recommended pairings and upsell phrasing
• Expected ticket time and any special prep steps to warn guests about
• Suggested modifiers and how they affect price

POS & service setup checklist

• Create/verify item codes and menu categories
• Set pricing, portion size flags, and cost centers
• Map items to proper kitchen printers and prep stations
• Configure modifiers and price impacts
• Test split checks, combos, and delivery/takeout flows
• Publish changes in test environment and run sample orders

Digital asset & external listings checklist

• Updated master menu PDF / print file
• Website menu page updated and mobile-optimized
• Delivery/aggregator menus reviewed and updated
• Google Business Profile description and menu updated
• Social post copy, imagery, and scheduling ready
• Loyalty program/email campaign drafted for launch

Supplier notification (sample email)

Subject: Upcoming menu change — order and availability confirmation

Dear [Supplier name],

We are planning a menu update effective [launch date]. Please confirm availability and lead times for these items: [item list with specs and required quantities]. Let us know any minimum order quantities, potential substitutions, and expected price changes by [response date]. If an item isn’t available, propose alternatives. Thank you — we aim to finalize orders by [order date].

Best, [Purchasing contact]

Day-of launch troubleshooting checklist

• Morning pre-shift huddle: confirm roles, expected covers, and any supply limits
• Keep a single communication channel open (e.g., manager group chat) for rapid issues
• Stock contingency items for high-risk components (backup proteins, sides)
• If an item is running late or out, agree on substitute or temporary unavailability script
• Document every comp, void, or major issue for later review
• Assign one person to monitor online orders and delivery platforms for errors

A/B rollout options and how to choose

Options:

• Soft (A/B) rollout — release a subset of items to select shifts or locations to measure performance, waste, and guest reaction before full rollout.
• Staged hours — new items available during non-peak hours first.
• Full rollout — publish everywhere at once (best when tested and supply is reliable).

Choose an A/B strategy when new dishes have uncertain prep time, supplier risk, or price sensitivity. Measure item sales, ticket times, comps, and waste during the test. Define success thresholds in advance (e.g., item keeps 70% of forecasted margins and <5% comp rate).

Post-launch monitoring & KPIs

• Item-level sales and contribution margin (daily for first week, then weekly)
• Number and reason for comps/voids by item
• Average ticket time and any changes during busy periods
• Food waste related to new items (overproduction, spoilage)
• Guest feedback & online reviews mentioning new items
• Inventory variance on high-use SKUs

Schedule quick stand-ups: daily for 3 days post-launch, then twice-weekly for the remainder of week 1. Do a full 30-day review to decide on permanent placement.

Templates & annexes

• One-page FOH cheat-sheet template (copy and adapt)
• Recipe card template with cost-per-portion and allergen table
• POS publish checklist (printable)
• Supplier email template (above)
• Post-launch incident log (date, shift, issue, owner, corrective action)

How to adapt this checklist

Smaller operations can compress timeframes; large multi-location groups should add regional owner sign-offs and standardized templates. Keep one authoritative source of truth (shared doc or system) so staff always know the latest menus and training material.