Daily Financial Dashboard (template & setup guide)

Purpose & Who this is for

This dashboard template helps managers and owners get the right daily numbers in front of shift leaders so they can spot margin leaks and operational problems before they become losses. It's aimed at independent restaurants through multi-location groups and suits general managers, ops managers, kitchen leads, and finance partners who need a compact, actionable daily view.

Core hunger this solves

Get the right daily numbers in front of managers to catch problems early — missing or inconsistent data that hides margin leaks and delays corrective action is the primary mal-hunger this dashboard tries to eliminate.

What to include on the dashboard (layout & visualization recommendations)

• Top-line row (quick situational awareness): Today vs. target sales, covers, average check, transactions. Use single-number cards with % change compared to same day last week and plan.
• Sales by period: Bar chart split by meal period (breakfast/lunch/dinner) or POS periods; include last-period comparison line.
• Covers & throughput: Line chart of covers by hour, with overlays for ticket volume and average check.
• Labor % (by role): Stacked bar showing scheduled vs. actual labor hours/cost by role, and a small card for labor % of sales.
• Food cost signal: Trend line of COGS as % of sales (rolling 7-day) and a table of top 5 menu items by cost variance.
• Variance & exceptions: Table or flag list showing major deviations (e.g., labor% > threshold, sales < forecast by X%, high voids/refunds).
• Action items & owner: Small panel listing today’s top actions assigned to managers (e.g., reduce prep, call supplier), with owner and status.

Key KPIs (definitions & formulas)

1. Net Sales — Sales after discounts, comps, and refunds. (Use POS net-sales field where possible.)
2. Covers — Number of guests served. (POS covers or estimated from covers per check × checks.)
3. Average Check = Net Sales / Number of Checks (or Net Sales / Covers if checks unavailable).
4. Labor Cost — Actual payroll cost for the period (wages + taxes + benefits included in payroll postings for the shift).
5. Labor % = Labor Cost / Net Sales.
6. Cost of Goods Sold (COGS) — Cost of ingredients used during the period. Prefer recipe-level depletion or POS-integrated usage. If not available, use beginning inventory + purchases - ending inventory for the period.
7. Food Cost % = COGS / Net Sales.
8. Prime Cost = Labor Cost + COGS.
9. Prime % = Prime Cost / Net Sales.
10. Void / Refund Rate = (Value of Voids + Refunds) / Net Sales.

Sample spreadsheet-friendly formulas

Use these as direct formulas when prototyping in Excel/Sheets before connecting to live data:

• Average Check = IF(NumberOfChecks>0, NetSales / NumberOfChecks, 0)
• Labor % = IF(NetSales>0, LaborCost / NetSales, 0)
• Food Cost % = IF(NetSales>0, COGS / NetSales, 0)
• Prime % = IF(NetSales>0, (LaborCost + COGS) / NetSales, 0)

Data mapping notes — common POS considerations

POS vendors vary in field names and aggregation. When mapping, verify these items explicitly:

• Net vs. Gross Sales: Does the POS provide net-sales (after discounts/voids) or gross? Prefer net for KPI denominators.
• Taxes: Exclude tax from Net Sales and COGS calculations.
• Voids, Comps, Discounts: Capture counts and $ separately so you can compute Void/Refund Rate and analyze discount impact.
• Payments & Tips: Tips should not be included in Net Sales; map payment types properly.
• Covers / Guests: Some POS systems require enabling guest counting or using average covers per check assumptions.
• Menu modifiers & itemization: Make sure recipe-level items and modifiers map to the correct inventory SKU for cost calculation.

Quick vendor examples (mapping approach, not exhaustive):

• Toast: Use the ‘net_sales’ and ‘checks’ endpoint, map ‘item_sales’ to recipe SKUs, and pull labor from payroll integration or Labor exports.
• Square: Use the Transactions / Orders API, subtract discounts and refunds to compute net sales, and use Item Variation IDs to align with recipes.
• Lightspeed / Upserve / Clover: Export itemized sales and payment reports; verify how refunds vs. comps are reported and map accordingly.

Implementation checklist (step-by-step)

1. Identify the dashboard owner and daily reviewer (shift manager + ops lead).
2. Agree the KPI definitions and thresholds with finance and operations — document them in the dashboard notes.
3. List available data sources: POS, payroll, inventory system, purchasing. Confirm export formats (CSV, API) and refresh cadence.
4. Prototype in a spreadsheet using the sample formulas and one week of historical data to validate calculations.
5. Build visual mockups: prioritize single-screen visibility for a morning handoff and a compact shift summary view.
6. Set up automated data feeds where possible. If APIs unavailable, schedule reliable CSV exports or nightly uploads.
7. Define exception alerts and thresholds (e.g., labor% > target + 2pt, food cost% > target + 1.5pt, sales < forecast -10%).
8. Train managers on how to interpret signals and the immediate actions to take for the top 5 exceptions.
9. Run a 2-week pilot, capture issues, refine mappings, and then roll out to all shifts/locations.

Troubleshooting guide — common mismatch issues & fixes

• Timing differences: POS close times vs. accounting dates can shift values. Use consistent business-day boundaries and document them.
• Discounts applied to payment vs. item level: If discounts are at payment level, allocate proportionally to items or remove them from item-level cost analysis.
• Labor hour mismatches: Ensure labor feed includes all paid time (clock-ins, manager overrides, paid breaks) and matches payroll journal entries.
• Ingredient vs. recipe cost mismatches: Verify recipes map to the same SKU units used in purchasing and inventory (weight vs. volume issues are common).
• Refunds & comps tallied differently: Reconcile refunds reported in POS to accounting refund journals and adjust net-sales mapping.
• Missing covers: When covers are not tracked, infer from checks and average covers per check, but label inferred values clearly.

Manager actions & playbook (when the dashboard flags a problem)

• Labor % high: Review sales forecast; reassign non-critical tasks, reduce overtime, or re-balance roles.
• Food cost spike: Check recent deliveries, recipe changes, waste reports, and comp/void patterns for high-cost items.
• Sales below forecast: Evaluate marketing triggers, menu availability, and customer feedback; consider immediate promotions if safe.
• High void/refund rate: Review POS logs to identify staff training issues or system errors and pull camera/ticket evidence if needed.

Adoption tips

• Keep the morning view to 5–7 numbers managers can act on quickly.
• Make the first row of cards binary-friendly: green/yellow/red with clear thresholds and next-step recommended actions.
• Link each exception back to a one-line action in the dashboard (who, what, by when).
• Review the dashboard in a 10–15 minute daily huddle to build habit and accountability.

Next steps & extensibility

Once the base dashboard is stable, consider adding: location roll-ups for multi-site teams, trend forecasting (7/30/90 days), recipe-level item cost alerts, and simple predictive alerts for staffing needs using historical covers.

Appendix — quick mapping checklist for engineers / integrators

• Confirm field names for sales, discounts, taxes, refunds, payment types, itemization, tickets/checks, guest counts.
• Decide on a canonical business date and time zone for all feeds.
• Document units and currencies for purchases and inventory to avoid unit-conversion errors.
• Store raw source exports for 30–90 days to support audits and troubleshooting.