Menu Change Communication & Launch Checklist (Interactive)

{ "Title": "Menu Change Launch Checklist", "IntroductionHtml": "

Purpose: Use this interactive checklist to coordinate a clean, low-friction menu change across kitchen, front of house, POS, and marketing. Capture signoffs, training completion, POS mapping verification, and day-of-launch readiness so everyone knows who did what and when.

How to use: Fill the launch details, work down the sections with the relevant teams, attach notes where useful, and save. The saved submission becomes a single reference for the launch and a record of readiness.

Quick templates & examples

Suggested staff announcement (edit before sending):

Team — On [LAUNCH DATE] at [TIME] we will put the updated menu live. Please join a 20-minute briefing on [DATE/TIME]. Key changes: [LIST 3–5 HIGHEST-IMPACT CHANGES]. See training notes and POS updates in the checklist. If you have questions, contact [MANAGER NAME].

Manager pre-shift briefing agenda (15–20 minutes):

1. Explain what changed and why.
2. Demonstrate new plating/portions or modifier flow.
3. Review POS buttons/modifiers and common order examples.
4. Assign FOH helpers for guest questions and remakes.
5. Confirm feedback channel and who logs issues.

Sample social post (short): "New seasonal menu launches [DATE] — fresh flavors, favorites tweaked. Book a table or order online. [link]"

POS mapping tip: Before launch, export a short test report with sample orders showing the updated item names, modifiers, and pricing. Confirm that modifiers map to the correct recipe/cost centers and that kitchen printer routing is unchanged.

", "SubmitLabel": "Save Launch Checklist", "SuccessMessage": "Launch checklist saved. Share the saved checklist with team members and keep this record for post-launch review.", "DataType": "menu.launch.checklist", "SchemaVersion": 1, "Fields": [ { "Key": "launch_location", "FieldType": "text", "Label": "Location / Unit", "HelpText": "Where this launch applies (store name, unit number, or 'All locations').", "Required": true }, { "Key": "launch_date", "FieldType": "text", "Label": "Planned launch date", "HelpText": "Use YYYY-MM-DD", "Required": true }, { "Key": "launch_time", "FieldType": "text", "Label": "Planned launch time", "HelpText": "Local time the menu goes live (e.g. 10:30 AM)", "Required": true }, { "Key": "prepared_by", "FieldType": "text", "Label": "Prepared / Submitted by", "HelpText": "Name and role of the person filling this form", "Required": true }, { "Key": "prelaunch_signoffs_header", "FieldType": "textarea", "Label": "Pre-launch signoffs (record names/dates below)", "HelpText": "Use the fields below to confirm cross-functional approvals." }, { "Key": "owner_signoff", "FieldType": "yesno", "Label": "Owner / Operator signoff completed?", "HelpText": "Confirm executive signoff on menu concept, pricing, and financial targets." }, { "Key": "owner_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date", "HelpText": "Name and date of signoff." }, { "Key": "gm_signoff", "FieldType": "yesno", "Label": "General Manager signoff completed?", "HelpText": "Confirms operational readiness, staffing, and guest impact." }, { "Key": "gm_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date" }, { "Key": "chef_signoff", "FieldType": "yesno", "Label": "Head Chef / Kitchen Manager signoff completed?", "HelpText": "Confirms recipe cards, portions, prep guide, and training plan." }, { "Key": "chef_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date" }, { "Key": "foh_signoff", "FieldType": "yesno", "Label": "Front-of-House manager signoff completed?", "HelpText": "Confirms service flow, guest-facing messaging, and remakes handling." }, { "Key": "foh_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date" }, { "Key": "marketing_signoff", "FieldType": "yesno", "Label": "Marketing / Communications signoff completed?", "HelpText": "Confirms assets, scheduling, and channels." }, { "Key": "marketing_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date" }, { "Key": "training_header", "FieldType": "textarea", "Label": "Training & staff readiness", "HelpText": "Record training completion and notes." }, { "Key": "training_completed", "FieldType": "yesno", "Label": "Has required training been completed for affected staff?", "HelpText": "Includes kitchen, floor, hosts, and any delivery/third-party partners." }, { "Key": "training_date", "FieldType": "text", "Label": "Training date (most recent)", "HelpText": "Date when staff were trained/briefed." }, { "Key": "training_notes", "FieldType": "textarea", "Label": "Training notes / agenda (paste or summarize)", "HelpText": "Record key teaching points, attendees, and follow-up actions." }, { "Key": "suggested_staff_message", "FieldType": "textarea", "Label": "Suggested staff announcement (edit before sending)", "HelpText": "A brief message you can copy into your scheduling or messaging tool." }, { "Key": "pos_header", "FieldType": "textarea", "Label": "POS, modifiers & systems", "HelpText": "Confirm POS and backend changes needed for the new menu." }, { "Key": "pos_updates_done", "FieldType": "yesno", "Label": "Have POS item names, prices, and routing been updated?", "HelpText": "Includes printer routing, course mapping, and delivery channels." }, { "Key": "pos_modifier_map_verified", "FieldType": "yesno", "Label": "Are modifier maps and extras verified against recipes?", "HelpText": "Ensure modifiers map to the right recipe/cost and inventory codes." }, { "Key": "pos_notes", "FieldType": "textarea", "Label": "POS notes / verification steps", "HelpText": "Example: exported test orders, screenshot confirmations, user who updated POS." }, { "Key": "marketing_header", "FieldType": "textarea", "Label": "Marketing assets", "HelpText": "Track what marketing assets are ready and where they'll be published." }, { "Key": "marketing_assets_ready", "FieldType": "yesno", "Label": "Are marketing assets ready?", "HelpText": "Includes website, social, email, in-store signage, and third-party platforms." }, { "Key": "marketing_assets", "FieldType": "checkbox", "Label": "Select prepared marketing assets", "HelpText": "Check all assets that are completed and scheduled.", "Options": [ { "Value": "menu_pdf", "Label": "Menu PDF / printable menu" }, { "Value": "website_menu", "Label": "Website menu page updated" }, { "Value": "pos_names", "Label": "POS item names & descriptions" }, { "Value": "social_post", "Label": "Social media post scheduled" }, { "Value": "email_blast", "Label": "Email campaign scheduled" }, { "Value": "in_store_signage", "Label": "Printed in-store menus / signage" }, { "Value": "loyalty_app", "Label": "Loyalty / app updated" }, { "Value": "third_party_delivery", "Label": "Third-party delivery menus updated" } ] }, { "Key": "marketing_assets_notes", "FieldType": "textarea", "Label": "Marketing notes / publish schedule", "HelpText": "Where and when assets will go live; contact person for each channel." }, { "Key": "day_of_launch_header", "FieldType": "textarea", "Label": "Day-of-launch readiness checklist", "HelpText": "Use these checks on the launch day before service begins." }, { "Key": "staff_briefed", "FieldType": "yesno", "Label": "All on-shift staff briefed at pre-shift?", "HelpText": "Confirm attendance or note make-up briefing plan." }, { "Key": "prep_stock_checked", "FieldType": "yesno", "Label": "Prep & stock levels verified for new items?", "HelpText": "Includes perishable prep and key ingredients." }, { "Key": "tasting_panel_done", "FieldType": "yesno", "Label": "Tasting or QC panel completed?", "HelpText": "Quick check for consistency and plating." }, { "Key": "temp_controls_set", "FieldType": "yesno", "Label": "Temperature and storage controls verified?", "HelpText": "For new items with specific holding or cooling needs." }, { "Key": "printed_menus_available", "FieldType": "yesno", "Label": "Printed/physical menus and POS displays available?", "HelpText": "If applicable for in-store guests." }, { "Key": "online_menus_updated", "FieldType": "yesno", "Label": "Website and ordering channels reflect new menu?", "HelpText": "Check web, app, and delivery partners." }, { "Key": "feedback_channel_open", "FieldType": "yesno", "Label": "Feedback and issue logging channel open?", "HelpText": "Confirm where staff will report problems and who will respond." }, { "Key": "final_signoff", "FieldType": "yesno", "Label": "Final readiness signoff (manager)", "HelpText": "Manager confirms all checks passed and gives green light." }, { "Key": "final_signoff_name_date", "FieldType": "text", "Label": "If yes, name & date", "HelpText": "Manager name and timestamp." }, { "Key": "additional_notes", "FieldType": "textarea", "Label": "Additional notes, risks, or follow-up actions", "HelpText": "Record any issues to review in the post-launch retro." } ] }