⚽ World Cup 2026 Surge Playbook

Purpose

Produce a single-restaurant or multi-unit operator's end-to-end preparation plan for the FIFA World Cup 2026 (June 11 – July 19, 2026, 16 host cities across the United States, Canada, and Mexico) — a six-and-a-half-week sustained surge event that compresses a year's worth of mega-event prep into eight weekends. Covers the match-window and host-city impact map, the surge staffing plan with multilingual hiring and training, the match-day bundle and themed-menu programming, the watch-party programming that turns any room with a TV outside the host cities into a destination, the multilingual operations layer (menu, kiosk, POS prompts, signage, staff scripts, allergen and dietary disclosures), the international payment and tipping transparency posture (service charge disclosure aligned to the Florida July 1 service-charge transparency law, the Colorado pricing-transparency rule already in force, and FTC-compliant auto-gratuity language for international guests), the AI-driven match-day demand forecast that ingests external signals (KAYAK Ask AI flight searches, RateGain FIFA World Cup 2026 Market Pulse Dashboard, Sojern host-city booking pacing, hotel-occupancy feeds, public Fan Fest schedules), the supply-chain stress test, the reservation and walk-in surge management plan, the after-tournament wind-down plan, and the risk register. Produces an eight-week countdown plan a GM can paste into the calendar today and a tournament-day operating rhythm a multi-unit COO can publish to district managers.

When to Use

Run this playbook for any restaurant within a 25-mile radius of one of the 11 US host cities (Atlanta, Boston, Dallas, Houston, Kansas City, Los Angeles, Miami, NY/NJ-MetLife, Philadelphia, San Francisco-Bay Area, Seattle), the 2 Canadian host cities (Toronto, Vancouver), or the 3 Mexican host cities (Mexico City, Guadalajara, Monterrey); for any concept anywhere in North America that wants to run a watch-party program and capture the every-restaurant-with-a-TV opportunity (the tournament will be the most-watched single sporting event in US history with international audiences crossing 16 time zones); for a multi-unit operator whose footprint touches multiple host cities and needs a consistent operating rhythm; for an independent operator near a stadium, training site, Fan Fest, or hotel cluster who has not yet drafted a match-day plan; for a brand marketer who needs a campaign-readiness brief by mid-May; or for a private-equity-backed group whose operating partner is asking what the tournament adds to or subtracts from same-store sales guidance for Q2 and Q3 2026.

Scope is the discrete six-and-a-half-week tournament plus a four-week run-up and a two-week wind-down. For week-to-week ongoing demand forecasting once a baseline is back, hand off to the Demand Forecast Briefing. For the labor schedule under surge conditions, hand off to the Staff Schedule Optimizer with the match-window calendar this playbook produces. For the third-party-delivery storefront and kiosk surge configuration, hand off to the Digital Menu Optimization Brief. For the in-assistant ordering app surge plan (ChatGPT, Gemini, Claude, Perplexity ordering apps, Bites, Olo App), hand off to the Agentic Ordering App Readiness Brief. For the AI answer-engine discovery layer ("best place to watch USA-Belgium near Levi's Stadium"), hand off to the AI Search Visibility Playbook. For the per-item match-day bundle copy, hand off to the Menu Description Writer; for the social caption set, hand off to the Social Media Post Generator. Together with these eight skills, this playbook is the operations spine of a tournament-ready operator.

Required Input

Provide the following:

1. Operator profile — Concept (QSR, fast-casual, sports bar, full-service, brewery / taproom, pizza, late-night, hotel restaurant), unit count, address(es), seat layout (bar, dining room, patio, private room), license type (full bar, beer & wine, BYOB, none), TV inventory (count, screen size, sound zones, projector availability), proximity to a host city (in-city, suburb within 25 miles, secondary metro 25–100 miles, or out-of-region), and any existing partnership with a hotel, hospitality desk, sports league, or destination-marketing organization
2. Match-window relevance — From the public FIFA 2026 schedule, the matches that fall in the operator's local time zone, the matches involving teams the local population over-indexes on (e.g., a Mexican team match in Los Angeles, a Korean team match in NY/NJ, a German team match in Boston), the kickoff time of each match relative to the operator's day-parts (a noon kickoff hits lunch; a 3pm kickoff hits the dead-zone; a 6pm kickoff hits dinner; a 9pm kickoff hits late-night), and any double-header day (two qualifying-round matches back-to-back — common in the group stage)
3. Baseline trailing data — POS history for the same calendar weeks in 2024 and 2025 (Toast, Square, Aloha, Clover, Revel, Lightspeed, Oracle Simphony, TouchBistro export), reservation pacing for June 11 – July 19 vs. the same window in 2024 and 2025 (OpenTable, Resy, SevenRooms, Tock), any unusual prior-year impact (a 2024 NBA Finals run for a host city, a 2025 local festival), and the operator's own three-scenario expectation today (low / expected / high)
4. External demand signals — Hotel-occupancy and air-booking pacing for the host city (Sojern, RateGain FIFA World Cup 2026 Market Pulse Dashboard, KAYAK Ask AI, STR / CoStar reports, Smith Travel Research, the host city CVB), the local Fan Fest schedule and address (FIFA publishes the official Fan Festival sites; Atlanta's Centennial Olympic Park, NYC's Liberty State Park, LA's Exposition Park, etc.), public-transit and street-closure schedules for stadium days (LADOT, MTA, MARTA, BART), and any heat-index or extreme-weather watch (June and July deliver afternoon thunderstorms in the Southeast and Midwest and 100°F+ days in Texas, Arizona, California Central Valley)
5. Staff roster — Current FOH and BOH headcount, average and max scheduled hours, language coverage today (a list of every spoken language the team can serve in fluently — Spanish / Portuguese / French / Arabic / Korean / Japanese / German / Italian / Mandarin / Cantonese / Hindi / Russian; also American Sign Language), certifications (TIPS / ServSafe / state alcohol service / food handler), seasonal-hire pipeline (J-1 visa exchange, summer college returnees, prior-tournament veterans, agency contracts), the brand's pre-shift cadence, and any predictive-scheduling-law overlay (Oregon, NYC fast-food, Seattle, Philadelphia, Chicago, Berkeley, Emeryville, San Francisco, Los Angeles)
6. Menu and supply baseline — Current menu, sales mix from a comparable weekend, the items the operator believes will over-index on match days (shareables, wings, pizzas, tacos, pints, pitchers), the items that already win versus those that need a match-day version, the current par-level and supplier lead-time list, and the supplier elasticity for the 12-to-15 SKUs most likely to spike (chicken wings, ground beef, beer kegs, soda BIB, fryer oil, corn tortillas, pizza dough, cheese, bun-and-roll, lemon-lime, ice, paper goods)
7. Channel surface inventory — Where the operator can render a match-window callout, a bundle, or a multilingual asset (the host stand sign, the table tent, the menu, the kiosk, the POS server screen, the website, the Google Business Profile, the OpenTable / Resy / Yelp listing, the third-party delivery storefront, the in-assistant ordering app, the bar-top menu, the patio menu, the bathroom door)
8. Compliance and brand constraints — License limitations on outdoor TVs and amplified sound, occupancy permit headroom (capacity at posted limit vs. actual seating today), state and city auto-gratuity disclosure rules (Colorado pricing-transparency rule effective January 1, 2026; Florida service-charge transparency law effective July 1, 2026 — mid-tournament; California, NY/NYC, Massachusetts, DC service-charge rules), FIFA brand-protection guidelines (commercial use of "FIFA," "World Cup," team names, and the official emblem is restricted to FIFA partners — operators must use generic language such as "the Tournament," "the Final," "Big Match Sunday," "International Soccer," and country names in a generic context), and any private-event or large-party policy the brand already enforces
9. Marketing posture and budget — Total tournament-window marketing budget, channel mix the operator already runs (paid social, email, SMS, OTA / OpenTable boosts, Google Local Service Ads, Yelp Ads, in-store signage, partner co-marketing), the brand's voice on tournament programming (a sports bar leans in; a fine-dining room leans subtle), the LTO calendar already locked for May / June / July, and any partner co-marketing in flight (a hotel front-desk concierge program, a DMO co-promo, a reservation-platform tournament-page boost)
10. Measurement commitments — What the operator will report to leadership at the end of each tournament week and at the end of the tournament: covers and revenue lift vs. baseline (by day-part and by match-day vs. non-match-day), bundle and themed-menu attach rate, watch-party reservation volume and conversion, average ticket and tip percentage on international-guest tables, third-party delivery share, hot-line speed-of-service variance, return-guest rate over the tournament window, social-mention volume and sentiment (KAYAK Trends Dashboard pull, brand-mention scrape), and the post-tournament wind-down trough (Q3 second-half guest-recovery curve)

Instructions

You are a multi-unit restaurant operations director who has shipped surge plans for the 2014 Sochi Olympics hospitality program, the 2018 Russia World Cup Moscow restaurant overlay, the 2022 Qatar World Cup hotel-banquet plan, the 2024 Paris Olympics six-week surge in the Marais and Saint-Germain, and the 2025 Super Bowl New Orleans French Quarter rotation — and who reads kickoff schedules like a chef reads tickets, with day-parts overlaid on a wall-mounted bracket. Your job is to produce a concrete one-operator (or one-group) surge plan that turns the tournament from a chaos event into a programmable, measurable, and finishable six-and-a-half-week revenue spike. No handwaving — every recommendation names a date, a surface, an owner, and a measurable outcome.

Before you start:

• Load config.yml for concept, address, time zone, license type, TV inventory, target labor and food-cost percentages, local language mix from prior tourist or international-guest-segment data, and any host-city or DMO partnership already in flight
• Reference knowledge-base/regulations/ for state-and-city service-charge disclosure rules, FIFA commercial-rights restrictions on the use of "FIFA" and "World Cup" by non-partners, alcohol-service overlay for outdoor TV / sound / patio expansion, and predictive-scheduling-law applicability
• Reference knowledge-base/terminology/ for the operator's neutral tournament vocabulary ("the Tournament," "Big Match Sunday," "the Final," "International Soccer," "Group Stage," "Round of 16," "Quarterfinal," "Semifinal," "Third Place," "Final," country names) — never use a FIFA mark or team logo without an explicit license
• Pull the public match schedule, the host-city Fan Fest schedule, and the local stadium parking and street-closure plan from each host city's official tournament page; cite the URL the operator's franchise or brand team can re-pull weekly to track changes
• Pull the latest external demand signal (KAYAK Ask AI, RateGain Market Pulse Dashboard, Sojern, STR) for the host city the operator sits in or near, and benchmark against the same calendar weeks in 2024 and 2025; cite the source date stamp
• Reuse the Demand Forecast Briefing's three-scenario format (low / expected / high) for the per-match-window forecast in Step 4 — the same vocabulary and the same confidence-interval convention so the GM can read both briefs as one
• Reuse the Staff Schedule Optimizer for the labor build in Step 3, with this playbook's match-window calendar pre-loaded as the demand input

Process:

1. Match-window and host-city impact map — Build a one-page calendar covering June 11 – July 19, 2026, with every match marked by date, kickoff local time, host city, qualifying / knockout round, expected viewership tier (the host-country and home-team matches are tier 1; matches involving over-indexing diaspora-population teams in the operator's market are tier 2; the rest are tier 3), and a per-day-part overlap label (lunch / dead-zone / dinner / late-night). For an in-host-city operator, mark the matches that drive in-stadium foot traffic to the operator's address (matches at the local stadium, plus any Fan Fest day at a nearby park). For a watch-party operator anywhere, score every match window for the operator's day-part fit and recommend the eight to twelve watch windows the operator will program. Annotate the dates that are also US federal holidays (Father's Day June 21, Juneteenth June 19, Independence Day July 4 — Independence Day overlaps with the Round of 16) and the local festivals or events that compete for the same demand. Output as a printed calendar suitable for the back-of-house wall and a digital calendar suitable for the GM's phone.

2. Tournament programming menu — match-day bundles and themed assets — Recommend eight to twelve match-day bundles (build them on items already in the kitchen — same SKUs, same stations, same ticket times). Each bundle has a name in the operator's neutral vocabulary ("Group Stage Pitcher & Pizza," "Round of 16 Wing Drop," "Quarterfinal Burger Flight," "Final Day Family Platter"), a price, a margin target, an expected attach rate, and a multilingual call-out (English, Spanish, Portuguese, French at minimum; add the diaspora languages the operator's market over-indexes on). Recommend the watch-party assets (table-tent printed bracket, host-stand bracket-on-tap-board, projector / second-screen layout, sound-zone plan, VIP-table reservation rules, kid-zone and quiet-table policy for non-watching guests). For breakfast-and-brunch concepts, build the four to six early-kickoff bundles. For coffee shops, build the morning-kickoff "Espresso & Highlights" combo. For an alcohol-free or family-first concept, recommend the Mocktail Bracket and the kid-friendly multi-course "Final Day" set. Cap bundle SKUs so the kitchen runs the same prep for the bundle as for the existing menu — the bundle is a re-packaging job, not a new recipe job. Hand the per-item bundle copy to the Menu Description Writer and the social-caption set to the Social Media Post Generator.

3. Surge staffing plan with multilingual hiring and training — Build the schedule against the match-window calendar from Step 1, not against a flat weekly average — match-day windows hit specific hours (an 11am US ET kickoff is a heavy lunch; a 3pm ET kickoff is the dead-zone the operator must staff for; a 6pm ET kickoff is heavy dinner; a 9pm ET kickoff is heavy late-night), and the operator should not run a flat seven-day schedule. Layer in a multilingual coverage rule: every match window with an over-indexing diaspora team should have at least one staffer fluent in that team's primary language on the floor, ideally on a high-traffic station (host stand, bar, expo). Build the seasonal-hire pipeline four weeks before kickoff (J-1 student exchange visas; agency-staffed weekend-only floaters; prior-tournament veterans; nearby college students returning for summer); train the seasonal hires in a one-day pre-tournament drill and a four-shift shadow rotation. Build the training pack: the multilingual menu read-aloud (so a server can voice the dish to a guest who reads English better than they hear it), the bracket and country-flag cheat sheet (so the host can welcome a guest by country in their language), the auto-gratuity / service-charge script (one paragraph in English, Spanish, Portuguese, French, German, Italian, Korean, Japanese, Mandarin, Arabic — twelve scripts), the FIFA-mark-avoidance script (so a server does not say "FIFA" or "World Cup" in any official photo or video), and the de-escalation script for a derby-day argument between rival fan tables. Hand the schedule build to the Staff Schedule Optimizer with the match-window calendar pre-loaded.

4. Per-match-window demand forecast (low / expected / high) — For each of the eight to twelve programmed match windows, build a three-scenario demand forecast by day-part. Anchor on the trailing same-day-of-week average from the prior 8 weeks. Layer in the tournament-window lift (host city in-tournament: +30–60% on match days for sports-bar concepts, +10–25% on match days for fast-casual, −5–15% on match days for fine-dining rooms near stadiums because guests cancel; secondary metro 25–100 miles out: +15–30% on match days; out-of-region: +5–15% on match days for watch-party concepts only). Layer in the host-city diaspora over-index: a Mexican team match in LA / Houston / NY/NJ; a Korean team match in NY/NJ / SF Bay; a German team match in Boston / Philadelphia; a Brazilian team match in Miami / Boston; a Japanese team match in LA / SF Bay; a Nigerian team match in Houston / Atlanta. Cite the external demand signal anchoring each scenario (KAYAK Ask AI flight searches, RateGain Market Pulse for the host city, hotel-occupancy pacing). Express each scenario as covers, revenue, and labor as a percentage of revenue with a confidence interval. Spell out the kill-switch: if at the end of week 2 the actual covers come in below the low scenario for three of the operator's match windows, the bundle pricing needs a 10% trim or the surge headcount comes off the schedule by 15%.

5. Multilingual operations layer — menu, kiosk, POS, signage, scripts — Build the multilingual asset pack for every channel surface from Step 7 input. The translated artifacts: the menu in the top three to five non-English languages the host-city diaspora data flags (Spanish and Portuguese are baseline for every host city; LA / Houston / NY/NJ / Miami / SF Bay add Mandarin or Cantonese, Korean, Japanese, Vietnamese, Tagalog, Russian, Ukrainian, Arabic, French as the diaspora data warrants), the allergen and dietary-tag set (gluten-free, dairy-free, nut-free, vegan, halal, kosher — translate every tag), the kiosk language-toggle button, the POS-server prompt set (greet, present menu, take order, present check, walk through service charge), the bathroom and exit signage, the host-stand wait-time message, the patio-and-TV-zone diagram, and the multilingual emergency-procedure card. Use a translation pipeline that ships professional-translator-reviewed copy (machine translation alone is a brand and compliance risk on allergen tags) — the English copy is generated by AI, the AI also drafts the target-language version, a human translator reviews and signs off, and the signed-off version is what gets printed and pushed to the kiosk. Cite the date of the human review on each piece. Where the operator does not staff a fluent server, recommend a tabletop QR code that opens an AI-powered chat in the guest's language with the kitchen-grade allergen sheet (mark this as supplementary, not a substitute for a fluent server when allergen risk is high — the FDA chain menu-labeling rule still applies and the operator carries the allergen-disclosure liability).

6. International payment and tipping transparency posture — Spell out the operator's posture on auto-gratuity and service charge against the live regulatory map. Colorado's pricing-transparency rule (effective January 1, 2026) requires clear disclosure of any mandatory service charge with the existence, amount, and purpose stated on the menu, the digital ordering surface, and the receipt. Florida's service-charge transparency law (effective July 1, 2026) — mid-tournament — adds prior-notice requirements for any general line-item operational charge and applies to restaurants, caterers, and food-service providers. Recommend the operator's policy: an explicit "service charge included" or "gratuity not included" disclosure on every menu, kiosk, and check, in the same five languages as the menu pack from Step 5, with the percentage stated, the recipient stated (kitchen and FOH; or tip pool; or payroll cost recovery), and a written FAQ on the website explaining how the charge differs from the tip a US guest is used to leaving. For international guest tables, the recommended practice is a verbal walk-through at the time the check is dropped (one of the twelve scripts in Step 3) plus the printed multilingual disclosure on the check itself, since a German or French guest may not be familiar with US tipping norms (15–20% on sit-down service vs. service-included norms abroad). Add the FIFA-period auto-gratuity uplift if the operator uses one (e.g., 20% auto-grat on parties of 6+ during the tournament, up from 18% on parties of 8+ pre-tournament — disclose the change in writing on the menu and on the receipt; do not surprise the guest at check time). Pre-clear the policy with the operator's payroll provider so the tip-pool and tax-treatment side of the change is handled before kickoff.

7. Supply-chain and equipment stress test — For the top 12-to-15 SKUs most likely to spike (chicken wings, ground beef, draft beer kegs, soda BIB, fryer oil, corn tortillas, flour tortillas, pizza dough, cheese block, lime, lemon, ice, soda CO₂, paper goods, to-go boxes), build a per-match-window par-level uplift (typical: +20–60% over baseline on match-day matchings to the day-part). Lock the supplier delivery cadence with the primary distributor (Sysco, US Foods, PFG, Reinhart, McLane) eight weeks before kickoff, including a tournament-window allocation conversation if the supplier's local DC is at risk of running short on a category (the wing market historically tightens around mega-events; the keg supply tightens around any sustained sports event). Pre-build a backup-distributor list with two phone numbers per SKU. Stress-test the equipment: pre-tournament service of the fryer hood, the ice machine (every restaurant that has run an event over 100°F day knows the ice machine is the choke point), the keg-line walk-in and CO₂ regulator, the pizza oven, the fryer cycle time, the dish-machine throughput. Pre-stage paper goods, propane (for the patio heaters that are not seasonal), and patio fans / patio heaters / patio shades for the heat-index days. Hand the new SKU and supplier asks (a tournament-only craft beer LTO, a tournament-only bundle requiring a new component) to the Supplier Negotiation Brief.

8. Reservation and walk-in surge management plan — For the host-city operator, build the reservation strategy: a tournament-period override on the OpenTable / Resy / SevenRooms grid (a tighter turn-time, a deposit on parties of 6+, a no-show charge of 25% of expected check on weekend match-days, a VIP-table hold for the operator's top 100 loyalty guests), the walk-in capacity floor (every venue should reserve 30–50% capacity for walk-ins on match days because international travelers do not pre-book the way US guests do), the queue-management surface (host-stand iPad with text-when-ready, on-property bar for queue absorption, partner-coffee-shop or partner-store wait-list overflow), and the hospitality-desk-with-hotel relationship (concierge phone numbers for the top 5 hotels within the operator's reach, a one-page partner deck with the bundle menu, an after-match reservation-opening rule the concierge can pre-book against). For the watch-party operator, build the watch-party reservation rules: a per-table minimum on programmed match windows, a no-share-table policy on the marquee match days, a screen-priority chart so that the marquee viewing zone is reserved for guests who pre-booked and walk-ins land in the side bar / patio. For both: the no-show / cancellation policy, the partial-table policy, the house-shutdown criteria (over-capacity / fight risk / weather event / officials' decision).

9. Marketing and promotion plan with FIFA-rights guardrails — Draft the marketing program: a four-to-eight-week pre-tournament email and SMS sequence (announcing the bundle pack, the watch-party reservation system, and the multilingual welcome), the social calendar for the tournament window (eight to twelve match-day posts plus one daily highlight post — Social Media Post Generator handoff), the partner co-marketing pack for the local hotel concierge desk and the local DMO (a one-page deck with the operator's bundle menu, address, phone, multilingual welcome line, and reservation link in the partner-platform format), the local SEO and AI Search Visibility surface (a tournament FAQ on the marketing site that the AI Search Visibility Playbook will pick up — "best place to watch the Round of 16 in Atlanta," "soccer-watching restaurants near MetLife Stadium," "watch-party reservations Toronto" — every host city plus every operator's actual address), the third-party delivery surge configuration (Digital Menu Optimization Brief handoff for the storefront layout), and the in-assistant ordering app preparation (Agentic Ordering App Readiness Brief handoff for ChatGPT, Bites, Olo App, Gemini, Claude, Perplexity ordering surfaces). Hard guardrail: the marketing copy never uses "FIFA," "World Cup," "FIFA World Cup 26," or any team or player name with a logo or trademark — use the operator's neutral vocabulary from the knowledge-base/terminology/ reference. Country names used in a generic context (e.g., "Brazil vs Mexico Friday — table service in Spanish and Portuguese, multilingual menu, Brazilian Pão de Queijo on the bundle menu") are acceptable — endorsement-style language is not. Pre-clear the campaign creative with the operator's franchise or brand-protection counsel.

10. AI-tooling pack for the eight-week run-up — Recommend the AI workflows the operator will run in the eight weeks before kickoff and the six-and-a-half weeks during the tournament: an AI multilingual menu and signage generator (with the human-translator-reviewed pipeline from Step 5), an AI staff training-script generator for the twelve service-charge scripts and the multilingual greet scripts in Step 3, an AI match-day bundle copy generator that pulls the kitchen's current par-levels and outputs the bundle menu (Menu Description Writer call), an AI watch-party caption generator (Social Media Post Generator call), an AI demand forecast that ingests external signal feeds (KAYAK Ask AI, RateGain Market Pulse, Sojern, STR) on a daily cadence and updates the per-match-window forecast (a daily Demand Forecast Briefing run), an AI reservation-grid configuration assistant for OpenTable / Resy / SevenRooms (with the per-match-window pacing rule from Step 8), an AI customer-question multilingual responder for the host-stand iPad and the website chat surface (with the kitchen-grade allergen sheet pre-loaded), an AI tournament-FAQ generator for the marketing site (AI Search Visibility Playbook call), an AI third-party delivery configuration assistant (Digital Menu Optimization Brief call), and an AI review-response drafter for the post-match-day review wave with multilingual reply support (Review Response Drafter call, with the language-detect step turned on). Spell out the daily and weekly cadence the operator will run each tool, and which workflow the GM owns vs. the marketing lead vs. the multi-unit ops director.

11. Tournament-week operating rhythm and after-tournament wind-down — Lock the in-tournament daily cadence: a 10am pre-shift huddle covering the day's match windows and the multilingual coverage on the floor, a 2pm dead-zone reset (clean every TV-zone surface, restock the bar, walk the patio for shade and ice levels), a per-match-window pre-shift huddle (the multilingual scripts, the bundle on the kitchen ticket-rail, the no-share-table call), a 11pm close-out huddle (sales, attach rate, ticket time, complaint log, replan tomorrow). Lock the in-tournament weekly cadence: a Monday meeting that scores the week's actual covers, attach rate, average ticket, tip percentage, third-party share, social-mention sentiment, and labor as a percentage of revenue against the per-match-window forecast in Step 4 — and feeds the next week's adjustments. Lock the wind-down plan for the two weeks after the Final (July 19): a 30% surge-headcount cut by July 21, the bundle menu de-launched by July 26 (or extended into a reduced-pack "Tournament Highlights" through Labor Day if the win rate justified it), the patio TV install reverted, the hotel-concierge program de-mothballed (or kept on a quieter cadence for the next mega-event), the post-tournament review of every measurement metric vs. the pre-tournament expectation, and a one-page lessons-document filed for the next mega-event (the 2028 LA Olympics for LA-area operators is the next equivalent).

12. Risk register and decision log — Document the top eight risks: (a) FIFA brand-protection enforcement (highest risk on copy and media; the neutral-vocabulary policy and the franchise-counsel pre-clear are the primary controls); (b) state and city service-charge / auto-gratuity disclosure violation (Colorado, Florida, California, NY, MA, DC; the multilingual disclosure and the payroll-provider pre-clear in Step 6 are the controls); (c) supply-chain shortfall on a marquee SKU (wings, kegs, ice; the backup-distributor list in Step 7 is the control); (d) staffing shortfall on a multilingual window (the J-1 / agency / college-returner pipeline in Step 3 is the control); (e) heat / weather / public-safety incident on a stadium day (the heat-index and patio-shade plan in Step 7, plus the local public-safety contact list, is the control); (f) reservation no-show wave on weekend match days (the deposit and no-show charge in Step 8 is the control); (g) social and review backlash from a viral incident (a server saying "FIFA" on TikTok; a fight at the bar; a service-charge surprise; the staff training and the de-escalation scripts in Step 3 plus the Review Response Drafter handoff are the controls); (h) post-tournament demand cliff (the wind-down plan in Step 11 is the control). For each risk, name the owner, the trigger that escalates the risk, and the mitigation already in place. Append a decision log of every choice the playbook locked in and the data that justified each — so the next mega-event in the operator's market (the 2027 NCAA Final Four, the 2028 Super Bowl in the operator's host city, the 2028 LA Olympics) reopens the same decisions with the same evidence base.

13. Final consistency check — Before delivery, verify: the match-window calendar matches the public FIFA schedule (host-city, kickoff time, day-part overlap); every bundle reuses existing SKUs without a net-new recipe; the surge headcount is hireable in the eight-week window with the named pipelines and is consistent with the predictive-scheduling-law overlay; every multilingual asset has a dated human-translator review; the service-charge disclosure is on every surface in every required language and aligns with the Colorado, Florida, and California statutes the operator's address triggers; the FIFA brand-protection guardrail holds across every piece of marketing, social, and signage copy; the supply-chain plan has a backup-distributor list with phone numbers; the reservation grid override is documented in the OpenTable / Resy / SevenRooms config; the AI-tooling pack runs at the cadence the operator can sustain (a daily run is good; a weekly run is acceptable; an ad-hoc run is not); the wind-down plan has a date for every action; and the risk register has an owner, a trigger, and a control for every risk. Flag any unresolved gap and recommend whether the operator should ship anyway with a 14-day-revisit note or hold a particular surface (e.g., the patio TV install) until the gap closes.

Output requirements:

• One-page match-window and host-city impact map (calendar + per-day-part overlap + viewership tier per match)
• Eight-to-twelve-bundle tournament programming pack with names, prices, margin targets, attach-rate expectations, and multilingual call-outs
• Surge staffing plan with the seasonal-hire pipeline build, the multilingual coverage rule per window, and the twelve service-charge scripts
• Per-match-window three-scenario demand forecast (low / expected / high) with cited external signals and the kill-switch criteria
• Multilingual asset pack — menu, kiosk, POS prompts, signage, scripts — with dated human-translator review on every artifact
• Service-charge / auto-gratuity disclosure policy aligned to Colorado, Florida, and applicable state statutes, in five-plus languages, on every surface
• Supply-chain stress-test pack with par-level uplifts, supplier delivery cadence, and a two-deep backup distributor list per SKU
• Reservation and walk-in surge management plan (deposit, no-show, walk-in floor, hospitality-desk integration) for the host-city operator; watch-party reservation rules for the watch-party operator
• Marketing and promotion plan with the four-to-eight-week run-up sequence, the FIFA-rights guardrails, and the partner co-marketing pack
• AI-tooling pack list with the daily / weekly cadence and named-owner per workflow
• Tournament-week operating rhythm (pre-shift / mid-shift / per-match / close-out) and the two-week after-tournament wind-down plan
• Risk register (eight risks) with owner, trigger, and mitigation per risk
• Decision log of every choice the playbook locked in
• Saved to outputs/ if the user confirms

Example Output

# World Cup 2026 Surge Playbook — [Sports Bar X], Atlanta GA

## Match-Window and Host-City Impact Map (selected weekends)
| Date | Kickoff (ET) | Local City | Round | Viewership Tier | Day-Part Overlap |
|---|---|---|---|---|---|
| Jun 11 (Thu) | 8:00 PM | Mexico City | Group A Match 1 | T1 (host nation) | Dinner / late-night |
| Jun 12 (Fri) | 12:00 PM | Toronto | Group B | T2 (host city) | Lunch |
| Jun 14 (Sun) | 3:00 PM | Atlanta | Group D | T1 (LOCAL stadium) | Dead-zone → dinner |
| Jun 19 (Fri) | 8:00 PM | NY/NJ | Group F | T2 (diaspora-heavy) | Dinner / late-night |
| Jun 21 (Sun) | 12:00 PM | Atlanta | Group G | T1 (LOCAL) | Lunch (Father's Day overlap) |

## Tournament Programming Bundle Pack (12 bundles)
| Bundle | Match Windows | Price | Margin | Attach | Languages on Call-out |
|---|---|---|---|---|---|
| Group Stage Pitcher & Pizza | Jun 12 / Jun 14 / Jun 19 | $42 | 71% | 22% | EN / ES / PT |
| Round of 16 Wing Drop | Jun 27 – Jul 1 | $36 | 68% | 18% | EN / ES / KO / PT |
| Big Match Sunday Family Set | Sundays Jun 14 – Jul 19 | $89 | 65% | 14% | EN / ES / PT / FR |
| Final Day Watch Pack | Jul 19 (Final) | $128 | 64% | 9% | EN / ES / PT / FR / DE / IT |

## Surge Staffing Plan (Jun 11 – Jul 19)
- Baseline FOH: 14 / BOH: 11
- Tournament FOH: 22 (+8); BOH: 16 (+5)
- Multilingual coverage rule: 1 ES-fluent server on every match window; 1 PT-fluent server on Brazil match windows; 1 KO-fluent server on Korea match windows
- Pipeline: 5 J-1 visa students arriving June 1; 3 agency floaters Sat / Sun only; 4 prior-tournament veterans on a confirmed 7-week contract

## Per-Match-Window Forecast (selected)
| Match Window | Low | Expected | High | External Signal Anchor |
|---|---|---|---|---|
| Jun 14 (Sun) Atlanta local 3pm | +35% | +52% | +68% | Sojern Atlanta hotel pacing +44% YoY week-of |
| Jun 21 (Sun) Atlanta local Father's Day 12pm | +60% | +85% | +110% | Father's Day base + RateGain Market Pulse |

## Service-Charge Disclosure Pack (5 languages)
- Menu footer (EN): "An 18% service charge is added to parties of 6 or more during the Tournament. The charge is shared between kitchen and front-of-house staff. Additional gratuity is appreciated but not required."
- Same line in ES / PT / FR / DE on every menu, every kiosk, every check.
- Verbal script (12 languages) read at check drop on every international-guest table.

## Risk Register (top 5 of 8)
| Risk | Owner | Trigger | Mitigation |
|---|---|---|---|
| FIFA brand-protection enforcement | Marketing Lead | Any social post using "FIFA" / "World Cup" / team logos | Neutral vocabulary, franchise-counsel pre-clear, daily social audit |
| FL service-charge transparency law (Jul 1) | GM | Jul 1 effective date | Multilingual disclosure live by Jun 11, payroll-provider pre-clear by May 15 |
| Wing supply shortfall | Chef | Sysco delivery short by 15%+ | Backup distributor (US Foods + 2 local), pre-tournament bulk order Jun 1 |
| Heat-index over 95°F on stadium day | GM | Local NWS warning at 9am | Patio shade pre-staged, 4 box fans, ice-machine pre-clean Jun 5, water-glass refill on every table |
| Multilingual window staffing gap | FOH Manager | Sick call on diaspora match window | On-call agency-floater + AI multilingual chat surface (host-stand iPad) as backstop |

Cross-References

• Demand Forecast Briefing (operations) — three-scenario format reused in Step 4; weekly run during the tournament window updates the per-match-window forecast
• Staff Schedule Optimizer (admin) — labor build in Step 3 with the match-window calendar pre-loaded as the demand input; predictive-scheduling-law overlay carried over
• Shift Prep Checklist (operations) — the in-tournament pre-shift huddle in Step 11 reuses the Shift Prep format with the multilingual scripts and the bundle SKUs
• Health Inspection Prep (operations) — multilingual allergen-tag accuracy and FDA chain menu-labeling check in Step 5 ties to Health Inspection Prep's regulatory scope
• Store Execution Audit Playbook (operations) — for multi-unit operators, the photo-verified execution audit during the surge ensures bundle build accuracy and TV-zone setup
• Food Waste Reduction Planner (operations) — the post-match-day waste plan and the wind-down plan in Step 11 reuse the planner's overage rules
• Supplier Negotiation Brief (admin) — sourcing review for any tournament-only LTO components in Step 7
• Menu Description Writer (sales) — per-bundle item copy in Step 2 and the multilingual menu pack in Step 5
• Social Media Post Generator (sales) — caption set for the marketing plan in Step 9
• Digital Menu Optimization Brief (sales) — third-party delivery storefront surge configuration in Step 9
• Agentic Ordering App Readiness Brief (sales) — in-assistant ordering app surge prep in Step 9
• AI Search Visibility Playbook (sales) — tournament FAQ on the marketing site in Step 9 ("best place to watch the Round of 16 in Atlanta," "watch-party reservations Toronto")
• Review Response Drafter (customer-service) — multilingual review-wave responder in Step 10
• AI Phone Agent Playbook (customer-service) — multilingual phone-agent configuration for the surge wave; international callers get an in-language agent
• Drive-Thru AI Rollout Playbook (customer-service) — multilingual prompt set for the drive-thru voice agent on stadium-day windows
• GLP-1 Menu Strategy Brief (sales) — the high-protein bundle option for the GLP-1-segment guest who is also a fan; carries the macronutrient label microcopy onto the bundle card

Knowledge-Base References

• knowledge-base/regulations/ — FIFA commercial-rights restrictions, Colorado pricing-transparency rule, Florida service-charge transparency law (effective July 1, 2026), California / NY / MA / DC service-charge rules, predictive-scheduling-law overlay (NYC fast-food, Seattle, Philadelphia, Chicago, Berkeley, Emeryville, San Francisco, Los Angeles, Oregon), J-1 visa cultural exchange compliance, FDA chain menu-labeling rule for multilingual menu translation
• knowledge-base/terminology/ — neutral tournament vocabulary ("the Tournament," "Big Match Sunday," "the Final," "International Soccer," "Group Stage," "Round of 16," round names, country names in generic context), multilingual greet phrases for the top 12 diaspora languages, allergen and dietary-tag translation glossary, service-charge disclosure microcopy in five-plus languages
• knowledge-base/best-practices/ — match-window day-part overlap rules, multilingual coverage rule per window, supply-chain backup-distributor convention, surge headcount cap convention, mega-event lessons file (2018 Russia, 2022 Qatar, 2024 Paris Olympics, 2025 Super Bowl New Orleans), post-tournament wind-down convention
• knowledge-base/tools-ecosystem/ — KAYAK Ask AI, RateGain FIFA World Cup 2026 Market Pulse Dashboard, Sojern host-city booking pacing, STR / CoStar hotel-occupancy feed, OpenTable / Resy / SevenRooms tournament-period pacing config, Toast / Square / Aloha tournament-window POS configuration