Seasonal Menu Transition Plan
Change a menu with minimal disruption.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Plan a seasonal menu change. Current menu and sales performance: [CURRENT_MENU]. Seasonal ingredients available from suppliers: [SEASONAL_INGREDIENTS]. Kitchen and staff capacity: [CAPACITY]. Change date: [DATE]. Create an eight-week plan: menu development and testing, costing, supplier agreements, staff training, allergen review, menu design and printing, soft launch, and review. Provide a timeline table with owner and deadlines, a tasting session agenda, a script for training servers, and a checklist for the first week. Include a risk list (supply shortages, new dishes that slow service) with mitigations, and a method for measuring dish performance after two and six weeks. Mark allergen and labelling steps for verification with the person responsible for food safety [VERIFY]. Also add a plan for using up old-menu stock, a communication to regulars about dishes that are leaving, and a feedback form for the first two weeks that records guest comments and server observations. Offer options and drafts, not rules: tag anything about tax, tipping or price display [VERIFY] for [JURISDICTION], and keep the rest of the plan practical either way.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.