Multi-Location Benchmark & Exceptions Dashboard

Purpose

This dashboard helps operators and leaders quickly spot locations that are underperforming or changing unexpectedly, understand the likely causes, and launch focused deep-dive actions. It is designed to be copied and tailored per enterprise standards so each group can own its benchmarks and follow-up workflows.

Primary Widgets (preserved and expanded)

• Sales per seat — total sales / number of seats. Useful for comparing capacity utilization across different-size sites. Visual: normalized bar chart or scatter by seat count.
• Covers — number of guests served. Visual: time-series sparkline and week-over-week % change.
• Check average — sales / covers. Visual: histogram and trend.
• Labor % — labor cost / sales. Visual: control chart with target band and alarm when outside thresholds.
• Food cost % — food cost / sales. Visual: stacked bar by major category (protein, produce, disposables) plus trend.
• Variance to plan — (actual − plan) / plan. Visual: table and heatmap showing % variance and magnitude.
• Exceptions list (outlier locations) — prioritized list of locations that exceed exception rules. Visual: sortable table with severity score and quick-actions column.
• Drill-ins — one-click links from a flagged location to focused reports: Shrink (waste & inventory variance), Staffing (schedule vs demand, overtime, productivity), Promotions (menu mix, uplift vs forecast).

KPI Definitions & Formulas

• Sales per seat = Total Sales (period) ÷ Number of seats (fixed count)
• Covers = Count of distinct guest covers (or transactions, depending on POS setup)
• Check average = Total Sales ÷ Covers
• Labor % = Total Labor Cost ÷ Total Sales
• Food Cost % = Cost of Goods Sold (food) ÷ Total Sales
• Variance to plan = (Actual − Plan) ÷ Plan

Exception Rules (examples you can copy and tailor)

Each exception should include both magnitude and trend so you focus on meaningful outliers.

• Absolute threshold: Flag if Food Cost % > Target + 3 percentage points.
• Relative threshold: Flag if Sales per seat is < 85% of peer-median for same format (daypart-adjusted).
• Statistical outlier: Flag if metric’s z-score > 2 over the rolling 8-week window.
• Adverse trend: Flag if metric moves negatively by > 5% week-over-week for 2 consecutive weeks.

Priority Scoring

Assign a simple priority score to rank exceptions so teams know where to act first. Example components:

• Severity (magnitude of deviation, normalized)
• Dollar impact (estimated weekly loss)
• Trend (worsening vs improving)
• Recurrence (how often this site has been flagged in past 12 weeks)

Combine into a weighted score to sort the exceptions list.

Suggested Visualizations & Controls

• Map or heatmap of locations color-coded by priority score.
• Table of locations with sparklines for each KPI, sortable by deviation and priority score.
• Time-series panel with overlayed target band and peer-median.
• Peer comparison scatter (e.g., food cost % vs check avg) to reveal different operating profiles.
• Filters: date range, daypart, weekday vs weekend, location type, region, trade area, and seat count buckets.

Drill-In Reports (templates)

Each flagged location should link to one or more of these pre-built deep-dive views:

• Shrink & Inventory — inventory variance by category, waste logs, receiving exceptions, supplier issues, last-cost movements.
• Staffing & Productivity — schedule vs actual hours, covers per labor-hour, overtime, top shift-level variances, manager note history.
• Promotions & Mix — menu mix change during promotion windows, uplift vs expected, discount impact on food cost %.
• Guest & Operations — ticket times, remakes, guest complaints, inspection notes, and staff training gaps.

Data Sources & Update Cadence

• POS (sales, covers, check data) — update daily (near-real-time if possible).
• Inventory & Receiving — daily or weekly depending on cycle count frequency.
• Labor & Payroll — daily to capture schedule changes; payroll detail weekly.
• Purchasing & Supplier costs — update when invoice/price changes occur (weekly recommended).

Operational Workflow & Governance

• Daily: regional managers review top 5 flagged locations from the exceptions list; quick owner assignment and short note (why flagged).
• Weekly: owners of flagged locations open a deep-dive report, record findings and an action plan (owners, due dates, expected impact).
• Escalation: if the same location is flagged 3 weeks in a row, escalate to operations head with recommended intervention (audit, mystery visit, supplier check).

Recommended Actions From Common Flags

• High food cost % with flat sales: run portion-size and recipe compliance audit; check latest invoice pricing.
• Low covers but high check avg: test targeted promotions to increase covers without harming check average.
• High labor % with falling sales: adjust schedules to match demand, upskill staff to improve throughput.
• Repeated variance to plan: verify plan assumptions (forecast accuracy) and review recent marketing/operational changes.

Notes on Tailoring & Reuse

This dashboard is intended to be copied into an enterprise domain and configured with local benchmarks, peer groups, and business rules. Keep the core exception logic but allow each region or format to tune thresholds and peer definitions.

Sample KPI Thresholds (starter defaults — adapt to your business)

• Food cost %: target ±2% band; flag > target + 3pp
• Labor %: target ±3pp; flag > target + 4pp or overtime > 8%
• Sales per seat: flag < 85% of peer-median
• Variance to plan: flag negative variance > 7%

What Success Looks Like

Teams use the dashboard daily to reduce time-to-awareness, close action loops faster, and reduce the recurrence of avoidable problems. Over time, it should reduce the number of repeated flags at the same sites and shorten mean-time-to-resolution for high-impact issues.