Quarterly Strategy & Review Playbook

A repeatable, restaurant-focused quarterly review playbook with meeting agenda, pre-read checklist, scorecard review flow, red-yellow-green trigger guidance, experiment review template, decision rules for investments and menu changes, and an action follow-up tracker.

Purpose

This playbook helps restaurant and hospitality teams run focused quarterly strategy reviews that turn financials, operations data, experiments, and guest feedback into clear decisions, prioritized experiments, and owned follow-ups.

Outcomes

  • Agree on the financial and operational story for the quarter.
  • Decide which experiments to continue, stop, or scale.
  • Authorize or defer investments and menu changes using consistent rules.
  • Create a short, prioritized action list with owners, deadlines, and verification steps.

Before the meeting (Pre-read)

Distribute a concise pre-read at least 48 hours before the meeting. The goal is to let meeting time be decision-focused rather than data-reading.

  • One-page scorecard (last quarter vs target vs same quarter last year; trend sparklines)
  • Quarterly P&L summary and cash flow notes
  • Top 5 variances and short explanations (inventory variance, food cost, labor, waste)
  • Experiment dashboard: active experiments, owners, start/end dates, interim metrics
  • Guest feedback highlights and key reviews/complaints
  • Critical supplier or equipment issues affecting ops

Suggested Agenda (90–120 minutes)

  1. Welcome & purpose (5 min) — facilitator sets expectations and desired decisions.
  2. Quick financial pulse (10–15 min) — headline revenue, margin, cash, big swings.
  3. Scorecard variances & highlights (25–30 min) — cover the top red/yellow items and root-cause hypotheses.
  4. Deep dive(s) on up to 2 priority issues (25–30 min) — data, hypotheses, proposed actions.
  5. Experiment reviews (20 min) — evaluate active experiments against hypothesis and metrics.
  6. Decisions & prioritization (15 min) — investments, menu changes, pilots, stop/scale choices.
  7. Actions, owners, and follow-up scheduling (5–10 min) — confirm owners, due dates, verification method.

Scorecard Review Flow

Structure the scorecard by theme (Financial, Operational, Guest, Team) and use a standard R/Y/G trigger so everyone speaks the same language.

Example KPIs

  • Revenue (total and by daypart)
  • Average check and covers
  • Food cost % and food cost variance vs target
  • Labor % and labor variance vs forecast
  • Waste / spoilage (volume, cost)
  • Ticket time / throughput
  • Guest NPS or satisfaction score and recent trends
  • Inventory variance / stockouts
  • Remakes & order accuracy

Red / Yellow / Green Trigger Definitions (examples — adapt to your business)

  • Green: KPI within target range or within acceptable variance (no immediate action beyond monitoring).
  • Yellow: KPI drifting from target (example: food cost 1–2 percentage points above target, or labor variance 5–10%). Requires root-cause check and a short-term corrective plan.
  • Red: KPI materially off target (example: food cost >2 percentage points above target or >target by 5%+ of cost; revenue decline >8% vs comparable period; inventory variance >5%). Requires immediate owner assignment, deep dive, and a timebound corrective action.

Note: These thresholds are examples. Use historical data and sensitivity to set thresholds appropriate for your concept and margin structure.

Experiment Review Template (use one row per experiment)

Field Description / Example
Name Descriptive name (e.g., "Lunch Combo Price Test")
Hypothesis If we reduce price by $1 and add a side, lunch conversion will increase and AOV will increase such that margin remains neutral or better.
Primary metric(s) Conversion rate, avg check, item margin
Target / success criteria Conversion +10%, avg check +5%, margin change >= -1pp
Owner Name and role
Timeline Start and planned end date
Result Quantitative outcome (numbers) and qualitative observations
Decision Continue / Scale / Stop / Modify
Learning Clear insight to apply elsewhere

Decision Rules (examples to make choices consistent)

  • Minor operational changes (cost < $2k): GM + Ops signoff.
  • Medium investments ($2k–$25k): require regional ops + finance review; include expected payback timeframe.
  • Major investments (> $25k): require a written proposal, ROI estimate, and multi-stakeholder approval including finance and leadership.
  • Menu changes: small pricing or description updates may be local; adding/dropping items or format changes require pilot (1–2 locations) with pre-defined acceptance metrics (sales lift, margin impact, guest feedback) and at least one full week of steady-state data across the relevant daypart before scaling.
  • When evidence is mixed, prefer pilots with clear measurement windows and a stop date rather than permanent rollouts.

Follow-up Tracking Sheet (template)

Action Owner Due Date Success Measure / Verification Status
Example: Launch lunch pilot Jane, GM 2026-05-15 10% conversion lift in pilot stores over 4 weeks In progress

Facilitation Tips

  • Assign a facilitator to keep the meeting on time and a scribe to capture decisions and actions in the tracking sheet.
  • Timebox deep dives; pick the most important items to avoid unfocused debate.
  • Treat the pre-read as mandatory. If someone hasn’t read it, they should not slow the meeting — assign a short follow-up instead.
  • Start meetings with the decisions you need to make — don’t let data exploration drive the agenda.
  • End by confirming the next date for follow-up and who will bring status updates.

How to Adapt

Make threshold numbers and KPIs specific to your concept (fast casual vs fine dining have different margins and acceptable variances). Keep the playbook modular: if you need a shorter operational quarter review (30–45 min), focus the agenda on only the top 3 KPIs and experiments.

Next Steps & Implementation Suggestions

  • Convert the scorecard and experiment templates into interactive forms so owners can submit status updates between reviews.
  • Automate the scorecard where possible by connecting POS, inventory, and labor systems to a dashboard so the pre-read numbers are updated automatically.
  • Maintain a running library of experiment learnings to reduce repeated failures and spread wins across locations.

Use this playbook as a living document: iterate thresholds, templates, and agenda items as you learn what helps your team make better quarterly decisions.


Discussion

Comments and conversation will live here.