Menu change communication & launch packet

Menu Change Communication & Launch Packet

Use this packet to plan and execute menu updates with minimal disruption. It collects a practical launch timeline, role responsibility matrix, recipe and plating materials, POS and menu-printing checklist, server talking points, marketing copy templates, rollback criteria, and post-launch monitoring steps. Copy and adapt every item to your kitchen, service model, POS system, and local rules.

Quick Start: Minimum Launch Checklist

• Confirm finalized recipes, portion specs, and plating photos approved by chef.
• Create updated POS items and prices in a test environment; confirm modifier/meal course behavior.
• Provide FOH talking points and allergen notes to servers in writing and practice run.
• Schedule side-by-side prep and test-service on a quiet shift or soft-launch day.
• Publish marketing assets no earlier than agreed launch time; coordinate online menu and reservation platforms.
• Define rollback criteria and who signs off to pause or remove items.

Launch Timeline Template (adapt to complexity)

1. T-minus 4+ weeks: Finalize recipes, portion specs, supplier availability, and costing.
2. T-minus 2 weeks: Enter test items into POS; create training schedule; draft FOH talking points and marketing copy.
3. T-minus 1 week: Print internal guides, portion photos; run kitchen prep trials; schedule server tastings and role-play.
4. T-minus 3 days: Lock POS pricing; finalize printed menus and online menu files; send FOH reminders and shift-by-shift talking points.
5. Launch Day: Early pre-shift huddle for FOH and BOH; manager monitoring checklist active; small controlled rollout or full rollout as planned.
6. Post-launch (0–72 hours): Monitor KPIs (ticket times, remakes, voids, guest complaints), collect staff feedback, and decide whether rollback criteria trigger.
7. Post-launch review (7–30 days): Analyze sales mix, food cost, labor impact, guest feedback; decide permanence or adjustments.

Roles & Communication Matrix

Assign clear owners. Example responsibilities:

• Project Lead / General Manager: Overall signoff, timeline owner, external communications.
• Executive Chef / Kitchen Manager: Recipe owner, plating photos, portion specs, training for cooks.
• FOH Manager: Server training, talking points, allergy notes, front-of-house troubleshooting.
• POS / Tech Lead: Create and test POS items, pricing, modifiers, and online menu sync.
• Marketing / Ops: Marketing assets, social copy, email, signage, timing of announcements.
• Shift Leads: Enforce standards, collect frontline feedback, escalate issues per rollback plan.

Recipe, Plating & Training Pack (deliverables)

• Final recipe document (ingredient list, pack size & supplier, order code, cost per portion).
• Portion & plating spec sheet with weight/volume, tolerances, and acceptable substitutions.
• High-resolution plating photos with front/side/top views and accepted garnish positions.
• Short video or demo checklist for prep steps that cause variation (if available).
• Kitchen training checklist (who trains whom, sign-off fields for each cook).
• Server tasting notes and practice order flow for FOH training with sign-off fields.

POS & Menu Printing Checklist

1. Add new menu item(s) in staging/test POS; set pricing, course, category, and printer routing.
2. Define modifiers, upsell prompts, allergen flags, and inventory depletion behavior if linked.
3. Test ticket printing and kitchen routing for multiple device types (expeditor printer, chef display, prep tickets).
4. Confirm online ordering platforms, third-party menus, and reservation systems show correct menu and pricing.
5. Prepare printed menus and inserts; check layout, proofread, and confirm final print run timing.
6. Schedule a POS publish time and communicate expected downtime or service notes to staff.

FOH Talking Points (sample language servers can use)

Provide short, practiceable lines and important notes. Example server script:

• Intro: “We’ve just added a new seasonal entrée—would you like a quick description or a sample?”
• One-line description: “It’s pan-seared salmon with miso butter, roasted baby carrots, and lemon-herb couscous.”
• Key selling point: “It’s a lighter, bright dish that pairs well with our citrus cocktail.”
• Allergen/ dietary note: “It contains dairy and gluten—we can adapt it by removing the couscous.”
• Upsell prompt: “Would you like that with a side salad or a soup today?”
• Closing practice: keep it under 20 words and match the restaurant tone.

Marketing & Announcement Templates

Provide copy blocks to adjust for channels.

• Social post: Short hook, one-sentence description, high-quality photo, CTA (reserve/order link).
• Email: Subject line, hero photo, short menu highlights, link to full menu, exclusive offer if desired.
• In-house sign: Name, 2–3 words of descriptor, price, allergen highlight, launch date.
• Keep release timing coordinated—online menu and POS must match the public announcement time.

Rollback Criteria & Plan (must be clear and actionable)

Define measurable triggers and the steps to remove or pause the item:

• Example triggers (any one may trigger rollback): remakes > 5% of item sales in a 3-hour window; consistent ticket time increases of >5 minutes for peak course; supplier quality problem reported more than once; sustained negative guest feedback about the item exceeding X complaints per 100 covers.
• Rollback steps: immediate stop-of-sale in POS (owner/manager), remove printed menus/inserts, update online menus, communicate to staff and marketing, investigate root causes, schedule corrective actions or recipe rollback.
• Decision authority: name role(s) authorized to trigger rollback (e.g., GM + Exec Chef or Regional Manager if multi-site).

Launch Day Manager Monitoring Checklist

1. Pre-shift quick huddle: confirm everyone’s role, confirm allergens, confirm POS is live with correct pricing.
2. Watch first 10 plates of each new item for plating consistency and temperature.
3. Monitor ticket times for whole shift; note any unusual variance between stations.
4. Collect FOH notes every hour during peak (brief check-ins).
5. Log any guest complaints or remakes with details: time, server, table, reason.
6. If rollback criteria met, follow the rollback steps and notify staff and external channels as needed.

Key Metrics to Monitor Immediately

• Sales mix and velocity (items sold per hour).
• Remake rate and voids for the new item.
• Average ticket time for courses affected by the new item.
• Guest feedback volume and sentiment (in-person and online).
• Food cost per plate and ingredient availability (inventory hits).

Post-launch Review (7–30 days)

Collect quantitative and qualitative data and convene a short review:

• Sales and contribution analysis vs. projected numbers.
• Operational impacts on kitchen throughput and service times.
• Staff feedback on complexity and training sufficiency.
• Customer feedback and review analysis; consider a brief guest survey for early impressions.
• Decide: keep, modify, relaunch (after fixes), or retire.

Attachments & Templates to Include with Packet

• Recipe_Template.pdf (ingredient, yield, cost per portion)
• Portion_Spec_Sheet.pdf (photo + weights + tolerances)
• POS_Update_Checklist.xlsx
• FOH_TalkingPoints.docx
• Server_Training_Signoff.xlsx
• Marketing_Copy_Templates.docx (social, email, signage)
• Launch_Timeline_Template.xlsx
• Rollback_Checklist.docx

How to Adapt This Packet for Multi-location or Franchise Use

Make a single master packet that can be versioned, then create location-specific copies with local supplier codes, manager signoffs, and local regulatory notes. Capture any local changes as learnings to update the master packet.

Final Notes

This packet is a practical starting point—your best results come from tailoring the timeline, checklists and rollback thresholds to match your menu complexity, volume, and team experience. Use the server sign-offs and kitchen training sheets to make sure knowledge is recorded, not just assumed. If you have a POS environment that supports staging or bulk updates, schedule a test publish ahead of the live launch and keep a rollback contact list readily available.