A restaurant sales forecast template helps an outlet manager plan expected guests (covers), average spend, kitchen production and appropriate staffing for the next service or week. A useful forecast separates customer demand from sales per guest and compares predictions with what actually happened. This original HoReCaHire restaurant sales forecasting guide provides a weekday calculation, a seven-day worksheet and a review method without inventing market-wide revenue or fixed ideal forecasting accuracy.
Restaurant sales forecasting formula
Forecast net sales = expected covers × forecast net spend per cover. For an outlet with takeaway or delivery activity, use additional separate forecasts such as expected transaction count × net value per transaction; a delivery order is not automatically a dine-in guest cover. Define and reconcile GST/taxes, refunds, discounts, charges and channel sales using consistent approved POS/finance reporting.
| Forecast input | Meaning | Good source |
|---|---|---|
| Expected dine-in covers | Projected genuine diners for one service | Verified POS history and reservations |
| Net sales per cover | Comparable sales divided by actual covers | Historical POS sales and actual cover counts |
| Event adjustment | Evidence-based change from normal demand | Confirmed booking or known closure/event |
| Channel orders | Predicted pickup or delivery transactions | Separate historical channel records |
| Period | Same date or daypart for every input | Service schedule and trading hours |
| Actual result | Verified completed transactions and covers | Closed POS report after service |
A repeatable seven-step forecasting SOP
- 1. Pull actual history: export recent comparable sales and covers by weekday and meal period.
- 2. Mark exceptions: identify unusual holidays, private functions, weather disruptions and closures.
- 3. Build cover baseline: average comparable days, excluding only justified exceptional observations.
- 4. Check spend per cover: use the correct net sales/cover denominator and account for actual menu changes.
- 5. Adjust for known demand: record reservations, large groups, nearby events and credible weather impacts explicitly.
- 6. Sense-check capacity: confirm physically safe usable seats, realistic service throughput and staff availability.
- 7. Compare forecast with actual: measure error, note causes, revise future assumptions.
Current operator guidance from the Restaurant Association and Toast’s POS reporting guide supports tracking covers, check values and sales by comparable service periods. No one historical average forecasts every holiday or private banquet correctly; quality improves when teams document the reasons forecasts missed.
Worked forecast: four comparable Fridays
A fictional restaurant recorded 80, 92, 88 and 100 covers on four recent ordinary Friday dinners. Average covers = (80 + 92 + 88 + 100) ÷ 4 = 90. With a comparable net spend of ₹750 per cover, baseline sales = 90 × ₹750 = ₹67,500. If a verified event is expected to add 10 genuinely additional covers, updated sales forecast = 100 × ₹750 = ₹75,000, assuming the spend mix remains similar. These amounts are deliberately invented, not actual HoReCaHire or client sales.
Copy-ready restaurant seven-day sales forecast worksheet
| Day | Forecast covers | Net spend/cover | Forecast net sales |
|---|---|---|---|
| Monday | [Enter] | [Enter] | [Covers × spend] |
| Tuesday | [Enter] | [Enter] | [Covers × spend] |
| Wednesday | [Enter] | [Enter] | [Covers × spend] |
| Thursday | [Enter] | [Enter] | [Covers × spend] |
| Friday | [Enter] | [Enter] | [Covers × spend] |
| Saturday | [Enter] | [Enter] | [Covers × spend] |
| Sunday | [Enter] | [Enter] | [Covers × spend] |
Restaurant forecast versus actual reconciliation
| Measure | Example | Calculation |
|---|---|---|
| Forecast Friday sales | ₹75,000 | 100 covers × ₹750 |
| Actual Friday covers | 96 covers | Verified dine-in count |
| Actual comparable net sales | ₹74,880 | Actual POS data (fictional) |
| Actual spend per cover | ₹780 | ₹74,880 ÷ 96 |
| Sales variance | −₹120 | Actual − forecast |
| Cover variance | −4 covers | 96 − 100 |
| Interpretation | Fewer diners but higher spend per diner | Investigate separately |
The forecast missed covers by four but missed sales by only ₹120 because actual spend per cover was higher. A manager looking only at the nearly correct sales number would overlook the demand forecast error. Conversely, correct covers and poor sales may indicate lower spend or menu mix changes. Both drivers deserve review.
Track forecast error without forcing a target
One simple daily sales forecast error measure is (actual − forecast) ÷ forecast × 100 when forecast is nonzero. In the fictional Friday example: (₹74,880 − ₹75,000) ÷ ₹75,000 × 100 = −0.16%. This percentage only describes one day and does not validate the method for every service. Review positive and negative misses over a genuine series, and separately monitor guest safety and staffing impact.
Forecasting when you have no history
For a newly opened café, begin with approved usable seats, genuinely achievable meal periods, conservative occupancy/turn assumptions and an expected net spend based on your own proposed menu. Build low, central and high demand scenarios. This is a feasibility estimate—not a promise customers will arrive or a licence to exceed permitted capacity. Update with actual POS history as enough comparable periods accumulate.
Restaurant sales forecast and kitchen/roster briefing
| Forecast output | Who needs it | Operational use |
|---|---|---|
| Expected covers by meal period | Kitchen / pastry / F&B | Approved production and fresh ingredient orders |
| Expected party sizes and reservations | Host / Restaurant Captain | Seating and realistic guest communication |
| Expected net sales and channel mix | Restaurant Manager / finance | Comparable performance planning |
| Uncertain exceptional demand | Duty Manager / staffing owner | Fair coverage and flexible contingency |
| Forecast error and open issues | Operations leadership | Review before next weekly plan |
Common restaurant sales forecasting mistakes
- Multiplying a number of bills by spend per guest rather than average bill.
- Comparing gross POS receipts with a prior week’s net-sales figure.
- Using a private-buyout day as a regular Friday without marking the exception.
- Adding the same group reservation to both baseline covers and special-event adjustments.
- Treating a booking enquiry as a confirmed table or assured guest arrival.
- Pressuring staff to work through legal breaks to match an optimistic forecast.
- Changing recorded actuals to make the forecast look accurate.
A 15-minute weekly forecast review
- Check data sources, refunds and comparable dayparts before discussing trends.
- Compare forecast and actual covers independently of spend per cover.
- Explain large exceptions using verified weather, events, availability and guest behaviour.
- Agree one controlled adjustment to the next forecast and document its reason.
- Pass realistic demand information to the kitchen and roster owner with safety and workload context.
Related HoReCaHire restaurant resources
See Restaurant Manager duties, F&B Director KPIs, Executive Chef operations, Waiter role and chef hiring in India. Restaurants can advertise genuine vacancies.
FAQs
What is the easiest restaurant sales forecast?
Estimate expected genuine covers and multiply by comparable average net spend per cover. Maintain separate transaction forecasts for non-dine-in channels.
How often should forecasts be updated?
A weekly plan and daily updates around reservations, weather or events are useful for many operations. Frequency should match actual volatility and reliable information.
Is forecast revenue equal to profit?
No. It predicts sales; ingredient, labour, occupancy, rent and many other expenses determine profitability.
Editorial references: Toast reporting resources and the Restaurant Association guidance linked above. All sales, covers, forecasts and templates are independently invented HoReCaHire teaching examples, not verified restaurant data.
