3.2 percentage points of labor cost difference. Between the best and the worst location in a network of 6 — with an identical concept, similar location sizes and comparable sales.
What explains the gap? Almost entirely the scheduling.
The best location plans on the basis of sales forecasts and historical peaks. The worst plans on gut feeling. The result: with monthly sales of €80,000, a 3.2-point labor cost gap means around €2,560 less margin per month — or €30,720 a year. Comparisons like this require a consistently calculated percentage; the calculation and comparison rules are in comparing labor cost across locations.
Contents
- Why Excel rotas burn money
- What smart scheduling software does (and doesn't do)
- Forecast integration: the decisive difference
- 3 worked examples: what optimisation delivers
- Intraday flexibility: when the plan changes
- What Kiosa offers
- FAQ
- Your next step
Why Excel rotas burn money
Excel isn't a bad tool. It's the wrong tool for dynamic staff planning.
An Excel rota has three structural weaknesses:
First: it's based on memory, not data. The scheduler writes next week's rota based on what they know about past weeks. If last Tuesday was busy, more people go on next Tuesday. Whether next Tuesday is a school holiday, a local event affects the area or a competitor on the street has closed — that information only goes in if the scheduler actively adds it.
Second: it doesn't link planning to results. After a week, the scheduler rarely knows whether the rota was right. Was Tuesday overstaffed? Were two people missing on Wednesday evening? That feedback loop is missing, because POS sales and the rota live in different systems.
Third: it doesn't scale. One location with six employees is still manageable. Three locations with eight employees each — plus availability, holiday periods, pay rules and working-time regulations — exceed the capacity of any manual system.
Whether software improves your labor cost percentage depends on data quality, forecasting, planning rules and how it's actually implemented in the business. So don't compare against an unsourced industry figure; document your own plan-vs-actual effort and percentage over several comparable periods before you start.
What smart scheduling software does (and doesn't do)
Scheduling software doesn't solve every staff planning problem. It isn't a magic wand.
What it does: it automates rule-based planning. Availability, skill requirements, minimum breaks, maximum weekly hours — all of this can be stored as rules. The result is a rota with no compliance errors that makes the best use of available staff.
What it doesn't do: it doesn't know whether more or fewer guests will come next Thursday than this week. For that it needs external data — namely, sales forecasts.
That is exactly where a simple scheduling app and a data-driven system differ. The simple app plans correctly and efficiently against availability. The data-driven system plans against expected sales — and adjusts staffing daily to the current demand forecast.
That sounds technical. It is. But the result is easy to measure: locations that plan against a forecast have a lower labor cost percentage than locations that plan against experience-based rules of thumb.
Forecast integration: the decisive difference
A forecast is a sales prediction for a future day or shift — calculated from historical patterns, weather data, public holidays, local events and incoming bookings.
The quality of the forecast determines the quality of staff planning.
A good forecasting system distinguishes between:
- Regular weekdays: Wednesday is structurally different from Friday. A Wednesday lunch in a city-centre restaurant follows different patterns from a Wednesday evening at a leisure location.
- Seasonality: summer vs. winter, school holidays vs. term time, Christmas trade vs. the January dip.
- External factors: weather (measurable, predictable), local events (researchable), public holidays (known).
- Trend adjustment: has a location been on an upward trend for four weeks? The forecast has to include that, not just last year's average.
If the forecast says next Tuesday will bring 18% less revenue than last Tuesday, it follows that fewer staff are needed. In concrete terms: with expected sales of €3,800 instead of €4,600, the optimal number of labor hours drops by 8–10 hours — a saving of €120–150 on a single day.
Projected over 52 weeks for a business open six days a week, this precise adjustment can potentially mean €37,000–46,000 less labor cost per year — without employing a single person fewer. Purely through more precise planning.
3 worked examples: what optimisation delivers
Example 1: single location, €80,000 monthly sales
Current: labor cost 31.5% → labor cost €25,200/month After optimisation: labor cost 28.8% → labor cost €23,040/month Saving: €2,160/month = €25,920/year
That's an improvement of 2.7 percentage points — a realistic value for moving from purely gut-based to data-supported planning.
Example 2: 3 locations, €240,000 monthly sales
Current: labor cost 30.8% across all locations → €73,920/month After optimisation (data-driven): labor cost 28.2% → €67,680/month Saving: €6,240/month = €74,880/year
A second effect comes in here: location comparison shows which location plans above and which below average. The underperformer is brought up to the best-practice level.
Example 3: 6 locations, €480,000 monthly sales
Starting point: 3.2 percentage points difference between the best and worst location (as described above) If all locations reach the labor cost percentage of the best location: additional margin of €15,360/month = €184,320/year
It isn't realistic for every location to reach the best one straight away. What is realistic is closing 50–60% of the gap over 12 months. That still adds up to €90,000–110,000 of additional annual margin — from staff planning alone.
Intraday flexibility: when the plan changes
Even the best plan becomes obsolete when reality changes. An unexpected rainy day. A group of 20 walking in without a reservation. An evening that suddenly picks up after a slow start.
Intraday adjustment — changing the plan during the running day — is the safety net.
Good scheduling software does this: it compares actual sales with the forecast every hour and flags when the deviation crosses a threshold. If lunch is 25% below plan, the early shift could finish sooner. If the evening is 20% above plan, someone should be called in.
A person still makes these decisions. But they make them based on current numbers — not on a plan drawn up the Tuesday before.
The concrete requirement: the POS has to deliver real-time data, and the scheduling system has to analyse it. Both are technically solvable. But it takes integration between the two systems — and that's missing in most businesses.
What Kiosa offers
Kiosa covers both sides, and you decide how much of it you use. One View provides the data basis for better scheduling. The Scheduling module (+€99 per location per month) creates a draft rota from the sales forecast, checks rest periods, maximum hours and contracts, and collects availability via the app. If you want to keep your scheduling tool, you stay with it and use One View as the data basis.
What One View delivers for planning:
- A daily forecast per location, based on historical patterns, weather data and public holidays
- Current labor cost percentage compared with the target corridor and the location average
- Early warning when a location is consistently above its labor cost target
- A weekly review: was the plan right? Where was there too much, where too little staff?
The result: the scheduler — whether at head office or the location manager on site — no longer plans from experience but from data.
Two approaches make sense: you keep planning in your tool for availability, rules and communication and use Kiosa for the steering data (forecast, labor cost percentage, early warning). Or you plan in the scheduling module and have plan, actual hours and sales in one system.
The effect is measurable in principle, but not guaranteed within a fixed timeframe. Before you start, define the KPI, comparison period and cost boundaries, and check the trend over several comparable planning cycles.
From analysis to action
What this is about: a commercial comparison and requirements checklist for scheduling software.
Put it into practice: Kiosa Scheduling: features and pricing
More on Labor costs and scheduling
- Restaurant Labor Cost Percentage: How to Calculate and Benchmark It
- Restaurant Employee Scheduling App: Fewer Calls, More Shifts Filled
FAQ
Do I need to switch my scheduling software? No. Kiosa reads the hours from your existing system and supplies forecast and analysis data; scheduling can stay in the tool you're used to. Alternatively, you plan in the scheduling module.
Which scheduling tools are compatible with Kiosa? Directly connected are gastromatic, e2n and ordio. For any other system, we'll clarify in the demo call whether and how it works.
How accurate are the forecasts? The sales forecast is precise enough to base staffing decisions on.
What is the first step? Setting up the connection between your POS and Kiosa. After that, Kiosa automatically starts building the data basis for forecasts.
Does this make sense for seasonal businesses too? For seasonal businesses, forecast accuracy is especially valuable. A system that knows seasonal patterns from past years plans the start and end of the season more precisely — exactly the weeks when over- or understaffing is most expensive.
What about part-time staff and irregular availability? Kiosa analyses hours on a daily and weekly basis — regardless of employees' contract type. The distinction between full-time, part-time and casual staff lives in the scheduling tool, not in Kiosa.
Typical scheduling mistakes and how to avoid them
Beyond the structural "Excel vs. software" problem, there are operational planning mistakes that regularly cost many businesses money.
Mistake 1: underestimating shift overhead. Every shift has set-up and close-down time. If you schedule an 8-hour shift, you effectively get 7 hours of productive time. If you don't account for that, you systematically understaff and fall back on expensive last-minute hours during service.
Mistake 2: treating all weekdays the same. Tuesday isn't Saturday. Not just in sales — in staffing structure too. A business that puts the same team on Tuesday as on Saturday pays too much for labor on five days out of seven.
Mistake 3: not planning for holidays and sickness. According to an analysis by the research institute of the German health insurer AOK (WIdO), the sick leave rate in the German hotel sector was 5.2% in 2025. Source: hotelier.de, citing WIdO/AOK, accessed 2 November 2026. A good rota builds this absence rate into its staffing reserve — instead of treating every sick day as an unplanned emergency.
Mistake 4: no learning cycle. Rota made, week over, new rota made. The step "was the plan right?" is completely missing in many businesses. Yet analysing plan deviations would be the easiest route to steady improvement. Which shifts were regularly overstaffed? Which were never enough? That knowledge improves every following rota.
Your next step
The simplest check: look at your labor cost percentage over the last three months. Is it above last year's value? Or does it swing a lot from week to week — which points to irregular planning?
If both apply — and in many businesses they do — the optimisation potential is right in front of you.
Book a 30-minute call. Together, we'll work out what data-driven scheduling would deliver in your specific business — with your own numbers.