Multi-location performance dashboard template

Purpose

This template helps multi-location operators compare performance, spot outliers fast, prioritize interventions, and spread winning practices. It balances a compact executive view with clear drilldowns so managers can move from ‘which location needs help’ to ‘what to investigate and who should act.’

Core widgets (compact view)

• Sales trend (by location & channel) — rolling 28-day trend with location selector and channel filters (dine-in, takeout, delivery).
• Labor cost % — labor cost / net sales × 100 (see definition below).
• Food cost % — food cost / net sales × 100.
• Covers / cover trend — covers per day and covers per labor hour.
• Ticket time (median) — median ticket time by location and daypart (more robust than average for skewed busy-period data).
• Top 5 menu items by contribution — contribution = price – ingredient cost; show rank, mix %, and margin impact.
• Month‑to‑date variance vs target — show variance % for sales, labor %, and food % against location targets.
• Location health scorecard — combined score (see scoring model below) with R/A/G color and quick action recommendations.

KPI definitions & calculation notes

Use consistent definitions across locations so comparisons are meaningful. Examples below assume standardized chart of accounts and POS/product mapping.

• Net Sales: sales after refunds and comps; use same time boundaries (day, week, MTD).
• Labor Cost %: (wages + payroll taxes + benefits allocated to hourly labor) / Net Sales × 100. Decide whether manager labor is included consistently across sites.
• Food Cost %: (ingredient cost issued to recipes + in-kitchen waste cost) / Net Sales × 100. Use recipe-level cost mapping from POS or inventory system for best fidelity.
• Waste (cost and rate): recorded waste cost / Net Sales or waste cost per 100 covers. Encourage standardized waste logging (reason codes: overproduction, spoilage, prep error, guest plate waste, theft/loss).
• Ticket time (median): time from order placed (or ticket created) to order completed or served. Use POS timestamps for consistency and segment by daypart.
• Contribution per item: Menu price – ingredient cost. Multiply by mix% to show impact on margin.

Health scorecard: example composite

Create a single, interpretable health score so leaders can prioritize quickly. Example approach:

1. Define component metrics and targets (Sales vs target, Labor %, Food %, Waste cost per 100 covers, Ticket median, Guest complaints per 1,000 covers).
2. Normalize each metric to 0–100 (100 = meets/exceeds target, lower = worse).
3. Weight components (example: Sales 25%, Food% 20%, Labor% 20%, Waste 15%, Ticket 10%, Complaints 10%).
4. Composite = weighted sum → map to 0–100 score and show R/A/G bands (e.g., >85 green, 70–85 amber, <70 red).

Suggested R/A/G thresholds (starting point)

Customize thresholds per concept, geography, and business model. Start with these as hypotheses and refine with historical data.

• Sales vs target: Green ≥ 98% of target; Amber 90–98%; Red < 90%.
• Labor %: Target ± acceptable band (example target 28%): Green within target ±1.5 pts; Amber ±1.5–3 pts; Red >3 pts adverse.
• Food %: Similar banding depending on cuisine; use recipe costing to set realistic target.
• Waste cost per 100 covers: Green < $X; Amber $X–1.5X; Red >1.5X (define $X from historical median).
• Ticket median: Green < target minutes; Amber within +20%; Red > +20%.

Drilldown recommendations (when a location is flagged)

• Time dimension: inspect by daypart and shift to see when issues occur.
• Labor: hours by role and hour-of-day; covers per labor-hour and overtime spikes.
• Food cost: top SKUs with highest variance, spoilage events, supplier price changes, portioning variance by shift/station.
• Waste: waste reason codes and waste by recipe/component; identify recurring items or shifts.
• Service speed: ticket time distribution (median + 90th percentile) and busiest servers/stations.
• Menu mix: migration toward low-margin items or unexpected shifts in top sellers.

Data sources & join keys

Typical sources: POS (sales, tickets, items, timestamps), payroll/timeclock (hours, labor costs), inventory/recipe costing, waste logs, supplier invoices, reservation/delivery platforms, and guest feedback tools. Use location ID, date, shift/daypart, and menu item code as primary join keys.

Refresh cadence & reliability

Design combination of near-real-time POS updates for sales and ticket speed, daily feeds for payroll, and daily or weekly inventory/waste reconciliations. Clearly document data latency and confidence per widget.

Layout & UX suggestions

• Top row: location selector, health score table (sorted by score), and sparkline trends for flagged locations.
• Middle row: core KPI tiles for sales, labor %, food %, waste rate (with R/A/G color).
• Lower row: actionable lists — top issues (by impact), recommended next actions, and links to location-level deep-dive dashboards or SOP checklist.
• Include an explicit ‘Confidence’ badge (Low/Medium/High) for each KPI when source data is incomplete or estimated.

How to use it to prioritize improvement

Sort locations by health score and absolute impact (e.g., lost margin dollars). Investigate high-impact red locations first. For each site, capture one hypothesis (likely cause), one immediate corrective action, one experiment to test, and the owner and target date — then track outcome economically (e.g., margin recovery).

Implementation checklist

1. Standardize KPI definitions and mapping across systems.
2. Configure data feeds and validate 28-day backfill for baseline comparisons.
3. Set initial targets/thresholds by cohort (urban vs suburban, format type) then refine after 30–90 days.
4. Define governance: who owns scores, cadence of review (weekly ops huddle + monthly regional review), and escalation rules.
5. Train managers on reading the dashboard and executing the drilldown checklist.

Quick wins to surface from dashboard use

• Spot locations where labor scheduling doesn’t match covers (high labor %, low covers).
• Identify menu items with high mix but low contribution — target for recipe or price change.
• Find sites with high waste cost per cover and trace to specific prep/process mistakes.

Notes on spreading best practices

When a site improves a metric, capture the specific change (shift schedule tweak, recipe instruction, supplier change) in a short Learn & Share note attached to the dashboard. Use the health score change + dollar impact as a case to replicate to similar cohort sites.

Where to go next (capability ideas)

Consider making thresholds editable by region managers and storing settings (so scorecards reflect local targets), adding automated alerts for red sites, and linking to an action-tracking worksheet for follow-up. See capability notes for implementation ideas.