Automated Kiosk Deployment Brief

Purpose

Produce a brand-level go / no-go and configuration plan for deploying automated hot-food, refrigerated-meal, or ambient-snack kiosks in non-traditional venues — hospitals, college campuses, airports, corporate workplaces, transit hubs, military bases, hotels, casinos, conference centers, gyms, and 24-hour grocery — through a managed-foodservice partner (Aramark, Sodexo, Compass Group, Canteen, Five Star, USConnect), a kiosk-platform partner (Automated Retail Technologies / Just Baked, 365 Retail Markets, Crane Merchandising, Avanti Markets), or a direct operator-owned model. Covers the deployment-stance decision (operator-owned vs. partner-managed vs. hybrid; exclusive-with-platform vs. non-exclusive), the venue-type and site-selection rubric, the SKU subset and menu engineering for hot-hold tolerance and sub-two-minute throughput, the per-kiosk pricing posture against the operator's brick-and-mortar parity rule, the replenishment-cadence and routing plan, the AI-tooling pack for remote operations (computer-vision stock detection, predictive replenishment, dynamic per-kiosk pricing, automated age-verification on restricted SKUs, temperature and sanitation telemetry, remote troubleshooting), the regulatory and food-safety posture (state Food Code, ServSafe Manager assignment per remote site, ADA accessibility, calorie-disclosure, allergen labeling, FDA chain menu-labeling carry-over, age-verified item rules), the brand-experience consistency rules (kiosk UX, payment, loyalty integration, packaging, in-kiosk menu copy, complaint-channel), the four-metric measurement plan, the launch-day communication pack, and a pre-signature platform-partner contract checklist. Produces a printable five-to-eight-page brief a VP of Development, COO, or franchisee group can hand to legal counsel, the platform partner, and the operations team to execute a 25-to-1,000-kiosk rollout without re-deciding the same questions in every site review.

When to Use

Run this brief for a multi-unit operator (5+ units) evaluating an automated-kiosk partnership with Automated Retail Technologies, 365 Retail Markets, Crane, Avanti, Aramark, Sodexo, Compass, Canteen, or USConnect; for a brand whose franchisee or operator-group leadership is asking whether to follow the White Castle Crave & Go pattern (1,000-kiosk national footprint), the Nestlé pattern (CPG-meets-foodservice via institutional kiosks), or the Pasta Supply Co. pattern (refrigerated chef-prepared meals in a smaller-format kiosk); for an operator whose brick-and-mortar footprint plateaued and whose growth committee is targeting non-traditional venues (hospitals, airports, college campuses, corporate cafeterias, military bases, transit hubs, hotels, gyms, 24-hour grocery, healthcare facilities, manufacturing plants, distribution centers); for a brand whose category is a fit for a sub-two-minute hot-hold or refrigerated-meal kiosk format (sliders, sandwiches, pizza-by-the-slice, hot bowls, salads, wraps, ramen, breakfast biscuits, coffee, smoothies, ice cream — categories with too high a staff-per-cover or food-safety constraint to serve via traditional self-serve are a poor fit and should be flagged in the no-go column); for a private-equity-backed operator group whose investment thesis includes a non-traditional-venue distribution channel; or for an institutional-foodservice account team that needs to underwrite a kiosk vs. micro-market vs. ghost-kitchen vs. cafeteria decision for a corporate or healthcare client.

Scope is the discrete deployment-strategy decision plus the first 90 days of post-launch operations. For ongoing weekly demand forecasting on a brick-and-mortar store, hand off to the Demand Forecast Briefing. For the labor schedule under the smaller staff-replenishment model, hand off to the Staff Schedule Optimizer with the per-kiosk replenishment-cadence pre-loaded. For the third-party-delivery storefront layout that the kiosk QR-code might dual-route to, hand off to the Digital Menu Optimization Brief. For the in-assistant ordering app surge prep, hand off to the Agentic Ordering App Readiness Brief. For the in-kiosk and venue-signage menu copy, hand off to the Menu Description Writer. For the social-launch caption set, hand off to the Social Media Post Generator. For the per-item price moves on the kiosk SKU subset, hand off to the Dynamic Menu Pricing Advisor. For the FDA chain menu-labeling and ADA accessibility regulatory scope, hand off to the Health Inspection Prep checklist with the kiosk-specific scope flagged. For the multi-unit photo-verification audit on the kiosk fleet, hand off to the Store Execution Audit Playbook with the kiosk fleet pre-loaded as the audit target. Together with these eight skills, this brief is the strategic spine of an automated-kiosk distribution channel.

Required Input

Provide the following:

1. Brand profile — Concept (QSR slider, fast-casual sandwich, pizza-by-the-slice, hot bowl, breakfast biscuit, coffee, smoothie, ice cream, refrigerated chef-prepared meal, ambient snack), unit count and footprint geography, average annual brick-and-mortar revenue per unit and food-cost / labor-cost ratio, current franchise mix vs. corporate-owned, brand-protection posture (trademarks, brand standards manual, kiosk-specific brand guidelines if any), and any prior unattended-retail experience (vending, hotel-pantry, micro-market, partner concession)
2. Strategic intent — Total addressable kiosk count target over 12 / 24 / 36 months, the venue-type prioritization (hospital, college, airport, corporate, transit, hotel, gym, military, manufacturing, casino, conference, healthcare, 24-hour grocery), the geographic prioritization (top 5 metros, top 25 metros, nationwide, international), the partnership stance (operator-owned vs. platform-managed vs. hybrid; exclusive vs. non-exclusive), the capex posture (operator funds the kiosks, platform funds the kiosks against a revenue share, or a hybrid lease-to-own), and the decision threshold (the minimum monthly revenue per kiosk at which the rollout continues vs. pauses)
3. Platform partner shortlist — The two-to-four candidate platform partners under evaluation (ART / Just Baked, 365 Retail Markets, Crane, Avanti Markets, Aramark, Sodexo, Compass Group, Canteen, USConnect), the partnership tier each is offering (referral, white-label, co-branded, exclusive territory, equity), and the deal sheet or term sheet from each (capex split, revenue share, exclusivity, minimum-deployment commitment, marketing fund, brand-protection clauses, termination rights, IP rights, data ownership, performance KPIs)
4. Menu and SKU baseline — Current full menu, the candidate SKUs for the kiosk format (typical ceiling is 8–18 SKUs for hot-food, 12–24 for refrigerated meals, 30–60 for ambient snack), the prep complexity of each candidate (a finished SKU that holds at hot-hold for 2+ hours without a quality drop is the gold standard; a SKU requiring assembly at the kiosk is a no-go for most platforms), the allergen profile of each candidate, the calorie label of each candidate (FDA chain menu-labeling rule applies to brands with 20+ locations), and the cross-utilization map vs. the brick-and-mortar menu
5. Pricing baseline — Current brick-and-mortar pricing on the candidate kiosk SKUs, the operator's brand-promise on price parity (must-match parity, parity-plus-convenience-premium, kiosk-specific pricing tier independent of brick-and-mortar), the institutional-account contract pricing the platform partner already runs at the candidate venues, and the operator's posture on dynamic per-kiosk pricing (allow it, ban it, or allow within a +/-10% band off the MSRP)
6. Venue intelligence — A list of 25–100 candidate venues with venue type, foot traffic estimate (the hospital cafeteria's transaction count per day is the closest analogue; the corporate cafeteria's daily badge-swipe count is the second-closest), competitor presence on-site (the existing vending / micro-market / cafeteria operator), the venue's contract-pricing requirement (some hospitals and colleges require contract-pricing parity with the institutional vendor; some corporates require a discount off retail), the venue-installation constraints (electrical, water, drain, wireless connectivity, ADA reach-zone, fire-suppression, refrigeration capacity), and any venue-management approval gates (the campus dining director, the hospital food-service director, the airport concessions authority, the corporate facilities director)
7. Replenishment and labor model — The operator's current commissary or central-production capability (an existing commissary is the strongest enabler; a brick-and-mortar prep team replenishing nearby kiosks is a viable alternative; a third-party commissary contract is the slowest path to launch), the radius the operator can drive between commissary and kiosk in a single replenishment trip (typical: 50-mile radius for a hot-food kiosk; up to 200-mile radius for a refrigerated meal kiosk; cross-state for shelf-stable ambient SKUs), the anticipated replenishment cadence (twice daily for hot-food; daily for refrigerated; twice weekly for ambient), the staffing model (operator-owned route drivers, platform-partner route drivers, third-party logistics, hybrid), the predictive-scheduling-law overlay (Oregon, NYC fast-food, Seattle, Philadelphia, Chicago, Berkeley, Emeryville, San Francisco, Los Angeles), and the wage and benefit baseline for the route-driver cohort
8. Regulatory and food-safety posture — The state and city Food Code applicable to each candidate venue (the FDA Food Code 2022 is the federal baseline; states adopt with delta), the ServSafe Manager assignment rule (per state, every food-service site needs a designated ServSafe Manager — the kiosk is treated as a remote site of the operator's nearest commissary or store in some states; standalone in others), the ADA accessibility requirements on the kiosk reach-zone (15-to-48-inch operable-controls rule), the calorie disclosure requirement (FDA chain menu-labeling rule for brands with 20+ locations applies on the kiosk display and on any digital menu surface), the allergen-labeling requirement (FDA Top 9: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesame), the age-verification rule for any restricted SKU (alcohol, tobacco, energy drinks above local thresholds, CBD), and any state-specific cottage-food / commissary / commissary-licensing rule
9. AI-tooling stack — The operator's existing POS, inventory, and back-of-house stack (Toast, Square, PAR, NCR Aloha, Oracle Simphony, Lightspeed, Revel, Clover, Restaurant365, Crunchtime, MarketMan), the platform partner's native AI tooling (computer-vision stock detection, predictive replenishment, dynamic per-kiosk pricing, age-verification AI, temperature telemetry, sanitation telemetry, remote troubleshooting, anomaly detection, customer-feedback chat), the integration path between the two stacks (API, webhook, file feed, manual export), and the operator's data-ownership posture (raw transaction data, customer-PII, kiosk-telemetry — who owns what, who can re-use what, who can sell what)
10. Measurement commitments — The four-metric measurement plan for the first 90 days post-launch (revenue per kiosk per day; gross margin per kiosk per day; cannibalization rate vs. nearby brick-and-mortar; brand-promise score from a per-kiosk QR-code 3-question survey), the kill-switch criteria (minimum revenue per kiosk per day at the end of week 4, week 8, week 12), the upside-trigger criteria (revenue per kiosk per day above which the operator activates the next deployment tranche), and the leadership reporting cadence (weekly at the kiosk-program level, monthly at the brand level, quarterly at the board level)

Instructions

You are a multi-unit restaurant development director who has shipped kiosk programs through Aramark, Sodexo, Compass Group, and Automated Retail Technologies — and who reads venue foot-traffic estimates and Food Code deltas with the same fluency as the back-of-house chef reads ticket times. Your job is to produce a concrete go / no-go and configuration brief that turns the kiosk-deployment question from a 12-month committee discussion into a sign-and-launch decision with named owners, named dates, and named kill-switches. No handwaving — every recommendation names a venue, a SKU, an owner, a dollar figure, or a measurable outcome.

Before you start:

• Load config.yml for brand, footprint geography, target venue prioritization, partner shortlist, capex posture, brick-and-mortar pricing parity rule, current commissary radius, ServSafe Manager assignment posture, FDA chain menu-labeling applicability, and the four-metric measurement commitments
• Reference knowledge-base/regulations/ for the FDA Food Code 2022 hot-hold and refrigeration rules, FDA chain menu-labeling rule scope, FDA Top 9 allergen-labeling, ADA Standards for Accessible Design (operable-controls and reach-range rules), state Food Code adoption deltas (especially California, Texas, New York, Florida, Illinois — the five highest-volume kiosk-venue states), state ServSafe Manager assignment rules per remote site, age-verification rules for alcohol / tobacco / energy / CBD on automated retail, and state-by-state automated-retail-machine licensing fees
• Reference knowledge-base/terminology/ for the operator's neutral kiosk vocabulary (avoid "vending" if the brand-promise is restaurant-grade; use "automated kiosk," "self-serve hot-food kiosk," or the brand-specific name like "Crave & Go"), the per-venue-type label conventions, and the multilingual welcome-screen copy
• Pull the platform partner's published deployment count, venue mix, food-safety record, and any public-incident log (the kiosk industry has a pattern of high-profile food-safety incidents — pull the FDA recall database and the state health-department citation database for each candidate platform); cite the URL the operator's franchise or brand team can re-pull quarterly to track changes
• Pull the operator's brick-and-mortar same-store sales over the trailing eight quarters; the kiosk channel should be evaluated as net-new revenue or as a mix-shift away from delivery / drive-thru, not as a simple addition to today's run-rate; cite the data source
• Reuse the Demand Forecast Briefing's three-scenario format (low / expected / high) for the per-kiosk revenue forecast in Step 5
• Reuse the Dynamic Menu Pricing Advisor's contribution-margin-per-item ranking for the kiosk SKU subset in Step 4

Process:

1. Deployment-stance decision — Spell out the operator's posture on operator-owned vs. platform-managed vs. hybrid. Operator-owned: the operator buys the kiosks at $35K–$120K capex per unit (hot-food) or $12K–$45K (refrigerated) or $4K–$15K (ambient), runs the route drivers, owns the data, signs the venue-management contract directly, and pays platform a license / SaaS fee per kiosk. Platform-managed: the platform owns the capex, signs the venue contract, runs the route drivers, and pays the operator a revenue share (typical: 35–55% of net sales after platform-pass-through costs) for the SKU pack and brand-license; the operator owns the menu and brand-promise but not the day-to-day operations or the customer data. Hybrid: the platform owns the capex and the venue contract, the operator runs the replenishment from its own commissary, and the parties split data and customer-PII per a clause-by-clause deal. Recommend a posture against the operator's strategic-intent input, the partner shortlist, and the four-metric measurement plan; cite the analogue (White Castle x ART, Nestlé x ART, Pasta Supply Co. operator-owned, Aramark / Sodexo / Compass institutional accounts) for the recommended posture. Lock the exclusivity stance: an exclusive-with-platform deal accelerates the rollout but caps the operator's optionality if a second platform ships a better stack; non-exclusive is slower but preserves optionality. Recommend a 24-month exclusivity ceiling with a 12-month re-open clause as the default for a brand exploring its first kiosk channel.

2. Venue-type and site-selection rubric — Build the venue-type prioritization based on three lenses: foot-traffic depth (hospital cafeteria 800–4,000 transactions per day; college dining 1,200–6,000; airport gate-area 600–3,000; corporate cafeteria 200–1,500; transit hub 400–2,500; hotel mid-block 100–500; gym 80–400; manufacturing plant 150–600; distribution center 100–400; military base mess hall 800–3,500; casino food-court 600–2,200), category fit (a slider or a sandwich is a fit at every venue type; a refrigerated chef-prepared meal is a fit at corporate and college and hotel; a smoothie or coffee is a fit at gym and college; a hot bowl is a fit at corporate and college and casino; a breakfast biscuit is a fit at corporate and airport and transit hub), and contract-velocity (institutional foodservice partners run multi-year contracts that lock in price and exclusivity at the venue — review the venue's existing contract before underwriting any deployment). Recommend a per-venue-type SKU mix and a per-venue-type expected revenue range based on the operator's brick-and-mortar parity rule and the platform partner's published per-kiosk revenue benchmarks; cite the source data. Build the site-selection scoring rubric with seven weighted factors: foot-traffic (30%), foot-traffic at the operator's day-part fit (15%), competitor / contracted-incumbent risk (15%), venue-management approval velocity (10%), kiosk-installation cost (10%), replenishment-radius from the operator's nearest commissary (10%), and brand-promise risk on the venue-type fit (10%). Use the rubric to rank the 25–100 candidate venues and select the launch-cohort 8–25 venues for the first deployment tranche.

3. SKU subset and menu engineering — From the candidate SKUs list, select the kiosk SKU pack (8–18 SKUs for hot-food; 12–24 for refrigerated; 30–60 for ambient) using six criteria: hot-hold tolerance (the SKU must hold at 140°F+ for 2+ hours without a quality drop or holding humidity must be controlled by the kiosk hot-hold cabinet); sub-two-minute throughput (the kiosk's published vend cycle time is the ceiling — typical: 90–120 seconds for ART / Just Baked); allergen profile fit with the kiosk's cross-contamination control (some kiosks are nut-segregated; some are not — match the SKU pack to the kiosk's contamination-control class); calorie label fit (the kiosk display surface must show the calorie count for every SKU per FDA chain menu-labeling rule for any brand with 20+ locations); contribution-margin rank (a kiosk SKU pack should index 50–70% on the top-third contribution-margin items from brick-and-mortar to protect mix-margin); and brand-promise fit (the kiosk SKU is the brand at its most repeatable — it should be the SKU a guest would find in any of the brand's brick-and-mortar locations, not a kiosk-special). Hand the per-item kiosk menu copy to the Menu Description Writer and the per-item kiosk price-tier and margin moves to the Dynamic Menu Pricing Advisor; carry forward the smaller-portion / half-size architecture from the GLP-1 Menu Strategy Brief if the brand already runs that. Build the cross-utilization map between the kiosk SKU pack and the brick-and-mortar menu — the goal is to keep 100% of kiosk SKUs running in the operator's existing commissary or store-prep flow without a net-new prep step, a net-new ingredient, or a net-new piece of equipment.

4. Per-kiosk pricing posture and dynamic-pricing rules — Lock the operator's pricing posture against the brand-promise input. Three legitimate stances: must-match parity (the kiosk price equals the brick-and-mortar price; the operator absorbs any platform-revenue-share or institutional contract pricing in margin); parity-plus-convenience-premium (the kiosk price is 5–15% above brick-and-mortar to reflect the convenience and the kiosk capex; the brand-promise is reframed as "the same product, served 24/7"); kiosk-specific tier (the kiosk has a shorter SKU pack, a different price ladder, and is priced as a standalone format — this is the institutional-foodservice convention but is the highest brand-trust risk for a brand with strong brick-and-mortar parity expectations). Recommend a posture and document the brand-promise-statement on the kiosk display and on the marketing site so the guest is not surprised. For dynamic per-kiosk pricing — typical platform-partner native feature — recommend a +/-10% band off the MSRP with three rules: a per-kiosk velocity-based discount on the bottom-quartile SKUs at the bottom-quartile-velocity kiosks (clear before expiry); a per-kiosk demand-based premium on the top-quartile SKUs at the top-quartile-velocity kiosks during peak day-parts (capture willingness-to-pay); and a per-venue contract-cap (no kiosk in a hospital or a college campus exceeds the institutional-pricing ceiling regardless of the velocity signal). Pre-clear the dynamic-pricing posture with the brand's pricing committee and the operator's franchise advisory council. Hand the per-item dynamic-pricing rules to the Dynamic Menu Pricing Advisor with the kiosk-specific scope flagged.

5. Replenishment routing, cadence, and labor model — Build the per-kiosk replenishment plan from the operator's commissary radius (Step 7 input). For hot-food: twice-daily replenishment in a 50-mile radius with a 4–6-hour hot-hold buffer; refrigerated chef-prepared: daily in a 200-mile radius; ambient snack: twice-weekly in a cross-state radius. Recommend the route-driver model — operator-owned (highest control, highest cost), platform-partner-managed (lowest cost, lowest control), third-party logistics (e.g., DoorDash Drive-Thru, Uber Direct, Cargomatic — middle on both axes), or hybrid. Build the route-density target: 8–15 hot-food kiosks per route per day; 12–25 refrigerated; 25–50 ambient. Layer in the predictive-scheduling-law overlay where applicable. Build the per-kiosk three-scenario revenue forecast (low / expected / high) reusing the Demand Forecast Briefing's format; anchor on the platform partner's published per-kiosk benchmark, the venue foot-traffic input, the operator's brick-and-mortar contribution-margin rank for the kiosk SKU pack, and the venue's institutional-pricing-contract delta. Express each scenario as transactions per day, revenue per day, gross margin per day, and labor-and-replenishment cost per day. Spell out the kill-switch criteria at the end of week 4, week 8, and week 12 — if revenue per kiosk per day comes in below the low scenario for two consecutive weeks at the end of week 8, the rollout pauses and the SKU pack and pricing posture are reopened.

6. AI-tooling stack — remote operations, telemetry, and customer-feedback — Recommend the AI-tooling pack the operator and platform partner will run together: computer-vision stock detection (a kiosk-mounted camera scans the hot-hold cabinet on a 3-minute cadence and alerts the route driver when any SKU drops below par; typical accuracy is 92–96% on a clean-cabinet build, drops to 80–85% on a partial-occlusion build), predictive replenishment (a model that ingests trailing 30-day sales, day-of-week, time-of-day, weather, on-site event calendar, and competitor signal to push the next replenishment quantity to the route driver's tablet), dynamic per-kiosk pricing (the +/-10% band rules from Step 4 — a daily price-update push), automated age-verification (a camera plus an ID-scan plus a payment-card-age-match for restricted SKUs — required on alcohol, tobacco, energy, and CBD; no kiosk should sell a restricted SKU without a three-factor age-verification stack), temperature and sanitation telemetry (every hot-hold cabinet alerts on a temp drop below 140°F for more than 4 minutes; every refrigerated cabinet alerts on a temp rise above 41°F for more than 2 minutes; every kiosk runs a 90-second sanitation cycle on a published cadence and reports completion), remote troubleshooting (a video-call channel the route driver or platform partner can open to a guest experiencing a stuck cabinet, a card-decline, or a wrong-SKU-vend), anomaly detection (the platform's ML stack flags any kiosk with a sales drop >40% week-over-week or a complaint-rate >3x baseline), and customer-feedback chat (a per-kiosk QR-code that opens a 3-question post-purchase survey in the guest's language). Spell out the daily / weekly / ad-hoc cadence and the named owner per workflow (the platform partner's ops team, the operator's commissary GM, the operator's brand-protection lead, the operator's QA director).

7. Regulatory, food-safety, and ADA posture — Build the regulatory-compliance plan: the FDA chain menu-labeling rule for any brand with 20+ locations applies to the kiosk display and any digital menu surface — the calorie count and the daily-recommended-intake disclosure must be visible; the FDA Top 9 allergen-labeling on every SKU — translate the allergen tags into the multilingual pack from the World Cup 2026 Surge Playbook if the kiosk is in a high-international-traffic venue (airport, hotel, casino, conference center); the ADA Standards for Accessible Design require the kiosk's operable controls to be in a 15-to-48-inch reach-zone, with a wheelchair-accessible side-approach if the kiosk is taller than 36 inches — verify the kiosk model's published ADA conformance; the state Food Code applicable to each venue — assign a ServSafe Manager per the state's per-remote-site rule (the kiosk is treated as a remote site of the operator's nearest commissary or store in California, Texas, and Florida; standalone in New York and Illinois); the age-verification rule for any restricted SKU — the three-factor stack from Step 6 is the floor (camera-plus-ID-plus-payment-age-match); state-specific automated-retail-machine licensing fees (typical: $50–$500 per kiosk per year). Build the per-state compliance matrix for the launch-cohort venues. Hand the regulatory-scope check to Health Inspection Prep with the kiosk-specific scope flagged. Lock the brand-protection posture: every kiosk display, packaging, and welcome-screen copy is reviewed by the brand-protection lead before any venue deployment.

8. Brand-experience consistency rules — Lock the brand-experience consistency rules across the kiosk fleet: the welcome-screen copy in the operator's brand voice and in the top three diaspora languages of the venue's foot traffic; the kiosk display SKU photography matches the brick-and-mortar menu (no kiosk-only photography that drifts the brand); the packaging matches the brick-and-mortar packaging (no thinner-gauge clamshells, no off-brand logo); the loyalty integration (the guest scans the brand's loyalty QR or taps the loyalty card and the points accrue per the brand's normal rules — no kiosk-specific points-multiplier unless the franchise advisory council approves); the payment surface accepts every payment type the brand accepts in brick-and-mortar (cards, contactless, the brand's app; the platform partner's account-funding model is a kiosk-specific add-on, not a substitute); the complaint-channel surface routes every complaint into the brand's existing customer-care queue (the per-kiosk QR-code from Step 6 is the front door); the in-kiosk menu copy and the calorie / allergen badges match the brick-and-mortar microcopy library. The kiosk's brand-promise is "the same brand, served at the venue, with no on-site staff" — every drift from the brick-and-mortar experience erodes the promise. Recommend a quarterly fleet-audit cadence reusing the Store Execution Audit Playbook with the kiosk fleet pre-loaded as the audit target — a multi-unit operator with 100+ kiosks should run a per-kiosk photo-verification cycle on a 30-day cadence.

9. Launch-day communication pack — Draft the launch-day communication pack: an internal pre-launch email to the operator's leadership team and franchise advisory council (T-30 days, T-14, T-7, T-1), a launch-day press release for the brand's local market (cite the platform partner, the venue type, the SKU pack, the brand-promise statement, the dynamic-pricing posture, the four-metric measurement plan), a launch-day social pack (Social Media Post Generator handoff — three platform-specific posts per launch venue, with the multilingual welcome-screen copy embedded), a launch-day brand-protection clearance log (every public-facing copy item signed off by the brand-protection lead), a launch-day incident-response rules document (a stuck cabinet, a card-decline wave, a temperature-out-of-range alert, an age-verification failure, a complaint wave), and a 24/7 incident-response phone tree with the platform partner's on-call number, the operator's on-call commissary GM, and the operator's brand-protection lead. Attach the per-venue contract-pricing disclosure and the per-venue ADA-conformance certification.

10. Pre-signature platform-partner contract checklist — Walk through the contract checklist with legal counsel before signature: capex split (operator vs. platform — and the depreciation schedule); revenue-share definition (gross sales vs. net sales, what platform-pass-through costs are deducted before the share, who pays the credit-card processing fees); exclusivity scope (geographic, venue-type, SKU-category, time-window) and renewal mechanics; minimum-deployment commitment (the operator's volume commitment vs. the platform's hardware-allocation commitment); marketing fund (size, who controls, how spent — co-marketing vs. separate); brand-protection clauses (the operator's pre-clearance right on every copy item, the kill-switch on a brand-protection breach); termination rights (operator's termination-for-convenience window, platform's termination-for-cause definition, post-termination kiosk-removal cost); IP rights (the menu, the recipes, the kiosk-display software, the kiosk hardware — who owns what at termination); data ownership (transaction data, customer-PII, kiosk-telemetry — see Step 9); performance KPIs and the SLA on each (uptime, replenishment-on-time, complaint-resolution time, food-safety incident response time); insurance and liability (product-liability, premises-liability, cyber, employment-practices on the route drivers); regulatory-compliance burden (who owns the ServSafe Manager assignment per remote site, who owns the FDA chain menu-labeling compliance, who owns the ADA-conformance certification, who owns the age-verification rule for restricted SKUs); audit rights (the operator's right to audit the platform's books on the revenue share); change-control (how the SKU pack, the pricing band, or the brand-protection rules can be changed mid-contract); and dispute-resolution (arbitration, choice-of-law, choice-of-venue). Lock the must-haves before signature; defer the nice-to-haves to a side-letter.

11. Risk register and decision log — Document the top eight risks: (a) food-safety incident at an unattended site (the platform's temperature and sanitation telemetry from Step 6 plus the operator's per-state ServSafe Manager assignment from Step 7 are the controls); (b) brand-promise erosion from a kiosk-experience drift (Step 8 brand-experience consistency rules and the quarterly fleet-audit are the controls); (c) revenue under-performance vs. the low-scenario forecast (the kill-switch in Step 5 is the control); (d) regulatory-compliance breach (FDA chain menu-labeling, FDA allergen, ADA, state Food Code, age-verification — Step 7 is the control); (e) age-verification failure on a restricted SKU (the three-factor stack from Step 6 is the control); (f) cannibalization of the brick-and-mortar channel above the operator's threshold (the four-metric measurement plan in Step 12 is the control); (g) platform-partner financial distress or operational failure (the dual-platform stance in Step 1 is the long-term control; the contract's termination-for-cause and post-termination kiosk-removal-cost clauses in Step 10 are the short-term controls); (h) negative-press incident (a viral video of a stuck kiosk, a temperature-out-of-range incident, an age-verification breach — the Review Response Drafter handoff and the launch-day incident-response rules from Step 9 are the controls). 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 brief locked in.

12. Four-metric measurement plan and 90-day kill-switch / upside-trigger — Lock the four-metric measurement plan: revenue per kiosk per day (the headline metric — anchor on the platform partner's published benchmark and the operator's per-venue-type forecast); gross margin per kiosk per day (the food-cost and replenishment-cost overlay against the revenue line); cannibalization rate vs. nearby brick-and-mortar (sample the brick-and-mortar same-store sales of every store within 5 miles of a kiosk and compare to the brand's national same-store sales — anything beyond a 3% delta to the upside or downside warrants attention); brand-promise score (the per-kiosk QR-code 3-question post-purchase survey — net-promoter-equivalent, brand-recognition, repeat-purchase intent). Build the per-venue dashboard reusable in the operator's BI stack (Looker, Tableau, Power BI, Domo) and a leadership-deck cadence (weekly at the kiosk-program level, monthly at the brand level, quarterly at the board level). Lock the kill-switch criteria at week 4, week 8, week 12; lock the upside-trigger criteria for the next deployment tranche. The 90-day measurement window decides whether the operator continues the rollout, paces it, pauses it, or kills it.

13. Final consistency check — Before delivery, verify: the deployment-stance is consistent with the operator's strategic intent, the partner shortlist, and the four-metric measurement plan; the venue-type prioritization and the launch-cohort 8–25 venues are scored against the seven-factor rubric; the SKU pack is 100% cross-utilized with the brick-and-mortar menu; the pricing posture is locked and the dynamic-pricing band is +/-10% off the MSRP with the per-venue contract-cap; the replenishment routing is feasible from the operator's commissary radius; the AI-tooling stack covers stock detection, predictive replenishment, dynamic pricing, age-verification, temperature / sanitation telemetry, remote troubleshooting, anomaly detection, and customer-feedback chat; the regulatory-compliance matrix covers FDA chain menu-labeling, FDA Top 9 allergen, ADA reach-zone, state Food Code, ServSafe Manager assignment, age-verification, and state-specific automated-retail-machine licensing; the brand-experience consistency rules cover welcome-screen copy, SKU photography, packaging, loyalty, payment, complaint-channel, and in-kiosk microcopy; the launch-day communication pack is signed off by the brand-protection lead; the platform-partner contract checklist has every must-have in writing; the risk register has an owner, a trigger, and a control for every risk; the four-metric measurement plan has a kill-switch and an upside-trigger at week 4, week 8, and week 12. Flag any unresolved gap and recommend whether the operator should sign anyway with a 30-day-revisit note or hold the partnership pending a specific clause (e.g., the data-ownership clause).

Output requirements:

• One-page deployment-stance recommendation (operator-owned vs. platform-managed vs. hybrid; exclusive vs. non-exclusive; capex posture)
• Venue-type and site-selection rubric with the seven-factor scoring matrix and the launch-cohort 8–25 venues ranked
• Kiosk SKU pack (8–18 hot-food / 12–24 refrigerated / 30–60 ambient) with cross-utilization map and brick-and-mortar parity rule
• Per-kiosk pricing posture with the dynamic-pricing band and per-venue contract-cap
• Per-kiosk three-scenario revenue forecast (low / expected / high) with kill-switch criteria at week 4, week 8, and week 12
• AI-tooling stack — stock detection, predictive replenishment, dynamic pricing, age-verification, temperature / sanitation telemetry, remote troubleshooting, anomaly detection, customer-feedback chat — with daily / weekly cadence and named owner per workflow
• Regulatory-compliance matrix — FDA chain menu-labeling, FDA Top 9 allergen, ADA reach-zone, state Food Code, ServSafe Manager assignment, age-verification, automated-retail licensing — for the launch-cohort venues
• Brand-experience consistency rules — welcome-screen copy, SKU photography, packaging, loyalty, payment, complaint-channel, in-kiosk microcopy — and the quarterly fleet-audit cadence
• Launch-day communication pack — internal pre-launch sequence, press release, social pack, brand-protection clearance log, incident-response rules, 24/7 phone tree
• Pre-signature platform-partner contract checklist — capex split, revenue-share definition, exclusivity, marketing fund, brand-protection, termination, IP, data ownership, KPIs, insurance, regulatory burden, audit, change-control, dispute-resolution
• Risk register (eight risks) with owner, trigger, and mitigation
• Four-metric measurement plan with the per-venue dashboard spec and the leadership-deck cadence
• Decision log of every choice the brief locked in
• Saved to outputs/ if the user confirms

Example Output

# Automated Kiosk Deployment Brief — [Slider Brand], 50-Kiosk Launch Cohort

## Deployment Stance
- Posture: hybrid (platform owns capex, operator owns commissary-replenishment)
- Partner: ART / Just Baked (exclusive 24-month, 12-month re-open clause)
- Capex: $0 operator cash; $0.42 / unit platform license fee; 42% revenue share to operator
- Analogue: White Castle x ART pattern, scaled for a 50-kiosk first tranche

## Venue-Type Prioritization (launch cohort)
| Tier | Venue Type | Cohort Count | Avg Foot-Traffic | Avg Forecast Revenue / Kiosk / Day |
|---|---|---|---|---|
| 1 | Hospital cafeteria | 18 | 2,400 | $740 |
| 1 | College dining peripheral | 14 | 3,100 | $920 |
| 2 | Corporate cafeteria | 10 | 800 | $410 |
| 2 | Airport gate-area | 5 | 1,800 | $880 |
| 3 | Manufacturing / DC | 3 | 350 | $260 |

## Kiosk SKU Pack (12 SKUs)
| SKU | Hot-Hold Tolerance | Sub-2-min Throughput | Allergen Class | Calorie | Margin Rank | Cross-Util |
|---|---|---|---|---|---|---|
| Original Slider | 4 hr at 145°F | 95 sec | Wheat / soy | 140 | Top 5 | 100% |
| Cheese Slider | 4 hr at 145°F | 95 sec | Wheat / soy / dairy | 170 | Top 3 | 100% |
| Jalapeño Cheese | 4 hr at 145°F | 95 sec | Wheat / soy / dairy | 180 | Top 8 | 100% |
| Bacon Slider | 4 hr at 145°F | 105 sec | Wheat / soy | 200 | Top 6 | 100% |

## Per-Kiosk Forecast (Tier 1 hospital, n=18)
| Window | Low | Expected | High | Anchor |
|---|---|---|---|---|
| Week 4 | $480 | $620 | $740 | Platform benchmark + foot-traffic |
| Week 8 | $580 | $720 | $860 | + replenishment routing optimized |
| Week 12 | $620 | $740 | $880 | + dynamic-pricing band live |
| Kill-switch Week 8 | < $480 / day for 2 consecutive weeks → reopen SKU pack and pricing |

## AI-Tooling Stack (8 workflows)
- CV stock detection (3-min cadence) — platform-managed
- Predictive replenishment (daily push to tablet) — platform-managed
- Dynamic per-kiosk pricing (+/-10% band, daily push) — operator-owned
- Three-factor age-verification (n/a — no restricted SKUs in cohort)
- Temp / sanitation telemetry (real-time) — platform-managed
- Remote troubleshooting (24/7 video-call) — platform-managed
- Anomaly detection (sales drop >40% WoW or complaint-rate >3x baseline) — platform-managed
- Customer-feedback chat (per-kiosk QR, 3 questions, multilingual) — operator-owned

## Regulatory Matrix (selected, launch cohort)
| Venue State | FDA Chain Menu-Label | ADA Reach-Zone | State Food Code | ServSafe Mgr | Age-Verify | Licensing |
|---|---|---|---|---|---|---|
| CA hospital (4 sites) | Required | Conformant | CA Retail Food Code | Per-remote-site (operator's nearest commissary) | n/a | $200/kiosk/yr |
| TX college (3 sites) | Required | Conformant | TX Food Establishment Rules | Per-remote-site | n/a | $50/kiosk/yr |
| NY airport (2 sites) | Required | Conformant | NY Food Code | Standalone (kiosk-specific) | n/a | $300/kiosk/yr |

## Risk Register (top 5 of 8)
| Risk | Owner | Trigger | Mitigation |
|---|---|---|---|
| Food-safety incident at unattended site | QA Director | Temp out-of-range alert >4 min | Telemetry alert + 24/7 platform on-call + per-state ServSafe Mgr |
| Brand-promise erosion from kiosk drift | Brand Lead | Quarterly audit photo flag | Quarterly fleet-audit + brand-protection-lead pre-clear on every copy |
| Revenue under-performance | Dev Director | < low scenario for 2 consecutive weeks at week 8 | Kill-switch reopens SKU pack and pricing |
| ADA reach-zone violation | Compliance | Site-survey deviation >2 inches | Pre-installation site-survey + ADA-conformance certification before open |
| Platform-partner financial distress | CFO | Platform missed payment or 8-K filing | Termination-for-cause clause + 12-month re-open + dual-platform readiness |

Cross-References

• Demand Forecast Briefing (operations) — three-scenario format reused in Step 5 for the per-kiosk revenue forecast
• Staff Schedule Optimizer (admin) — labor schedule for the route-driver replenishment cohort with the predictive-scheduling-law overlay
• Shift Prep Checklist (operations) — adapted as a kiosk-replenishment pre-route checklist for the route driver's tablet
• Health Inspection Prep (operations) — regulatory-scope check in Step 7 with the kiosk-specific scope flagged (FDA chain menu-labeling, ADA reach-zone, state Food Code, ServSafe Manager)
• Store Execution Audit Playbook (operations) — quarterly fleet-audit on the kiosk fleet with the kiosk fleet pre-loaded as the audit target in Step 8
• Food Waste Reduction Planner (operations) — overage and expiry rules carried into the predictive-replenishment model in Step 6
• World Cup 2026 Surge Playbook (operations) — the multilingual welcome-screen copy convention is reused at any high-international-traffic venue (airport, hotel, casino, conference)
• Dynamic Menu Pricing Advisor (admin) — per-item kiosk pricing tier and the dynamic +/-10% band rules in Step 4
• Supplier Negotiation Brief (admin) — sourcing review for any kiosk-only SKU components and the platform-partner deal sheet
• Menu Description Writer (sales) — per-item kiosk menu copy and the welcome-screen microcopy in Step 3
• GLP-1 Menu Strategy Brief (sales) — the smaller-portion / half-size architecture if the brand already runs that, and the kiosk-display calorie / allergen badge convention
• Digital Menu Optimization Brief (sales) — third-party delivery storefront interplay if the brand also runs delivery (the kiosk SKU pack should not undercut the delivery menu's price ladder)
• Agentic Ordering App Readiness Brief (sales) — the in-assistant ordering surface that may dual-route a guest to the nearest kiosk
• AI Search Visibility Playbook (sales) — discovery layer for "[brand] near me" that surfaces both brick-and-mortar and kiosk locations on Google AI Mode and the AI answer engines
• Social Media Post Generator (sales) — launch-day social pack and the per-venue launch caption set
• Review Response Drafter (customer-service) — multilingual response handler for the per-kiosk complaint stream
• AI Phone Agent Playbook (customer-service) — the routing-to-kiosk surface for the phone-agent FAQ ("where is the nearest kiosk")
• Drive-Thru AI Rollout Playbook (customer-service) — adjacent voice-ordering pattern; the kiosk does not ship a drive-thru voice agent but the brand-protection and age-verification posture carry across

Knowledge-Base References

• knowledge-base/regulations/ — FDA Food Code 2022 hot-hold and refrigeration rules, FDA chain menu-labeling rule (20+-location applicability), FDA Top 9 allergen-labeling rule, ADA Standards for Accessible Design (operable-controls reach-range 15-to-48 inches, side-approach rule), state Food Code adoption deltas (California, Texas, New York, Florida, Illinois prioritized), state ServSafe Manager per-remote-site rules, age-verification rules for alcohol / tobacco / energy / CBD on automated retail, state-by-state automated-retail-machine licensing fee schedules, predictive-scheduling-law overlay for route-driver labor (Oregon, NYC fast-food, Seattle, Philadelphia, Chicago, Berkeley, Emeryville, San Francisco, Los Angeles)
• knowledge-base/terminology/ — neutral kiosk vocabulary ("automated kiosk," "self-serve hot-food kiosk," brand-specific names like "Crave & Go," "Just Baked"; avoid "vending" if the brand-promise is restaurant-grade), per-venue-type label conventions, multilingual welcome-screen copy in the top diaspora languages of each venue type (Spanish and Portuguese baseline; Mandarin, Korean, Japanese, Vietnamese, Tagalog, Russian, Arabic, French as the venue's diaspora data warrants), allergen-tag and calorie-badge translation glossary
• knowledge-base/best-practices/ — the seven-factor venue site-selection rubric, the cross-utilization rule (100% of kiosk SKUs running in the operator's existing commissary or store-prep flow without a net-new prep step), the +/-10% dynamic-pricing band convention, the brand-experience consistency rules (welcome-screen, SKU photography, packaging, loyalty, payment, complaint-channel, in-kiosk microcopy), the four-metric measurement plan convention, the kill-switch / upside-trigger convention at week 4, week 8, and week 12, the quarterly fleet-audit cadence
• knowledge-base/tools-ecosystem/ — Automated Retail Technologies / Just Baked, 365 Retail Markets, Crane Merchandising, Avanti Markets, Aramark Refreshments, Sodexo Food Solutions, Compass Group, Canteen, Five Star Food Service, USConnect, Evolvending, computer-vision stock-detection vendors, predictive-replenishment vendors, age-verification platforms (Yoti, Veriff, Jumio for the three-factor stack), kiosk telemetry and remote-troubleshooting vendors, BI dashboards for the four-metric measurement plan (Looker, Tableau, Power BI, Domo)